Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Server 2008 R2 SP1 -- dotNET meltdown


  • Please log in to reply
44 replies to this topic

#1 Aleonymous

Aleonymous

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:07:20 PM

Posted 03 December 2018 - 11:17 AM

Hi all,

 

A couple of weeks ago my computer suffered an HDD crash together with a failing PSU, which resulted in various small problems that I managed to resolve (no data loss, thankfully). Crashes and lock-ups (no BSODs) happened due to the bad HDD and a few random reboots due to the PSU. Some of these unhappy events might have happened during a Windows Update.

 

The main (non-fatal) symptoms I'm currently experiencing are:

  • 1. Can't open Server Manager (MMC could not create the snap-in, CLSID: FX:{18ea...8fbb})
  • 2. Can't access Windows Features On/Off toggles
  • 3. Some installed programs won't start or they'll crash w/ no message (e.g. Java JAR-apps or Viber Desktop)
  • 4. Some software won't even install (e.g. CCleaner's .exe installer fails to start -- no response after double-click)

Thankfully all my critical software is working (Chrome, MS Office, scientific stuff like MATLAB and CST) and Windows Explorer, albeit unstable, does its job. I'm able to manually start all the modules of the Server Manager that I've needed so far (e.g. Disk Mgmt). However, I'm afraid at how this might "escalate" and I'm loath to format/re-install...

 

Troubleshooting throughout the internet, I've narrowed things down to a .NET Framework issue (v4.7.2 and my OS is otherwise fully updated), like a bad/corrupred update or something. So, with the help of our precious internet, I've tried several "easy" stuff like the following, in no particular order and without luck:

  • un/re-installs, updates (OS, .NET, individual programs)
  • running with admin rights, rebooting after changes
  • chkdsk and sfc /scannow (it finds corrupted files but can't fix 'em)
  • regedit to delete offending CLSID key (won't delete), or copy-it from a healthy installation (it didn't help)
  • clearing system32 Tasks folder
  • rename/copy-over C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\Machine.config
  • Registry repair with CCleaner (before trying to install newest version effectively locked me out of it...)

I admit I've done all the above in a sort of a random manner, but made sure to follow the instructions correctly each time.

 

Thanks for reading. Any help would be appreciated!



BC AdBot (Login to Remove)

 


#2 Aleonymous

Aleonymous
  • Topic Starter

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:07:20 PM

Posted 05 December 2018 - 06:01 AM

I also noticed that the Language setting toolbar has disappeared from the windows taskbar (regional/keyboard settings are checked, and it should appear there). Thankfully the [Alt]+[Shift] keyboard shortcut works...



#3 SleepyDude

SleepyDude

  • Malware Response Team
  • 3,195 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Portugal
  • Local time:05:20 PM

Posted 07 December 2018 - 10:11 AM

Hi,

 

Download and run the SUR tool

http://support.microsoft.com/kb/947821

 

Attach to your post the log from the following location: C:\Windows\Logs\CBS\CheckSUR.log

Note: If the file is too big please Zip it and upload the ZIP file to a service like Dropbox, Google Drive, OneDrive or upload to SendSpace and just provide the link for the file here.


• Please do not PM me asking for support. Post on the forums instead it will increases the chances of getting help for your problem by one of us.
• Posts in the Malware section that are not replied to within 4 days will be closed. PM me or a moderator to reactivate.
• Please post your final results, good or bad. We like to know! Thank you!

 
Proud graduate of GeekU and member of UNITE
___
Rui

 
 


#4 Aleonymous

Aleonymous
  • Topic Starter

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:07:20 PM

Posted 07 December 2018 - 10:18 AM

Well, here it comes: I download the SUR tool (500MB+), and when I double click on the .msu file it attempts to start but stops with the error msg/popup:

 

[Windows Update Standalone Installer] Installer encountered an error: 0x8007000d. The data is invalid. [OK]

 

Here is the generated log file:

 

 
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2018-11-15 17:29
 
Checking Windows Servicing Packages
 
Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_788_for_KB4041681~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1: :Ý
 
Checking Package Watchlist
 
Checking Component Watchlist
 
Checking Packages
 
Checking Component Store
(f) CSI Manifest Zero Length 0x00000000 winsxs\Manifests\amd64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.23841_none_db3ef4a792632281.manifest amd64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.23841_none_db3ef4a792632281 
(f) CSI Manifest Zero Length 0x00000000 winsxs\Manifests\amd64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.23841_none_995952ebac8d7332.manifest amd64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.23841_none_995952ebac8d7332 
(f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\amd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.1.7601.24059_none_e96409dbb99f5771.manifest amd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.1.7601.24059_none_e96409dbb99f5771 
(f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\amd64_microsoft-windows-ie-setup_31bf3856ad364e35_11.2.9600.18952_none_7b63ec725cfbb726.manifest amd64_microsoft-windows-ie-setup_31bf3856ad364e35_11.2.9600.18952_none_7b63ec725cfbb726 
 
Summary:
Seconds executed: 938
 Found 5 errors
  CSI Manifest Zero Length Total count: 2
  CSI Manifest Failed Catalog Check Total count: 2
  CBS MUM Corrupt Total count: 1
 
Unavailable repair files:
winsxs\manifests\amd64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.23841_none_db3ef4a792632281.manifest
winsxs\manifests\amd64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.23841_none_995952ebac8d7332.manifest
winsxs\manifests\amd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.1.7601.24059_none_e96409dbb99f5771.manifest
winsxs\manifests\amd64_microsoft-windows-ie-setup_31bf3856ad364e35_11.2.9600.18952_none_7b63ec725cfbb726.manifest
servicing\packages\Package_788_for_KB4041681~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_788_for_KB4041681~31bf3856ad364e35~amd64~~6.1.1.0.cat
 
Customer Experience report successfully uploaded.  Thank you for participating.  For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.

Edited by Aleonymous, 07 December 2018 - 10:21 AM.


#5 SleepyDude

SleepyDude

  • Malware Response Team
  • 3,195 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Portugal
  • Local time:05:20 PM

Posted 07 December 2018 - 10:35 AM

Hi,

 

The log isn't from today! but lets try this...

 

Install Update using Dism

  • Please download KB4041681 http://download.windowsupdate.com/c/msdownload/update/software/secu/2017/09/windows6.1-kb4041681-x64_6d9242a96d4f1bbea20b8d05ee07db2b91654d72.msu save the file to c:\windows\temp
  • change the name of the update file to a smaller name windows6.1-KB4041681-x64.msu
    (keep the extension .msu in the end of the file name in case its visible if not ignore that)
  • open the Command Prompt as Administrator (Tutorial)
  • type or Copy & Paste the following commands line by line:

    cd  /d  c:\windows\temp
    expand  windows6.1-KB4041681-x64.msu  -f:*  C:\windows\temp
    DISM.exe  /Online  /Add-Package  /PackagePath:C:\windows\temp\windows6.1-KB4041681-x64.cab
     
  • You should receive the message:
    The operation completed successfully.
    Restart Windows to complete this operation.
    Do you want to restart the computer now (Y/N)?
  • Make sure to allow the computer to restart if prompted.

    If you receive any other message:
  • Right-click on the Command Prompt window and click Select All, this will invert all of the colours by selecting the text, now press enter. All of this text is now copied.
  • Paste (Ctrl+V) it into your next post please.

 


• Please do not PM me asking for support. Post on the forums instead it will increases the chances of getting help for your problem by one of us.
• Posts in the Malware section that are not replied to within 4 days will be closed. PM me or a moderator to reactivate.
• Please post your final results, good or bad. We like to know! Thank you!

 
Proud graduate of GeekU and member of UNITE
___
Rui

 
 


#6 Aleonymous

Aleonymous
  • Topic Starter

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:07:20 PM

Posted 07 December 2018 - 10:44 AM

Hello again (also: many thanks for helping me!)

 

No luck, again. It crashed with an error. Here's the CMD output:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
 
C:\Users\Administrator>cd\
 
C:\>cd windows
 
C:\Windows>cd temp
 
C:\Windows\Temp>expand mypack.msu -f:* c:\windows\temp
Microsoft (R) File Expansion Utility  Version 6.1.7600.16385
Copyright (c) Microsoft Corporation. All rights reserved.
 
Adding c:\windows\temp\WSUSSCAN.cab to Extraction Queue
Adding c:\windows\temp\Windows6.1-KB4041681-x64.cab to Extraction Queue
Adding c:\windows\temp\Windows6.1-KB4041681-x64-pkgProperties.txt to Extraction
Queue
Adding c:\windows\temp\Windows6.1-KB4041681-x64.xml to Extraction Queue
 
Expanding Files ....
Progress: 1 out of 4 files
Expanding Files Complete ...
4 files total.
 
C:\Windows\Temp>DISM.exe /Online /Add-Package /PackagePath:C:\windows\temp\windo
ws6.1-KB4041681-x64.cab
 
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
 
Image Version: 6.1.7601.18489
 
Processing 1 of 1 -
An error occurred - Package_for_RollupFix Error: 0x800f0900
 
Error: 0x800f0900
 
DISM failed. No operation was performed.
For more information, review the log file.
 
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
 
C:\Windows\Temp>


#7 SleepyDude

SleepyDude

  • Malware Response Team
  • 3,195 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Portugal
  • Local time:05:20 PM

Posted 07 December 2018 - 10:49 AM

  • Download SFCFix.exe (by Niemiro) and save it to the Desktop
  • Run SFCFix (accept the security warning and follow the instructions on the screen)
  • Upon completion, a log file SFCFix.txt should be created on your Desktop
  • Attach the SFCFix.txt log to your post

• Please do not PM me asking for support. Post on the forums instead it will increases the chances of getting help for your problem by one of us.
• Posts in the Malware section that are not replied to within 4 days will be closed. PM me or a moderator to reactivate.
• Please post your final results, good or bad. We like to know! Thank you!

 
Proud graduate of GeekU and member of UNITE
___
Rui

 
 


#8 Aleonymous

Aleonymous
  • Topic Starter

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:07:20 PM

Posted 07 December 2018 - 11:04 AM

It concluded its work (no crashes), but I'm not sure everything went as planned. Here's the (quite small) TXT output file:

 

SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-12-07 17:50:20.338
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Not using a script file.
 
 
 
 
AutoAnalysis::
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
   CBS & SFC total detected corruption count:     0
   CBS & SFC total unimportant corruption count:  0
   CBS & SFC total fixed corruption count:        0
   SURT total detected corruption count:          5
   SURT total unimportant corruption count:       0
   SURT total fixed corruption count:             0
AutoAnalysis:: directive completed successfully.
 
 
 
 
Successfully processed all directives.
 
 
 
Failed to generate a complete zip file. Upload aborted.
 
 
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2018-12-07 18:02:56.323
----------------------EOF-----------------------


#9 SleepyDude

SleepyDude

  • Malware Response Team
  • 3,195 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Portugal
  • Local time:05:20 PM

Posted 07 December 2018 - 11:18 AM

The log didn't show the corrupted files but we have them on the other old log...

 

Run SFC /scannow and wait to finish, next

 

 

Export the CBS folder

  • Open the folder C:\Windows\Logs
  • Right-click on the CBS folder, and select Copy
  • Go back to your Desktop, right-click on it, and select Paste. You should now see a copy of the CBS folder appear on your Desktop called CBS
  • Right-click on this new folder, and navigate through Send to, and select Compressed (zipped) folder
  • A new file, also called CBS (CBS.zip), but this time with a different icon, will be created
    If zip file is too large to upload to the forum please share the file using a service like Dropbox, Google Drive, OneDrive or upload to SendSpace and just provide the link for the file here.

 


• Please do not PM me asking for support. Post on the forums instead it will increases the chances of getting help for your problem by one of us.
• Posts in the Malware section that are not replied to within 4 days will be closed. PM me or a moderator to reactivate.
• Please post your final results, good or bad. We like to know! Thank you!

 
Proud graduate of GeekU and member of UNITE
___
Rui

 
 


#10 Aleonymous

Aleonymous
  • Topic Starter

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:07:20 PM

Posted 07 December 2018 - 11:28 AM

Done. Here's a dropbox link to the compressed CBS folder: https://www.dropbox.com/s/hkiakr092fcxhwu/CBS.zip?dl=0 (60MB)

 

In the folder, there were 4 large .cab files and 5 ascii logs. I ran this tool several times in the past weeks too, so the main CBS.log file is rather large.



#11 Aleonymous

Aleonymous
  • Topic Starter

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:07:20 PM

Posted 07 December 2018 - 11:52 AM

@SleepyDude -- Week is done (Greece here), I am going to commute home now and I probably won't respond much during the weekend. I can remotely access this computer, so I proceed this troubleshooting, but less vigorously until Monday. Thanks again for your time!  :bowdown:  



#12 SleepyDude

SleepyDude

  • Malware Response Team
  • 3,195 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Portugal
  • Local time:05:20 PM

Posted 07 December 2018 - 12:05 PM

Thanks for the update.

 

I have to check the logs and create a fix for you so it will take some time...


• Please do not PM me asking for support. Post on the forums instead it will increases the chances of getting help for your problem by one of us.
• Posts in the Malware section that are not replied to within 4 days will be closed. PM me or a moderator to reactivate.
• Please post your final results, good or bad. We like to know! Thank you!

 
Proud graduate of GeekU and member of UNITE
___
Rui

 
 


#13 SleepyDude

SleepyDude

  • Malware Response Team
  • 3,195 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Portugal
  • Local time:05:20 PM

Posted 08 December 2018 - 01:33 PM

Hi,

 

Lets do some fixing...


!!! WARNING !!! The following fix is only relevant for this system and no other, applying this fix on another computer will not work and most likely will cause problems...

  • Download SFCFix.exe (by Niemiro) and save it to the Desktop
  • Download the file Aleonymous1.zip and save this to your Desktop
  • On your Desktop, make sure you have the two files: myjIXnC.pngSFCFix.exe and sfpcJCen14An3ndjNGCI7mByhjHJud.png Aleonymous1.zip
  • Drag the file Aleonymous1.zip onto the file SFCFix.exe and release it
  • The SFCFix tool will process the script
  • Upon completion, a log file SFCFix.txt should be created on your Desktop
  • Open the SFCFix.txt log and copy & paste the contents to your post

 

After executing the fix please run SFC /scannow again and let me know the result.


• Please do not PM me asking for support. Post on the forums instead it will increases the chances of getting help for your problem by one of us.
• Posts in the Malware section that are not replied to within 4 days will be closed. PM me or a moderator to reactivate.
• Please post your final results, good or bad. We like to know! Thank you!

 
Proud graduate of GeekU and member of UNITE
___
Rui

 
 


#14 Aleonymous

Aleonymous
  • Topic Starter

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:07:20 PM

Posted 09 December 2018 - 10:01 AM

Alright, downloaded this ZIP (Chrome would't let me, so I used FF) and ran it through SFCFix. It was super-fast and produced this, apparently successful, log:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-12-09 16:52:08.174
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Using .zip script file at C:\Users\Administrator\Desktop\HDD crisis\OS failing\Aleonymous1.zip [0]
 
 
 
 
PowerCopy::
Successfully took permissions for file or folder C:\Windows\servicing\Packages\package_788_for_kb4041681~31bf3856ad364e35~amd64~~6.1.1.0.cat
Successfully took permissions for file or folder C:\Windows\servicing\Packages\package_788_for_kb4041681~31bf3856ad364e35~amd64~~6.1.1.0.mum
Successfully took permissions for file or folder C:\Windows\WinSxS\x86_wcf-m_sm_mof_31bf3856ad364e35_6.1.7601.24213_none_c701878cf7860174\servicemodel.mof
Successfully took permissions for file or folder C:\Windows\WinSxS\x86_wcf-m_sm_mof_31bf3856ad364e35_6.1.7601.24213_none_c701878cf7860174\servicemodel.mof.uninstall
Successfully took permissions for file or folder C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-ie-setup_31bf3856ad364e35_11.2.9600.18952_none_7b63ec725cfbb726.manifest
Successfully took permissions for file or folder C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.23841_none_995952ebac8d7332.manifest
Successfully took permissions for file or folder C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.23841_none_db3ef4a792632281.manifest
Successfully took permissions for file or folder C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.1.7601.24059_none_e96409dbb99f5771.manifest
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_netfx-mscorwks_dll_b03f5f7f11d50a3a_6.1.7601.24255_none_a842c347f0addbab\mscorwks.dll
 
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\Packages\package_788_for_kb4041681~31bf3856ad364e35~amd64~~6.1.1.0.cat to C:\Windows\servicing\Packages\package_788_for_kb4041681~31bf3856ad364e35~amd64~~6.1.1.0.cat.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\Packages\package_788_for_kb4041681~31bf3856ad364e35~amd64~~6.1.1.0.mum to C:\Windows\servicing\Packages\package_788_for_kb4041681~31bf3856ad364e35~amd64~~6.1.1.0.mum.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\Winsxs\x86_wcf-m_sm_mof_31bf3856ad364e35_6.1.7601.24213_none_c701878cf7860174\servicemodel.mof to C:\Windows\WinSxS\x86_wcf-m_sm_mof_31bf3856ad364e35_6.1.7601.24213_none_c701878cf7860174\servicemodel.mof.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\Winsxs\x86_wcf-m_sm_mof_31bf3856ad364e35_6.1.7601.24213_none_c701878cf7860174\servicemodel.mof.uninstall to C:\Windows\WinSxS\x86_wcf-m_sm_mof_31bf3856ad364e35_6.1.7601.24213_none_c701878cf7860174\servicemodel.mof.uninstall.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\Winsxs\Manifests\amd64_microsoft-windows-ie-setup_31bf3856ad364e35_11.2.9600.18952_none_7b63ec725cfbb726.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-ie-setup_31bf3856ad364e35_11.2.9600.18952_none_7b63ec725cfbb726.manifest.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\Winsxs\Manifests\amd64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.23841_none_995952ebac8d7332.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.23841_none_995952ebac8d7332.manifest.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\Winsxs\Manifests\amd64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.23841_none_db3ef4a792632281.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.23841_none_db3ef4a792632281.manifest.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\Winsxs\Manifests\amd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.1.7601.24059_none_e96409dbb99f5771.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.1.7601.24059_none_e96409dbb99f5771.manifest.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\Winsxs\amd64_netfx-mscorwks_dll_b03f5f7f11d50a3a_6.1.7601.24255_none_a842c347f0addbab\mscorwks.dll to C:\Windows\WinSxS\amd64_netfx-mscorwks_dll_b03f5f7f11d50a3a_6.1.7601.24255_none_a842c347f0addbab\mscorwks.dll.
 
Successfully restored ownership for C:\Windows\servicing\Packages\package_788_for_kb4041681~31bf3856ad364e35~amd64~~6.1.1.0.cat
Successfully restored permissions on C:\Windows\servicing\Packages\package_788_for_kb4041681~31bf3856ad364e35~amd64~~6.1.1.0.cat
Successfully restored ownership for C:\Windows\servicing\Packages\package_788_for_kb4041681~31bf3856ad364e35~amd64~~6.1.1.0.mum
Successfully restored permissions on C:\Windows\servicing\Packages\package_788_for_kb4041681~31bf3856ad364e35~amd64~~6.1.1.0.mum
Successfully restored ownership for C:\Windows\WinSxS\x86_wcf-m_sm_mof_31bf3856ad364e35_6.1.7601.24213_none_c701878cf7860174\servicemodel.mof
Successfully restored permissions on C:\Windows\WinSxS\x86_wcf-m_sm_mof_31bf3856ad364e35_6.1.7601.24213_none_c701878cf7860174\servicemodel.mof
Successfully restored ownership for C:\Windows\WinSxS\x86_wcf-m_sm_mof_31bf3856ad364e35_6.1.7601.24213_none_c701878cf7860174\servicemodel.mof.uninstall
Successfully restored permissions on C:\Windows\WinSxS\x86_wcf-m_sm_mof_31bf3856ad364e35_6.1.7601.24213_none_c701878cf7860174\servicemodel.mof.uninstall
Successfully restored ownership for C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-ie-setup_31bf3856ad364e35_11.2.9600.18952_none_7b63ec725cfbb726.manifest
Successfully restored permissions on C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-ie-setup_31bf3856ad364e35_11.2.9600.18952_none_7b63ec725cfbb726.manifest
Successfully restored ownership for C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.23841_none_995952ebac8d7332.manifest
Successfully restored permissions on C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.23841_none_995952ebac8d7332.manifest
Successfully restored ownership for C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.23841_none_db3ef4a792632281.manifest
Successfully restored permissions on C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.23841_none_db3ef4a792632281.manifest
Successfully restored ownership for C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.1.7601.24059_none_e96409dbb99f5771.manifest
Successfully restored permissions on C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.1.7601.24059_none_e96409dbb99f5771.manifest
Successfully restored ownership for C:\Windows\WinSxS\amd64_netfx-mscorwks_dll_b03f5f7f11d50a3a_6.1.7601.24255_none_a842c347f0addbab\mscorwks.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_netfx-mscorwks_dll_b03f5f7f11d50a3a_6.1.7601.24255_none_a842c347f0addbab\mscorwks.dll
PowerCopy:: directive completed successfully.
 
 
 
 
Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 9 datablocks.
Finish time: 2018-12-09 16:52:10.719
Script hash: 6wGuhEMJYJNENCUCEecpP4nY1Xp25HKMIoBfw6BMgpI=
----------------------EOF-----------------------


#15 Aleonymous

Aleonymous
  • Topic Starter

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:07:20 PM

Posted 09 December 2018 - 10:02 AM

The SFC /scannow was also 100% complete and "clean" (no violations).  Server manager opens normally. I am not rebooting to see if the other stuff are also fixed...






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users