![]() ![]() Secure Boot suddenly stopped working for Windows 7 but not for Windows 10. I'm dual booting Windows 10 on one SSD and Windows 7 on the other SSD motherboard is the Asus Sabertooth Z170. On March 21, poster evilsofa on HardForum said: This morning on un-hibernating I got a black screen with: "The system found unauthorized changes on the firmware, operating system, or UEFI drivers." Yesterday I installed latest Windows updates, restarted, and shortly afterwards hibernated the machine. I have a PC with an Asus motherboard running Windows 7 Pro. The earliest report I can find of the freeze comes from Nick Baker, posted on March 19 on the Superuser forum: ![]() ![]() Back when it was Optional, only a few people installed it, and a small percentage of them with the right (wrong?) Asus motherboard saw their machines freeze. KB 3133977 went from Optional on March 15 to Recommended on April 12. KB 3133977, in turn, was a fix for an earlier bug in KB 2990184, which was a fix for a problem with backing up a Federal Information Processing Standard (FIPS) password to Active Directory in FIPS compliance mode. Windows 7 users with those motherboards didn't have any outward warnings of the setting - Win7 doesn't support Secure Boot - until BitLocker patch KB 3133977 appeared. Many people who own machines with Asus motherboards are wondering why Asus turned on Secure Boot in UEFI. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |