[SOLVED] Server 2022 - Windows Update Failing KB5027225 - 0x800f081f

[algiz]

unsuccessful.
CBS logs attached.

 

[Gary R]

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attachment SFCFixScript.txt and also save it on your desktop.
• Save any work you have open, and close all programs.
• 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
• Open the file, then copy and paste its content in your next reply.

Next ...

• Click Search button and type Command Prompt
• From the results, right click on the Command Prompt icon, and select Run as administrator
• A Command Window will open.
• Copy paste the command below into it, then press Enter
• Dism /Online /Cleanup-Image /RestoreHealth
• Once DISM has finished running ...
  • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
• If the file is too large, upload it to a file sharing service, and post me the link.
• Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

 

[algiz]

Dism & SFCFix successful.

SFCFix version 3.0.2.1 by niemiro.
Start time: 2023-07-21 16:34:51.673
Microsoft Windows Server 10 Build 20348 - amd64
Using .zip script file at C:\Users\OPDVGHTC\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS
Successfully took permissions for file or folder C:\Windows\WinSxS\Manifests

Successfully created directory tree \\?\C:\Windows\WinSxS\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_zh-tw_d9d0ef04cea42992.
Successfully created directory tree \\?\C:\Windows\WinSxS\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_10.0.20348.1_zh-tw_9382d7f84c3663cf.

Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_zh-tw_d9d0ef04cea42992\Microsoft.Windows.Networking.SlbMuxEvents.resources.dll to C:\Windows\WinSxS\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_zh-tw_d9d0ef04cea42992\Microsoft.Windows.Networking.SlbMuxEvents.resources.dll.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_zh-tw_d9d0ef04cea42992\SlbMuxRes.dll.mui to C:\Windows\WinSxS\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_zh-tw_d9d0ef04cea42992\SlbMuxRes.dll.mui.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_10.0.20348.1_zh-tw_9382d7f84c3663cf\SlbMuxPerfCounters.dll.mui to C:\Windows\WinSxS\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_10.0.20348.1_zh-tw_9382d7f84c3663cf\SlbMuxPerfCounters.dll.mui.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\Manifests\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_10.0.20348.1_zh-tw_9382d7f84c3663cf.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_10.0.20348.1_zh-tw_9382d7f84c3663cf.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\Manifests\amd64_microsoft-windows-slb-mux-deployment_31bf3856ad364e35_10.0.20348.1547_none_68ce0f932e0be5a5.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-slb-mux-deployment_31bf3856ad364e35_10.0.20348.1547_none_68ce0f932e0be5a5.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\Manifests\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_zh-tw_d9d0ef04cea42992.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_zh-tw_d9d0ef04cea42992.manifest.

Successfully restored ownership for C:\Windows\WinSxS
Successfully restored permissions on C:\Windows\WinSxS
Successfully restored ownership for C:\Windows\WinSxS\Manifests
Successfully restored permissions on C:\Windows\WinSxS\Manifests
PowerCopy:: directive completed successfully.




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_zh-tw_2c200ceca431863a.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_zh-tw_604d8d61b22553cf.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_10.0.20348.1_zh-tw_9382d7f84c3663cf.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft-w..anguagepack_31bf3856ad364e35_10.0.20348.1_4dbd2488da3b551d.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft-w..anguagepack_31bf3856ad364e35_10.0.20348.946_ace64bae9b42a4a1.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_zh-tw_2c200ceca431863a.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_zh-tw_2c200ceca431863a\v!10.0.20348.1.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_zh-tw_d9d0ef04cea42992.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_zh-tw_604d8d61b22553cf.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_zh-tw_604d8d61b22553cf\v!10.0.20348.1.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_10.0.20348.1_zh-tw_9382d7f84c3663cf.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft-w..anguagepack_31bf3856ad364e35_10.0.20348.1_4dbd2488da3b551d.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft-w..anguagepack_31bf3856ad364e35_10.0.20348.946_ace64bae9b42a4a1.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_zh-tw_2c200ceca431863a.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_zh-tw_2c200ceca431863a\v!10.0.20348.1.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_zh-tw_2c200ceca431863a.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_zh-tw_d9d0ef04cea42992.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_zh-tw_604d8d61b22553cf.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_zh-tw_604d8d61b22553cf\v!10.0.20348.1.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_zh-tw_604d8d61b22553cf.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 18 datablocks.
Finish time: 2023-07-21 16:35:13.856
Script hash: JQikxjn8VY7P4QWWvi/OiuAABUlF9lgS8Kg6CQgjz4c=
----------------------EOF-----------------------

 

[Gary R]

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attachment SFCFixScript.txt and also save it on your desktop.
• Save any work you have open, and close all programs.
• 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
• Open the file, then copy and paste its content in your next reply.

Next ...

• Click Search button and type Command Prompt
• From the results, right click on the Command Prompt icon, and select Run as administrator
• A Command Window will open.
• Copy paste the command below into it, then press Enter
• Dism /Online /Cleanup-Image /RestoreHealth
• Once DISM has finished running ...
  • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
• If the file is too large, upload it to a file sharing service, and post me the link.
• Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

 

[algiz]

successful.

SFCFix version 3.0.2.1 by niemiro.
Start time: 2023-07-21 21:14:18.224
Microsoft Windows Server 10 Build 20348 - amd64
Using .zip script file at C:\Users\OPDVGHTC\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\Manifests

Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..oyment-languagepack_31bf3856ad364e35_10.0.20348.1_zh-tw_4dbd2488da3b551d.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..oyment-languagepack_31bf3856ad364e35_10.0.20348.1_zh-tw_4dbd2488da3b551d.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..oyment-languagepack_31bf3856ad364e35_10.0.20348.946_zh-tw_ace64bae9b42a4a1.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..oyment-languagepack_31bf3856ad364e35_10.0.20348.946_zh-tw_ace64bae9b42a4a1.manifest.

Successfully restored ownership for C:\Windows\WinSxS\Manifests
Successfully restored permissions on C:\Windows\WinSxS\Manifests
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 18 datablocks.
Finish time: 2023-07-21 21:14:33.143
Script hash: i3t75EwmKfX2VILlnhYR9nf6hBhkPKGzXuKOCdZkIPU=
----------------------EOF-----------------------

 

[Gary R]

Latest log looks error free, please try updating again.

If successful please let me know.

If not, please post your latest CBS.log

 

[algiz]

update not successful.
CBS logs attached.

 

[Gary R]

Going to be out for next couple of hours, will look over your latest log as soon as I get back.

 

[Gary R]

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attachment SFCFixScript.txt and also save it on your desktop.
• Save any work you have open, and close all programs.
• 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
• Open the file, then copy and paste its content in your next reply.

Next ...

• Click Search button and type Command Prompt
• From the results, right click on the Command Prompt icon, and select Run as administrator
• A Command Window will open.
• Copy paste the command below into it, then press Enter
• Dism /Online /Cleanup-Image /RestoreHealth
• Once DISM has finished running ...
  • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
• If the file is too large, upload it to a file sharing service, and post me the link.
• Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

 

[algiz]

SFCFix & Dism successful.

SFCFix version 3.0.2.1 by niemiro.
Start time: 2023-07-22 23:14:38.898
Microsoft Windows Server 10 Build 20348 - amd64
Using .zip script file at C:\Users\OPDVGHTC\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS
Successfully took permissions for file or folder C:\Windows\WinSxS\Manifests

Successfully created directory tree \\?\C:\Windows\WinSxS\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_en-us_764e4740ea117310.
Successfully created directory tree \\?\C:\Windows\WinSxS\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_10.0.20348.1_en-us_3000303467a3ad4d.

Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_en-us_764e4740ea117310\Microsoft.Windows.Networking.SlbMuxEvents.resources.dll to C:\Windows\WinSxS\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_en-us_764e4740ea117310\Microsoft.Windows.Networking.SlbMuxEvents.resources.dll.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_en-us_764e4740ea117310\SlbMuxRes.dll.mui to C:\Windows\WinSxS\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_en-us_764e4740ea117310\SlbMuxRes.dll.mui.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_10.0.20348.1_en-us_3000303467a3ad4d\SlbMuxPerfCounters.dll.mui to C:\Windows\WinSxS\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_10.0.20348.1_en-us_3000303467a3ad4d\SlbMuxPerfCounters.dll.mui.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\Manifests\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_10.0.20348.1_en-us_3000303467a3ad4d.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_10.0.20348.1_en-us_3000303467a3ad4d.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\Manifests\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_en-us_764e4740ea117310.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_en-us_764e4740ea117310.manifest.

Successfully restored ownership for C:\Windows\WinSxS
Successfully restored permissions on C:\Windows\WinSxS
Successfully restored ownership for C:\Windows\WinSxS\Manifests
Successfully restored permissions on C:\Windows\WinSxS\Manifests
PowerCopy:: directive completed successfully.




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_en-us_728dd8382f5e452c.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_en-us_a6bb58ad3d5212c1.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_10.0.20348.1_en-us_3000303467a3ad4d.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft-w..anguagepack_31bf3856ad364e35_10.0.20348.946_4963a3eab6afee1f.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_en-us_728dd8382f5e452c.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_en-us_728dd8382f5e452c\v!10.0.20348.1.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_en-us_764e4740ea117310.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_en-us_a6bb58ad3d5212c1.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_en-us_a6bb58ad3d5212c1\v!10.0.20348.1.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_10.0.20348.1_en-us_3000303467a3ad4d.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft-w..anguagepack_31bf3856ad364e35_10.0.20348.946_4963a3eab6afee1f.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_en-us_728dd8382f5e452c.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_en-us_728dd8382f5e452c\v!10.0.20348.1.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_en-us_728dd8382f5e452c.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_en-us_764e4740ea117310.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_en-us_a6bb58ad3d5212c1.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_en-us_a6bb58ad3d5212c1\v!10.0.20348.1.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_en-us_a6bb58ad3d5212c1.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 25 datablocks.
Finish time: 2023-07-22 23:15:00.258
Script hash: AN4CA9Cmfyad+e5J0+rkxmfcRl04mT2Vt882kQ/xAU4=
----------------------EOF-----------------------

 

[Gary R]

Looking over your log now.

One new item to fix, but some items being flagged that I thought we'd already fixed. Will have to look closer at why they're still showing as errors. May have to consult, which means it may be some time before I get back to you.

In the meantime, since we've made quite a few changes, can you please post me a new copy of 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.
• The file will likely be too large to upload here, if so please upload to a file sharing service.
• Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Please post me the link to the file

 

[algiz]

Thank you for your help.
Components attached

 

[Gary R]

Thanks. Got a few things to check that are new for me, so may take a while, I'll get back to you as soon as I can.

 

[Gary R]

Sorry for the long wait, because of the nature of your problem there are a number of complications that we're trying to feel our way through, so I'm looking to deal with things one step at a time.

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attachment SFCFixScript.txt and also save it on your desktop.
• Save any work you have open, and close all programs.
• 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
• Open the file, then copy and paste its content in your next reply.

Next ...

• Click Search button and type Command Prompt
• From the results, right click on the Command Prompt icon, and select Run as administrator
• A Command Window will open.
• Copy paste the command below into it, then press Enter
• Dism /Online /Cleanup-Image /RestoreHealth
• Once DISM has finished running ...
  • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
• If the file is too large, upload it to a file sharing service, and post me the link.
• Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

 

[algiz]

I appreciate your help.

Let me know if there's anything else I can do.

this time. SFCFixScript successful.

but Dism Error

SFCFix version 3.0.2.1 by niemiro.
Start time: 2023-07-25 08:26:17.689
Microsoft Windows Server 10 Build 20348 - amd64
Using .txt script file at C:\Users\OPDVGHTC\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-slb-mux-deployment_31bf3856ad364e35_10.0.20348.1547_none_68ce0f932e0be5a5.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux-deployment_31bf3856ad364e35_none_3df94ea2cfaf0d72.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux-deployment_31bf3856ad364e35_none_3df94ea2cfaf0d72.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-slb-mux-deployment_31bf3856ad364e35_10.0.20348.1547_none_68ce0f932e0be5a5.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux-deployment_31bf3856ad364e35_none_3df94ea2cfaf0d72.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux-deployment_31bf3856ad364e35_none_3df94ea2cfaf0d72\v!10.0.20348.1.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux-deployment_31bf3856ad364e35_none_3df94ea2cfaf0d72\v!10.0.20348.1547.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-slb-mux-deployment_31bf3856ad364e35_10.0.20348.1547_none_68ce0f932e0be5a5.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux-deployment_31bf3856ad364e35_none_3df94ea2cfaf0d72.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux-deployment_31bf3856ad364e35_none_3df94ea2cfaf0d72\v!10.0.20348.1.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux-deployment_31bf3856ad364e35_none_3df94ea2cfaf0d72.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux-deployment_31bf3856ad364e35_none_3df94ea2cfaf0d72\v!10.0.20348.1547.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1846 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux-deployment_31bf3856ad364e35_none_3df94ea2cfaf0d72.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 29 datablocks.
Finish time: 2023-07-25 08:26:18.485
Script hash: 6neS8UdEHGJ+Ck94iqygOakb03d6ZzjdX0zd+QNnpbI=
----------------------EOF-----------------------

 

[Gary R]

We need to see if we can find a little more information on why the same things keep getting flagged, even after we've repaired them. So can you please do the following for me ....

• Download and run Process Monitor
  • Leave this running while you perform the next steps.
• Try updating the system just like you have in the past.
• Stop Process Monitor as soon as it fails.
  • You can simply do this by clicking the "Square" icon on the toolbar (third one from the left) or by hitting Ctrl+E
• Select the File menu ... Save ... and save the file to your Desktop.
  • The name will be LogFile.PML.
• Zip the file, and upload to a file sharing service.
• Provide the link to LogFile.PML
• Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Also attach a copy of your ... C:\Windows\Logs\CBS\CBS.log ... with your reply.

 

[algiz]

I try updating , this time , error code is 0x800f0983

CBS.log attached

logfile.pml download link : Share Files Online without registration

 

[Gary R]

Well, nice to have a different error code, suggests we've acheived something, won't know what till I've looked over the latest logs.

ProcMon logs tend to be rather large, so sorting through them can often take quite a while. I'll get back to you as soon as I can.


CBS.log posted is dated 21st July ....

1st entry ...

2023-07-21 09:11:45, Info CBS TI: --- Initializing Trusted Installer ---

Last entry ...

2023-07-21 21:53:45, Info CBS Deletion of: \\?\C:\Windows\CbsTemp\{CDAF66A7-5A87-474B-A3FC-A81BB8FF3AB5} successful

So think you may have posted me the wrong one.

 

[algiz]

I'm sorry, my bad.

re-upload CBS.log

 

[Gary R]

No problem, we all make mistakes from time to time, it's easily done.

Need to cross reference what's showing in your latest CBS.log with what ProcMon is telling us, and I know that this will take me quite some time, am probably going to need to consult as well, which will cause further delays, so I don't expect to get back to you any time soon.