[SOLVED] Another Windows Server 2022 update failure (0x800f081f)

philg · Aug 19, 2024

Hi, Ive seen several such posts here already but the sfcfix scripts seem to be "for this system only", so here is my problem and log files...
I have a fairly new install of Server Std 2022 21H2 20348.2461, which has failed to install the monthly CU's for the last 2 months (July and August) server was only commissioned 3 months or so ago.

I tried installing the KB full patch from the catalogue and that failed too (much the same as other posts I have seen here recently).

I tried the:
sfc /scannow --> Windows Resource Protection did not find any integrity violations.
Dism /Online /Cleanup-Image /RestoreHealth --> The restore operation completed successfully. (nothing obvious found)

ComponentScanner gave me this: No corruptions were detected, but 5 warnings were found in the COMPONENTS hive. and the log is attached,

The CBS folder was too big (zipped) to attach here, so I have shared it here: CBS.zip
Worst case I can rebuild the server but it is in production so I'd rather not if that can be avoided.

Regards,
Phil

philg · Aug 29, 2024

bump - anyone?
Have I missed something from the required info?

Maxstar · Sep 2, 2024

Hi and welcome to Sysnative,

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.

philg · Sep 2, 2024

Hi Maxstar,

Attached is the components hive file.

Regards,
Phil

Maxstar · Sep 2, 2024

Hi,

Here's the first fix.

Step 1. Download

SFCFix and save it to your desktop.

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. Reboot the server and run

ComponentsScanner again.

Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
Follow the on-screen instructions.
Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
Post the logfile ComponentsScanner.txt as attachment into your next reply.

philg · Sep 2, 2024

OK Thanks, I have run the above. Attached are the new SFCFix.txt and ComponentsScanner.txt.

....
Found 1 inconsistencies between WinSxS and COMPONENTS hive
Checking for malformed Deployment keys
Checking CatalogThumbprints & c! marks
1 warnings detected
Generating report

Should I try windows update again at this stage or is there more to do first?

Regards,
Phil

Maxstar · Sep 2, 2024

Please run run the following DISM command first and post the result. If it fails with error 2 attach a new copy of the CBS logs.

Code:

DISM /online /cleanup-image /RestoreHealth

philg · Sep 2, 2024

Yes, DISM failed with error 2.
See attached...

Maxstar · Sep 2, 2024

Here's the next fix.

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.

Code:

DISM /online /cleanup-image /RestoreHealth

philg · Sep 2, 2024

OK, attached the files, DISM still failed with error 2, but got to 50% this time (was only 24% last time)

Maxstar · Sep 2, 2024

Here's the next fix.

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.

Code:

DISM /online /cleanup-image /RestoreHealth

philg · Sep 2, 2024

Thanks, unfortunately, exactly the same (DISM failed again at 50.4%)
Here are the logs...

Maxstar · Sep 2, 2024

Here's the next fix, and we need to replace a number of components as it seems.

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.

Code:

DISM /online /cleanup-image /RestoreHealth

philg · Sep 2, 2024

Yes, I don't understand how a fairly fresh install has got so badly messed up, although maybe previous attempts to fix it made it worse...
Some progress.... DISM got passed 50.4% this time... It got to 100%$ but then failed...

[==========================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.
...

Maxstar · Sep 2, 2024

This is a common issue with Server 2022, and actually some kind of bug, at least the latest fixes have not made the problem more worse.

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.

Code:

DISM /online /cleanup-image /RestoreHealth

philg · Sep 2, 2024

OK DISM seems to have succeeded this time...
Now should I try windows update?

Maxstar · Sep 2, 2024

Yes, please attempt to update and post the result. If it fails attach a new copy of the CBS logs.

philg · Sep 2, 2024

I got all excited when I saw in the GUI it got to 100% Installing... But then it still failed with error 0x0800f081f

CBS logs attached...

Maxstar · Sep 2, 2024

It looks like this server was installed with an evaluation version and partial installed language packs!

Open an elevated command prompt and run the following commands. Copy paste the result in your next post.

Code:

dir /s /a %systemroot%\WinSxS\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_ja-jp_a51e8f77a7577270
certutil -hashfile %systemroot%\WinSxS\Manifests\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_ja-jp_a51e8f77a7577270.manifest SHA256

philg · Sep 2, 2024

Interesting... This is a new (in April/May) Dell server, which came preinstalled (to me at least) and activated with the key form the dell portal. I believe I sucessfully updated it when we first got hold of it (but its possible it failed from the outset). It says it is activated etc. when I check in Windows, but almost certainly activation and key entry was done post imaging from Dell.
Its the first time I have had a new Dell box in years, so I just assumed when I got it (from our interim supplier) that all was good - perhaps that was my mistake!!
Maybe the best option is to start again form fresh with the master image! I will have words with our supplier (who in turn no doubt will have words with Dell).

That's a bit of a PITA as its been installed in a DC and whilst I have full access over IPMI its live and I cant really take if offline just like that - will have to plan it all.
Thanks for your help, and I understand if there is no more that can be achieved here.

Anyway here is the results of the Dir/Certutil... Seems like there are no files in that folder...
Not sure if you meant to include >dirlist.txt in that command?

C:\Windows\system32>dir /s /a %systemroot%\WinSxS\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_ja-jp_a51e8f77a7577270
Volume in drive C is OS
Volume Serial Number is 284A-63B4

Directory of C:\Windows\WinSxS\Temp\InFlight\b378476bc0aada016d1500008c156c27

20/05/2024 15:22 <DIR> amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_ja-jp_a51e8f77a7577270
0 File(s) 0 bytes

Total Files Listed:
0 File(s) 0 bytes
1 Dir(s) 163,734,241,280 bytes free

C:\Windows\system32>
C:\Windows\system32>certutil -hashfile %systemroot%\WinSxS\Manifests\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_ja-jp_a51e8f77a7577270.manifest SHA256
CertUtil: -hashfile command FAILED: 0x80070002 (WIN32: 2 ERROR_FILE_NOT_FOUND)
CertUtil: The system cannot find the file specified.

[SOLVED] Another Windows Server 2022 update failure (0x800f081f)

Member

Attachments

Member

Windows Update Moderator, Security Analyst

Member

Attachments

Windows Update Moderator, Security Analyst

Attachments

Member

Attachments

Windows Update Moderator, Security Analyst

Member

Attachments

Windows Update Moderator, Security Analyst

Attachments

Member

Attachments

Windows Update Moderator, Security Analyst

Attachments

Member

Attachments

Windows Update Moderator, Security Analyst

Attachments

Member

Attachments

Windows Update Moderator, Security Analyst

Attachments

Member

Attachments

Windows Update Moderator, Security Analyst

Member

Attachments

Windows Update Moderator, Security Analyst

Member