[SOLVED] Windows 2016 - Unable to update, DISM/SFC errors

T

TomMA

Member
Joined
Feb 21, 2022
Posts
11
Hi,

I'm having some issues with a Windows 2016 install. I'm unable to install any updates or install any additional features.


Output from DSIM below

Code: 
Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

[==                         4.5%                           ]
Error: 1009

The configuration registry database is corrupt.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

SFC
Code: 
Beginning system scan.  This process will take some time.


Windows Resource Protection could not perform the requested operation.

CBS folder attached.


Any help is greatly appreciated.

Thank you!
 

Attachments

Hi,

Thank you for the reply.

I am getting the below -

Code: 
Loading registry hive from C:\Windows\Sysnative\config\COMPONENTS
Parsing loaded hive, please wait...
Sequence numbers do not match! Hive is dirty and the transaction logs should be reviewed for relevant data!
Failed to parse hive. This could indicate major hive corruption (System.ArgumentOutOfRangeException)

Thank you
 
Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. 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.
3. 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.
4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.
 
Thanks, the ComponentsScanner tool should fix the sequence number error for you, unless there is something "off" with your COMPONENTS hive. I can't see any immediate problems from my initial analysis.
 
I forgot to mention, I've notified the developer of the ComponentsScanner tool as well; the data in your COMPONENTS hive appears to be intact so there shouldn't be any major corruption as far as I can tell.
 
Hi,

Thank you for your help and the update.

Anything else you can think of I can try?

Thanks
 
Unfortunately not at the moment, there is something wrong with your COMPONENTS hive, I'm just not sure exactly what. When I've heard back about why the parsing exception was thrown, I'll let you know as soon as possible.
 
Could you please backup your existing COMPONENTS hive and then copy the attached one to the following location:

Rich (BB code): 
%systemroot%\System32\Config

Afterwards, could you please try and update?
 

Attachments

Hi,

Thank you.

Unable to add Windows features or update but SFC and DISM now run!

Code: 
Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

[===========================96.2%=======================   ]
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 http://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

I have tried DISM using a known good server install and the windows imagine with the same result.

Seems to be these from CBS.log?

Code: 
(p)    CSI Payload Corrupt            amd64_netfx4-servicemodel_mof_files_b03f5f7f11d50a3a_4.0.15744.706_none_51547772b3043ae3\ServiceModel.mof
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_microsoft-windows-e..seclientsync-server_31bf3856ad364e35_10.0.14393.4770_none_ed07d53ed6a8a8a0\SyncShare.cdxml
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_microsoft-windows-e..seclientsync-server_31bf3856ad364e35_10.0.14393.4770_none_ed07d53ed6a8a8a0\SyncShareTTSvc.exe
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_3e85a3ebaeb3a84b\Microsoft.Msmq.Activex.Interop.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_3e85a3ebaeb3a84b\Microsoft.Msmq.PowerShell.Commands.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_e2670867f6563715\Microsoft.Msmq.Runtime.Interop.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_e2670867f6563715\Microsoft.Msmq.Activex.Interop.dll
Repair failed: Missing replacement payload.


CBS directory attached.

Thank you again.
 

Attachments

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.
 

Attachments

Hi,

Thank you

Output of SFCFix.text
Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-03-08 08:44:39.931
Microsoft Windows Server 10 Build 14393 - amd64
Using .zip script file at C:\Users\administrator.VVLONDON\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\x86_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_e2670867f6563715\microsoft.msmq.activex.interop.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\x86_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_e2670867f6563715\microsoft.msmq.runtime.interop.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_netfx4-servicemodel_mof_files_b03f5f7f11d50a3a_4.0.15744.706_none_51547772b3043ae3\servicemodel.mof
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_3e85a3ebaeb3a84b\microsoft.msmq.activex.interop.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_3e85a3ebaeb3a84b\microsoft.msmq.powershell.commands.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-e..seclientsync-server_31bf3856ad364e35_10.0.14393.4770_none_ed07d53ed6a8a8a0\syncshare.cdxml
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-e..seclientsync-server_31bf3856ad364e35_10.0.14393.4770_none_ed07d53ed6a8a8a0\syncsharettsvc.exe

Successfully copied file C:\Users\administrator.VVLONDON\AppData\Local\niemiro\Archive\x86_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_e2670867f6563715\microsoft.msmq.activex.interop.dll to C:\Windows\WinSxS\x86_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_e2670867f6563715\microsoft.msmq.activex.interop.dll.
Successfully copied file C:\Users\administrator.VVLONDON\AppData\Local\niemiro\Archive\x86_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_e2670867f6563715\microsoft.msmq.runtime.interop.dll to C:\Windows\WinSxS\x86_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_e2670867f6563715\microsoft.msmq.runtime.interop.dll.
Successfully copied file C:\Users\administrator.VVLONDON\AppData\Local\niemiro\Archive\amd64_netfx4-servicemodel_mof_files_b03f5f7f11d50a3a_4.0.15744.706_none_51547772b3043ae3\servicemodel.mof to C:\Windows\WinSxS\amd64_netfx4-servicemodel_mof_files_b03f5f7f11d50a3a_4.0.15744.706_none_51547772b3043ae3\servicemodel.mof.
Successfully copied file C:\Users\administrator.VVLONDON\AppData\Local\niemiro\Archive\amd64_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_3e85a3ebaeb3a84b\microsoft.msmq.activex.interop.dll to C:\Windows\WinSxS\amd64_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_3e85a3ebaeb3a84b\microsoft.msmq.activex.interop.dll.
Successfully copied file C:\Users\administrator.VVLONDON\AppData\Local\niemiro\Archive\amd64_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_3e85a3ebaeb3a84b\microsoft.msmq.powershell.commands.dll to C:\Windows\WinSxS\amd64_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_3e85a3ebaeb3a84b\microsoft.msmq.powershell.commands.dll.
Successfully copied file C:\Users\administrator.VVLONDON\AppData\Local\niemiro\Archive\amd64_microsoft-windows-e..seclientsync-server_31bf3856ad364e35_10.0.14393.4770_none_ed07d53ed6a8a8a0\syncshare.cdxml to C:\Windows\WinSxS\amd64_microsoft-windows-e..seclientsync-server_31bf3856ad364e35_10.0.14393.4770_none_ed07d53ed6a8a8a0\syncshare.cdxml.
Successfully copied file C:\Users\administrator.VVLONDON\AppData\Local\niemiro\Archive\amd64_microsoft-windows-e..seclientsync-server_31bf3856ad364e35_10.0.14393.4770_none_ed07d53ed6a8a8a0\syncsharettsvc.exe to C:\Windows\WinSxS\amd64_microsoft-windows-e..seclientsync-server_31bf3856ad364e35_10.0.14393.4770_none_ed07d53ed6a8a8a0\syncsharettsvc.exe.

Successfully restored ownership for C:\Windows\WinSxS\x86_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_e2670867f6563715\microsoft.msmq.activex.interop.dll
Successfully restored permissions on C:\Windows\WinSxS\x86_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_e2670867f6563715\microsoft.msmq.activex.interop.dll
Successfully restored ownership for C:\Windows\WinSxS\x86_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_e2670867f6563715\microsoft.msmq.runtime.interop.dll
Successfully restored permissions on C:\Windows\WinSxS\x86_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_e2670867f6563715\microsoft.msmq.runtime.interop.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_netfx4-servicemodel_mof_files_b03f5f7f11d50a3a_4.0.15744.706_none_51547772b3043ae3\servicemodel.mof
Successfully restored permissions on C:\Windows\WinSxS\amd64_netfx4-servicemodel_mof_files_b03f5f7f11d50a3a_4.0.15744.706_none_51547772b3043ae3\servicemodel.mof
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_3e85a3ebaeb3a84b\microsoft.msmq.activex.interop.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_3e85a3ebaeb3a84b\microsoft.msmq.activex.interop.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_3e85a3ebaeb3a84b\microsoft.msmq.powershell.commands.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-msmq-powershell_31bf3856ad364e35_10.0.14393.4770_none_3e85a3ebaeb3a84b\microsoft.msmq.powershell.commands.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-e..seclientsync-server_31bf3856ad364e35_10.0.14393.4770_none_ed07d53ed6a8a8a0\syncshare.cdxml
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-e..seclientsync-server_31bf3856ad364e35_10.0.14393.4770_none_ed07d53ed6a8a8a0\syncshare.cdxml
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-e..seclientsync-server_31bf3856ad364e35_10.0.14393.4770_none_ed07d53ed6a8a8a0\syncsharettsvc.exe
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-e..seclientsync-server_31bf3856ad364e35_10.0.14393.4770_none_ed07d53ed6a8a8a0\syncsharettsvc.exe
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 7 datablocks.
Finish time: 2022-03-08 08:44:41.219
Script hash: UlWYOum2jZ1V3SVoh/6s0Hn4dtQaAoSIdFA7Lav0G5s=
----------------------EOF-----------------------


DISM now completes

Code: 
C:\Users\administrator.VVLONDON>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

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

Still unable to update / install additional windows features unfortunately.
 

Attachments

Rich (BB code): 
2022-03-08 12:14:23, Error                 CSI    0000000c (F) HRESULT_FROM_WIN32(14098) #383424# from Windows::ServicingAPI::CCSITransactionAnalysis_ICSIInventory::EnumComponentsDeployments(flags = (ICSIINVENTORY_ENUMCOMPONENTSDEPLOYMENTS_FLAG_INCLUDE_PINNED|ICSIINVENTORY_ENUMCOMPONENTSDEPLOYMENTS_FLAG_INCLUDE_INSTALLED|ICSIINVENTORY_ENUMCOMPONENTSDEPLOYMENTS_FLAG_ASSEMBLY_NOT_FOUND_RETURNS_NULL), cComponents = 1)
[gle=0x80073712]
2022-03-08 12:14:23, Info                  CBS    Failed to EnumerateComponentDeployment, component: amd64_microsoft-windows-tpm-tasks_31bf3856ad364e35_10.0.14393.4651_none_fb952033b3d6e365 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-03-08 12:14:23, Info                  CBS    Failed to load component owners on component: amd64_microsoft-windows-tpm-tasks_31bf3856ad364e35_0.0.0.0_none_0601f49959a66a68, version: 10.0.14393.4651 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-03-08 12:14:23, Info                  CBS    Failed to load current component state [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-03-08 12:14:23, Info                  CBS    Failed to find or add the component family [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-03-08 12:14:23, Info                  CBS    ComponentAnalyzerEvaluateSelfUpdate call failed. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-03-08 12:14:23, Info                  CBS    Failed to evaluate self update [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-03-08 12:14:23, Info                  CBS    Failed to evaluate non detect parent update [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-03-08 12:14:23, Info                  CBS    Failed to evaluate non parent [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-03-08 12:14:23, Info                  CBS    failed to evaluate single applicability [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-03-08 12:14:23, Info                  CBS    Failed to evaluate applicability [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-03-08 12:14:23, Info                  CBS    Failed to get applicability on updates [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-03-08 12:14:23, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB4502496~31bf3856ad364e35~amd64~~10.0.1.3, Update: 4502496-2_neutral [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-03-08 12:14:23, Info                  CBS    Failed to evaluate applicability state for XML package: Package_2_for_KB4502496~31bf3856ad364e35~amd64~~10.0.1.3 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-03-08 12:14:23, Error                 CBS    Failed to check whether package is partially installed, package: Package_for_KB4502496~31bf3856ad364e35~amd64~~10.0.1.3 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-03-08 12:14:23, Info                  CBS    Failed to evaluate applicability state for XML package: Package_for_KB4502496~31bf3856ad364e35~amd64~~10.0.1.3 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-03-08 12:14:23, Error                 CBS    Failed to check whether package is partially installed, package: Package_for_KB4535680~31bf3856ad364e35~amd64~~10.0.1.2 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-03-08 12:14:23, Info                  CBS    Failed to call EvaluateApplicability on internal CBS package. [HRESULT = 0x80073712]

It looks like the Deployment key is empty for that corresponding component. Fortunately, I do have the same deployment key on my Windows Server 2016 so I should at least be able to partially reconstruct it. Could you please provide the CBS hive using the following instructions?

Step#1 - Export CBS hive
  • Click on the Start button and in the search box, type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (.).
  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send To -> Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload to Dropbox or OneDrive or WeTransfer and just provide the link here.
 
Thanks, could you please enter the following command into a command prompt window:

Rich (BB code): 
fsutil hardlink list %systemroot%\servicing\Packages\Package_2_for_KB4502496~31bf3856ad364e35~amd64~~10.0.1.3.cat
fsutil hardlink list %systemroot%\servicing\Packages\Package_3281_for_KB4048953~31bf3856ad364e35~amd64~~10.0.1.3.cat
fsutil hardlink list %systemroot%\servicing\Packages\Package_1114_for_KB5007192~31bf3856ad364e35~amd64~~10.0.1.8.cat
fsutil hardlink list %systemroot%\servicing\Packages\Package_1114_for_KB5008207~31bf3856ad364e35~amd64~~10.0.1.5.cat

Please copy and paste the output to your next post.
 
Code: 
C:\>fsutil hardlink list %systemroot%\servicing\Packages\Package_2_for_KB4502496~31bf3856ad364e35~amd64~~10.0.1.3.cat
\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_2_for_KB4502496~31bf3856ad364e35~amd64~~10.0.1.3.cat
\Windows\WinSxS\Catalogs\9dce598ed82b08e3f09adcf93bb65cb254d7e94bc43d34657a122e655ce6fb0c.cat
\Windows\servicing\Packages\Package_2_for_KB4502496~31bf3856ad364e35~amd64~~10.0.1.3.cat

C:\>fsutil hardlink list %systemroot%\servicing\Packages\Package_3281_for_KB4048953~31bf3856ad364e35~amd64~~10.0.1.3.cat
\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_3281_for_KB4048953~31bf3856ad364e35~amd64~~10.0.1.3.cat
\Windows\WinSxS\Catalogs\7015f94360b401a2273c3e6561f48d862216bd2b571a1c97454ca3c523af9bd4.cat
\Windows\servicing\Packages\Package_3281_for_KB4048953~31bf3856ad364e35~amd64~~10.0.1.3.cat

C:\>fsutil hardlink list %systemroot%\servicing\Packages\Package_1114_for_KB5007192~31bf3856ad364e35~amd64~~10.0.1.8.cat
\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_1114_for_KB5007192~31bf3856ad364e35~amd64~~10.0.1.8.cat
\Windows\WinSxS\Catalogs\6eab347bf3a815bc2956541bf66a1ac8212d27df1f172aae20580c069e4388dd.cat
\Windows\servicing\Packages\Package_1114_for_KB5007192~31bf3856ad364e35~amd64~~10.0.1.8.cat

C:\>fsutil hardlink list %systemroot%\servicing\Packages\Package_1114_for_KB5008207~31bf3856ad364e35~amd64~~10.0.1.5.cat
\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_1114_for_KB5008207~31bf3856ad364e35~amd64~~10.0.1.5.cat
\Windows\WinSxS\Catalogs\57dcd3e49a1e19e8761c645aca1f12c3f4b687d3ca48510abab0bafd30d07f5f.cat
\Windows\servicing\Packages\Package_1114_for_KB5008207~31bf3856ad364e35~amd64~~10.0.1.5.cat

Thank you
 
Possible CatalogThumbprint values:

Rich (BB code): 
57dcd3e49a1e19e8761c645aca1f12c3f4b687d3ca48510abab0bafd30d07f5f
6eab347bf3a815bc2956541bf66a1ac8212d27df1f172aae20580c069e4388dd

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

Note: This won't repair the issue but will add some of the missing values while I attempt to reconstruct the other missing ones. Please bear in mind, there appears to be several Deployment keys which are completely empty and therefore we may have to evaluate the feasibility of manually repairing them. Do you have any backup images of the server? If you do, then we can check if the Deployment keys which are missing can be repaired using the backup.
 

Attachments

Hi,

Thanks for the continued help, I have backups but this issue seems to also be present in them.
If you believe this isn't going to be feasible then I may have to look at rebuilding the server.

Contents of fixlog.txt

Code: 
Fix result of Farbar Recovery Scan Tool (x64) Version: 08-03-2022
Ran by Administrator (10-03-2022 19:11:15) Run:1
Running from C:\Users\Administrator\Desktop
Loaded Profiles: Administrator & MSSQL$MICROSOFT##WID
Boot Mode: Normal
==============================================

fixlist content:
*****************
CreateRestorePoint:
Reg: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
Reg: reg add HKLM\COMPONENTS\CanonicalData\Deployments\73bae58e393..b50fc63d330_31bf3856ad364e35_10.0.14393.4651_b14ef908643b8c61 /v appid /t REG_BINARY /d 37336261653538653339333530396630623862376462353066633633643333302C2043756C747572653D6E65757472616C2C2056657273696F6E3D31302E302E31343339332E343635312C205075626C69634B6579546F6B656E3D333162663338353661643336346533352C2050726F636573736F724172636869746563747572653D616D6436342C2076657273696F6E53636F70653D4E6F6E537853
Reg: reg add HKLM\COMPONENTS\CanonicalData\Deployments\73bae58e393..b50fc63d330_31bf3856ad364e35_10.0.14393.4651_b14ef908643b8c61 /v CatalogThumbprint /t REG_SZ /d 57dcd3e49a1e19e8761c645aca1f12c3f4b687d3ca48510abab0bafd30d07f5f /f


*****************

Error: (0) Failed to create a restore point.

========= reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS =========

The operation completed successfully.



========= End of Reg: =========


========= reg add HKLM\COMPONENTS\CanonicalData\Deployments\73bae58e393..b50fc63d330_31bf3856ad364e35_10.0.14393.4651_b14ef908643b8c61 /v appid /t REG_BINARY /d 37336261653538653339333530396630623862376462353066633633643333302C2043756C747572653D6E65757472616C2C2056657273696F6E3D31302E302E31343339332E343635312C205075626C69634B6579546F6B656E3D333162663338353661643336346533352C2050726F636573736F724172636869746563747572653D616D6436342C2076657273696F6E53636F70653D4E6F6E537853 =========

The operation completed successfully.



========= End of Reg: =========


========= reg add HKLM\COMPONENTS\CanonicalData\Deployments\73bae58e393..b50fc63d330_31bf3856ad364e35_10.0.14393.4651_b14ef908643b8c61 /v CatalogThumbprint /t REG_SZ /d 57dcd3e49a1e19e8761c645aca1f12c3f4b687d3ca48510abab0bafd30d07f5f /f =========

The operation completed successfully.



========= End of Reg: =========


==== End of Fixlog 19:11:20 ====

Thanks
 
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