Windows 10: Boot loop after update no safe mode option-repair fails- restore fails

Ubuntu shows 13.9GB free which is what I remember being clear when the update failed due to insufficient free space. Don't know why Diskpart shows 0.

 

Can you please post screenshot of below commands:


Code: Diskpart List Volume[/quote]

 

We need to rebuild BCD data store.

Since the BCD store exists and lists a Windows installation, you'll first have to "remove" it manually and then try to rebuild it again. At the prompt, execute the bcdedit command as shown and then press Enter:

Execute below command to point Command Prompt to C: drive.

C:


bcdedit /export C:\bcdbackup

The bcdedit command is used here to export the BCD store as a file: bcdbackup. There's no need to specify a file extension.

The command should return the following on screen:

The operation completed successfully.

Meaning the BCD export worked as expected.


At this point, you need to adjust several file attributes for the BCD store so you can manipulate it. At the prompt, execute the attrib command exactly like this:

attrib c:\boot\bcd -h -r -s

What you just did with the attrib command was remove the hidden, read-only, and system attributes from the file bcd. Those attributes restricted the actions you could take on the file. Now that they're gone, you can manipulate the file more freely - specifically, rename it.

To rename the BCD store, execute the ren command as shown:

ren c:\boot\bcd bcd.old

Now that the BCD store is renamed, you should now be able to successfully rebuild it.

Try rebuilding the BCD again by executing the following, followed by Enter:

bootrec /rebuildbcd

Restart your computer after rebuilding the BCD store.

If the issue not resolved please follow below instructions.

Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.


Please execute below command and reboot your computer to see issue resolves.


Code: DISM /Image:C:\ /Cleanup-Image /RevertPendingActions[/quote] Please replace partition letter C: with Windows installed partition letter. When computer boots into Windows Recovery Environment (WinRE) environment the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assign any other drive letter usually D: drive letter is assign to Windows installed partition. The Bcdedit /enum | find "osdevice" command can be use to find out the drive letter of the Windows installed partition the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.

 

I must be doing something wrong or not understanding.

 

Please execute following command:

Code: bcdboot E:\Windows /s C: /f ALL[/quote]



You may need to replace E: drive letter with Windows OS installed partition drive letter.

Restart your computer.

 

Have you restarted your computer?

 

OK that did the trick! Windows is now running again. I went straight to Update and see its trying to pull down version 1607 KB4023057. Unplugged the wifi to kill the download. Will look more at other threads on how to stop updates until I see MS has resolved these issues. Can you explain what actually fixed the issue? Thank you for all of the help. I hope others will benefit from this thread.

 

I don't see how Windows update causing the boot files to become corrupted. You can create a system restore point and install the Windows updates don't worry anything goes wrong i will help you repair your computer. Just to be safe keep a note of the KB numbers of the Windows updates that will be installed we can use the KB number to uninstall the Windows update from Windows Recovery Environment.

You are very welcome!

 

OK Update is back doing its thing. I looked at Update history and see that my Brother HL-2170W printer was updated 20 times in the last few days and more than 100 times in the last several months. KB4023057 is now successfully installed.

 

If those printer updates have installed you have nothing to worry about it we will deal with the printer update after installing all updates.

 

Last night around 9pm I noticed the pc was doing another update. Endless boot loop again. I ran through the steps from yesterday with one new result and it will not boot.

 

Do you remember the KB number of the last update?

 

No unfortunately I didn't see what it was. It it something I can find in a folder?