- May 7, 2013
- 10,396
The Windows Update log should be examined when the you're experiencing problems with downloading an update rather than installing it. The log can be quite cryptic and difficult to debug so I hope this guide helps to solve some of the errors which I've come across.
Gathering the Windows Update Log:
The WindowsUpdate.log file is a single file on systems prior to Windows 10 and be found in the following location:
However, on Windows 8.1 and above, the WindowsUpdate.log has to be generated from several .etl files. There is another caveat here which I'll explain in a moment. To parse the .etl files into a single log file, you'll need to enter the following Powershell cmdlet:
This will produce the same traditional log file. However, on Windows 10 1709 builds and below, the cmdlet relies on the Microsoft Symbol Server so if the you're having difficulty with running the cmdlet, you need to ensure that the SymSrv.dll is present in the following directory:
Warning: Please request for help if the the file is missing, please do not alter any permissions related to the Windows Defender directory, otherwise you will introduce a dangerous vulnerability to your system which will be exploited by malicious software.
Troubleshooting 0x800706d9 - EPT_S_NOT_REGISTERED:
This is a connectivity error with the Windows Update server. Please remove or disable any proxies or third-party firewalls and then ensure that the Windows Firewall is enabled using the following command from an elevated command prompt:
Warning: Please note that the command will reset any custom policies/settings which you have implemented and therefore please create a suitable backup beforehand.
Example: Server 2016 won't update
Troubleshooting 0x80248007 - WU_E_DS_NODATA:
This is quite a simple error to resolve. The DataStore (found under %systemroot%\SoftwareDistribution) doesn't have the information which the Windows Update client is expecting. You will need to rename the SoftwareDistribution folder and then check for updates again. To rename the SoftwareDistribution then you will need to enter the following commands from an elevated command prompt:
If you are unable to stop one of the services then please remove any "optimiser" software. It can also be due to over zealous security software.
Example: [SOLVED] - Windows 10 Update Infinite Checking Loop
Troubleshooting 0xc1900401 - No More Packages To Download:
This error code is documented by Microsoft somewhere but I can't appear to find it? It had an error description of no more packages to download.
This is an odd one, the Windows Update client will offer an update which is already technically installed. You can either use WUSA or FRST64 to remove the problematic update. If you are unable to remove the update using WUSA then please request help; do not attempt to create a FRST64 fix script yourself since you may irreparably damage your operating system.
Example: [SOLVED] - (KB5010796) Downloading 0%
Troubleshooting 0x80072EFD - WININET_E_CANNOT_CONNECT:
This is a similar error to 0x800706d9 and means that the Windows Update client was unable to establish a connection with the download server. There can be a few reasons for this as mentioned before: third-party firewalls, proxies such as VPNs and third-party AV software.
The following troubleshooting steps should be undertaken:
Example: Windows 7x64 cant get updates installed after the previous to last (2019-12) Update
Troubleshooting 0x800703F1 - ERROR_BADDB:
This error indicates that your COMPONENTS or DRIVERS hive is corrupt and usually will need to be manually repaired. Please run the ComponentsScanner tool and allow it to make repairs if it needs to. Otherwise, please request help from a Windows Update helper and do not attempt to make any repairs yourself.
Warning: Please do not attempt to manually resolve this error yourself under any circumstances, this includes attempting to use an earlier version of either hive, since this can lead to synchronization issues between your WinSxS folder and/or Driver Store.
Example: [SOLVED] - Windows update giving 0x800703f1 error
Windows Update Services:
Windows Update is dependent on a number of services in order to detect and download updates correctly. If you're experiencing Windows Update issues, then please ensure that the following services exist and are not disabled on your machine.
References:
Get-WindowsUpdateLog (WindowsUpdate)
Gathering the Windows Update Log:
The WindowsUpdate.log file is a single file on systems prior to Windows 10 and be found in the following location:
Rich (BB code):
%systemroot%\WindowsUpdate.logHowever, on Windows 8.1 and above, the WindowsUpdate.log has to be generated from several .etl files. There is another caveat here which I'll explain in a moment. To parse the .etl files into a single log file, you'll need to enter the following Powershell cmdlet:
Rich (BB code):
Get-WindowsUpdateLogThis will produce the same traditional log file. However, on Windows 10 1709 builds and below, the cmdlet relies on the Microsoft Symbol Server so if the you're having difficulty with running the cmdlet, you need to ensure that the SymSrv.dll is present in the following directory:
Rich (BB code):
C:\Program Files\Windows Defender\SymSrv.dllWarning: Please request for help if the the file is missing, please do not alter any permissions related to the Windows Defender directory, otherwise you will introduce a dangerous vulnerability to your system which will be exploited by malicious software.
Troubleshooting 0x800706d9 - EPT_S_NOT_REGISTERED:
Rich (BB code):
2022/02/28 21:11:06.9806508 1384 3880 DownloadManager BITS job {862E971A-86E3-46C1-B6F7-3DCC5DD33CB1} hit a transient error, updateId = {CDF3E348-B93C-4E03-9889-0497DB3E31AC}.200 <NULL>, error = 0x800706D9
2022/02/28 21:11:06.9817353 1384 3880 DownloadManager Error 0x800706d9 occurred while downloading update; notifying dependent calls.This is a connectivity error with the Windows Update server. Please remove or disable any proxies or third-party firewalls and then ensure that the Windows Firewall is enabled using the following command from an elevated command prompt:
Rich (BB code):
netsh advfirewall resetWarning: Please note that the command will reset any custom policies/settings which you have implemented and therefore please create a suitable backup beforehand.
Example: Server 2016 won't update
Troubleshooting 0x80248007 - WU_E_DS_NODATA:
Rich (BB code):
2022/03/09 18:09:12.2084120 9296 660 Agent *FAILED* [80248007] Failed to prepare the call security
2022/03/09 18:09:12.2100965 10244 4788 ComApi *FAILED* [80248007] ISusInternal:: BeginDownloadUpdates
2022/03/09 18:09:12.2107711 10244 4788 WIL *FAILED* [80248007] file = onecore\enduser\windowsupdate\client\comapi\downloadjob.cpp, line = 433
2022/03/09 18:09:12.2111357 10244 4788 ComApi *FAILED* [80248007] Method failed [CDownloadJob::BeginDownload:482]
2022/03/09 18:09:12.2111459 10244 4788 ComApi * END * Download ClientId = Update;ScanForUpdates (cV: QfTMaRjXS0WOkYcP.18.3.1.0.0)
2022/03/09 18:09:12.2111498 10244 4788 ComApi MarkUpdatesAsFailed invoked (cV = QfTMaRjXS0WOkYcP.18.3.1.0.0)
2022/03/09 18:09:12.2112484 10244 4788 WIL *FAILED* [80248007] file = onecore\enduser\windowsupdate\client\comapi\downloadjob.cpp, line = 497
2022/03/09 18:09:12.2112621 10244 4788 ComApi *FAILED* [80248007] Failed to start federated download against service 855E8A7C-ECB4-4CA3-B045-1DFA50104289 (cV = QfTMaRjXS0WOkYcP.18.3.1.1)
2022/03/09 18:09:12.2112667 10244 4788 WIL *FAILED* [80248007] file = onecore\enduser\windowsupdate\client\comapi\federateddownloadjob.cpp, line = 335
2022/03/09 18:09:12.2112845 10244 4788 ComApi * END * Federated Download encountered unrecoverable error, hr=0x80248007 (cV = QfTMaRjXS0WOkYcP.18.3.1.1)
2022/03/09 18:09:12.2164451 10244 13528 ComApi *FAILED* [80248007] Method failed [CUpdateDownloader::EndDownload:464]This is quite a simple error to resolve. The DataStore (found under %systemroot%\SoftwareDistribution) doesn't have the information which the Windows Update client is expecting. You will need to rename the SoftwareDistribution folder and then check for updates again. To rename the SoftwareDistribution then you will need to enter the following commands from an elevated command prompt:
Rich (BB code):
net stop wuauserv
net stop bits
rename %systemroot%\SoftwareDistribution SoftwareDistribution.bak
net start wuauserv
net start bitsIf you are unable to stop one of the services then please remove any "optimiser" software. It can also be due to over zealous security software.
Example: [SOLVED] - Windows 10 Update Infinite Checking Loop
Troubleshooting 0xc1900401 - No More Packages To Download:
This error code is documented by Microsoft somewhere but I can't appear to find it? It had an error description of no more packages to download.
Rich (BB code):
2022/01/26 13:00:33.0975473 7076 7084 DownloadManager Generating download request for update E8C13149-34AA-441B-865F-73CD4354C0D0.1.
2022/01/26 13:00:33.1814352 7076 7084 DownloadManager Calling into handler 0xc to generate download request for update E8C13149-34AA-441B-865F-73CD4354C0D0.1.
2022/01/26 13:00:33.1814427 7076 7084 Handler *FAILED* [C1900401] UUP GDR: Completed
2022/01/26 13:00:33.1814509 7076 7084 Handler *FAILED* [C1900401] file = onecore\enduser\windowsupdate\client\engine\handler\osdeployment\downloader\osasyncdownloader.cpp, line = 218
2022/01/26 13:00:33.1862976 7076 7084 Handler *FAILED* [C1900401] file = onecore\enduser\windowsupdate\client\engine\handler\osdeployment\handler\uhosdeployment.cpp, line = 356
2022/01/26 13:00:33.1863071 7076 7084 DownloadManager *FAILED* [C1900401] GDR
2022/01/26 13:00:33.4650514 7076 7084 Handler OnDownloadJobFailure - UUP update E8C13149-34AA-441B-865F-73CD4354C0D0.1 in the sandbox C:\Windows\SoftwareDistribution\Download\50cac1185dc569aa87dc46ba81f4f2f9 failed with 0xc1900401.
2022/01/26 13:00:33.4650544 7076 7084 Handler OnDownloadJobFailure - UUP update E8C13149-34AA-441B-865F-73CD4354C0D0.1 found 1l downloaders.
2022/01/26 13:00:33.4697819 7076 7084 DownloadManager *FAILED* [C1900401] Error occurred while downloading update E8C13149-34AA-441B-865F-73CD4354C0D0.1; notifying dependent calls.This is an odd one, the Windows Update client will offer an update which is already technically installed. You can either use WUSA or FRST64 to remove the problematic update. If you are unable to remove the update using WUSA then please request help; do not attempt to create a FRST64 fix script yourself since you may irreparably damage your operating system.
Example: [SOLVED] - (KB5010796) Downloading 0%
Troubleshooting 0x80072EFD - WININET_E_CANNOT_CONNECT:
Rich (BB code):
2020-03-11 21:12:21:187 1172 14f0 AU #############
2020-03-11 21:12:21:187 1172 14f0 AU ## START ## AU: Search for updates
2020-03-11 21:12:21:187 1172 14f0 AU #########
2020-03-11 21:12:21:188 1172 14f0 AU <<## SUBMITTED ## AU: Search for updates [CallId = {47DFA318-D22C-491A-8990-96F603E02B95}]
2020-03-11 21:12:21:188 1172 2b8c Agent *************
2020-03-11 21:12:21:188 1172 2b8c Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2020-03-11 21:12:21:188 1172 2b8c Agent *********
2020-03-11 21:12:21:188 1172 2b8c Agent * Online = Yes; Ignore download priority = No
2020-03-11 21:12:21:188 1172 2b8c Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2020-03-11 21:12:21:188 1172 2b8c Agent * ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77} Windows Update
2020-03-11 21:12:21:188 1172 2b8c Agent * Search Scope = {Machine}
2020-03-11 21:14:31:253 1172 2b8c Misc WARNING: Send failed with hr = 80072efd.
2020-03-11 21:14:31:253 1172 2b8c Misc WARNING: SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2020-03-11 21:14:31:253 1172 2b8c Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://ds.download.windowsupdate.com/v11/2/windowsupdate/redir/v6-win7sp1-wuredir.cab>. error 0x80072efd
2020-03-11 21:14:31:253 1172 2b8c Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
2020-03-11 21:14:31:253 1172 2b8c Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efd
2020-03-11 21:14:31:253 1172 2b8c Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efd
2020-03-11 21:14:31:253 1172 2b8c Misc WARNING: DownloadFileInternal failed for http://ds.download.windowsupdate.com/v11/2/windowsupdate/redir/v6-win7sp1-wuredir.cab: error 0x80072efdThis is a similar error to 0x800706d9 and means that the Windows Update client was unable to establish a connection with the download server. There can be a few reasons for this as mentioned before: third-party firewalls, proxies such as VPNs and third-party AV software.
The following troubleshooting steps should be undertaken:
- Remove all VPNs and third-party security software
- Resetting and enabling the Windows Firewall using netsh advfirewall reset
- Ensure that HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections only has the default subkeys and values
Example: Windows 7x64 cant get updates installed after the previous to last (2019-12) Update
Troubleshooting 0x800703F1 - ERROR_BADDB:
Rich (BB code):
2022/03/30 23:16:52.5656897 6152 5796 ComApi Deserialized installable update 2022-03 Cumulative Update Preview for Windows 10 Version 21H1 for x64-based Systems (KB5011543), UpdateID = {38391110-3A6F-4E29-8B2A-7776168910AE.1}, CallbackInfo cookie length = 1880
2022/03/30 23:16:52.5661193 6152 5796 ComApi Using handler to query deployment status for update 38391110-3A6F-4E29-8B2A-7776168910AE.1
2022/03/30 23:16:52.5687305 6152 5796 UDP QueryUpdateDeploymentStatusInternal invoked in Readonly mode for Update : 38391110-3A6F-4E29-8B2A-7776168910AE.1
2022/03/30 23:16:52.5701376 6152 5796 Handler Enter GetPostRebootResult for Deployment handler. Reporting cookie data: {ProductName":"Client.OS.RS2.amd64"
2022/03/30 23:16:52.5717663 6152 5796 Handler Sandbox folder C:\WINDOWS\SoftwareDistribution\Download\15fdc319276f08f3d8929bf78b77b392 exists
2022/03/30 23:16:52.6623003 6152 5796 Handler Using the update's service stack dll file 'C:\WINDOWS\SoftwareDistribution\Download\15fdc319276f08f3d8929bf78b77b392\Metadata\UpdateAgent.dll'
2022/03/30 23:16:53.2046853 6152 5796 Handler Update status code is 0x800703F1
2022/03/30 23:16:53.2046867 6152 5796 Handler Failed to install the update
2022/03/30 23:16:53.2103157 6152 5796 Handler Leave GetPostRebootResult for Deployment handler
2022/03/30 23:16:53.2103375 6152 5796 WIL *FAILED* [80240FFF] file = onecore\enduser\windowsupdate\client\engine\updatedeploymentprovider\lib\dpreportingdata.cpp, line = 1098
2022/03/30 23:16:53.2104738 6152 5796 WIL *FAILED* [80240FFF] file = onecore\enduser\windowsupdate\client\engine\updatedeploymentprovider\lib\dpreportingdata.cpp, line = 1075
2022/03/30 23:16:53.2104769 6152 5796 WIL *FAILED* [80240FFF] file = onecore\enduser\windowsupdate\client\engine\updatedeploymentprovider\lib\updatedeploymentprovider.cpp, line = 500
2022/03/30 23:16:53.2104909 6152 5796 UDP *FAILED* [80240FFF] QueryUpdateDeploymentStatus exited with hr = 0x80240fff
2022/03/30 23:16:53.2106057 6152 5796 WIL *FAILED* [80240FFF] file = onecore\enduser\windowsupdate\client\comapi\update.cpp, line = 4221
2022/03/30 23:16:53.2112671 6152 5796 ComApi Reloading CUpdate 381391110-3A6F-4E29-8B2A-7776168910AE.1 from datastore...This error indicates that your COMPONENTS or DRIVERS hive is corrupt and usually will need to be manually repaired. Please run the ComponentsScanner tool and allow it to make repairs if it needs to. Otherwise, please request help from a Windows Update helper and do not attempt to make any repairs yourself.
Warning: Please do not attempt to manually resolve this error yourself under any circumstances, this includes attempting to use an earlier version of either hive, since this can lead to synchronization issues between your WinSxS folder and/or Driver Store.
Example: [SOLVED] - Windows update giving 0x800703f1 error
Windows Update Services:
Windows Update is dependent on a number of services in order to detect and download updates correctly. If you're experiencing Windows Update issues, then please ensure that the following services exist and are not disabled on your machine.
- wuauserv (Windows Update Agent)
- BITS (Background Intelligent Transfer Service)
- DoSvc (Delivery Optimisation Service)
- UsoSvc (Update Orchester Service)
- AppReadiness (App Readiness Service)
References:
Get-WindowsUpdateLog (WindowsUpdate)