EMERGENCY - Boot Loop After Win Update

Hey zbook,

I don't think that will work cuz I get all 0s in those files. What do you suggest?

.... EDIT .....
But Brink gave me an idea. I can disconnect my ssd from the PC and hook it up to one of the computers in the public library.

I can just transfer files from my ssd to the library's computer and then onto a flash drive. What do you think?

Hi zbook,

I can't explain those errors you pointed out.

But Brink suggested I create and boot from a Peppermint Live USB to recover my files. I think its the best thing to do without going through all those steps that haven't recovered my drive - though I greatly appreciate the help.

I think I'll go to the library and download that file to my USB flash drive. Then go home, boot up my PC with it and transfer my files to another flash drive. After that I'll restore from a Macrium backup then transfer those files to the PC.

Let me know what you think.

Hi zbook,

Someone suggested to remove the latest update through the command prompt in the recovery environment. He suggested the following which doesn't make sense:

"wusa /uninstall /kb:2744842 /quiet /forcestart"

Is the kb in the command the latest update? Would this solve my issue? If so do I enter that command above exactly as it says?

What progress was made with Ubuntu? Peppermint?

Earlier this year there were problems with Spectre and Meltdown.
Some Microsoft Windows updates had caused inaccessible boot device or loss of function of USB ports.
The method to uninstall the Windows updates used a dism command.
If you know of a cause and effect related to a Windows update you can uninstall the Widows update using command prompt and the dism command.
Were you able to establish a connection with a problematic Windows update?
Or was that trial and error?

This is a command that can be used to uninstall a Windows update:
Find the package(s) that were just installed by date. Run the following command on the last installed package:
example: dism.exe /image:e:\ /remove-package /packagename:Package_for_KB4014329~31bf3856ad364e35~amd64~~10.0.1.0
Reboot.
This is an example for kb4014329. So if you are able to identify a Windows update as the problem then you would start with the kb# and enter the additional information related to theis KB# and then reboot.

There were some commands used earlier that I did not see the complete results.
Please run these commands and post images of the results:

Open command prompt > X:\Sources>
type these commands:

1) bootrec /fixmbr
2) bootrec /fixboot
3) bootrec /scanos
4) bootrec /rebuildbcd

(This searches for windows installations not included in the BCD and then asks if you would like to add to it)
(It will display that it successfully scanned all installations and the identified installations will be 0 or 1 or more)
If 0 it displays: Total identified windows installations: 0 The operation completed successfully.
If 1 it displays: Total identified windows installations: 1 [1] D:\windows Add installation to boot list? Yes/No/All:
If 2 it displays: Total identified windows installations: 2 [1] D:\windows Add installation to boot list? Yes/No/All:
etc.
Type A
reboot
Please post an image of the commands and results into the thread.

zbook said:

What progress was made with Ubuntu? Peppermint?

Were you able to establish a connection with a problematic Windows update?
Or was that trial and error?

This is a command that can be used to uninstall a Windows update:
Find the package(s) that were just installed by date. Run the following command on the last installed package:
example: dism.exe /image:e:\ /remove-package /packagename:Package_for_KB4014329~31bf3856ad364e35~amd64~~10.0.1.0
Reboot.
This is an example for kb4014329. So if you are able to identify a Windows update as the problem then you would start with the kb# and enter the additional information related to theis KB# and then reboot.

Please run these commands and post images of the results:

Open command prompt > X:\Sources>
type these commands:

1) bootrec /fixmbr
2) bootrec /fixboot
3) bootrec /scanos
4) bootrec /rebuildbcd

(This searches for windows installations not included in the BCD and then asks if you would like to add to it)
(It will display that it successfully scanned all installations and the identified installations will be 0 or 1 or more)
If 0 it displays: Total identified windows installations: 0 The operation completed successfully.
If 1 it displays: Total identified windows installations: 1 [1] D:\windows Add installation to boot list? Yes/No/All:
If 2 it displays: Total identified windows installations: 2 [1] D:\windows Add installation to boot list? Yes/No/All:
etc.
Type A
reboot
Please post an image of the commands and results into the thread.

Hi zbook,

I'll be doing the peppermint thing today.

To answer your other question, and again as i said before, the bootloop is attributable to the latest update 2 days ago when I 1st complained about it.

Regarding deleting the update, I know it was the update from 2 days ago. But I don't know the name. Before I run the command to delete it, how could I find out the name to be sure?

As you asked, I ran the 4 commands. Take a look at the images I took of their result.

These links have some additional troubleshooting options:

The first is from Microsoft and is the method to uninstall Windows updates found to be problematic after Spectre and Meltdown:

• Use the Command Prompt to uninstall the update:

• At the recovery screen, select Troubleshoot, then Advanced Options, and then Command Prompt. You may be asked to enter a BitLocker Recovery Key or username/password.  If prompted for a username/password, you must enter a local administrator account.
• In the Command Prompt window, type the command listed below for your version of Windows and press ENTER.

For 32-bit versions of Windows:
dism.exe /image:c:\ /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~x86~~16299.248.1.17
For 64-bit versions of Windows:
dism.exe /image:c:\ /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.248.1.17
Note: If Windows is not stored on the C: drive, replace the C: in the above commands with the appropriate drive letter.

• Close the Command Prompt and click Continue to exit the Recovery Environment.
• Restart to enter Windows. Important: To ensure that your system has the latest security updates, reinstall updates as soon as possible. Select the Start button, and then go to Settings > Update & security > Windows Update, select Check for updates and install the latest updates.

https://support.microsoft.com/en-us/...ry-13-2018-upd


The second is from NeoSmart Knowledgebase and has:
Attempt Two: Manually Repairing the Windows Bootloader

Desperate times call for desperate measures.



Attempt Three: Nuclear Holocaust

Back at the main page of the recovery center, go ahead and select “Command Prompt” yet again from that list.
The first order of business is to make sure the MBR and bootsector contain the right references to the Windows bootloader:

Fixing the Windows Bootloader via the setup DVD

Zbook,

When I enter the command I get these errors in the image I attached. Take a look and let me know. I used various ways of entering the command.