[SOLVED] Windows 10 20H2 x64 fails to update to 22H2 with error 0x8007000d (Windows Update)

AntonUnknown

New member
Mar 16, 2025
3
It happened on the old laptop which was unused for several years. Originally it had Windows 7, then it was upgraded to Windows 10 20H2 and then left unused. Several days ago I decided to power it on and install updates. Many updates were installed successfully, but this one didn't. I tried installing it multiple times with the same result. I tried rolling back using system restore, but it didn't help.
I tried to check system disk, at first with GUI (it didn't ask for reboot) and then with command line (with reboot), both runs didn't find any errors.
I tried Dism /Online /Cleanup-Image /RestoreHealth and sfc /scannow, these commands fixed some errors, but the update still fails.
I found an article which said it is required to install KB5015878 before updating to 22H2. I downloaded the standalone package, but its installation failed with the same error (0x8007000d).
There are interesting messages in logs. I think this is the main cause:
Code:
2025-03-16 15:54:45, Info                  CSI    000006bd Playback delta generated succesfully : [l:11 ml:12]'MsMpRes.dll'
2025-03-16 15:54:45, Info                  CSI    000006be Playback delta generated succesfully : [l:12 ml:13]'shellext.dll'
2025-03-16 15:54:45, Error                 CSI    000006bf@2025/3/16:12:54:45.264 (F) onecore\base\wcp\rtllib\win32lib\delta_library.cpp(340): Error NTSTATUS_FROM_WIN32(ERROR_INVALID_DATA) originated in function Windows::Rtl::DeltaDecompressBuffer expression: g_pfnApplyDeltaGetReverseB( ( (DELTA_FLAG_TYPE)0x00000000 ), ReferenceInput, CompressedInput, &FileTimeInDeltaHeader, &UncompressedOutput, &ReverseOutput)
[gle=0x80004005]
2025-03-16 15:54:45, Error                 CSI    000006c0 (F) Hydration failed with error NTSTATUS_FROM_WIN32(ERROR_INVALID_DATA) . Delta Type: Forward Delta , IntegrityState Valid: true , RetrievedChecksum: 3203248522 , ComputedChecksum: 3203248522[gle=0x80004005]
2025-03-16 15:54:45, Error                 CSI    000006c1 (F) Hydration failed for component Windows-Defender-Service, version 10.0.19041.3636, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} on file MpAsDesc.dll with NTSTATUS -1073283059. Matching Component = Windows-Defender-Service, version 10.0.19041.746, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}. FileHasForwardReverseDeltas  = false, GenerateReverseDelta = true[gle=0x80004005]
2025-03-16 15:54:45, Error                 CSI    000006c2 (F) Matching binary MpAsDesc.dll missing for component Windows-Defender-Service, version 10.0.19041.3636, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}[gle=0x80004005]
2025-03-16 15:54:45, Info                  CBS    Sending WER
2025-03-16 15:54:45, Error                 CSI    000006c3@2025/3/16:12:54:45.264 (F) onecore\base\wcp\componentstore\storelayout.cpp(1703): Error 800f0984 [Warning,Facility=15 (0x000f),Code=2436 (0x0984)] originated in function ComponentStore::CRawStoreLayout::HydrateFile expression: ((SCODE) (((unsigned long)(1)<<31) | ((unsigned long)(15)<<16) | ((unsigned long)(0x984))) )
[gle=0x80004005]
2025-03-16 15:54:45, Error                 CSI    000006c4@2025/3/16:12:54:45.264 (F) Attempting to mark store corrupt with category [l:18 ml:19]'CorruptPayloadFile'[gle=0x80004005]
2025-03-16 15:54:45, Info                  CSI    000006c5 Playback delta generated succesfully : [l:11 ml:12]'MsMpCom.dll'
2025-03-16 15:54:45, Info                  CSI    000006c6 Playback delta generated succesfully : [l:12 ml:13]'winshfhc.dll'

I tried to investigate more, searched for articles about WinSxS directory structure, but the file MpAsDesc.dll seems fine to me:

Code:
C:\Windows\WinSxS\amd64_windows-defender-service_31bf3856ad364e35_10.0.19041.746_none_a39f6d9ab59bd8b7>dir
 Volume in drive C is Acer
 Volume Serial Number is B4FA-FA2A

 Directory of C:\Windows\WinSxS\amd64_windows-defender-service_31bf3856ad364e35_10.0.19041.746_none_a39f6d9ab59bd8b7

14.02.2021  21:02    <DIR>          .
14.02.2021  21:02    <DIR>          ..
14.02.2021  21:02    <DIR>          f
23.12.2020  23:21            95 048 MpAsDesc.dll
07.12.2019  12:08         1 418 680 MpAzSubmit.dll
07.12.2019  12:08           942 520 MpClient.dll
07.12.2019  12:08           468 120 MpCmdRun.exe
07.12.2019  12:08           331 704 MpCommu.dll
07.12.2019  12:08           268 720 MpOAV.dll
07.12.2019  12:08           893 368 MpRtp.dll
07.12.2019  12:08         2 376 632 MpSvc.dll
14.02.2021  21:01            90 440 MsMpCom.dll
07.12.2019  12:08           103 384 MsMpEng.exe
07.12.2019  12:08            13 232 MsMpLics.dll
14.02.2021  21:02    <DIR>          r
07.12.2019  12:08             1 091 ThirdPartyNotices.txt
26.12.2020  03:16            19 968 winshfhc.dll
              13 File(s)      7 022 907 bytes
               4 Dir(s)  299 880 153 088 bytes free

C:\Windows\WinSxS\amd64_windows-defender-service_31bf3856ad364e35_10.0.19041.746_none_a39f6d9ab59bd8b7>dir f
 Volume in drive C is Acer
 Volume Serial Number is B4FA-FA2A

 Directory of C:\Windows\WinSxS\amd64_windows-defender-service_31bf3856ad364e35_10.0.19041.746_none_a39f6d9ab59bd8b7\f

14.02.2021  21:02    <DIR>          .
14.02.2021  21:02    <DIR>          ..
31.01.2021  14:40             5 238 MsMpCom.dll
02.12.2020  19:41               488 winshfhc.dll
               2 File(s)          5 726 bytes
               2 Dir(s)  299 880 022 016 bytes free

C:\Windows\WinSxS\amd64_windows-defender-service_31bf3856ad364e35_10.0.19041.746_none_a39f6d9ab59bd8b7>dir r
 Volume in drive C is Acer
 Volume Serial Number is B4FA-FA2A

 Directory of C:\Windows\WinSxS\amd64_windows-defender-service_31bf3856ad364e35_10.0.19041.746_none_a39f6d9ab59bd8b7\r

14.02.2021  21:02    <DIR>          .
14.02.2021  21:02    <DIR>          ..
31.01.2021  14:40             5 055 MsMpCom.dll
02.12.2020  19:41               435 winshfhc.dll
               2 File(s)          5 490 bytes
               2 Dir(s)  299 880 022 016 bytes free

C:\Windows\WinSxS\amd64_windows-defender-service_31bf3856ad364e35_10.0.19041.746_none_a39f6d9ab59bd8b7>fsutil hardlink list MpAsDesc.dll
\Program Files\Windows Defender\MpAsDesc.dll
\Windows\WinSxS\amd64_windows-defender-service_31bf3856ad364e35_10.0.19041.746_none_a39f6d9ab59bd8b7\MpAsDesc.dll

Windows Explorer shows that MpAsDesc.dll has a valid digital signature.
 

Attachments

Hi @AntonUnknown,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team
 
I found a similar thread and the COMPONENTS hive was requested there, so I'm uploading mine now just in case.
Also some clarification.
I ran dism before sfc because some article said this is the correct sequence. So:
  • the sfc log is in the CBS.log
  • the dism log is in the CbsPersist_20250316171711.log
  • interesting messages about MpAsDesc.dll are in the CbsPersist_20250316131245.log
 

Attachments

Hi and welcome to Sysnative,

Please try to upgrade to 22H2 using the following tool, but maybe it is blocked by Microsoft in Russia.

Download the
61c988c2082b1-updateassistent.png
Windows 10 Update Assistant to your desktop.
  • Right-click on Windows10Upgrade9252.exe and select the option: Run as administrator.
  • Press the Update now button, click after the compatibility check on Next.
  • The Update Assistant will now download the latest Feature Update.
  • After verifying the download, the Feature Update will be installed.
  • When this process is ready, click on the Restart now button to complete the installation.
 
Sorry for the late reply. I was busy recently.
This tool wasn't blocked. It worked in the end, though I ran into other problems which I solved myself.
At the first try this tool seemed to work, but after a reboot the update rolled back and I got a blue screen loop. It was caused by drivers. The first one was a touchpad driver ETD.sys (there are lots of posts about it on the Internet). The second one was a dedicated video card driver from NVIDIA (my laptop has dual graphics: integrated Intel and dedicated NVIDIA). I removed both drivers using Apps & features and disabled NVIDIA video card in the Device manager. Then I tried to use this tool again. Interestingly, I got blue screen during the last reboot, but then the update continued. So the update succeeded, now I have the 22H2 version. The touchpad works using the default PS/2 mouse driver (and I mostly use USB mouse anyway). Didn't try to install NVIDIA drivers yet, I'll try later.
Now I remember why I didn't use this laptop for a long time. The manufacturer officially doesn't support Windows 10 on this laptop and there are driver problems. The NVIDIA card never worked properly after updating to Windows 10.
Thanks for you help!
 
Hi,

You're welcome, And thanks for lettings us know this system is up-to-date now. If you are still having issues with the Nvidia driver please start a new thread in the Windows 10 Section.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top