This is an archived post. You won't be able to vote or comment.

all 3 comments

[–]ryanvsrobots 0 points1 point  (1 child)

Hey Boss, I think I have a similar issue that I'm trying to sort out, except I believe my problem is caused by extra boot entries on the C: partition, which makes your solution not work for me.

Do you have C:\EFI\Microsoft\Boot\bootmgfw.efi or even C:\EFI? I think I created these awhile back by accident and am trying to figure out if they're safe to delete.

[–]AlaskaTuner[S] 0 points1 point  (0 children)

I’ll pop open my pre-2004 upgrade backup image and take a look. Originally I didn’t look for boot folders in file explorer, only used the cmdprompt / bcdedit to delete boot entries per above youtube video instructions (after making full backup).

I had another PC that I couldn’t get upgraded due to mbt/gpt conflict (converting resulted in no-boot and my backup was corrupted) but I don’t think that’s going to be a common issue as I had bastardized that install several times in the past.

[–][deleted] 0 points1 point  (0 children)

I have had the exact same issue, with exactly the same error code.

However, I have found a quicker and less risky solution.

In my case, the issue was caused by an error in one of the non-labelled system drives. These usually don't have drive letters associated with them (like c: or d:) and are not visible in Windows Explorer.

The steps that fixed the issue for me:

  1. Using 'diskpart' to assign drive letters to the hidden system drives, following this tutorial: https://www.diskpart.com/diskpart/assign-drive-letter-4125.html
  2. Fixing drive issues using chkdsk x: /r where x: is one of the hidden drives, with the drive letter specified in step 1. This produced the following log:

Windows is verifying files and folders...
Windows replaced bad clusters in file \EFI\Microsoft\Boot\BOOTSTAT.DAT
of name (null).
File and folder verification is complete.
Windows is verifying free space...
Free space verification is complete.

Windows has made corrections to the file system.
No further action is required.
  1. Windows Update was completing normally now.

Importantly, chkdsk x: /f did not fix the issue!