We've noticed a number of our customers contacting us over the last week reporting that their computers will no longer start and this appears to be in conjunction with a recent software update downloaded from Windows Update. Specifically, it seems to only affect computers running Windows 7 with ASUS motherboards, where the Secure Boot option is turned on. Whilst we've only had this confirmed on ASUS motherboards other manufacturers also use Secure Boot and may also have similar problems.
On turning the computer on, users are presented with a black screen with text stating
"The system found unauthorized changes on the firmware, operating system or UEFI drivers"
and a prompt to enter the BIOS. The problem is caused by the Secure Boot setting of the BIOS - this is only really intended to be used with Windows 8 or later, and it's recommended for it to be turned off for Windows 7 but will be active by default. Thankfully it's very easy to change this setting and get the computer back up and running again.
First, you need to enter the computer's BIOS. This can be done by either following the prompt when receiving this message or by tapping the delete key on the keyboard when turning the computer on. Once you're on the ASUS BIOS screen, press F7 to enter advanced mode and navigate to the 'Boot' tab.
Scroll down to near the bottom of the list and you should see the Secure Boot option. Highlight it and press enter. This will open a new screen. On this screen, select the OS Type option and press enter, which will pop up a small dialog box with two options. It should currently be set to Windows UEFI mode, instead select Other OS and press enter.
With this done, all you then need to do is press F10 to save and exit, you'll get another box pop up showing the changes that you've made and just select yes. The computer will then restart.
With this change made, the error message should then be gone and the computer will load normally again.
While the location of the BIOS options will vary depending on the manufacturer, if you are having this issue with a different brand of motherboard changing the Secure Boot option like this should fix the problem in the same way.
