How to Fix Windows 10 Upgrade Error Code 0x80200056

Windows 10 update process has been quite simplified and users receive and install new updates automatically by default. Windows 10 is definitely an improvement over the last couple of Windows OS versions and it brings a new concept to life where the smartphone and PC structures and design begin to look more alike.

Updating Windows 10 can always cause plenty of different error codes and listing them down would definitely take a while. Each error code is usually caused by something different so you never know just what it would take to fix each error. Follow the article in order to find out what to do when facing this error in particular.

Fix Windows 10 Upgrade Error Code 0x80200056

Users have reported that this error code usually appears if users want to install the Preview Builds manually or automatically. These updates are a part of the Windows Insider Program where users are able to test out new builds and features of Windows 10 before anyone else.

The error message appears with the “Failed to download the new preview build, please try again later. 0x80200056” text written next to it and it won’t let you download the new preview build in the Settings app >> Update and recovery >> Preview builds. Find out how to fix this by following the instructions below.

Solution 1: A Simple Command Prompt Hotfix

Users who were having this issue reported that they were able to fix this certain issue by using this command which was able to fix the problem easily. This fix uses a tool called BITS admin which manages the Background Intelligence Transfer Service, which is one of the core services for Windows Update. Follow the instructions below!

1. Open Command Prompt by searching for it in the Start menu. Right-click on it at the list of results and select the Run as administrator option. You can also open the Run dialog box and type in “cmd” and click OK.

2. Copy and paste the command below in order to execute this command. Make sure you click Enter afterwards.

bitsadmin.exe /reset /allusers

3. Restart your computer and try running the update again.

Solution 2: Run the System File Checker Tool and DISM

This problem may occur if some of the system files necessary for the update are either missing from your system or if they are corrupt and can’t be accessed. This is especially valid if the error code is displayed next to the ERROR_SXS_ASSEMBLY_MISSING message. Make sure your follow the instructions below in order to fix this.

1. Run the DISM (Deployment Image Servicing and Management) tool. This tool is particularly useful if you want to check whether your system is ready for the following update. The tool can be used to scan and check your Windows image for errors and inconsistencies.
   If you want to take a look at detailed instructions on how to operate this tool, check out our article on the topic: dism repair.
2. Use the SFC.exe (System File Checker) tool which is accessed via the administrative Command Prompt (the same as DISM tool). The tool will scan your Windows system files for broken or missing files and it’s able to fix or replace the files instantly. This can be quite useful if you need those files for the updating process since the ERROR_SXS_ASSEMBLY_MISSING appears if there is a problem with one of your system files.
   If you want to take a look at detailed instructions on how to operate this tool, check out our article on the topic: sfc scan.
   

Solution 3: Sign In With Your Insider Account

Users have reported that the update doesn’t work properly if you want to install the Preview Built but if you are not logged in with your insider account.

In order to become a part of the Windows Insider Program, you need to register with a specific Microsoft account which should be used on your computer as well. Switch the account to the Insider one by following the steps below.

1. Click on the Start menu button located at the bottom left part of your screen and click on your current account’s icon in order to bring up the context menu.

2. Click on the Sign out option which should be the last and wait for the login screen to show up.
3. When the login screen shows up, choose your Insider account, type in the password and try updating your computer again.

Alternative:

1. Use the Ctrl + Alt + Del key combination in order to bring up a blue screen with several useful options on display. Choose the Switch user option.

2. When the login screen shows up, choose your Insider account, type in the password and try running the Preview build update again.

Solution 4: Run the Disk Cleanup Tool

In order for the updating process to proceed smoothly, you will need to prepare your computer for the update by making sure you check out everything on the list which should prepare your computer for an update.

Some users have reported that simply running the Disk Cleanup tool managed to help them fix the issue almost immediately. It seems that your storage drive needs to be well optimized, especially for bigger updates. It can also occur if your hard drive doesn’t have enough space to install the update properly but running this tool takes care of that as well.

1. Click on either the Start menu button at the left corner of the taskbar or click on the Search button right next to it. Type in “Disk cleanup” and choose it from the list of results.

2. Disk cleanup will firstly scan your computer for unnecessary files and it will prompt you with the option of choosing which files do you want to delete. Click on each option and read the description displayed below. If you decide to delete these files, check the box next to the files.

3. Click the OK button in order to proceed with the process. After the tool finishes, try running the update again.

Alternative: You can also run the Disk Cleanup tool by using the Command Prompt if you are comfortable with that option. However, you will need to find out the letters of your hard drive partitions so that you can know which drive do you want to cleanup.

1. Click on the Start menu and type in Command Prompt. You can also open the Run dialog box and type in “cmd” and click OK.

2. Copy and paste the following command in the Command Prompt window. The Drive placeholder should be replaced with the letter representing the partition you want to clean.

c:\windows\SYSTEM32\cleanmgr.exe /dDrive

3. Try running the update again.

Solution 5: Perform a Clean Boot

Performing a clean boot is a process where you run your Windows by using only the most basic items without any additional startup items. This method is ideal for running Windows Updates because you make sure none of the background applications you have installed are not interfering with the process.

Find out more on how to perform a clean boot on Windows 8, 8.1, and 10 by clicking here to open our article on the topic.

Solution 6: Reset Windows Update Components

This method is somewhat advanced and it takes a while to accomplish it. However, users have reported that, even when the other methods failed, resetting the components was still able to fix their issue.

Before proceeding with this solution, it’s recommended that you close all of your running programs and it’s advisable to create a backup of your registry just in case something goes terribly wrong while you edit it. Backup your registry by following the instructions in our backup registry settings.

1. Let’s proceed with the solution by killing the following services which are the core services related to Windows Update: Background Intelligent Transfer, Windows Update, and Cryptographic Services. Disabling them before we start is crucial if you want the remainder of the steps to perform smoothly.
2. Search for “Command Prompt”, right-click on it, and select the “Run as administrator” option. Copy and paste the following commands and make sure you click Enter after each one.

net stop bits
net stop wuauserv
net stop appidsvc
net stop cryptsvc

3. After this, you will have to delete some files which should be deleted if you want to continue with resetting the update components. This is also done via Command Prompt with administrative privileges.

Del “%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat”

4. The following step can be skipped if this is not last resort. This step is considered to be the aggressive approach but it will definitely reset your updating process from its very core. So we can recommend that you try this out. It has been suggested by a lot of people on online forums.
5. Change the name of the SoftwareDistribution and catroot2 folders. In order to do this, at an administrative command prompt, copy and paste the following commands and click Enter after copying each one.

Ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak
Ren %systemroot%\system32\catroot2 catroot2.bak

6. The following commands will help us reset the BITS (Background Intelligence Transfer Service) and the wuauserv (Windows Update Service) to their default security descriptors. Make sure you don’t modify the commands below so it’s for the best if you simply copy them.

exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)

7. Let’s navigate back to the System32 folder in order to proceed with the solution at hand.

cd /d %windir%\system32

8. Since we have completely reset the BITS service, we will need to reregister all of the files necessary for the service to run and operate smoothly. However, each of the files requires a new command in order to make it reregister itself so the process may end up being lengthier than what you are used to. Copy the commands one by one and make sure you don’t leave out any of them. Here is a list of files which need to be reregistered along with the corresponding commands next to them.
9. Some files may have been left behind after these processes so we are going to look for them in this step. Open the Registry Editor by typing “regedit” in either the search bar or the Run dialog box. Navigate to the following key in Registry Editor:

HKEY_LOCAL_MACHINE\COMPONENTS

10. Click on the Components key and check the right side of the window for the following keys. Delete them all if you locate any of them.

PendingXmlIdentifier
NextQueueEntryIndex
AdvancedInstallersNeedResolving

11. The next thing we are going to do is reset Winsock by copying and pasting the following command back into the administrative Command Prompt:

netsh winsock reset

12. If you are running Windows 7, 8, 8.1, or 10, at a command prompt, copy the following command, and tap the Enter key:

netsh winhttp reset proxy

13. If all of the steps above have gone through painlessly, you can now restart the services you killed in the very first step by using the commands below.

net start bits
net start wuauserv
net start appidsvc
net start cryptsvc

14. Restart your computer after following through with all of the steps which are listed.

Solution 7: Run the Windows Update Troubleshooter

Windows comes prepared when it comes to solving issues related to different aspects of your computer. Troubleshooters which are preinstalled on your computer are not certain to solve your issue but they can definitely help you at least to figure out what the problem is so that you can possibly submit it to Microsoft or that you can explain to someone more experienced.

Additionally, if the problem’s solution is obvious, troubleshooter may suggest a solution or it may even try to fix the problem automatically which is a great thing, especially for inexperienced users.

1. Open the Settings app by clicking on the Start button and then the gear icon just above. You can also search for it.

2. Open the Update & Security section and navigate to the Troubleshoot menu.
3. First of all, click on the Windows Update option and follow the instructions on screen to see whether there is something wrong with Windows Update services and processes.

4. After the troubleshooter finishes, navigate to the Troubleshoot section again and open the Internet Connections troubleshooter.
5. Check to see if the problem is solved.