Windows 10: 2004 update fails, I believe it's caused by multiple boot entries.

So I have a similar issue to this fella however I think my boot partition is fine, it's the other entries that are causing the issue.

In BIOS I have three boot entries on my main SSD. Looking at EasyUEFI, I see that two of them are on the C: partition. (Ignore the USB drive)

I've disabled them here but they're still showing up in BIOS, and I think Windows is trying to boot to them during/after the update, causing it to bootloop, fail, and roll back the update.

Are these extra entries safe to delete? I'm pretty sure I created these incorrectly when trying to recreate the system partition via command line awhile back. Is there another fix? Thank you.

submitted by /u/ryanvsrobots
[link] [comments]

:)

 

2004 Fails Multiple Times

2004 has installed fine on all my other computers yet on a two year old laptop it has failed multiple times. Both through MCT and WU. Seems to be at the second boot or whatever, then it rolls back.

 

multiple entries of modem in settings

In settings-devices I have over 70 entries for my Archer_VR1600v modem all saying "not connected" and only one entry with nothing listed next to it. I need to reset my network settings daily to get any connection to the internet. Would these multiple listings
be the cause of this resetting problem?

*** Merge thread due to similar issue ***

 

Windows Booting very slow after 2004 update ,

@JonGraef - that is an interesting observation, BUT it might be an effect rather than a cause. Nontheless, I have seen old and new reports where the Windows WMI (WBEM) repository can get out of sync with "reality" (i.e. what bits and peices under the "hood"
are where, and other properties), and cause that event 6006, and a slow boot or slow display of login screen. There is an easy way to check it out, and if the first "verify" command works, then go no further, it has probably got rebuilt OK:

"

• To perform a repair/re-sync of the Windows 10 WMI repository:
  1. Open an elevated command prompt. (right click the start menu icon, choose admin cmd or powershell)
     
  2. Verify the WMI repository is not corrupt by running the following command:

• If the repository is not corrupted, a “WMI Repository is consistent” message will be returned; if you get something else, go to step 3, otherwise if the repository is consistent, more troubleshooting will be required as the repository is not likely the
  problem.

1. Run the following commands to repair WMI:

• If the repository salvage fails to work, then run the following command to see if it resolves the issue:

• After the last command, there should be a “WMI Repository has been reset” message returned that verifies the command was successful.