Windows Update ends with error 0x800f0982 / 0x8024200d

[German]In Windows it may happen that the installation of updates (e.g. with the Windows 10 Updates KB4480116 and KB4482887) via Windows Update terminates with the error code 0x800f0982 or 0x8024200d. Here is some information about this error


Advertising


The error description

I came recently across this error on German site administrator.de. During the installation of the Windows 10 updates KB4480116 and KB4482887, an affected person received the error code 0x800f0982.

Windows 10 Update KB4480116) und KB4482887 Fehler 0x800f0982

alle Windows 10 Clients erhalten bei den beiden o. g. Updates den Fehler 0x800f0982.

I described these updates in the blog post Patchday Patchday Windows 10-Updates (January 8, 2019)  [KB4480116] and in the post Windows 10 V1809: Update KB4482887 released (03/01/2019) [KB4482887].

A similar error description for the error codes 0x800f0982 and 0x8024200d can be found in my German blog within the comments for the article Patchday Patchday Windows 10-Updates (9. Oktober 2018):

Update KB4464330 for Windows 10 Version 1809: At the moment it seems not uncommon that the automatic update fails with 0x800f0982 at the first attempt. And only in the second attempt (the Windows update itself starts) then correctly is installed.

Another user adds that the error 0x8024200d occurs during the update installation. For example, there was the cumulative KB4464330 update for Windows 10 version 1809.

Update Error 0x8024200d


Advertising

The above screenshot is from this forum thread, where someone gets the error code 0x8024200d displayed.

Update error 0x8024200d

I had mentioned the meaning of this error code within this comment here. The error code 0x8024200d stands for ‘Need another download’ in Windows. So there is something missing for the update installation of the KB package.

Since the updates can be installed (in many cases) within a second attempt, my explanation was that the current Servicing Stack Update (SSU) for that update is missing. Microsoft has been releasing an updated Servicing Stack Update (SSU) for Windows 7 SP1 as well as the still supported Windows 10 versions (and of course the server counterparts) for almost every update cycle for quite some time.

Update error 0x800f0982

The update error 0x800f0982 makes it more difficult – at least I didn’t find a direct description of Microsoft’s code. 

Trying to decode the code 0x800f0982

But you can try to decode the error code 0x800f0982. I described this approach in the blog post How to decode Windows errors?. The 0x8 stands for an error, the value f in 0x800f indicates the so-called facility code. This stands for the system service that is responsible for the error. The value F covers in this case four different sources, from RPC calls to COM/OLE errors. But it is not a Win32 error and also not a certificate error.

What remains is the actual error code 0x0982, for which I didn’t find much. Somewhere a compiler error came to my attention – and the decimal equivalent 2434 is listed in this Microsoft document as a network error (NERR_AcctLimitExceeded = A user’s session with this server has been deleted). But I’m not sure if this is true. 

If you search the Internet, you will find the error code 0x800f0982 in connection with modified ISO installations (e.g. nLite). So it could also be one of the popular tools for cleaning up or simply a broken update package. In this forum thread someone describes another case where a bug in the installer caused this code.

Hints about a Layout Error in the Compont Store

In the above mentioned nLite forum thread someone posted the WindowsUpdateLog file. There you can find the entry:

2018-10-13 17:33:25, Error CSI 0000014f@2018/10/13:15:33:25.797 (F) Attempting to mark store corrupt with category [l:21 ml:22]’CorruptComponentValue'[gle=0x80004005]

2018-10-13 17:33:25, Error CSI 00000150@2018/10/13:15:33:25.797 (F) onecore\base\wcp\componentstore\storelayout.cpp(2244): Error 800f0982 [Warning,Facility=15 (0x000f),Code=2434 (0x0982)] originated in function ComponentStore::CRawStoreLayout::AddComponentFile expression: ((SCODE) (((unsigned long)(1)<<31) | ((unsigned long)(15)<<16) | ((unsigned long)(0x982))) )
[gle=0x80004005]

The update error 0x800f0982 is therefore triggered as a warning in a C++ routine that is responsible for resolving the component store layout. The GLE code 0x80004005 stands for E_FAIL = Unknown Error. An affected person has also posted an excerpt from the error log in this forum thread.

2018-10-13 17:33:25, Info CSI 0000014c Component Microsoft-Windows-Security-SPP-VirtualDevice, version 10.0.17763.55, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} does not have a winner but has 2 other component version(s)
2018-10-13 17:33:25, Info CSI 0000014d Component Microsoft-Windows-BootEnvironment-Core-BootManager-PCAT.Resources, version 10.0.17763.55, arch x86, culture [l:5]’en-us’, nonSxS, pkt {l:8 b:31bf3856ad364e35} does not have a winner but has 1 other component version(s)
2018-10-13 17:33:25, Error CSI 0000014e (F) Can not identify matching versions for component Microsoft-Windows-BootEnvironment-Core-BootManager-PCAT.Resources, version 10.0.17763.55, arch x86, culture [l:5]’en-us’, nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2018-10-13 17:33:25, Error CSI 0000014f@2018/10/13:15:33:25.797 (F) Attempting to mark store corrupt with category [l:21 ml:22]’CorruptComponentValue'[gle=0x80004005]
2018-10-13 17:33:25, Error CSI 00000150@2018/10/13:15:33:25.797 (F) onecore\base\wcp\componentstore\storelayout.cpp(2244): Error 800f0982 [Warning,Facility=15 (0x000f),Code=2434 (0x0982)] originated in function ComponentStore::CRawStoreLayout::AddComponentFile expression: ((SCODE) (((unsigned long)(1)<<31) | ((unsigned long)(15)<<16) | ((unsigned long)(0x982))) )
[gle=0x80004005]
2018-10-13 17:33:25, Info CBS Added S:\INSTALL\Microsoft\Patches\KB4464330.log to WER report.
2018-10-13 17:33:25, Info CBS Not able to add pending.xml to offline WER report. [HRESULT = 0x80070002 – ERROR_FILE_NOT_FOUND]

The error is triggered by the component store in the layout routine and represents a warning. And there is an attempt to mark the component store used by Windows Update as corrupt. 

#1: First approaches to troubleshooting

To exclude a corrupted Windows where old files cause incompatibility with the update service, you can perform a system error check (Check and repair Windows system files and component store). If damages are present, they are usually detected and repaired.

In order to exclude broken packages in the update store as a cause, you could run the update troubleshooter or empty/reset the update cache (this concerns the order Windows\SoftwareDistribution). I explained the last step in more detail in the blog post Windows Update Error 0x8007042B.

This will usually not really help. Also trying to download and install the update manually will fail. However, you should perform these diagnostic steps to avoid such errors. You should also ensure that the latest Servicing Stack Update (SSU) for Windows is installed. 

#2: Broken update package from Microsoft

In the past there have been cases where Microsoft has delivered a broken update which could not be installed and which caused the installation with the error code 0x800f0982. However, these updates were withdrawn. This also corresponds to the hint in this forum thread, where an error in the installer of a software caused this code.

#3: Empty SystemResource folder

While searching for this error I came across this MS Answers forum thread. Someone got the error code from the update KB4482887 (dated March 1, 2019). The usual methods, like deleting the update store (folder SoftwareDistribution), running the update troubleshooter or checking for system errors (Check and repair Windows system files and component store) did not work for this user.

Ordner Windows\SystemResources

A second user, marlae35, claims to have solved the problem by emptying the Windows\SystemResources folder (see screenshot above).

I got the same problem on update KB4482887, and went through this issue on the cumulative 2019-02 KB4486553 update today and that wouldn’t install – Spent 2-3 hours messing around it and tried various things — finally I had to delete all the folders/files in the Windows\SystemResources folder and it worked.

I tried the delete in the Windows\SystemResources folder and did not work on the KB4482887.  Does Microsoft actually test these installs or do they just push them out to waste everybody time? I just went through this in Oct 2018 on another update that Microsoft eventually pulled because it was so screwed up.

This folder does indeed exist under Windows 10 (Windows 7 does not have the folder). Deleting individual files did not help. Only when he deleted the contents of the complete folder, the update could be installed. His theory: There was a broken update from October 2018 in the system, which caused the consequential error. But this didn’t help everyone. Update KB4482887 is an optional update anyway, which I would hide. Maybe someone will help. 

Similar articles
Win10 Wiki
Uninstalling ‘uninstallable’ Windows Updates
How to decode Windows errors?
Windows 10: Analyze upgrade errors
Windows 10: Upgrade error 80240020
Windows: How to decode update 0x8024…. errors
Check and repair Windows system files and component store


Advertising


This entry was posted in issue, Update, Windows and tagged , , , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *