Windows Server 2012R2 - sfc /scannow unable to fix some of them

Thank you!

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 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.
  9. If script succeeds, attempt the update again and attach CBS.log
 

Attachments

fail.

View attachment cbs.txt

Code: 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-05-01 14:45:53.638
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .txt script file at C:\Users\Administrateur\Desktop\SFCFixScript.txt [0]
 

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 imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_adobe-flash-for-windows_31bf3856ad364e35_7.3.9600.18654_none_0def083cc85519f0.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a9afe0d1f7a..b9aa9d4febe_31bf3856ad364e35_7.3.9600.18654_6c014b19b37923bd.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_adobe-flash-for-windows_31bf3856ad364e35_7.3.9600.18654_none_0def083cc85519f0.
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\a9afe0d1f7a..b9aa9d4febe_31bf3856ad364e35_7.3.9600.18654_6c014b19b37923bd.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
RegistryScript:: directive completed successfully.
 

Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 12 datablocks.
Finish time: 2018-05-01 14:45:54.247
Script hash: pq8gf9g9fIHN7NWLpKeOnmqF+DSNl6Zuci/bFhqEENM=
----------------------EOF-----------------------
 
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 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:
    tags around the log to break up the text.
  9. If the script succeeds, attempt the update again and attach CBS.log
 

Attachments

Code: 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-05-01 15:48:04.694
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .txt script file at C:\Users\Administrateur\Desktop\SFCFixScript.txt [0]
 

RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.18384 (winblue_ltsb.160621-0600)\ComponentFamilies\amd64_adobe-flash-for-windows_31bf3856ad364e35_none_b4179b8118d18c9f.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.18384 (winblue_ltsb.160621-0600)\ComponentFamilies\amd64_adobe-flash-for-windows_31bf3856ad364e35_none_b4179b8118d18c9f\v!7.3.9600.18654.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.18384 (winblue_ltsb.160621-0600)\ComponentFamilies\amd64_adobe-flash-for-windows_31bf3856ad364e35_none_b4179b8118d18c9f\v!7.3.9600.18654.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.18384 (winblue_ltsb.160621-0600)\ComponentFamilies\amd64_adobe-flash-for-windows_31bf3856ad364e35_none_b4179b8118d18c9f.
RegistryScript:: directive completed successfully.
 

Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 14 datablocks.
Finish time: 2018-05-01 15:48:04.788
Script hash: J3GpE4odIiRQ8g3LlAYqynuxReZq+l2IZgu4ImHW6Aw=
----------------------EOF-----------------------

files
 
Reboot the Server when able, and retry the flash update with ProcMon. If it fails, attach CBS.log and an updated copy of the components hive.

Apologies for so many retries, but this is very complicated and needs to be done step by step.
 
No worries, I'm pleased to get support.

Flash Update was not present any more in the available update, I add to run a new search for important updates to get it in the list.
Component was not available, so a restart was required.
'Windows preparation in progress, do not switch off', so I have to wait before I can send you Component

files :
cbs
log
 
But did the update fail? Because the way you describe it, it looks like that it succeeded. If it didn't, there'd be nothing to configure. After the configuration is complete, please recheck for updates and let me know whether the Flash update is still listed.
 
hmm, seems server is in a loop ...

preparation.PNG

then

arret.PNG

then reboot, restart and back to first picture.
 
after 10 loops, server is back to life...
Where do I find setupapi.dev.log ?
 
Exchange server is down due to
Code: 
[FONT=Arial]Microsoft.Exchange.Data.Directory.ADTopologyEndpointNotFoundException[/FONT]
IIS is running,
OWA and ECP are down.
I have to fix this. could it be linked to the file we fix ?
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-d..services-core-files_31bf3856ad364e35_6.3.9600.18476_none_80b6378ffae9759b\Active Directory Diagnostics.xml

setup file View attachment setupapi.dev.zip
component
 
Yes, it could. The file was damaged and I replaced it with a good copy.

Please try the following steps:

Step 1. Right-click the windows icon and then click Run.
Step 2. Type services.msc and then hit enter from the keyboard.
Step 3. Locate and double-click the 'Microsoft Exchange Active Directory Topology'.
Step 4. Click 'Start' to start the service.
 
it start then stop
in Eventvwr :

Code: 
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=4828). The local server is not assigned to any site. This can be caused by incorrect configuration of subnets or sites or by replication latency. AD Topology Service won't start until this issue is resolved.
 
since the modification, server restart several times and I do not meet any issue with Exchange.
seems it happens since loops
 
Hello,
I had to restore the server.
Update still fails and AD was damaged.
 
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