14279 Windows 10 Resource Protection Couldn't Start Repair Service

just upgraded to insider 14279 went quite smoothly no real issues but  every time i try sfc /scannow now i get a message  "resource protection couldnt start repair service "

tried net start trustinstaller but still get the same error

|
Answer
Answer

Not yet...

Microsoft does not reply directly to insider feedback, it is just one way in, our feedback to them.

I usually just wait for the next insider build and they list the known issues in the hub

or sometimes a tweeter message to Gabe gets a quicker response.

I have tested it on four systems, both with & without clean installs and it is defiantly broken.

I have tried safe mode, booting with ISO command prompt mode both online and offline commands,

in powershell, enabling trustinstaller, etc all do not work.

Definately broken, here's my CBS log-

2016-03-08 20:11:27, Info                  CBS    TI: --- Initializing Trusted Installer ---
2016-03-08 20:11:27, Info                  CBS    TI: Last boot time: 2016-03-08 16:29:22.554
2016-03-08 20:11:27, Info                  CBS    Starting TrustedInstaller initialization.
2016-03-08 20:11:27, Info                  CBS    Ending TrustedInstaller initialization.
2016-03-08 20:11:27, Info                  CBS    Starting the TrustedInstaller main loop.
2016-03-08 20:11:27, Info                  CBS    TrustedInstaller service starts successfully.
2016-03-08 20:11:27, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart
2016-03-08 20:11:27, Info                  CBS    Startup processing thread terminated normally
2016-03-08 20:11:27, Info                  CBS    Starting TiWorker initialization.
2016-03-08 20:11:27, Info                  CBS    Ending TiWorker initialization.
2016-03-08 20:11:27, Info                  CBS    Starting the TiWorker main loop.
2016-03-08 20:11:27, Info                  CBS    TiWorker starts successfully.
2016-03-08 20:11:27, Info                  CBS    TiWorker: Client requests SFP repair object.
2016-03-08 20:11:27, Info                  CBS    Universal Time is: 2016-03-08 20:11:27.648
2016-03-08 20:11:27, Info                  CBS    Loaded Servicing Stack v10.0.14279.1000 with Core: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14279.1000_none_25a158fc7f85c69d\cbscore.dll
2016-03-08 20:11:27, Info                  CSI    00000001@2016/3/8:20:11:27.710 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffe67446c49 @0x7ffe677716b8 @0x7ffe67771acf @0x7ff6291c2ef8 @0x7ff6291c3c67 @0x7ffe918112f3)
2016-03-08 20:11:27, Info                  CBS    NonStart: Set pending store consistency check.
2016-03-08 20:11:27, Info                  CBS    Failed to load sfp DLL from path: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14279.1000_none_25a158fc7f85c69d\\wrpint.dll [HRESULT = 0x800700c1 - ERROR_BAD_EXE_FORMAT]
2016-03-08 20:11:27, Info                  CBS    Failed to initialize WRP integrity check and repair. [HRESULT = 0x800700c1 - ERROR_BAD_EXE_FORMAT]
2016-03-08 20:11:27, Info                  CBS    TiWorker: Client requests SFP repair object.
2016-03-08 20:11:27, Info                  CBS    Failed to load sfp DLL from path: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14279.1000_none_25a158fc7f85c69d\\wrpint.dll [HRESULT = 0x800700c1 - ERROR_BAD_EXE_FORMAT]
2016-03-08 20:11:27, Info                  CBS    Failed to initialize WRP integrity check and repair. [HRESULT = 0x800700c1 - ERROR_BAD_EXE_FORMAT]
2016-03-08 20:11:27, Info                  CBS    Failed to get class factory for service: 1 [HRESULT = 0x800700c1]
2016-03-08 20:13:27, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2016-03-08 20:13:27, Info                  CBS    TiWorker signaled for shutdown, going to exit.
2016-03-08 20:13:27, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2016-03-08 20:13:27, Info                  CBS    Ending the TiWorker main loop.
2016-03-08 20:13:27, Info                  CBS    Starting TiWorker finalization.
2016-03-08 20:13:27, Info                  CBS    CbsCoreFinalize: ManifestCacheFinalize
2016-03-08 20:13:27, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2016-03-08 20:13:27, Info                  CBS    CbsCoreFinalize: ComponentAnalyzerFinalize
2016-03-08 20:13:27, Info                  CBS    CbsCoreFinalize: PackageTrackerFinalize
2016-03-08 20:13:27, Info                  CBS    CbsCoreFinalize: CoreResourcesUnload
2016-03-08 20:13:27, Info                  CBS    CbsCoreFinalize: SessionManagerFinalize
2016-03-08 20:13:27, Info                  CBS    CbsCoreFinalize: CapabilityManagerFinalize
2016-03-08 20:13:27, Info                  CBS    CbsCoreFinalize: PublicObjectMonitorFinalize
2016-03-08 20:13:27, Info                  CBS    CbsCoreFinalize: Enter vCoreInitializeLock
2016-03-08 20:13:27, Info                  CBS    CbsCoreFinalize: WcpUnload
2016-03-08 20:13:27, Info                  CBS    CbsCoreFinalize: DrupUnload
2016-03-08 20:13:27, Info                  CBS    CbsCoreFinalize: CfgMgr32Unload
2016-03-08 20:13:27, Info                  CBS    CbsCoreFinalize: DpxUnload
2016-03-08 20:13:27, Info                  CBS    CbsCoreFinalize: SrUnload
2016-03-08 20:13:27, Info                  CBS    CbsCoreFinalize: CbsEsdUnload
2016-03-08 20:13:27, Info                  CBS    CbsCoreFinalize: CbsTraceInfoUninitialize
2016-03-08 20:13:27, Info                  CBS    CbsCoreFinalize: CbsEventUnregister
2016-03-08 20:13:27, Info                  CBS    CbsCoreFinalize: AppContainerUnload
2016-03-08 20:13:27, Info                  CBS    CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2016-03-08 20:13:27, Info                  CBS    Ending TiWorker finalization.
2016-03-08 20:13:27, Info                  CBS    Ending the TrustedInstaller main loop.
2016-03-08 20:13:27, Info                  CBS    Starting TrustedInstaller finalization.
2016-03-08 20:13:27, Info                  CBS    Ending TrustedInstaller finalization.

If you have done the copy file procedure of mine above then you have mistakenly copied the X86 version of the file over as I have just replicated your log file on my own PC.

You need the X64 version from the AMD64 Onecore Servicing file 

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info


Last updated February 2, 2021 Views 6,006 Applies to: