Windows 11 Pro, WU 0x800f0983, sfc errors

R4to0 · May 1, 2025

Fails at 19%.

Maxstar · May 2, 2025

Here's the next fix.

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.

Code:

DISM /online /cleanup-image /RestoreHealth

R4to0 · May 3, 2025

Fails at 20% now.

Maxstar · May 4, 2025

Here's the next fix.

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.

Code:

DISM /online /cleanup-image /RestoreHealth

R4to0 · May 4, 2025

Failing at 20.6%.

Maxstar · May 4, 2025

Here's the next fix.

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.

Code:

DISM /online /cleanup-image /RestoreHealth

R4to0 · May 4, 2025

Fails at 20.6%

Maxstar · May 5, 2025

I think it might be better to perform a repair install (in-place-upgrade), manually repairing all the corruptions will take forever if it will succeed at all.

R4to0 · May 6, 2025

I agree, this seems to be a endless loop as it never ends. I'm still asking myself how it did happened as I'm very cautious when updating Windows, avoiding sudden shutdowns, etc.

Luckily a fiber company finally came in my area and installed for me, so I'm not constrained on a 4G connection anymore as I stated in first post. I'll go ahead and do a clean install once I have time to do so. I may try to follow/replicate what you were doing before reinstalling, by recreating these registry keys although I don't know which DWORD values to use there, some were 40 and others 46 based on your fixes.

Again, thank you for your time and patience on writing these fixes one by one, it must be very annoying when such things happens and looks like it never ends.

Maxstar · May 7, 2025

It's very difficult to ascertain what the exact cause was, but please try to install the Hyper-V component again and post the latest CBS logs when it failed with error 0x80073701.

R4to0 · May 7, 2025

Attempting to install or uninstall a Hyper-V component gave me error 0x800736b3, then trying again gave me error 0x80073708.

Since this system is getting beyond repair and has to be reinstalled, I wouldn't mind if it gets even more broken. I tried to work on these fixes in the same way you did for me as they appear. Once I patched these:

Code:

DerivedData\VersionedIndex\10.0.26100.3764 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-hyper-v-o..p-merged-deployment_31bf3856ad364e35_none_42e777e65eec9ae8\v!10.0.26100.1591
DerivedData\VersionedIndex\10.0.26100.3764 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-hyper-v-o..s-merged-deployment_31bf3856ad364e35_none_481f3160172fabe1\v!10.0.26100.1882
DerivedData\VersionedIndex\10.0.26100.3764 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-hyper-v-sysprep-provider_31bf3856ad364e35_none_097c7f6b9ceaaaac\v!10.0.26100.1150
DerivedData\VersionedIndex\10.0.26100.3764 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-hyper-v-o..p-merged-deployment_31bf3856ad364e35_none_42e777e65eec9ae8\v!10.0.26100.2894
DerivedData\VersionedIndex\10.0.26100.3764 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-hyper-v-p..e-merged-deployment_31bf3856ad364e35_none_f4f7561008165ef7\v!10.0.26100.2894

progress bumped from 20% to 51%! Then three more:

Code:

DerivedData\VersionedIndex\10.0.26100.3764 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-hyper-v-winhv_31bf3856ad364e35_none_ccaafd226086672a\v!10.0.26100.1591
DerivedData\VersionedIndex\10.0.26100.3764 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-hyper-v-winhvr_31bf3856ad364e35_none_d9499343cd9885fa\v!10.0.26100.1591
DerivedData\VersionedIndex\10.0.26100.3764 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-hyper-v-winhvr_31bf3856ad364e35_none_d9499343cd9885fa\v!10.0.26100.2454

and DISM started taking a looong time to finish, making downloads in background from WU servers. In the end it reached 100% with the classic error code "0x800f081f" and message "The source files could not be found.". Consecutive retries were the same. I've also tried specifying a path to the source file from ISO image with no luck.

Code:

dism /online /cleanup-image /RestoreHealth /Source:WIM:I:\sources\install.wim:6

I did not tried to install updates for Windows this time, I remember these were failing as well last time I tried.

Attached CBS logs, one for dism command and other for attempting to remove a Hyper-V component.

Maxstar · May 8, 2025

Great, here's the next fix for the missing files.

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

R4to0 · May 8, 2025

DISM succeeded this time, even after multiple calls!

Code:

PS C:\Users\rmaci> dism /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.26100.1150

Image Version: 10.0.26100.3476

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

SFC also found corrupted files and repaired them. Consecutive calls also did not reported anything corrupt.

Code:

PS C:\Users\rmaci> sfc /scannow

Beginning system scan.  This process will take some time.

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

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.
PS C:\Users\rmaci> 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.

Unfortunately removing "Hyper-V Services" component results in error 0x80070308. Don't know if there's anything that can be done at this stage.

R4to0 · May 8, 2025

Additionally, installing KB5055627 through Windows Update gave me Install error 0x800f0991.

Maxstar · May 9, 2025

Rich (BB code):

2025-05-08 15:58:21, Info                  CSI    0000036c Over-removing a TLC, s/b internal error Microsoft-Hyper-V-PVHD-Parser, version 10.0.26100.1150, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2025-05-08 15:58:21, Error                 CSI    0000036d@2025/5/8:18:58:21.476 (F) onecore\base\wcp\componentstore\analysis.cpp(1259): Error STATUS_REQUEST_OUT_OF_SEQUENCE originated in function CServicingFamilyEntries::RemoveInstalledTlc expression: (null)
[gle=0x80004005]

Let's take a look at the previous error first.

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.

R4to0 · May 9, 2025

Attached.

Maxstar · May 10, 2025

Hi,

Open an elevated command prompt and run the following commands. Attach Dirlist.txt to your next post.

Code:

dir /s /a %systemroot%\WinSxS\amd64_microsoft-hyper-v-pvhd-parser_31bf3856ad364e35_10.0.26100.1_none_866e05b742d98e73 > "%userprofile%\Desktop\Dirlist.txt"
dir /s /a %systemroot%\WinSxS\amd64_microsoft-hyper-v-pvhd-parser_31bf3856ad364e35_10.0.26100.1150_none_2561adcd8a36dc71 >> "%userprofile%\Desktop\Dirlist.txt"

R4to0 · May 10, 2025

Maxstar said:
Hi,

Open an elevated command prompt and run the following commands. Attach Dirlist.txt to your next post.

Code:

dir /s /a %systemroot%\WinSxS\amd64_microsoft-hyper-v-pvhd-parser_31bf3856ad364e35_10.0.26100.1_none_866e05b742d98e73 > "%userprofile%\Desktop\Dirlist.txt" dir /s /a %systemroot%\WinSxS\amd64_microsoft-hyper-v-pvhd-parser_31bf3856ad364e35_10.0.26100.1150_none_2561adcd8a36dc71 >> "%userprofile%\Desktop\Dirlist.txt"

None of these paths exists.

Code:

Microsoft Windows [Version 10.0.26100.3476]
(c) Microsoft Corporation. All rights reserved.

C:\Users\rmaci>dir /s /a %systemroot%\WinSxS\amd64_microsoft-hyper-v-pvhd-parser_31bf3856ad364e35_10.0.26100.1_none_866e05b742d98e73 > "%userprofile%\Desktop\Dirlist.txt"
The system cannot find the path specified.

C:\Users\rmaci>dir /s /a %systemroot%\WinSxS\amd64_microsoft-hyper-v-pvhd-parser_31bf3856ad364e35_10.0.26100.1150_none_2561adcd8a36dc71 >> "%userprofile%\Desktop\Dirlist.txt"
The system cannot find the path specified.

C:\Users\rmaci>

Maxstar · May 10, 2025

Hmm, that's odd! I've just installed a new VM today but it does not contain the RTM (26100.1) component. I have also installed a custom build from UUP but the RTM component were missing as well! So please run the following tool first to see if it will report all the broken components keys, however, I don't think it will succeed completely since the payloads are missing. But let's see!

Download

ComponentsScanner and save it to your desktop.

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.

R4to0 · May 10, 2025

Attached.

Windows 11 Pro, WU 0x800f0983, sfc errors

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Member

Moderator, Windows Update Expert, Security Analyst

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Member

Attachments

Member

Moderator, Windows Update Expert, Security Analyst

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Member

Moderator, Windows Update Expert, Security Analyst

Member

Attachments