[SOLVED] DISM error Error: 0x800f081f, Windows update from 21H1 to 21H2 BSOD on first boot

[xerion]

Hi all,

I was wondering if you can give me some help.
Windows 10 PRO update to 21H2 completes but then I Get a BSOD on first boot (reference by pointer)
I checked my DISM read the CBS log that says there are corrupted packaged.
Here are the steps.

SFC shows no errors

PS C:\WINDOWS\system32> sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

DISM return file not found.
I've also tried adding a source from a windows ISO. Tried the ESD as well as exported my image to a wim but no luck at all

C:\WINDOWS\system32> Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1766

[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

SFCFix
Also showed the same error as DISM.
In the CBS log I see for a few packages :
Info CBS Store corruption, manifest missing for package:
Error CBS Failed to resolve package .... [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION]
Info CBS Mark store corruption flag because of package:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-06-25 13:36:59.897
Microsoft Windows 10 Build 19043 - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2022-06-25 13:43:29.159
----------------------EOF-----------------------

Thank you in advance

 

[Maxstar]

Hi and welcome to Sysnative,

Step 1. Run SFCFix with the attached ZIP file. (This is the first batch with replacement files)
Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFix.zip and save it to your desktop.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result, and attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

 

[xerion]

Hi, thank you for that.
I am attaching the SFCFix.txt, the new CBS.log and dism.log

The DISM command failed again. Similarly to the previous time it got stuck at 62.3% though this time it took much longer to report the failure.
From what I can see in the CBS log we are down to 23 corruptions from about 314 that I had before, so it must have been doing something !

PS C:\WINDOWS\system32> DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1766

[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

 

[Maxstar]

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFix.zip and save it to your desktop.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

 

[xerion]

Seems like the DISM completed successfully.
I expected that this would solve the update to 21H2 version but it does not seem to be the case.
I should say that in the past I had tried the windows update utility to get the update since the option to upgrade was not available for me.
That was resulting in BSOD after first boot and changes were reverted.

This time I have option to update and I got the message below.

 

[xerion]

I am attaching the latest CBS.log from when attempting the update.
From what I see these relevant part is this with an error of STATUS_SXS_ASSEMBLY_MISSING

2022-07-06 09:36:55, Error                 CSI    00000019@2022/7/6:16:36:55.435 (F) onecore\base\wcp\componentstore\csd_locking.cpp(95): Error STATUS_SXS_ASSEMBLY_MISSING originated in function CCSDirectTransaction::LockComponent expression: (null)
[gle=0x80004005]
2022-07-06 09:36:55, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CBS.log to WER report.
2022-07-06 09:36:55, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-07-06 09:36:55, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-07-06 09:36:55, Info                  CBS    Not able to add poqexec.log to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-07-06 09:36:56, Error                 CSI    0000001a (F) STATUS_SXS_ASSEMBLY_MISSING #37863# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
2022-07-06 09:36:56, Error                 CSI    0000001b (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #37718# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = Microsoft-Windows-Product-Data-21h2-EKB-Deployment, version 10.0.19041.1706, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Microsoft-Windows-Product-Data-21h2-EKB-Package~31bf3856ad364e35~amd64~~10.0.19041.1706.5dffd2000f1aa7cae0309619d19e4e62', rah = (null), manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]
2022-07-06 09:36:56, Info                  CBS    Failed to pin deployment while resolving Update: Microsoft-Windows-Product-Data-21h2-EKB-Package~31bf3856ad364e35~amd64~~10.0.19041.1706.5dffd2000f1aa7cae0309619d19e4e62 from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2022-07-06 09:36:56, Info                  CBS    Failed to bulk stage deployment manifest and pin deployment for package:Microsoft-Windows-UpdateTargeting-ClientOS-21h2-EKB-Package~31bf3856ad364e35~amd64~el-GR~10.0.19041.1023 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2022-07-06 09:36:56, Info                  CBS    CommitPackagesState: Started persisting state of packages
2022-07-06 09:36:56, Info                  CBS    CommitPackagesState: Completed persisting state of packages
2022-07-06 09:36:56, Info                  CSI    0000001c@2022/7/6:16:36:56.506 CSI Transaction @0x24f65683d10 destroyed
2022-07-06 09:36:56, Info                  CBS    Perf: Resolve chain complete.
2022-07-06 09:36:56, Info                  CBS    Failed to resolve execution chain. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2022-07-06 09:36:56, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

 

[Maxstar]

Hi,

Upload your COMPONENTS hive.

• Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
• Please copy this file to your desktop.
• Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
• Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
• If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

 

[xerion]

Here it is.

 

[Maxstar]

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFixScript.txt and save it to your desktop.
• Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

 

[xerion]

Attaching the relevant files.
DISM failed.

I can see 1 corruption
2022-07-07 00:28:24, Info CBS (p) CSI Manifest Corrupt amd64_microsoft-windows-p..21h2-ekb-deployment_31bf3856ad364e35_10.0.19041.1706_none_734f7838b4cff7f7

 C:\WINDOWS\system32> DISM /online /cleanup-image /RestoreHealth
>>

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1766

[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

 

[Maxstar]

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFix.zip and save it to your desktop.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

 

[xerion]

The DISM failed after the SFCFIX

I see this in the CBS but I've no idea what that is
STATUS_OBJECT_NAME_NOT_FOUND #440635#

DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1766

[=======================    41.1%                          ]
Error: 2

The system cannot find the file specified.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

 

[Maxstar]

2022-07-07 23:31:01, Error                 CSI    00000008 (F) STATUS_OBJECT_NAME_NOT_FOUND #440635# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0xd5baf7ade8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[216]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1737 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-p..21h2-ekb-deployment_31bf3856ad364e35_none_a8bbac9acf46c295\v!10.0.19041.[gle=0xd0000034]
2022-07-07 23:31:01, Error                 CSI    1706'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 3136793472)[gle=0xd0000034]
2022-07-07 23:31:01, Error                 CSI    00000009@2022/7/8:06:31:01.220 (F) onecore\base\wcp\sil\ntsystem.cpp(5363): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
[gle=0x80004005]
2022-07-07 23:31:01, Error                 CSI    0000000a (F) STATUS_OBJECT_NAME_NOT_FOUND #440634# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0xd5baf7ade8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[216]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1737 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-p..21h2-ekb-deployment_31bf3856ad364e35_none_a8bbac9acf46c295\v!10.0.19041.1706'; a:(OBJ_CASE[gle=0xd0000034]
2022-07-07 23:31:01, Error                 CSI    _INSENSITIVE)}, disp = Unmapped disposition: 3136794496)[gle=0xd0000034]
2022-07-07 23:31:01, Error                 CSI    0000000b (F) STATUS_OBJECT_NAME_NOT_FOUND #440633# from Windows::Rtl::SystemImplementation::CBufferedRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_ALL_ACCESS), oa = @0xd5baf7b4a8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[216]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1737 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-p..21h2-ekb-deployment_31bf3856ad364e35_none_a8bbac9acf46c295\v!10.0.19041.1706'; a:(OBJ_CASE_INSENS[gle=0xd0000034]
2022-07-07 23:31:01, Error                 CSI    ITIVE)}, disp = Unmapped disposition: 3136795892)[gle=0xd0000034]

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFixScript.txt and save it to your desktop.
• Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

 

[xerion]

That did it.
DISM completed successfully and then I was able to perform the update to 21H2 without any issues.

Thank you for your support during this process. It is greatly appreciated.
It does make me wonder though if there is anything that I could do to avoid having such issues, or it just something that happens on some occasions.

 

[Maxstar]

You're welcome. Glad to hear that the feature update 21H2 is succesfully installed..
I'll mark this thread as solved!

There are several reasons for this kind of corruptions, like:
- Third-party cleaning tools such as registry cleaners and/or doubtful optimizing tools.
- Power and system failures during the Windows Update process.
- Hardware issues such as a malfunctioning harddrive or memory corruptions.

The best way to avoid such issues is to make regular backups.