Friday, 31 July 2015

Solution to error 0x80240020: Upgrade to Windows 10

So the whole “delete the contents of the downloads directory” thing didn’t work for me.

Today I noticed a tweet linking to an article, which in turn referred to a post in the Microsoft forums.

Apparently, the error 0x80240020 is not an indication of any download corruption – just that you’re computer is in a “holding pattern” waiting for the green light from Microsoft, as they’re staging the upgrade process. I think it would have been preferable to have just had this sitting quietly on my computer, rather than littering my Update History with “Update failed” messages.

So if you don’t want to wait, there’s a registry key you can set. (Instructions for setting registry key repeated here from the forum post)

  1. Locate the registry key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\OSUpgrade]

  2. It should exist, but if not, create it.

  3. Create a new DWORD (32-bit) Value with Name = "AllowOSUpgrade” (without the quotes), and set the Value = 0x00000001.

Now go back to the Windows Update in Control Panel, and tada – a new screen appears!

Windows Update in Control Panel, prompting to Get started

Click on the Get started button and things start happening..

It thinks for a short time, then the Windows Update prompt appears on your desktop:

Dialog prompting to start the upgrade now

And back in the Control Panel, you’re also prompted to restart. Clicking Start the upgrade now, or Restart now both do the same thing

Windows Update in Control Panel, prompting to restart

Your computer reboots, and the upgrade proceeds.

After a little while, and a few reboots later, you now have Windows 10!

About Windows 10 dialog



Russ Smith said...

I followed the registry key hack and it did indeed allow me to upgrade my 8.1 Pro to 10 Pro.

However, the Windows 10 installation was horrendously broken from A-Z. I restored my original OS NOT via some sort of "Recovery" software but instead by copying another hard drive with a few day old 8.1 image on it onto my drive with Windows 10.

Reading around the web I saw a comment that suggested Core 2 quad CPUs may be problematic with Windows 10 - and that's the machine that Windows 10 broke on.

That is to say, it's possible Microsoft isn't just load balancing, but delaying for software development some systems' upgrades. When one twiddles a registry key to FORCE the upgrade, maybe the Windows 10 you get won't work on your machine - as with mine.

David Gardiner said...

Good point Russ,

sorry to hear it didn't go well. Hopefully Microsoft are working on a fix for your hardware and you can successfully upgrade soon.