Perhaps this is related to the update itself having some issues (it seems people are reporting instability with it).
I tried windows update troubleshooter but it fails to run "The Windows Update diagnostic failed to run".
I tried disabling and re-enabling .net windows features.
I tried sfc /scannow and DISM restorehealth, but restoring fails "Error: 0x800f081f The source files could not be found.", I then tried downloading an iso image from microsoft, picking the correct index for pro version as source with install.wim and still got the same error.
I tried resetting windows update components (following their official instructions, I don't think I can link it because of the spam filter though).
Finally, following the instructions for this post:
Note: I restarted after running the commands to be able to zip the CBS folder, since the cbs.log file was still in use by TiWorker.
I tried windows update troubleshooter but it fails to run "The Windows Update diagnostic failed to run".
I tried disabling and re-enabling .net windows features.
I tried sfc /scannow and DISM restorehealth, but restoring fails "Error: 0x800f081f The source files could not be found.", I then tried downloading an iso image from microsoft, picking the correct index for pro version as source with install.wim and still got the same error.
I tried resetting windows update components (following their official instructions, I don't think I can link it because of the spam filter though).
Finally, following the instructions for this post:
Code:
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.
Code:
C:\Windows\System32>Dism /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 10.0.26100.1
Image Version: 10.0.26100.1
[==========================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
Code:
Loading registry hive from C:\WINDOWS\System32\config\COMPONENTS
Hive is currently in use, making backup copy
Parsing loaded hive, please wait...
Sequence numbers do not match! Hive is dirty and the transaction logs should be reviewed for relevant data!
hbin header incorrect at absolute offset 0x3650000!!! Percent done: 99.66%
Hive parsed successfully - found 91,557 keys and 271,672 values
Starting corruption scan
Sequence mismatch! Primary = 6269. Secondary = 6268
Scanning CanonicalData\Catalog for corruptions
Scanning CanonicalData\Deployments for corruptions
Scanning DerivedData\Components for corruptions
Scanning VersionedIndex\...\ComponentFamilies for corruptions
Checking WinSxS catalogs against CanonicalData\Catalogs
Checking WinSxS components against DerivedData\Components
Checking f! marks
Checking manifests
Checking for malformed Deployment keys
Checking CatalogThumbprints & c! marks
Generating report
Archiving previous report C:\Users\host\Desktop\ComponentsScanner.txt to C:\Users\host\AppData\Local\Sysnative\ComponentsScanner\Reports\ComponentsScanner_03_16_2025_04_23_34.txt
The corruption scan completed after 28.28 seconds.
No corruptions were detected in the COMPONENTS hive.
Please note this tool is only able to detect certain corruptions and there may be problems that it is unable to find.
If you are experiencing issues with Windows Update or require further support, please visit Sysnative.com for
free advice.Note: I restarted after running the commands to be able to zip the CBS folder, since the cbs.log file was still in use by TiWorker.
