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

[Maxstar]

Dell server, which came preinstalled (to me at least)

Yes, and this could be the issue with preinstalled environments!

Please run the following command in an elevated prompt.

DISM /online /get-intl > "%USERPROFILE%\desktop\DISM-lang.txt"

It should show the same output as below I think?!

Deployment Image Servicing and Management tool
Version: 10.0.20348.681

Image Version: 10.0.20348.2527

Reporting online international settings.

Default system UI language : en-US
System locale : en-US
Default time zone : Pacific Standard Time
Active keyboard(s) : 0409:00000409
Keyboard layered driver : PC/AT Enhanced Keyboard (101/102-Key)

Installed language(s): de-DE
  Type : Partially localized language, MUI type.
  Fallback Languages en-US
Installed language(s): en-US
  Type : Fully localized language.
Installed language(s): es-ES
  Type : Partially localized language, MUI type.
  Fallback Languages en-US
Installed language(s): fr-FR
  Type : Partially localized language, MUI type.
  Fallback Languages en-US
Installed language(s): it-IT
  Type : Partially localized language, MUI type.
  Fallback Languages en-US
Installed language(s): ja-JP
  Type : Partially localized language, MUI type.
  Fallback Languages en-US
Installed language(s): ko-KR
  Type : Partially localized language, MUI type.
  Fallback Languages en-US
Installed language(s): nl-NL
  Type : Partially localized language, MUI type.
  Fallback Languages en-US
Installed language(s): pl-PL
  Type : Partially localized language, MUI type.
  Fallback Languages en-US
Installed language(s): pt-PT
  Type : Partially localized language, MUI type.
  Fallback Languages en-US

The operation completed successfully.

 

[Maxstar]

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!!

When I have to set up or build a new server, I always use the latest MSDN ISO to reinstall the server:
1. Installation from scratch + snapshot / image.
2. First update attempt to bring it up to the latest build + snapshot.
3. Configuring the server.. etc...

 

[philg]

When I have to set up or build a new server, I always use the latest MSDN ISO to reinstall the server:
1. Installation from scratch + snapshot / image.
2. First update attempt to bring it up to the latest build + snapshot.
3. Configuring the server.. etc...

Yes, so do I usually... Well I tend to use our partner pack image these days, if not, my MSDN (visualstudio is it is now known). But seeing as we purchased this new server from Dell and had it configured by our DC hosting partner, its was more "out of my hands" - I could have reinstalled it but I didn't think it was that important... Little did I know.
And doing all remotely over IPMI now the box is in use is going to be a pain but maybe worth it. Not sure the license key from Dell will work with the MSDN ISO these days though (and as it was purchased as is, I don't want to be using an MSDN license in production really if we can avoid it)

Anyway, attached is the output from above. Sorry for the delay, I left the office and realized I had more to do!!
I wonder if the problem was caused by switching it to English (UK) as maybe it came setup as EN-US.
Maybe I can remove those partial language packs - clutter I will never need (and I can switch it back to EN (US) if need be too, at least temporarily if that will make any difference).

Regards,
Phil

 

[Maxstar]

Hi,

1. Yes, you can use the MSDN ISO also with OEM licenses, just enter that key during the installation process.
2. Switching back to EN-GB is not the issue.

(...) Maybe I can remove those partial language packs.

3. Unfortunately, that doesn't work!
4. Spanish (es-ES), French (fr-FR), Italian (it-IT), Japanese (ja-JP), Korean (ko-KR), Polish (pl-PL).
5. You'll need to install them first, and after a reboot it should be possible to remove them completely without any (leftovers) orphaned entry's in the registry.
6. Then I would run the following commands:

DISM /online /cleanup-image /RestoreHealth
DISM /online /cleanup-image /AnalyzeComponentStore

 

[philg]

OK I have successfully (I think) installed then removed the language packs.
DISM now reports just two languages en-us and en-gb (which I want to keep as that's our locale).

And it does not error when running either:
DISM /online /cleanup-image /RestoreHealth
DISM /online /cleanup-image /AnalyzeComponentStore

I tried running the offline installer for KB5041160 and that still failed, so I tried Windows Update again, and it seems that this one has got further 44% (which I don't think I have seen it get to before) but then hung there for ages...

It still failed, again with 0x800f081f, but after much more time, so maybe that's progress!
In the hopes that maybe it is now recoverable, I have attached a new set of files CBS log (I removed the archived logs to save space as that was from yesterday), Components hive and DSIM log file.

Thanks,
Phil

 

[Maxstar]

2024-09-03 14:42:26, Error                 CSI    0000054a (F) STATUS_OBJECT_NAME_NOT_FOUND #686210733# from Windows::Rtl::SystemImplementation::CSystemIsolationLayer_IRtlSystemIsolationLayerTearoff::TransferFileEx(flags = (OpenForBackupIntent), op = 'Move', odir = NULL, oname = [l:181]'\??\C:\Windows\CbsTemp\31129086_3408131640\Windows10.0-KB5041160-x64.cab\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_10.0.20348.1_en-us_3000303467a3ad4d.manifest', ndir = @0x19816266de0, nname = [l:41 ml:63]'d9e1ea1c07feda0186730000c40fdc27_manifest', d[gle=0xd0000034]
2024-09-03 14:42:26, Error                 CSI    isp = Unmapped disposition: 0)
[gle=0xd0000034]

Great, but please upload a new copy of the COMPONENTS hive since a lot of things have been changed. And yes we are definitely making progress now!

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]

Sorry, missed that one!

 

[Maxstar]

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

Afterwards attempt tot update again and post the result including the latest CBS logs.

 

[philg]

Still failed but quicker this time...

EDIT: Sorry forgot the sfcfix.txt

 

[Maxstar]

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

Afterwards attempt tot update again and post the result including the latest CBS logs.

 

[philg]

OK this is getting a bit repetitive.
Thanks for your efforts so far, I'm willing to keep trying if you are (but this will be my last post today!)
I understand completely if you have had enough!

If I knew one more fix would fix it then great but I have a fear that this could drag on and on, and really, reinstalling Windows might be the best option (especially going forward to prevent any re-occurrence).

Incidentally, if we decide this is a endless loop of different fixes, do you think the best option is to wipe the drive and reinstall from scratch (or maybe just a repair using the most up to date MSDN ISO AUG 2024 as it stands)?

 

[Maxstar]

Windows Update problems are often complex to deal with like such cases, but here is the following fix!

If I knew one more fix would fix it then great but I have a fear that this could drag on and on....

No, but this is a common issue as mentioned in post #15, so please be patient!

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.

Afterwards attempt tot update again and post the result including the latest CBS logs.

 

[philg]

OK I have patience if you do
Here is the latest update...
This time it failed with a different error: 0x800f0982!

 

[Maxstar]

Hi,

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

Afterwards attempt tot update again and post the result including the latest CBS logs.

 

[philg]

OK another 0x800f0982 I'm afraid.
More language pack issues?

 

[Maxstar]

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

Afterwards attempt tot update again and post the result including the latest CBS logs.

 

[philg]

Got to 100% quickly but still failed (0x800f0982)

 

[Maxstar]

And 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 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.

Afterwards attempt tot update again and post the result including the latest CBS logs.

 

[philg]

Oh wow... I think it just succeed...
2024-08 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5041160)
Status: Pending restart
Rebooting to confirm, but its looking promising!

 

[Maxstar]

Great let me know the result...