Find out what steps you can take if an incompatible driver in preventing you from turning on the Memory integrity setting in Windows Security.
Continue reading...
Continue reading...
Why do incompatible drivers prevent using Memory integrity? - Microsoft Support
- Thread starter TWF Bot
- Start date
WELCOME TO THEWINDOWSFORUM COMMUNITY!
Our community has more than 63,000 registered members, and we'd love to have you as a member. Join us and take part in our unbiased discussions among people of all different backgrounds about Windows OS, Software, Hardware and more.
- Nov 5, 2018
- 2,509
- 2,082
Just a thought. High mem has always been a favorite place to stash code for program cracks as well. Even A/V programs stay out of the memory range. Conflicts and collisions in high mem are responsible for many of the blue screens. Microsoft's first attempt was the WHQL program which the OEMs thought was great until they found out M/S was charging $49,000 USD to certify (much higher now) so many refused to submit new drivers.
This line from the article really confuses me, "Microsoft does not recommend that you delete drivers to attempt to restore this setting". I get the elimination of the blue screen thing but be aware that restoring Memory integrity is also just another way of M/S sniffing out cracks too as the have been so aggressively doing with Windows Security (aka Defender).
This line from the article really confuses me, "Microsoft does not recommend that you delete drivers to attempt to restore this setting". I get the elimination of the blue screen thing but be aware that restoring Memory integrity is also just another way of M/S sniffing out cracks too as the have been so aggressively doing with Windows Security (aka Defender).
Similar threads
- Article
