[SOLVED] Windows 10 1709 unable to install updates

[lolmachine4]

Hi,

I've registered here because I got a feeling this is my last resort before I have to re-image that PC, which isn't an easy job on this particular machine (company's only HR PC, yey)
I am providing every log as requested in the "posting instructions" forum. Please understand that english is not my native language, so some things might get lost in translation.
The initial error that started me debugging this machine was a simple (so I thought) upgrade error number: 0x800706be. Seems to me after 4 hours this is not an easy fix...

Step#2: sfc does not run, I get the following error message (translated):
"Windows-Resourceprotection is not able to start this service".
Step #3: DISM does not run, I get the following error message (at 4.5%):
"The remote procedure call has failed".
Step #4: SFCFix finds 0 errors or files that need replacing.
Step #5: Logile is provided here:
Dropbox - CBS.log


Additional Infos:
- in Eventlog, I get a ton of messages that TIWorker has crashed, looking like this - sorry it's german, but I guess that doesn't matter, errors are universal:

Read More:

Name der fehlerhaften Anwendung: TiWorker.exe, Version: 10.0.16299.843, Zeitstempel: 0x8fa41fee
Name des fehlerhaften Moduls: wcp.dll, Version: 10.0.16299.843, Zeitstempel: 0x4324747f
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000012a245
ID des fehlerhaften Prozesses: 0x474
Startzeit der fehlerhaften Anwendung: 0x01d497ad931dcc49
Pfad der fehlerhaften Anwendung: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.16299.541_none_16e8222032163850\TiWorker.exe
Pfad des fehlerhaften Moduls: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.16299.541_none_16e8222032163850\wcp.dll
Berichtskennung: dd0799e1-6f8c-4532-a384-cb7cad50a9b9
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

- I've tried doing an InPlace-Upgrade to 1809 which failed after the 2nd reboot and reverted the machine back to 1709
- I've tried replacing the mentioned files above with known-good copies from a different machine, which didn't help either (yes, I restored the initial permissions back)
- I've disconnected the machine from WSUS and searched updates online with the same results
- It seems the machine last updated in June 2018 if that helps searching KB numbers
- Everything else on this machine runs perfectly except updates/upgrades
- I've updated every driver using SDIO

At this point, normally I would just scrap that thing entirely and re-install windows, but as usual, with special one-of-a-kind-PCs this isn't the fastest option here...

I hope the informations I have posted can get this fixed before I get the big hammer aka my USB KEY and format this thing :banghead:

kind regards

 

[lolmachine4]

UPDATE

Sorry for the doublepost, but I can't edit my first post, so I have to post my updates here.

While waiting for a reply from the experts, I tried different things to fix this myself.
- I've tried every SSU Update since Jun 2018 with a self-build SFCFix. The Fix was applied correctly, which I double checked, the "CREATED ON"-Date of the files changes for those filed I replaced
- Tried a Repair Install of the same OS (1709), same result as 1809
- Deinstalled all Antivirus-Software and cleaned it with the proper cleaning tool from the vendor
- Ran SFCFixScript for wcp.dll, which I will post here:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-12-20 13:16:55.228
Microsoft Windows 10 Build 16299 - amd64
Using .txt script file at C:\Users\WINDOWSUSERNAME\Desktop\SFCFixScript.txt [3]




FileScan::
[0: 1] C:\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.16299.15_none_d02cf1b780117c58\wcp.dll
File is untraceable.
 Found: 9k8jDpcMcKqEockERCpDjYopFC8ou+WpbTx3YYhVxzo=
 Found: 10.0.16299.15
Trace not available.



[1: 1] C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.16299.15_none_2c4b8d3b386eed8e\wcp.dll
File is untraceable.
 Found: w0V3b8XGKKbtYOoFd5DpBNPXhNu3Stfte30dWUzHvF0=
 Found: 10.0.16299.15
Trace not available.



[2: 1] C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.16299.456_none_16e251c03219d5cd\wcp.dll
File is untraceable.
 Found: 8ZLgmf7189Kng3rJoVoU2zPvxDf/INM7StVrI8+8i2g=
 Found: 10.0.16299.456
Trace not available.



[3: 1] C:\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.16299.456_none_bac3b63c79bc6497\wcp.dll
File is untraceable.
 Found: l60p5ew6Z+V+zt6YL8re2b0tmwJY772JDODcmp9jWwY=
 Found: 10.0.16299.456
Trace not available.



[4: 1] C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.16299.245_none_16ec1d963212a637\wcp.dll
File is untraceable.
 Found: 3KsLC2i8Xc6Gefjs/H6Md4ZvZkaURxLXSdoOnZlZkWg=
 Found: 10.0.16299.245
Trace not available.



[5: 1] C:\test\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.16299.782_none_16bde6863235bbb9\wcp.dll
File is untraceable.
 Found: qVSZryH1EQ0OEJOLYFEHQMjY5EGIPcYdQ2hNAZTWBT0=
 Found: 10.0.16299.782
Trace not available.



[6: 1] C:\test\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.16299.782_none_ba9f4b0279d84a83\wcp.dll
File is untraceable.
 Found: 2bv8dlLhRI2TPPG6MyseUbrnYg47K5+khegmBbv37JQ=
 Found: 10.0.16299.782
Trace not available.



[7: 1] C:\SFCFix\Backups\C\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.16299.541_none_16e8222032163850\wcp.dll
File is untraceable.
 Found: c0Df3ELNsc08Q3tNkFLrc7zYn3i3xWUDViYdjmnz2uE=
 Found: 10.0.16299.541
Trace not available.



[8: 1] C:\Users\WINDOWSUSERNAME\Desktop\Neuer Ordner (2)\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.16299.541_none_16e8222032163850\wcp.dll
File is untraceable.
 Found: UTRpcnYAXE4eUafVx1vT8FBofgQOFu6FzNNyf2iz4pk=
 Found: 10.0.16299.843
Trace not available.



[9: 1] C:\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.16299.541_none_bac9869c79b8c71a\wcp.dll
File is untraceable.
 Found: BzHVsf032XZD/PLU+GQK7kPkFIyIJpztvs3SC5iDnxI=
 Found: 10.0.16299.541
Trace not available.



[10: 1] C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.16299.541_none_16e8222032163850\wcp.dll
File is untraceable.
 Found: UTRpcnYAXE4eUafVx1vT8FBofgQOFu6FzNNyf2iz4pk=
 Found: 10.0.16299.843
Trace not available.



[11: 1] C:\$WINDOWS.~BT\NewOS\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.1_none_fa254b2e1f73e660\wcp.dll
File is untraceable.
 Found: yRrpSw9Rr/s2PXiskHg3AFh837a8+tRcmNAn7njoalQ=
 Found: 10.0.17763.1
Trace not available.



[12: 1] C:\$WINDOWS.~BT\NewOS\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.1_none_9e06afaa6716752a\wcp.dll
File is untraceable.
 Found: v+HmqSmYB2nYgnz/V4Ur0kPYsl+GaIZ9fsUuLBzvVt8=
 Found: 10.0.17763.1
Trace not available.
FileScan:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 30 datablocks.
Finish time: 2018-12-20 13:16:56.119
Script hash: 5W4O7M8f2532xWylFXSnUO/Lgr1EjZm8/fyYTE8z8II=
----------------------EOF-----------------------

This result has me wondering. This file clearly exists in this folder.

Hope this helps.

 

[lolmachine4]

Last update, as I fixed the issue myself. I can't believe this actually worked...
All that was needed was to perform a cleant boot (=disable all non-microsoft services at startup via msconfig). Now everything is running fine. I suspect one of our ancient legacy software was loading some weird old service that caused this.

 

[Sysnative Windows Update]

Great! Thanks for letting us know!