[SOLVED] [WinServer2012 x64] Could not reproject corrupted file(s)

OK, that was helpful. Thank you. Please do the following.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt 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
 

Attachments

Code:
SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-10-11 16:54:33.283
Microsoft Windows Server 2012  - amd64
Using .txt script file at C:\Users\Admin\Desktop\SFCScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074 (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_none_4a207b402ad93a1c\v!6.2.9200.17074.

WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074 (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_none_4a207b402ad93a1c\v!6.2.9200.17074.

Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074 (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_none_4a207b402ad93a1c\v!6.2.9200.17074.

Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074 (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_none_4a207b402ad93a1c\v!6.2.9200.17074 with error code ERROR_FILE_NOT_FOUND.
RegistryScript:: directive failed to complete successfully.




Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 420 datablocks.
Finish time: 2017-10-11 16:54:34.377
Script hash: bWphe6bHXLEb1WgCpiuIRMZNlyrK5KODy2s7vqBLzSY=
----------------------EOF-----------------------
 

Attachments

Thank you. Please do the following.

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Attempt to install KB3173426 just like you have in the past.
3. Stop Process Monitor as soon as the update fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


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 attach the LogFile.PML file as well as your CBS.log.
 
Please do the following.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt 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
 

Attachments

Code:
SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-10-12 07:24:09.720
Microsoft Windows Server 2012  - amd64
Using .txt script file at C:\Users\Admin\Desktop\SFCScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-cbsapi_31bf3856ad364e35_none_6435a14242b99e0c\v!6.2.9200.17074.
Successfully took ownership and permissions for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack-admin_31bf3856ad364e35_none_8cce7571b17dfb06\v!6.2.9200.17074.
Successfully took ownership and permissions for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack-ds_31bf3856ad364e35_none_e274ba21a075e6da\v!6.2.9200.17074.
Successfully took ownership and permissions for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack-net_31bf3856ad364e35_none_ff62e59f75171f0e\v!6.2.9200.17074.
Successfully took ownership and permissions for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack-termsrv_31bf3856ad364e35_none_503322be3db10a4e\v!6.2.9200.17074.
Successfully took ownership and permissions for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_none_4a207b402ad93a1c.
Successfully took ownership and permissions for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-tiscavengetask_31bf3856ad364e35_none_8335fb1f05cd6cee\v!6.2.9200.17074.
Successfully took ownership and permissions for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-trustedinstaller_31bf3856ad364e35_none_b62a7edd54dd337d\v!6.2.9200.17074.
Successfully took ownership and permissions for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\x86_microsoft-windows-servicingstack-admin_31bf3856ad364e35_none_30afd9edf92089d0\v!6.2.9200.17074.
Successfully took ownership and permissions for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\x86_microsoft-windows-servicingstack-ds_31bf3856ad364e35_none_86561e9de81875a4\v!6.2.9200.17074.
Successfully took ownership and permissions for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\x86_microsoft-windows-servicingstack-net_31bf3856ad364e35_none_a3444a1bbcb9add8\v!6.2.9200.17074.
Successfully took ownership and permissions for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\x86_microsoft-windows-servicingstack_31bf3856ad364e35_none_ee01dfbc727bc8e6.

WARNING: Failed to create backup for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-cbsapi_31bf3856ad364e35_none_6435a14242b99e0c\v!6.2.9200.17074.

Successfully deleted registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-cbsapi_31bf3856ad364e35_none_6435a14242b99e0c\v!6.2.9200.17074.
WARNING: Failed to create backup for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack-admin_31bf3856ad364e35_none_8cce7571b17dfb06\v!6.2.9200.17074.

Successfully deleted registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack-admin_31bf3856ad364e35_none_8cce7571b17dfb06\v!6.2.9200.17074.
WARNING: Failed to create backup for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack-ds_31bf3856ad364e35_none_e274ba21a075e6da\v!6.2.9200.17074.

Successfully deleted registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack-ds_31bf3856ad364e35_none_e274ba21a075e6da\v!6.2.9200.17074.
WARNING: Failed to create backup for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack-net_31bf3856ad364e35_none_ff62e59f75171f0e\v!6.2.9200.17074.

Successfully deleted registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack-net_31bf3856ad364e35_none_ff62e59f75171f0e\v!6.2.9200.17074.
WARNING: Failed to create backup for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack-termsrv_31bf3856ad364e35_none_503322be3db10a4e\v!6.2.9200.17074.

Successfully deleted registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack-termsrv_31bf3856ad364e35_none_503322be3db10a4e\v!6.2.9200.17074.
Successfully deleted registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_none_4a207b402ad93a1c\v!6.2.9200.17074.
WARNING: Failed to create backup for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-tiscavengetask_31bf3856ad364e35_none_8335fb1f05cd6cee\v!6.2.9200.17074.

Successfully deleted registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-tiscavengetask_31bf3856ad364e35_none_8335fb1f05cd6cee\v!6.2.9200.17074.
WARNING: Failed to create backup for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-trustedinstaller_31bf3856ad364e35_none_b62a7edd54dd337d\v!6.2.9200.17074.

Successfully deleted registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-trustedinstaller_31bf3856ad364e35_none_b62a7edd54dd337d\v!6.2.9200.17074.
WARNING: Failed to create backup for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\x86_microsoft-windows-servicingstack-admin_31bf3856ad364e35_none_30afd9edf92089d0\v!6.2.9200.17074.

Successfully deleted registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\x86_microsoft-windows-servicingstack-admin_31bf3856ad364e35_none_30afd9edf92089d0\v!6.2.9200.17074.
WARNING: Failed to create backup for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\x86_microsoft-windows-servicingstack-ds_31bf3856ad364e35_none_86561e9de81875a4\v!6.2.9200.17074.

Successfully deleted registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\x86_microsoft-windows-servicingstack-ds_31bf3856ad364e35_none_86561e9de81875a4\v!6.2.9200.17074.
WARNING: Failed to create backup for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\x86_microsoft-windows-servicingstack-net_31bf3856ad364e35_none_a3444a1bbcb9add8\v!6.2.9200.17074.

Successfully deleted registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\x86_microsoft-windows-servicingstack-net_31bf3856ad364e35_none_a3444a1bbcb9add8\v!6.2.9200.17074.
Successfully deleted registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\x86_microsoft-windows-servicingstack_31bf3856ad364e35_none_ee01dfbc727bc8e6\v!6.2.9200.17074.

Failed to open registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-cbsapi_31bf3856ad364e35_none_6435a14242b99e0c\v!6.2.9200.17074  with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack-admin_31bf3856ad364e35_none_8cce7571b17dfb06\v!6.2.9200.17074  with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack-ds_31bf3856ad364e35_none_e274ba21a075e6da\v!6.2.9200.17074  with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack-net_31bf3856ad364e35_none_ff62e59f75171f0e\v!6.2.9200.17074  with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack-termsrv_31bf3856ad364e35_none_503322be3db10a4e\v!6.2.9200.17074  with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_none_4a207b402ad93a1c.
Failed to open registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-tiscavengetask_31bf3856ad364e35_none_8335fb1f05cd6cee\v!6.2.9200.17074  with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\amd64_microsoft-windows-trustedinstaller_31bf3856ad364e35_none_b62a7edd54dd337d\v!6.2.9200.17074  with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\x86_microsoft-windows-servicingstack-admin_31bf3856ad364e35_none_30afd9edf92089d0\v!6.2.9200.17074  with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\x86_microsoft-windows-servicingstack-ds_31bf3856ad364e35_none_86561e9de81875a4\v!6.2.9200.17074  with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\x86_microsoft-windows-servicingstack-net_31bf3856ad364e35_none_a3444a1bbcb9add8\v!6.2.9200.17074  with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.2.9200.17074  (win8_gdr.140808-1627)\ComponentFamilies\x86_microsoft-windows-servicingstack_31bf3856ad364e35_none_ee01dfbc727bc8e6.
RegistryScript:: directive failed to complete successfully.




Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 422 datablocks.
Finish time: 2017-10-12 07:24:11.161
Script hash: F1cFLtxMkq81xcCHJNmzLbJGM47tctL2wBlwd7ODxZA=
----------------------EOF-----------------------

Allright, after applying the fix and rebooting the system KB3173426 is listed as successfully installed now. It seems that the next update (KB3156019) will be successful as well, yet another reboot is required - I'll be back with the next one that doesn't work...
Thanks again so far, I really appreciate your help!
 
Please do the following AND THEN CHECK FOR UPDATES. This update may no longer show up as needing installed. Please let me know.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt 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
 

Attachments

Code:
SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-10-14 20:18:25.349
Microsoft Windows Server 2012  - amd64
Using .txt script file at C:\Users\Admin\Desktop\SFCScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-ntdll_31bf3856ad364e35_none_13be95395ddc6d7a\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_none_dafb6888df961258\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-csrsrv_31bf3856ad364e35_none_84a052ba122c6e9f\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-advapi32_31bf3856ad364e35_none_49a3428f159a3330\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-advapi32.resources_31bf3856ad364e35_de-de_e9911f422b70bc9e\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-lsa.resources_31bf3856ad364e35_de-de_dad18a90a021cd8e\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-lsa-minwin_31bf3856ad364e35_none_3902942ef7d8ca79\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_de-de_7c245380dfc53d98\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-msauditevtlog_31bf3856ad364e35_none_bee07573172aac84\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_none_2003e93c9ec12938\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-security-credssp_31bf3856ad364e35_none_d137a96567edf1d7\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-security-digest_31bf3856ad364e35_none_925401d488780c9f\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_none_08fd017ef4755428\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-shcore_31bf3856ad364e35_none_037d8903cb8635ea\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-smb10-minirdr_31bf3856ad364e35_none_1c474f5e1c2a89c3\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_none_5038ca368704679a\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-smbminirdr.resources_31bf3856ad364e35_de-de_523c1f2e95c9b633\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-smbminirdr_31bf3856ad364e35_none_caf94479a9c1c995\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-t..localsessionmanager_31bf3856ad364e35_none_2da9c02b78b5a5fb\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-usercpl_31bf3856ad364e35_none_6adf6ff6ff6c50f0\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-winlogon_31bf3856ad364e35_none_f5b8cb6e623872d3\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-lsa-minwin_31bf3856ad364e35_none_43573e812c398c74\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-ntdll_31bf3856ad364e35_none_1e133f8b923d2f75\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-security-digest_31bf3856ad364e35_none_9ca8ac26bcd8ce9a\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-security-kerberos_31bf3856ad364e35_none_1351abd128d61623\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-advapi32.resources_31bf3856ad364e35_de-de_8d7283be73134b68\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-advapi32_31bf3856ad364e35_none_ed84a70b5d3cc1fa\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_de-de_2005b7fd2767cc62\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-msauditevtlog_31bf3856ad364e35_none_62c1d9ef5ecd3b4e\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-security-credssp_31bf3856ad364e35_none_75190de1af9080a1\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-shcore_31bf3856ad364e35_none_a75eed801328c4b4\6.2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-usercpl_31bf3856ad364e35_none_0ec0d473470edfba\6.2.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-ntdll_31bf3856ad364e35_none_13be95395ddc6d7a\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_none_dafb6888df961258\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-csrsrv_31bf3856ad364e35_none_84a052ba122c6e9f\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-advapi32_31bf3856ad364e35_none_49a3428f159a3330\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-advapi32.resources_31bf3856ad364e35_de-de_e9911f422b70bc9e\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-lsa.resources_31bf3856ad364e35_de-de_dad18a90a021cd8e\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-lsa-minwin_31bf3856ad364e35_none_3902942ef7d8ca79\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_de-de_7c245380dfc53d98\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-msauditevtlog_31bf3856ad364e35_none_bee07573172aac84\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_none_2003e93c9ec12938\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-security-credssp_31bf3856ad364e35_none_d137a96567edf1d7\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-security-digest_31bf3856ad364e35_none_925401d488780c9f\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_none_08fd017ef4755428\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-shcore_31bf3856ad364e35_none_037d8903cb8635ea\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-smb10-minirdr_31bf3856ad364e35_none_1c474f5e1c2a89c3\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_none_5038ca368704679a\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-smbminirdr.resources_31bf3856ad364e35_de-de_523c1f2e95c9b633\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-smbminirdr_31bf3856ad364e35_none_caf94479a9c1c995\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-t..localsessionmanager_31bf3856ad364e35_none_2da9c02b78b5a5fb\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-usercpl_31bf3856ad364e35_none_6adf6ff6ff6c50f0\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-winlogon_31bf3856ad364e35_none_f5b8cb6e623872d3\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-lsa-minwin_31bf3856ad364e35_none_43573e812c398c74\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-ntdll_31bf3856ad364e35_none_1e133f8b923d2f75\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-security-digest_31bf3856ad364e35_none_9ca8ac26bcd8ce9a\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-security-kerberos_31bf3856ad364e35_none_1351abd128d61623\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-advapi32.resources_31bf3856ad364e35_de-de_8d7283be73134b68\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-advapi32_31bf3856ad364e35_none_ed84a70b5d3cc1fa\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_de-de_2005b7fd2767cc62\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-msauditevtlog_31bf3856ad364e35_none_62c1d9ef5ecd3b4e\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-security-credssp_31bf3856ad364e35_none_75190de1af9080a1\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-shcore_31bf3856ad364e35_none_a75eed801328c4b4\6.2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-usercpl_31bf3856ad364e35_none_0ec0d473470edfba\6.2.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-ntdll_31bf3856ad364e35_none_13be95395ddc6d7a\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_none_dafb6888df961258\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-csrsrv_31bf3856ad364e35_none_84a052ba122c6e9f\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-advapi32_31bf3856ad364e35_none_49a3428f159a3330\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-advapi32.resources_31bf3856ad364e35_de-de_e9911f422b70bc9e\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-lsa.resources_31bf3856ad364e35_de-de_dad18a90a021cd8e\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-lsa-minwin_31bf3856ad364e35_none_3902942ef7d8ca79\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_de-de_7c245380dfc53d98\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-msauditevtlog_31bf3856ad364e35_none_bee07573172aac84\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_none_2003e93c9ec12938\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-security-credssp_31bf3856ad364e35_none_d137a96567edf1d7\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-security-digest_31bf3856ad364e35_none_925401d488780c9f\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_none_08fd017ef4755428\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-shcore_31bf3856ad364e35_none_037d8903cb8635ea\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-smb10-minirdr_31bf3856ad364e35_none_1c474f5e1c2a89c3\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_none_5038ca368704679a\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-smbminirdr.resources_31bf3856ad364e35_de-de_523c1f2e95c9b633\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-smbminirdr_31bf3856ad364e35_none_caf94479a9c1c995\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-t..localsessionmanager_31bf3856ad364e35_none_2da9c02b78b5a5fb\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-usercpl_31bf3856ad364e35_none_6adf6ff6ff6c50f0\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-winlogon_31bf3856ad364e35_none_f5b8cb6e623872d3\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-lsa-minwin_31bf3856ad364e35_none_43573e812c398c74\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-ntdll_31bf3856ad364e35_none_1e133f8b923d2f75\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-security-digest_31bf3856ad364e35_none_9ca8ac26bcd8ce9a\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-security-kerberos_31bf3856ad364e35_none_1351abd128d61623\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-advapi32.resources_31bf3856ad364e35_de-de_8d7283be73134b68\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-advapi32_31bf3856ad364e35_none_ed84a70b5d3cc1fa\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_de-de_2005b7fd2767cc62\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-msauditevtlog_31bf3856ad364e35_none_62c1d9ef5ecd3b4e\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-security-credssp_31bf3856ad364e35_none_75190de1af9080a1\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-shcore_31bf3856ad364e35_none_a75eed801328c4b4\6.2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-usercpl_31bf3856ad364e35_none_0ec0d473470edfba\6.2.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 453 datablocks.
Finish time: 2017-10-14 20:18:28.559
Script hash: emTMqTFuybdX3pKafNgV+OrbVatl2ozDuPuHz88HKqM=
----------------------EOF-----------------------

After applying the fix KB3175024 is still listed.
 

Attachments

Please do the following AND THEN CHECK FOR UPDATES. This update may no longer show up as needing installed. Please let me know.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt 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
 

Attachments

Code:
SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-10-14 23:10:01.359
Microsoft Windows Server 2012  - amd64
Using .txt script file at C:\Users\Admin\Desktop\SFCScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-msauditevtlog_31bf3856ad364e35_none_bee07573172aac84\6.2.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-msauditevtlog_31bf3856ad364e35_none_bee07573172aac84\6.2.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-msauditevtlog_31bf3856ad364e35_none_bee07573172aac84\6.2.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 453 datablocks.
Finish time: 2017-10-14 23:10:01.437
Script hash: LuB7pYJtnFfmfCUe8IdaS9X2oBDkhtrq4uhOVx93S4c=
----------------------EOF-----------------------

Now the update was successful. I'll proceed with the other ones (already 5 were successful so far) and let you know the next one failing.
 
Uhm...quick info: the last update (I don't know which KB number) required a reboot but the system didn't boot as expected. A blue screen appeared with error 0xc0000139. Even booting in safe mode and trying a repair install failed.
So for now, we cannot access the server. As we don't have a good restore point to rely on we're going to try a clean reinstall of the server...
 
Damn. That's not the kind of news I hoped to wake up to. I'm extremely sorry that this happened. If I remember correctly this machine was a local domain controller also serving as a file server. Do you still have your VM that you made? We could use that.

Also, since it was a file server we need to make sure all of the documents are copied somewhere before they are overwritten. Please let me know if you need assistance with this.
 
Don't you worry, I was totally aware that the hold operation we were going through the last 500 posts was quite a bit risky without having a restore point to rely on. Yet I apologize the ending of this thread leading to install the system from scratch...
However the new Server was set up in less than an hour, the files were on a seperate drive so nothing to worry about. We managed to get the system running again so we can go back to business as usual.
Well, and now there are over 170 pending updates waiting to be installed, so no time to loose ;-)
What I'm still courious about is what could have caused these system file corruptions (and the last error that leaded to the BSOD), could this have been caused by one or more unsuccessful installed updates, do you have any assumptions?
During the install process I noticed that on the system drive there was enough unallocated space (265 GB) so we installed the system there, which means the old system still exists and for now shows up as drive (F:). The VM also is still accessible - so could we get the "old" system running again?
 
I'm VERY happy that you are back up and running. I felt absolutely horrible.

I really don't know what could have caused the corruption on the machine. I would only be guessing. I know if you disable updates for long enough the system doesn't know how to apply the updates to account for a machine that is so outdated. Also if an update is installing and the machine gets rebooted and it's partially installed...that can cause issues as well.

So at this point I think we will just leave well enough alone. Thank you so much for your patience and again I sincerely appologize for the inconvenience. You take care.
 
Allright, thanks again for your professional guidance - you guys are doing a great job around here!
 

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

Back
Top