Windows update KB3177467 crashes windows 7 causing system to boot loop

I work as the IT manager for a small non-profit in Ireland that reuses computers for education and we recently had to deal with the following strange issue.

After installing the windows update KB3177467 on windows 7 the operating system is no longer recognised and the system goes in a repair boot loop. System recovery starts, automatic repair cannot recognise the existence of the windows operating system, it fails to fix the issue and reboots back into recovery.

We had reports from our school clients for more than 100 computers so far with the same issue and we expect many more.

To the best of my ability and understanding of windows, I came up with the following step by step guide that resolved the issue for us. The process basically is recovering windows by rebuilding windows BCD, replacing the file that fails signature verification with the new BCD, booting in windows and verifying all system files.

  1. Start windows recovery (inevitable at this stage of the issue as it starts by default)
  2. When automatic repair starts press cancel as quickly as possible
  3. Select “view advanced options for system recovery and support
  4. Select keyboard layout (UK or US will be ok)
  5. Select a local admin user and log in with the user’s password
  6. Open a terminal by clicking on command prompt
  7. Allow edits to existing windows BCD by fixing the file attributes: attrib c:boot\bcd -h -r -s
  8. Rename the old BCD: ren c:boot\bcd bcd.old
  9. Rebuild windows BCD with the bootrec command: bootrec /rebuildbcd
  10. Once bootrec recognises the existing windows OS on the hard drive type “Y” and press enter to confirm the creation of the new BCD
  11. Once the new BCD is created successfully you will receive the message “The operation completed successfully
  12. Knowing that the system will fail to verify the file C:\Windows\System32\winload.exe you can proceed with replacing it with the files from the recovery partition
    1. Backup the old winload.exe file by typing the following commands:

      • ren d:windows\system32\winload.efi winload.efi.bak

      • ren d:windows\system32\winload.exe winload.exe.bak

  13. Copy the original recovery files from the recovery partition to the system32 folder by following these commands (successful completion returns the message “1 file(s) copied”):
      • copy winload.exe d:windows\system32\

      • copy winload.efi d:windows\system32\

  14. You can now close the terminal windows and reboot the system
  15. Windows will fail to boot again because the new winload.exe files fails to verify (windows cannot verify the digital signature for this file)
  16. Press enter and then F8 for additional boot options
  17. Select boot option - Disable driver signature enforcement
  18. Once windows load normally login using an administrator account (camaraadmin)
  19. Go to start and search for: cmd
  20. Right click on the result (terminal shortcut) and select - Open as Administrator
  21. Run the following command to repair the system: sfc /scannow
  22. Once the system scan finishes reboot your computer and windows should function normally.

I hope this guide helps some people deal with this strange issue. Hopefully an official reply from Microsoft will be available soon as to why so many people are having various different problems with this specific update and ideally resolve this.



Reply In reply to deleted message
Has KB3177467 been pulled. I have a Windows 7 that doesn't have this patch and Windows update is not advertising it for intall.
Check under the installed updates tab, it might already be installed for you and didn't crash your system. I started with a fresh install of Windows 7 pro 64bit on a VM and after doing all the updates including KB3177467 today it didn't crash for me this time. Could be related to additional software that was installed before so I'm going to dig through the system logs and see if there is anything there that would give me more info on what could have caused the crash in the first place. If I find anything useful I'll post it here.
Forgive me father for I have synth...
Thank you so much. This article saved my bacon. Had a laptop get this patch from our 3rd party patch management tool. On reboot it came up to a black screen with a white underscore cursor. Couldn't do anything with it. No F8 menu even. Booted up from a Win7 install USB drive, went into the Repair Windows section and picked up your instructions from step 6. Everything went smooth from there. I was so pleased when Windows boot normally. Microsoft really blew it with this patch.

Necro'ing the thread.
If Windows/Microsoft Update works okay without this patch, STAY AWAY FROM IT.

On a Lenovo T420i, it seems like it's the culprit for sporadic network disconnections on GPU activity. It only happened when online video (Netflix, small video ads, etc) is present.

I even went through installing Windows fresh, then installing JUST this patch, then network drivers, then firing up a browser instance (you name it, tried with all), go to Netflix... Boom. It happened.

On a cmd window aside, with 'ping -t', while videos show up, the network disconnects briefly (wired/wifi), ping reports a 'General failure' 3 times, then it comes back online. This reset frequency ranges about 30~90 seconds per occurrence, killing SSH connections and any no-resume-capable downloads.

Next thing to try is ditching it into hidden, since it looks like it's the only available patch in a WU cycle (some design behavior they say), and carry on with the rest of the updates. I'll see how it goes, and report back.



Discussion Info

Last updated January 23, 2020 Views 10,513 Applies to: