Windows:SFC/SCANNOW:Windows 资源保护无法启动修复服务

Windows:SFC/SCANNOW:Windows 资源保护无法启动修复服务

我无法运行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

我还没有尝试在安全模式下运行它。

答案1

哇,我从来没有想到过这一点。我在评论中找到了答案。

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

我当时使用的是名为 console2 的 32 位控制台,并以管理员身份运行 - 非常令人沮丧,因为什么都没起作用。对我来说,这是链条中缺失的一环。真的很感激,因为这已经困扰了我好几个月了。微软真的应该用更有意义的错误消息来解决这个问题……我想知道有多少人因为误导性的错误消息而浪费了时间!

我也在使用 Console2。当我从糟糕的 Microsoft cmdshell(以管理员身份运行命令提示符)运行它时,它就正常工作了。

相关内容