Share this article

Improve this guide

Full Fix: Windows 10 build install fails with error 0x8020000f

7 min. read

Updated onMarch 25, 2024

updated onMarch 25, 2024

Share this article

Improve this guide

Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more

Key notes

Windows 10 build 14385 for both PC and Mobile is out, but it appears many Insiders couldn’t install the latestupdatedue to various error codes. We have already reported about the 0x80246019 error code that prevented Insiders from downloading the latestWindows 10build, but a new error reared its ugly head.

This time, it’s error 0x8020000f that doesn’t allow Insiders toinstallthe current build. Actually, this is not the first time when this error has prevented Insiders from getting their hands on Microsoft’s builds. Last year, thousands of users couldn’t download build 10159 due to the same error code.

Can’t install the latest Insider builds due to error 0x8020000f

Error 0x8020000f can be problematic and prevent you from downloading the latest builds. Speaking of errors, here are some similar issues that users reported:

Solution 1 – Switch to the Slow Ring temporarily

If you’re having problems with error 0x8020000f and you can’tinstallthe latest build, you might want to consider switching to the Slow Ring temporarily. To do that, follow these steps:

After making these changes, the problem should be resolved and you’ll be able toinstallthe latestupdates.

Solution 2 – Check your antivirus

If you can’tinstallthe latest Windows 10 build due to error 0x8020000f, the problem might be your antivirus. Your antivirus can sometimes interfere with certain Windows features and it can cause this and other errors to appear.

To fix the problem, it’s advised that you check your antivirus settings and disable certain features. In some cases, you might even have to completely disable your antivirus. In case this doesn’t work, your next step would be to uninstall your antivirus.

Even if you remove your third-party antivirus, you’ll still be protected by Windows Defender, so there’s no need to worry about your safety. After you remove the antivirus, check if the problem is still there.

If removing the antivirus solves your problem, perhaps this might be a good time to consider a new antivirus software.

There are many great antivirus tools on the market, and you will be pleased to know that many of theantiviruses with the highest detection ratedon’t interfere with your system.

Solution 3 – Make sure that you’re not using a metered connection

According to users, they weren’t able toinstallthe latest builds due to error 0x8020000f. Apparently, this was caused by the metered connection. In case you don’t know, Windows 10 won’t download anyupdateswhile using a metered connection in order to save your monthly data.

However, this can be an issue and prevent you from downloading the latestupdates. To fix the issue, you just have to do the following:

After making this change, check if the problem is still there. Several users reported that after they disabled the metered connection feature, the issue was resolved, so be sure to try that.

Solution 4 – Disconnect all USB devices

Sometimes error 0x8020000f can appear due to your USB peripherals. We have all sorts of USB peripherals connected to our PCs, and sometimes these devices can interfere with theupdateprocess. To fix the problem, it’s advised to disconnect all unnecessary USB devices from your PC.

As a rule of thumb, you should just leave your mouse and keyboard connected and try toupdateagain. Other devices such as Wi-Fi adapters can also cause this problem, so you might have to remove your Wi-Fi card and check if that helps. Here’s anarticle dedicated to fixing Windows Update error 0x8007139fif you are interested.

Solution 5 – Run Disk Cleanup

If you can’tinstallthe latest build due to the 0x8020000f error, you might be able to fix the problem simply by runningDisk Cleanup. Sometimes temporary files might be corrupted and they can interfere with theinstallationprocess, so it’s advised to remove them. To perform Disk Cleanup, do the following:

After cleaning the old files, try toinstalltheupdateagain and check if the problem is still there.

Solution 6 – Run SFC and DISM scans

If your current Windowsinstallationis corrupted, you might encounter 0x8020000f error whileinstallingnew builds. This can be a big problem, but you might be able to fix it simply by performing an SFC scan. To do that, follow these steps:

After the scanning process is finished, check if the issue is still there. Sometimes theSFCscan can’t fix the problem, and if that happens, you need to run a DISM scan by doing the following:

After performing both scans, check if the problem is still there. If you were unable to run the SFC scan before, try running it once again after running the DISM scan.

Another option is to useautomated repair softwarethat will make the job a whole lot easier. We recommend these tools because they can repair multiple Windows-related errors, restore your OS, repair malware damage, and more.

Solution 7 – Disable proxy

If you want to protect your privacy online, using a proxy might be one of the simplest ways to do it. However, sometimes your proxy might interfere with certain Windows features, and that can cause error 0x8020000f whileinstallingupdates.

To fix this issue, users are recommending that you disable your proxy and check if that helps. To do that, just follow these simple steps:

After doing that, your proxy should be completely disabled and the problem will be resolved.

Not being able to download the latest builds due to error 0x8020000f can be quite annoying, but in most cases, you can fix this problem by disabling the metered connection or by switching temporarily to the Slow ring.

Full Fix: Windows 10 build install fails with error 0x8020000f#

Can’t install the latest Insider builds due to error 0x8020000f#

Solution 1 – Switch to the Slow Ring temporarily#

Solution 2 – Check your antivirus#

Solution 3 – Make sure that you’re not using a metered connection#

Solution 4 – Disconnect all USB devices#

Solution 5 – Run Disk Cleanup#

Solution 6 – Run SFC and DISM scans#

Solution 7 – Disable proxy#