Windows: SFC /SCANNOW: Windows Resource Protection не удалось запустить службу восстановления

Question

Я не могу запустить SFC . Как мне это исправить?

C:\>sfc /scannow

Windows Resource Protection could not start the repair service.

C:\>net start trustedinstaller
The requested service has already been started.

C:\>Dism /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Error: 11

You cannot service a running 64-bit operating system with a 32-bit version of DISM.
Please use the version of DISM that corresponds to your computer's architecture.

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

C:\>findstr /c:"[SR]" %windir%\logs\cbs\cbs.log

C:\>

Dism.log

2017-11-03 16:06:12, Info                  DISM   PID=6268 TID=3252 Scratch directory set to 'C:\Users\Chloe\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2017-11-03 16:06:12, Info                  DISM   PID=6268 TID=3252 DismCore.dll version: 6.3.9600.17031 - CDISMManager::FinalConstruct
2017-11-03 16:06:12, Info                  DISM   PID=6268 TID=3252 Successfully loaded the ImageSession at "C:\windows\System32\Dism" - CDISMManager::LoadLocalImageSession
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2017-11-03 16:06:12, Info                  DISM   DISM Manager: PID=6268 TID=3252 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2017-11-03 16:06:12, Info                  DISM   DISM.EXE: 
2017-11-03 16:06:12, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2017-11-03 16:06:12, Info                  DISM   DISM.EXE: 
2017-11-03 16:06:12, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.3.9600, Running architecture=x86, Number of processors=8
2017-11-03 16:06:12, Info                  DISM   DISM.EXE: Dism.exe version: 6.3.9600.17031
2017-11-03 16:06:12, Info                  DISM   DISM.EXE: Executing command line: Dism  /Online /Cleanup-Image /ScanHealth
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Loading Provider from location C:\windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Connecting to the provider located at C:\windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-11-03 16:06:12, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2017-11-03 16:06:12, Info                  DISM   DISM.EXE: 
2017-11-03 16:06:12, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2017-11-03 16:06:12, Info                  DISM   DISM.EXE: 
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

Я еще не пробовал запускать его в безопасном режиме.

Answer 1

Вау, я бы никогда этого не ожидал. Я нашел ответ в комментарии.

https://www.technipages.com/windows-fix-windows-resource-protection-could-not-start/comment-page-2#comment-875476

Я использовал 32-битную консоль с именем console2 и работал от имени администратора - чертовски разочаровал, потому что ничего не получалось. Для меня это было недостающее звено в цепи. Действительно благодарный человек, так как это беспокоило меня в течение многих месяцев. Microsoft действительно должна была поймать это с более значимым сообщением об ошибке… Интересно, сколько человеческих лет было потрачено впустую из вводящих в заблуждение сообщений об ошибках!

Я также использовал Console2. Когда я запускал его из дерьмовой оболочки Microsoft cmd (командная строка запускалась от имени администратора), то это работало.