Troubleshoot problems updating Windows 10

In Windows 10, you decide when and how to get the latest updates to keep your device running smoothly and securely. This article will help you answer questions and troubleshoot common problems with your Windows 10 update.

If you’re looking for info on how to activate Windows 10 or to verify that your installation of Windows 10 is activated, see Activate Windows 10.

Have issues installing Windows updates? Start here.

Your device may not be able to update to the latest version of Windows 10 for a few reasons. The following tips can help you pinpoint the issue affecting your device.

Before you begin, make sure your device is plugged into a power source and connected to the internet. Then, try the steps listed below to get your PC to update.

Some updates require administrator access. If your account doesn’t have administrator access, see Create a local user or administrator account in Windows 10. Or if someone else at home or in your office has an administrator account on your device, try asking them to install the updates.

Before trying any of the solutions below, make sure you back up your personal files. You can use File History to back up your files to another drive, or insert a USB drive and use File Explorer to drag and copy important files to the USB drive. If you’re signing into Windows with a Microsoft account, your system settings will be automatically restored after updating, once you’re connected to the internet.

You can also back up your files with OneDrive. For more info, go to Back up your Documents, Pictures, and Desktop folders with OneDrive.

Make sure that your device has enough space. Your device requires at least 16 GB of free space to upgrade a 32-bit OS, or 20 GB for a 64-bit OS. If your device has a small hard drive, you may need to insert a USB drive to update it.

If your PC is running low on storage, try the techniques at Free up drive space in Windows 10.

Many updates require you to restart your device. Save your work and close all open applications. Then, select Start > Power , and select either Update and restart or Update and shut down.

Even if you have downloaded some updates, there may be more available. After trying the preceding steps, run Windows Update again by selecting Start > Settings > Update & Security > Windows Update > Check for updates. Download and install any new updates.

Remove any external storage devices and drives, docks, and other hardware plugged into your device that aren’t needed for basic functionality. Then try to run updates again and see if this resolved your issue. If it didn’t, continue to the next tip.

If you’ve added hardware to your device, check for third-party driver updates and installation instructions on the hardware manufacturer’s website. Update any drivers, then try to run updates again and see if this resolved your issue. If it didn’t, continue to the next tip.

In the search box on the taskbar, type device manager, then select Device Manager from the list of results.

In the window that appears, look for any device with a yellow exclamation mark next to it. (You may have to select each category to view the list of devices.) Select the device name.

Select Action, and then choose either Update driver or Uninstall to correct the errors.

Common troubleshooting questions

If you are receiving an error message with a specific error code, try running the Windows Update Troubleshooter. If that doesn’t resolve the issue, see Fix Windows Update errors and follow the instructions to help resolve common update issues.

The time required to download and install updates depends on connection speed, network settings, and the size of the update. If the installation remains stuck at the same percentage, try checking for updates again or running the Windows Update Troubleshooter.

To check for updates, select Start > Settings > Update & Security > Windows Update > Check for updates.

To get help, in the search box on the task bar, type get help, then select Get Help from the list of results. To leave feedback if you run into further problems, in the search box on the taskbar, type feedback hub, then select Feedback Hub from the list of results.

Windows 10 is the most secure Windows ever, and we recommend you stay updated to protect your PC from security risks and to keep it running smoothly. However, you can temporarily pause updates as well as schedule a restart to install updates at a time that’s convenient for you.
Learn how to temporarily pause updates
Find out how to schedule a restart to install updates at a convenient time

You will only receive a notification when it’s time to restart your computer to apply the installed updates.

If you need to know where you left off in your work after an update, use Timeline to jump back in.

To get started with Timeline, select Task View on the taskbar, or press the Windows logo key +Tab and select the activity you want to resume.

Monthly quality updates on Windows 10 are quite small and have a minimal impact on data usage. Feature updates typically happen twice per year, and you can control when to install them. They require more data but are less frequent.

If you’re on a metered connection, some updates for Windows won’t be installed automatically. Metered connections in Windows 10

Your computer might be slow for a number of reasons, but updating to the latest version of Windows 10 can improve its performance. For help with a slow computer, see Tips to improve PC performance in Windows 10.

If you’re having trouble finding your files after an upgrade, see Find lost files after the upgrade to Windows 10 for other things to try.

Warning: Microsoft only recommends trying the procedures in this section if you’re comfortable working in the command line. These procedures require administrator permissions on your device.

In the search box on the taskbar, type command prompt, then select Run as administrator from the list of options. Select Yes. Next, in the window that appears, type the following commands one at a time, including the spaces as shown. After you type each command, press Enter. Then let each command complete before you type the next command.

net stop wuauserv

ren %systemroot%\softwaredistribution softwaredistribution.bak

ren %systemroot%\system32\catroot2 catroot2.bak

net start wuauserv

After all these commands are completed, close the Command Prompt window and restart your computer.

In some instances, third-party antivirus or security software can cause errors when you try to update to the latest version of Windows 10. You can temporarily uninstall this software, update your PC, and then reinstall the software after your device is up to date. We recommend using third-party antivirus or security software that’s compatible with the latest version of Windows 10. You can check compatibility by visiting the software manufacturer’s website.

Note: Before uninstalling software, make sure you know how to reinstall your programs and that you have any necessary product keys.

In the search box on the taskbar, type command prompt, and then select Run as administrator from the list of options. Select Yes. In the window that appears, type the following command, including the space as shown:
chkdsk/f C:
and then press Enter. Repairs will automatically start on your hard drive, and you’ll be asked to restart your device.

A clean restart starts Windows with a minimal set of drivers and startup programs. This helps eliminate software conflicts that occur when you install a program or an update that may cause issues updating your PC.
Learn how to do a clean restart

In the search box on the taskbar, type command prompt, then select Run as administrator from the list of options.

In the window that appears, type this command including spaces as shown:
DISM.exe /Online /Cleanup-image /Restorehealth

Press Enter. When the command operation has run successfully, you’ll see a confirmation message from Command Prompt that says, “The restore operation completed successfully” or “The operation completed successfully”.
Note: If you don’t see a confirmation message, retype the command and try again.

Next, type this command, including the space as shown:
sfc /scannow

Press Enter. Wait until the sfc scan verification reaches 100% completion, and then close Command Prompt.

Try running the Windows Update again.

Go to the software download page and select Download tool now to download the clean installation tool. Make sure to carefully read the notes on the software download page before using the tool.

Still stuck?

Contact Microsoft support if you continue to have problems with your Windows updates.

Check computer update windows

Windows-Update-Checker : KUC

Downloads Update Lists FAQ

KUC is a small utility that will check what updates are installed, missing or removable on your Windows7, W2008R2 system.
[SP1 must be installed]

KUC will download all missing updates and install new and/or remove not needed once.

KUC is running on any computer with .Net 4.6.1 installed.

References of the following systems are included:

Win7 x64 and Win7 x86,
W2008R2 and W2008R2 Server Core,
WMS2011,
WHS2011, WSS2008R2ess, SBS2011ess,
W7Ex64-online, W7Ex86-online, W7Ex64-install.wim, W7Ex86-install.wim

I have created these references from installation images (wims) that have all updates installed.
(Except the –online references)

You can easily manage KUC’s output file in Excel .

For each package, update or hotfix you get the following information:

[KB#] : The knowledgebase (KB) number of the update

[Version] : The version number of the update

[State] : The installation state of the update: installed, install pending, staged, superseded.
Packages that have been added by KUC have an empty [State].

[Release Type] :
Update, Security Update, Hotfix, Language Pack, etc.

[Install Time] : The date and time, the package was installed.

[Package Identity] :
The (short) name of the package.

[Language] : If the package is language depended, you find the installation language here.

(The information above depend on DISM)

[Filename] : The name of the .msu file of the package.

[Superseded] : Just ‘yes’ or (nothing). The result depends on my update list (see above).
Do not mix up this column with the [State] column. This column is set by KUC, the [State] column by the operating system.

[SupersedingUpdates] :
Here you find the KB-number(s) of the update(s) that supersede this update. (Note: only the most recent update(s) can be found here, intermediate updates are ignored). (Example: KB3 supersedes KB2, witch supersedes KB1. For both, KB1 and KB2 this column will contain KB3)

[KUC-Type] : If a package only updates a specific feature or addition, the name of this feature or addition can be found her.

[KUC-State] : The column you should look at. (See Description below)

[KUC-StateRemarks] :
Special information about the package.

[NotInstalledSupersedingUpdates] :
KUC also will check, if all of the superseding updates are installed. If some are not installed, you can find them here.

· ADD : update is missing.

· ADD/EXCLUSIVE : Those updates should be installed exclusively.

· ADD/GDR : Add this normal update to avoid Windows message “new updates are available”.

· ADD/LDR : Add this “BF” update to avoid Windows message “new updates are available”.

· ADDLATER : update is missing but you should to do something else before you install it, look at the [KUC-StateRemarks] column to find out more.

· BAD : Oh oh! Something was going wrong during the update installation. First, remove all BAD packages. Then try to add the package again.

· BAD/IGNORE : Something was going wrong during the update installation. You can’t remove this package directly. Try to reinstall GDR&LDR version of those KB#s.

· IGNORE : see [KUC-StateRemarks] for detail.

· KEEP : You should not or cannot remove this package.

· OK : I like those .

· OK/ADD : The package is missing; you could add it, but needn’t.

· OK/GDR : Keep this normal update to avoid Windows message: ’new updates are available’.

· OK/IGNORE : The package is copied from the reference because you checked ‘do not ignore any’ and irrelevant.

· OK/INFO : The package is installed; there may be some additional actions to perform.

· OK/LDR : Keep this “BF” update to avoid Windows message: ’new updates are available’.

· OK/REMOVE : You can remove this package. Look at [KUC-StateRemarks] for detail.
(Example: LDR “BF” version of this package is installed; you can remove the GDR version.)

· REMOVE : You get the KUC-state under several circumstances.
1. The OS marked this package as “Superseded” (in column [State]).
2. You have installed an update that was designed for the RTM version of windows or witch is included in service pack 1 (SP1).
3. This package is superseded and all of the superseding updates are installed.
In all these cases, you can remove the package.

· REMOVE/ADD : Normally you get this KUC-State, if you have installed a package in a lower version than that of the reference. So first remove the old and then add the new version.

• REMOVE/FORCED : You get this KUC-State, if you decide to remove/ignore packages for features you do not want.

· REMOVELATER : Most common reason for this KUC-State is: This package is superseded but not all superseding updates are installed!

· unknown : I hate those .
New updates -not found in the reference- are also listed here.
If you get one of those and it is not a new update, please tell me, I may be able to add it to the reference. New updates will be included in the next release.

· … More to come on next releases

I also added some routines to handle special cases like » only install 2615701, if 2619234 is installed «, or » not integratable «, » don’t integrate «, .

Installation:
Just place the file in a folder you like. I suggest to use the folder C:\WU.
KUC does not make any changes to your System.

Execution:

To run/use the program, you have two choices:

Choice 1. Create the packages.txt your own, on a computer, you want or from a wim-image, you like. Then run KUC and tell him were to find the packages.txt file.

Command to create the packages.txt file for online systems:
dism /online /get-packages /format:table /English >Packages.txt

Command to create the packages.txt file for offline images:
dism /imagepath:D:\Offlinepath /get-packages /format:table /English >Packages.txt
(Replace D:\offlinepath as you need)

Choice 2. Let KUC generate the packages.txt file of your online system.
(Not possible for server-core or wim-images.)
To do this you must run KUC as administrator . (KUC cannot run dism without this right.)

With the first choice you are able to check the [KUC-State] of computers of friends,
of computers that do not support KUC or of installation images.

KUC searches for windows additions that you have installed on your system.

If an addition is installed “ found ”, the search for missing updates of this addition is automatically selected. All missing updates will be added to the output file with [KUC-State] “ADD”.

If an addition is not installed “ not found ” you can decide if you want to add it or leave it.

1. Leave it unchecked: All not needed packages will get the [KUC-State] “REMOVE”

2. Check it: The installation package of this addition and all superseding packages will be placed in the output file with [KUC-State] “ADD”.

All additions will be marked in the [KUC-Type] column.

Note: Not every addition can be integrated. For example “Management Framework” needs .Net 4.0, which is not available in most foundation wims. [KUC-StateRemarks] will inform you.

Note: All labels and checkboxes have tool-tips. So just move your cursor over them.

Don’t ignore any packages of the reference:
KUC normally ignores some packages of the reference with low relevance. This option should only be checked for special propose.

check for missing IE8 updates:
If IE9 is not found you cannot change this. KUC will search for missing IE8 updates.
If IE9 is found and the box is unchecked, IE8 updates will be treated as removable.
If IE9 is found and this box is checked KUC will search for missing IE8 updates.

check for missing RSAT (Remote Server Admin Tool) updates:

If RSAT is found, you cannot change this. If RSAT is not found and the box is unchecked, remaining RSAT updates will be marked as removable.
If you check the box, KUC will search for missing RSAT updates. Since RSAT updates are normal updates on servers, you cannot uncheck this box there. If you cannot install RSAT on a special foundation, this box is disabled.

AD LDS = Active Directory Lightweight Directory Services

VPC = Virtual PC

WIF = Windows Identity Foundation

WUA = Windows Update Agent

ADFS = Active Directory Federation Services

Media Server = just guess

ServerBPA = BPA for server foundation

BPA = Best Practice Analyzer

SystemReadiness = Tool for checking updates (registry and installation)

WinHelp = Utility to view help files created in Windows Help format.

Fmapi = File Management API

MSAgent = Microsoft Agent

NTBackup = the old NTBackup/Restore utility for Windows 7

BrowserChoice = User will be asked what browser he wants

ClientBPA = BPA for client foundation

disable AMD CorePark. = Update that disables AMD Core Parking

check for ALL Server Additions:

If the foundation is server, you select all possible server additions by one click.

check for ALL other Additions:

You can select all possible other additions by one click here.

After you make your decisions KUC starts to run and gives you a first overview of your installation.

Not installed Additions are red ; installed are blue .

KUC found 341 packages (not updates) in your windows installation and 1075 in the reference (+10 extra -95 ignored (depending on your former decisions). KUC also found 761 packages that are not present. Moreover, Oh-Oh 2 packages have a BAD KUC-State.
4 packages for IE8, 5 for IE9, 30 for VPC, 2 for WIF and five for the other additions are found in the input file.

There are +9 new packages for IE9, +4 new for VPC and +3 new for WIF. Nothing new could be found for the other additions. (“disable AMD CorePark.” is new; but was not selected).

Now let’s have a look on the 2. Option Window.

KUC found 767 packages to and 13 to remove in your input file.
273 input packages have no Category (No Cat.) +612 (to add) and -10 (to remove).

20 input packages are for drivers +82 (to add) –3 (to remove).

1 input package is for Media +12 (to add). (Windows Media Player network share and/or Media Center).

2 input packages are for Group Policy +12 (to add) and none to remove.

Some options are disabled. This depends on the foundation and the additions that are installed.
Note that the Vmdriver checkbox is disabled due to VPC is installed.

You do not have any “BF” packages (you did not use “force LDR installation”). There are +232 packages to add and -0 to remove.

Since you have no “BF” there are obviously no GDR/LDR combos.

You did not install any packages for the features IIS, MSMQ, NFS, SNMP or SUA.

As you can see KUC selected only the features that have been installed before.

Also, note that some updates belong to more than one category.

Select Check Options 2:

check for superseded updates:
KUC gives you an overview about all superseded updates installed on the test system. All no longer needed updates will get [KUC-State] “REMOVE”.

Note: This is a very important checking. Some users are wondering, why they get so much packages marked as “missing” on their systems, even if they had installed all of SoLoR updates.
If this box is unchecked, ALL missing updates (superseded or not) will be placed in the output file with [KUC-State] “ADD”. Therefore, if you do not want superseded updates leave this box checked.

use “GDR/LDR” to keep to avoid ‘update available’:

Some superseded updates will popup with ‘update available’ message if they are not installed. KUC takes care the this small number of updates are not removed form your system.

check for ‘force LDR install’ packages:
(This option is only checkable, if the ‘check for superseded updates’ option is selected.)
If you do not check this box ‘force LDR-installation’ packages will be ignored.

KUC check for updates that are present as GDR and LDR:
(This option is only checkable, if the ‘check for superseded updates’ and the ‘force LDR install’ option are selected.)

If you use a “force LDR-installation“-method to install updates, sometimes updates are present in GDR and LDR version. Normally there is no reason to keep both.
Depending on the number of GDR/LDR combos, KUC will propose a checking now.

Note: This is a very important checking, too. Users are often wondering, why KUC adds both (normal and BF_) versions to the output file. You can control this with this check box.
If this box is unchecked KUC assumes, that you want both, the GDR and the LDR version of a package. Therefore, KUC adds both of them to the output file. Also if KUC finds both versions installed he does not mark the GDR version as removable.
If this box is checked, KUC will find GDR versions that you can remove and will only add the LDR (BF_) version of missing updates to the output.