Can't update to Windows 10 20H2

[Finnja]

Hi, so I'm trying to update from windows 10 1909 to 20H2, but when I try to update, I get the "making sure you're ready to install" dialogue box because of something called virtualbox (LDPlayer). I installed LDPlayer once, but have since removed every trace of it. I also removed all of my other emulators just in case they were the problem, to no avail. I've run the trouble shooter, restarted the PC, but still get the error. Does anyone know how I can fix this without reinstalling windows?

[Nathanpete]

This question is better suited for the forums on the microsoft website IMO. 

 

Is this dialogue box appearing when the rest of the computer is working normally, or has the update process taken over the computer and screen like it usually does, and it erroring out and reverting changes? 

(Actually now that I think about it, there are no changes to revert because it is failing early into the process, when it is just checking compatibility)

 

And how do you know if you actually removed every trace of LDPlayer, because obviously you didn't or it wouldn't be causing errors. I have multiple issues where even open source software has bad uninstallers and leaves traces in the registry leaving plenty of artifacts, particularly with context menus. 

[emosun]

Is there an issue with the machine using 1909?

[JoostinOnline]

The latest windows build is a buggy mess. I would suggest avoiding it if possible. Or at least not being in a rush to update. I'm not sure what's causing your problem, but I wouldn't be surprised if it was yet another 20H2 bug. Just run Disk Cleanup as administrator (right click on it for that option) to remove your downloaded update.

[Finnja]

5 minutes ago, Nathanpete said:

This question is better suited for the forums on the microsoft website IMO. 

 

Is this dialogue box appearing when the rest of the computer is working normally, or has the update process taken over the computer and screen like it usually does, and it erroring out and reverting changes? 

(Actually now that I think about it, there are no changes to revert because it is failing early into the process, when it is just checking compatibility)

 

And how do you know if you actually removed every trace of LDPlayer, because obviously you didn't or it wouldn't be causing errors. I have multiple issues where even open source software has bad uninstallers and leaves traces in the registry leaving plenty of artifacts, particularly with context menus. 

I get the dialog box right when I click "solve problems" in the windows "check for updates section"

[WhitetailAni]

5 minutes ago, JoostinOnline said:

The latest windows build is a buggy mess. I would suggest avoiding it if possible. Or at least not being in a rush to update. 

Hmm? My system fails at Windows at the first hint of weirdness and it's been running 20H2 without a hitch.

What exactly have you been having problems with?

 

As for OP, I'd agree with @Nathanpete over on your original thread and take this to the MS forums.

[SorryBella]

1 minute ago, FakeKGB said:

Hmm? My system fails at Windows at the first hint of weirdness and it's been running 20H2 without a hitch.

Ive had multiple BSODs when im running virtual machines (emulators or virtualbox) with any hardware accelerated apps on 20H2 which doesnt pop at all from previous updates.

[Finnja]

2 minutes ago, FakeKGB said:

Hmm? My system fails at Windows at the first hint of weirdness and it's been running 20H2 without a hitch.

What exactly have you been having problems with?

 

As for OP, I'd agree with @Nathanpete over on your original thread and take this to the MS forums.

Will do, thanks everyone who replied!

[WkdPaul]

18 minutes ago, Finnja said:

*snip*

I installed LDPlayer once, but have since removed every trace of it.

*snip*

You obviously didn't, if you did, then Windows Updater wouldn't detect it.

 

Check the registry, you probably still have entries in there and that's what is causing the issue.

[kanyewestlover911]

21 minutes ago, Finnja said:

Hi, so I'm trying to update from windows 10 1909 to 20H2, but when I try to update, I get the "making sure you're ready to install" dialogue box because of something called virtualbox (LDPlayer). I installed LDPlayer once, but have since removed every trace of it. I also removed all of my other emulators just in case they were the problem, to no avail. I've run the trouble shooter, restarted the PC, but still get the error. Does anyone know how I can fix this without reinstalling windows?

i had this same issue and fixed it by going to microsoft's website  and get the windows 10 update installer and it fixed my issue 

[WhitetailAni]

1 minute ago, SorryClaire said:

Ive had multiple BSODs when im running virtual machines (emulators or virtualbox) with any hardware accelerated apps on 20H2 which doesnt pop at all from previous updates.

I've never had those problems, and I've run many OS's in VMs - 98 SE, 2000, XP, Vista, Mint 17.3, ReactOS, TempleOS.

Though my Windows install is MBR, not GPT (it was upgraded from Windows 7), so maybe that could be it?

[Nathanpete]

10 minutes ago, wkdpaul said:

You obviously didn't, if you did, then Windows Updater wouldn't detect it.

 

Check the registry, you probably still have entries in there and that's what is causing the issue.

Exactly, I have had bad experiences with even actively updated (as in like 3 times a year) open source software have had pretty shit uninstallers that don't clean the registry and broke my context menus and the "choose an app to open this file with" dialogue window. IIRC it was some sort of open source replacement for the default photos app in windows. I downloaded like 4 different apps and tried them out, settled on the FastStone app, but the other apps remained attached to various image file extensions and I had to spend about and hour and a half doing CTRL+F in Regedit removing remnants. I wasn't able to fix the context menus (the laptop's context menus are still filled with entries that do absolutely nothing), but I was able to fix the relations for the file extensions for images.