[SOLVED] Failed to bind the online servicing stack

P

peteds

Active member
Joined
Dec 1, 2021
Posts
37
Hi techies. I've searched and searched but not yet found a working solution to my problem. It seems the last SSU didn't install properly and now we are faced with dism and sfc will not do anything.
Server 2012 R2
2022-07-21 15:07:10, Warning DISM DISM OS Provider: PID=6236 TID=6932 Failed to bind the online servicing stack - CDISMOSServiceManager::get_ServicingStackDirectory(hr:0x80070003)
2022-07-21 15:07:10, Error DISM DISM OS Provider: PID=6236 TID=6932 Unable to retrieve servicing stack folder for DLL search path modification. - CDISMOSServiceManager::SetDllSearchPath(hr:0x80070003)
2022-07-21 15:07:10, Error DISM DISM OS Provider: PID=6236 TID=6932 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::SetWindowsDirectory(hr:0x80070003)
2022-07-21 15:07:10, Error DISM DISM.EXE: Failed to set the windows directory to 'C:\Windows'. HRESULT=80070003

CBS Failed to create CBS worker - waiting for a second and trying again [HRESULT = 0x80004002]

I've checked for multiple versions of the SSU in C:\Windows\Servicing\Version but only this folder exists. 6.3.9600.19991 and i've checked the registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version which also has 6.3.9600.19991 with a path of %SystemRoot%\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91
If i search the WinSxS folder for this the only thing found is the manifest file.

Thanking you all in advance, Pete
 
SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

Afterwards, please run the following command from an elevated command prompt:

Rich (BB code): 
DISM /Online /Cleanup-Health /RestoreHealth

If you have any errors, then please provide the CBS log along with the DISM log.
 

Attachments

Thanks, i have performed the actions and attach the logs. At least DISM seems to be trying now. I tried with scanhealth restorehealth but it returns error 0x80004002



Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-07-22 12:56:54.196
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .zip script file at C:\Users\pete.sharrock.adm\Desktop\SFCFix.zip [0]




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

Successfully created directory tree \\?\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91.

Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\amd64_installed to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\amd64_installed.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\bfsvc.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\bfsvc.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\CbsCore.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\CbsCore.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\CbsMsg.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\CbsMsg.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\cleanupai.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\cleanupai.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\cmiadapter.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\cmiadapter.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\cmiaisupport.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\cmiaisupport.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\cmitrust.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\cmitrust.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\cmiv2.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\cmiv2.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\CntrtextInstaller.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\CntrtextInstaller.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\dpx.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\dpx.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\DrUpdate.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\DrUpdate.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\drvstore.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\drvstore.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\fveupdateai.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\fveupdateai.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\GlobalInstallOrder.xml to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\GlobalInstallOrder.xml.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\luainstall.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\luainstall.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\msdelta.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\msdelta.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\mspatcha.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\mspatcha.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\poqexec.exe to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\poqexec.exe.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\securebootai.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\securebootai.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\smiengine.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\smiengine.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\smipi.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\smipi.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\TiFileFetcher.exe to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\TiFileFetcher.exe.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\timezoneai.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\timezoneai.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\TiWorker.exe to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\TiWorker.exe.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\WcmTypes.xsd to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\WcmTypes.xsd.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\wcp.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\wcp.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\wdscore.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\wdscore.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\winsockai.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\winsockai.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\wrpint.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\wrpint.dll.
Successfully copied file C:\Users\pete.sharrock.adm\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\ws2_helper.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\ws2_helper.dll.

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




Successfully processed all directives.



Failed to generate a complete zip file. Upload aborted.


SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2022-07-22 13:01:04.225
Script hash: RXpuPDO4AfQs0NqXmgVKpqJEXHk37oDcZKcbh0bTXZ8=
----------------------EOF-----------------------
 

Attachments

Before using the SFCFix, even dism /online /get-drivers would fail. This command now works at least.
 
DISM is still failing very early and there isn't much indication as to why in your DISM or CBS log. Let's get a Process Monitor trace to see what is happening:

Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try running DISM /Online /Cleanup-Image /RestoreHealth just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square icon on the toolbar as shown below.
j8MhY5V.png

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your DISM.log Examples of services to upload to are Dropbox or OneDrive or WeTransfer.
 
SFCFixScript.txt
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.[/list]
 

Attachments

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-07-22 15:48:50.303
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .txt script file at C:\Users\pete.sharrock.adm\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{75207391-23F2-4396-85F0-8FDB879ED0ED}.
Successfully took ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{75207391-23F2-4396-85F0-8FDB879ED0ED}\InprocServer32.
Successfully took ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{752073A1-23F2-4396-85F0-8FDB879ED0ED}.

Successfully imported registry key HKEY_CLASSES_ROOT\CLSID\{75207391-23F2-4396-85F0-8FDB879ED0ED}.
Successfully imported registry key HKEY_CLASSES_ROOT\CLSID\{75207391-23F2-4396-85F0-8FDB879ED0ED}\InprocServer32.
Successfully imported registry key HKEY_CLASSES_ROOT\CLSID\{752073A1-23F2-4396-85F0-8FDB879ED0ED}.

Successfully restored ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{75207391-23F2-4396-85F0-8FDB879ED0ED}.
Successfully restored ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{75207391-23F2-4396-85F0-8FDB879ED0ED}\InprocServer32.
Successfully restored ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{752073A1-23F2-4396-85F0-8FDB879ED0ED}.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2022-07-22 15:48:51.303
Script hash: whKWPfHSK4xN2h3w8kRb27QSvws3HiqcSNJfzBPLTwc=
----------------------EOF-----------------------
 
I have since run the restorehealth command but nothing has changed i'm afraid.
 
Could you please provide the latest CBS and DISM logs? Additionally, please open a command prompt window and then enter the following commands:

Rich (BB code): 
reg query "HKEY_CLASSES_ROOT\CLSID\{75207391-23F2-4396-85F0-8FDB879ED0ED}" /s
reg query "HKEY_CLASSES_ROOT\CLSID\{75207391-23F2-4396-85F0-8FDB879ED0ED}"

Please post the output in your next post.
 
HKEY_CLASSES_ROOT\CLSID\{75207391-23F2-4396-85F0-8FDB879ED0ED}
(par d‚faut) REG_SZ Component Based Servicing Session Proxy/Stub

HKEY_CLASSES_ROOT\CLSID\{75207391-23F2-4396-85F0-8FDB879ED0ED}\InprocServer32
(par d‚faut) REG_EXPAND_SZ %SystemRoot%\servicing\CbsApi.dll
ThreadingModel REG_SZ Both


HKEY_CLASSES_ROOT\CLSID\{75207391-23F2-4396-85F0-8FDB879ED0ED}
(par d‚faut) REG_SZ Component Based Servicing Session Proxy/Stub

HKEY_CLASSES_ROOT\CLSID\{75207391-23F2-4396-85F0-8FDB879ED0ED}\InprocServer32
 

Attachments

@BlueRobot, i would just like to say thank you for your help in this matter. Hopefully you/we will find a solution.
 
Thanks, could you please open a command prompt window and then enter the following command:

Rich (BB code): 
reg query "HKEY_CLASSES_ROOT\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}" /s

Please post the output in your next post.
 
Additionally, please enter the following command too and then post the output:

Rich (BB code): 
dir %systemroot%\servicing
 
HKEY_CLASSES_ROOT\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}\LocalServer32
(par d‚faut) REG_EXPAND_SZ %SystemRoot%\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\TiWorker.exe

R‚pertoire de C:\Windows\servicing

12/06/2015 02:19 <DIR> .
12/06/2015 02:19 <DIR> ..
29/10/2014 03:21 37ÿ376 CbsApi.dll
18/03/2014 12:05 42ÿ496 CbsMsg.dll
18/03/2014 12:23 <DIR> Editions
18/03/2014 12:23 <DIR> fr-FR
19/12/2021 01:24 <DIR> Packages
19/12/2021 01:27 <DIR> Sessions
22/08/2013 15:27 <DIR> SQM
29/10/2014 03:19 106ÿ496 TrustedInstaller.exe
18/04/2021 00:00 <DIR> Version
29/10/2014 04:41 13ÿ824 wrpintapi.dll
 
Thanks, that all appears to look normal to me, however, I have found a couple of other missing registry keys from your Process Monitor trace which are being queried by DISM. Let's add those back as well.

Once they're successfully added, then please attempt to run DISM again. If it fails with the same errors as last time, then please provide a new Process Monitor log.
 

Attachments

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-07-22 17:41:37.828
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .txt script file at C:\Users\pete.sharrock.adm\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{DF0B3D60-548F-101B-8E65-08002B2BD119}.
Successfully took ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{DF0B3D60-548F-101B-8E65-08002B2BD119}\InprocServer32.
Successfully took ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{00020420-0000-0000-C000-000000000046}.
Successfully took ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{00020420-0000-0000-C000-000000000046}\InprocServer32.

Successfully imported registry key HKEY_CLASSES_ROOT\CLSID\{DF0B3D60-548F-101B-8E65-08002B2BD119}.
Successfully imported registry key HKEY_CLASSES_ROOT\CLSID\{DF0B3D60-548F-101B-8E65-08002B2BD119}\InprocServer32.
Successfully imported registry key HKEY_CLASSES_ROOT\CLSID\{00020420-0000-0000-C000-000000000046}.
Successfully imported registry key HKEY_CLASSES_ROOT\CLSID\{00020420-0000-0000-C000-000000000046}\InprocServer32.

Successfully restored ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{DF0B3D60-548F-101B-8E65-08002B2BD119}.
Successfully restored ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{DF0B3D60-548F-101B-8E65-08002B2BD119}\InprocServer32.
Successfully restored ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{00020420-0000-0000-C000-000000000046}.
Successfully restored ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{00020420-0000-0000-C000-000000000046}\InprocServer32.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 8 datablocks.
Finish time: 2022-07-22 17:41:38.310
Script hash: FuQkBrVdCmrVt7HwPY1RHDZdtic49K87VJJ+ldrURGs=
----------------------EOF-----------------------

I've uploaded CBS DISM and PrcMon to

Logs v2
 
Reg query result
HKEY_CLASSES_ROOT\CLSID\{DF0B3D60-548F-101B-8E65-08002B2BD119}
(par d‚faut) REG_SZ PSSupportErrorInfo

HKEY_CLASSES_ROOT\CLSID\{DF0B3D60-548F-101B-8E65-08002B2BD119}\InprocServer32

HKEY_CLASSES_ROOT\CLSID\{DF0B3D60-548F-101B-8E65-08002B2BD119}
(par d‚faut) REG_SZ PSSupportErrorInfo

HKEY_CLASSES_ROOT\CLSID\{DF0B3D60-548F-101B-8E65-08002B2BD119}\InprocServer32
(par d‚faut) REG_SZ C:\Windows\System32\oleaut32.dll
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top