Gfrktyl

Last night windows updated itself with some kernel drivers related patches and as a result today morning my Windows 7 won't even boot in safe mode.

It tried to repair itself, but no good

Root cause found:

- - - - - - - - - - - - - - - -

a patch is preventing the system from starting

Repair action: System files integrity check and repair

Result: Failed. Error code = 0x4005

I know which updates it installed, particularly I want to remove KB2160329 and KB981852. All I can get is Console...

Any ideas how to remove those updates?

Faced that issue today, my way to solve it:

1. Start up with F8


2. Run in safe mode


3. Windows should uninstall dubious KB2160329


4. Make sure that you will restart back to safe mode


5. Restart to normal mode


6. Windows will revert the update here as well

Hope that helps..

By the way, I've spotted that in C:WindowsSystem32 I have now the 6.1.7600.16585 version, while the latest available in the system is 6.1.7600.20738 (check C:Windowswinsxs).
Might it be some case of signature overwriting?

Just had this problem today after a BIOS update. The update process changed the SATA mode from ACHI to IDE. This prevented Win7 to start. I tried to go in recovery mode or use the installation disk without any success.

Then I changed back the SATA mode to ACHI and all worked back without any issue. Just want to post in case this can help anyone to have back a working system ASAP.

A quick Google search shows a few people with this same issue in Windows 7. The fix seems to be restoring backup copies of corrupted registry files.

Excerpted from a conversation on social.technet.microsoft.com:

"I first booted from the Windows 7 install disc to get to the system recovery console. I then selected Command Line. From there, I had to change from the X: drive to the C: drive by typing "C:". I then typed "cd windowssystem32config" to get to the registry file directory. By typing "dir" I could see that two of the five hive files (default, sam, security, software, and system) had recent copies with an "rmbak" extension: default.rmbak and software.rmbak. I then executed the following commands:

ren software software.bak

copy software.rmbak software

ren default default.bak

copy default.rmbak default

I would suggest you execute the "ren" then "copy" commands as above for any other hives that have "rmbak" backups with the same date/time stamp. This ensures your registry remains in sync. You can now reboot and see if your computer comes up.

Reboot"

Some variation on that fix might be just what you're looking for.

Ref:
http://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/20458464-8989-4bf9-80e1-c1c45182b83b

You're apparently not the only one with this problem. It's apparently KB981852 causing the problem.

See:

http://social.answers.microsoft.com/Forums/en/vistawu/thread/df590178-0a95-43e2-b5d3-3ba67dcc78bf

Also, you might try rebooting with "Last Known Good Configuration". WHen rebooting, hit F8 to get the boot menu. On the Advanced menu choose "Last Known Good Configuration". As long as you haven't logged on since installing the patches (and since you can't boot, that seems to be a safe assumption in your case), Last Known Good should get you going.

See:

http://windows.microsoft.com/en-US/windows7/Using-Last-Known-Good-Configuration

My problem was the BIOS. The computer had not been turned on for over a year. When setting up the BIOS, I left it at the default which was not correct.

Changed back to SATA mode ACHI. Booted up fine.