Can't login after Windows 7 update

[Oldguy]

Just did a shutdown on my affected computer and there was 1 update to install.....took a chance and allowed it.....Microsoft must have gotten the message regarding the issues of their last update because I am now able to finally login. Want to thank everyone on this forum for all the information.

 

[goldbergsfg]

How did you get the update? Did you just leave the computer ON? How did you shut is down to find the update. A controlled shut down or a hard shutdown?

Thanks

 

[Oldguy]

On the user account screen you should have a button in the lower right corner that will give you the options of shutting down or restart.....I chose shutdown and that's when the available update was shown....

 

[goldbergsfg]

100% success. I had my daughter leave her computer on last evening hoping Microsoft would push the new update. Sure enough they did and now it is working without any other work on my part.

THANK YOU OLDGUY for your latest posting. It saved a lot of work.

 

[Bertison]

RE: shutdowns - in my efforts to permanently remove any and all Win10 KB's, I took this path: -

Always use Start - Log off (I set my Start button to "Log off" permanently.)

When Shutdown Logos appear, I could see all the usual actions, including "Shut Down and Install Updates", and "Shut Down". I took the "Shut Down" option and blocked any possible Installs.

I also set Windows Update to "Check For Updates But Let Me Choose When To Install Them." I check Windows Update every day before I Log off/Shut down and I check the list of Win 10 updates. If they are present, I uncheck and Hide them. It annoys me that I have to do this, to prevent Microsoft forcing an unwanted O/S onto my PC.

 

[hokieman91]

FIX - Bad Microsoft patch KB3097877

Been a busy morning - thx Microsoft

Anyway, this worked for me for the machines stuck at login (safe mode doesn't work, repair doesn't work, SFC doesn't work...) If you are unable to roll your system back (system restore BEFORE the update), you will have to do this fix from a command line.
1. F8 at post and select "Repair your Computer"
2. Login with an account that has administrative privileges on the machine since you will need to modify system files.
3. Under "Choose a recovery tool" select "Command Prompt"
4. You will need to determine the drive where your OS is installed (this was the trick for me since Microsoft told me to use drive X - which is not correct for the vast majority of systems out there since if you look at the label of the disk, it is BOOT) - easy way just keep switching drive letters (C, D, etc) until you find the disk label that states you are on the "OSDisk"
5. The DISM command is how to remove the patch and I have pasted the command below for both x86 and x64 systems

x86 - [FONT=&quot]dism /image:C:\ /remove-package /PackageNameackage_for_KB3097877~31bf3856ad364e35~x86~~6.1.1.1[/FONT]

x64 - [FONT=&quot]dism /image:C:\ /remove-package /PackageNameackage_for_[/FONT]KB3097877~31bf3856ad364e35~amd64~~6.1.1.1

Note that "C" (after image) is the drive labeled OSDisk - you may need to modify or you will get errors

You can also run

dism /image:C:\ /get-packages -----this command lists all updates installed since package name changes for x86 and x64 systems

IF YOU HAVE MULTIPLE SYSTEMS compromised like I did - I copied these commands into notepad, saved as fix.txt, save to a flash drive and then you can copy/paste since I could not do this on the multiple systems that were bricked today

using "F" for my flash (replace as necessary) - run f:/notepad.exe fix.txt - that will open up your saved notepad file with those commands and then copy/paste/enter to save you time

After DISM removes the update, reboot and you are good to go.

Microsoft has already updated the bad patch online so the next time you do Windows Update, you will get the good one.

If you have an internal WSUS server like me, make certain you either uninstall/decline that update OR run another synch to get the superseded fixed update.

Hope this helps!!

 

[hokieman91]

FIX - Bad Microsoft patch KB3097877
Been a busy morning - thx Microsoft

Anyway, this worked for me for the machines stuck at login (safe mode doesn't work, repair doesn't work, SFC doesn't work...) If you are unable to roll your system back (system restore BEFORE the update), you will have to do this fix from a command line.
1. F8 at post and select "Repair your Computer"
2. Login with an account that has administrative privileges on the machine since you will need to modify system files.
3. Under "Choose a recovery tool" select "Command Prompt"
4. You will need to determine the drive where your OS is installed (this was the trick for me since Microsoft told me to use drive X - which is not correct for the vast majority of systems out there since if you look at the label of the disk, it is BOOT) - easy way just keep switching drive letters (C, D, etc) until you find the disk label that states you are on the "OSDisk"
5. The DISM command is how to remove the patch and I have pasted the command below for both x86 and x64 systems

x86 - [FONT=&quot]dism /image:C:\ /remove-package /PackageNameackage_for_KB3097877~31bf3856ad364e35~x86~~6.1.1.1[/FONT]

x64 - [FONT=&quot]dism /image:C:\ /remove-package /PackageNameackage_for_[/FONT]KB3097877~31bf3856ad364e35~amd64~~6.1.1.1

Note that "C" (after image) is the drive labeled OSDisk - you may need to modify or you will get errors

You can also run

dism /image:C:\ /get-packages -----this command lists all updates installed since package name changes for x86 and x64 systems

IF YOU HAVE MULTIPLE SYSTEMS compromised like I did - I copied these commands into notepad, saved as fix.txt, save to a flash drive and then you can copy/paste since I could not do this on the multiple systems that were bricked today

using "F" for my flash (replace as necessary) - run f:/notepad.exe fix.txt - that will open up your saved notepad file with those commands and then copy/paste/enter to save you time

After DISM removes the update, reboot and you are good to go.

Microsoft has already updated the bad patch online so the next time you do Windows Update, you will get the good one.

If you have an internal WSUS server like me, make certain you either uninstall/decline that update OR run another synch to get the superseded fixed update.

Hope this helps!!