[SOLVED] Windows 10 Anniversary Update installation ends with error message 0x80070003

Martin2 · Aug 28, 2016

Hi,

I have a problem when installing the Anniversary Update (1607) of Windows 10 to my existing Windows 10 1511 version. I tried Windows Update, the Upgrade assistant and the Media Creation Tool. All tools start installing the update but end with an unspecified error or the error code 0x80070003. Google helped me to analyse the CBS.log file which pointed to several problems with corrupted Windows and Avast files. The Avast issues could be partly solved with deinstallation and the solution in this thread https://www.sysnative.com/forums/wi...avast-causing-corrupt-manifest-files-fix.html.

Nevertheless there is still one line left in the CBS.log regarding Avast:

"000058bd [SR] Cannot verify component files for Avast.VC110.CRT, version 11.0.60610.1, arch amd64, versionScope neutral, pkt {l:8 b:2036b14a11e83e4a}, type [l:5]"win32", manifest is damaged (FALSE)"

I could also fix lots of other issues by rebuilding the component store from the Windows installation iso file, but one issue is left which I cannot repair:

"2016-08-28 11:52:25, Error CSI 000058c2@2016/8/28:09:52:25.453 (F) base\wcp\componentstore\csd_core.cpp(666): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function CCSDirect::GetComponentManifest expression: (null) [gle=0x80004005]"

I ran the SFCfix tool, please see the CBS.log file and the file SFCFix.txt attached. Thank you in advance!

Best regards
Martin

Aura · Aug 31, 2016

Hi Martin2,

Do you still need assistance with this issue?

Martin2 · Aug 31, 2016

Hi Aura,

Yes, I don't know what to try next, I even tried an upgrade installation which failed with the same error. Thanks.

Aura · Sep 2, 2016

Sorry for the delay. By upgrade installation, do you mean an In-Place Upgrade, also known as Repair Install?

Martin2 · Sep 2, 2016

Yes, I tried the In-Place Upgrade. But this wasn't possible like I know it from Windows 7. I started the setup from the USB Stick created with the Media Creation Tool for Version Windows 10 Pro 1607 and followed the steps, but I didn't see this screen where I can choose "Upgrade" or "Custom". Is there another way for the In-Place-Upgrade?
Thanks.

Aura · Sep 2, 2016

You can mount the .iso directly, and execute the setup.exe within it to launch the In-Place Upgrade that way.

Martin2 · Sep 2, 2016

Same issue like with the installation from USB Stick:

Windows 10 Setup_2016-09-02_23-07-39.png

"Error during installation of Windows 10" without error code.

Aura · Sep 2, 2016

I see that you followed the instructions in the avast! thread, did you run the SFCFix script at the end? It looks to me like this key hasn't been deleted.

Code:

[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396]

Martin2 · Sep 3, 2016

Yes, I ran both scripts from post #1 and I don't have the whole subfolder "HKEY_LOCAL_MACHINE\COMPONENTS" anymore:

Aura · Sep 3, 2016

This is because the COMPONENTS Hive isn't loaded. Can you run the second SFCFix script again, and copy/paste the log here?

This one:

Code:

::
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396]

[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c]

[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.11.0.avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_b2556b4035446b41]

Martin2 · Sep 3, 2016

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-09-03 14:20:47.468
Microsoft Windows 10 Build 10586 - amd64
Using .txt script file at D:\Downloads\SFCFix\SFCFixScript.txt [0]

RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.11.0.avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_b2556b4035446b41.

Failed to delete registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396.
Failed to delete registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c.
Failed to delete registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.11.0.avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_b2556b4035446b41.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.11.0.avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_b2556b4035446b41.
RegistryScript:: directive failed to complete successfully.

Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2016-09-03 14:20:48.337
Script hash: /obSQMtMefLQkM13I9SCK2iXlUslj2V+2uxnIwHBhPw=
----------------------EOF-----------------------

Aura · Sep 3, 2016

Yeah, it failed to delete these entries. Download the following Script.reg and save it on your desktop. Double-click on it and accept to merge the changes in your Registry. Next you'll get either a success message, or an error one. Let me know which one you get and if it's an error one, let me know what it says.

Martin2 · Sep 3, 2016

It was successful and even better: sfc /scannow now states that the integrity check was successful. The log doesn't contain error lines anymore, just "Info". I will now try to update Windows 10 once again and let you know if it was successful.

Martin2 · Sep 3, 2016

Nope, I get still the error message 0x80070003 after ~85% of completion. I tried to upgrade with the Windows 10 Upgrade Assistant and didn't delete the cached files.

Aura · Sep 3, 2016

Are you able to do the In-Place Upgrade now, or not?

Martin2 · Sep 4, 2016

Same issue. I did the following steps:
1. I mounted the iso for Win10 64Bit, the setup.exe has the following version information:

2. Executed setup.exe and followed the setup screens:

Two screens are shown in between very shortly telling that the system will be restarted which it isn't. That's one of them, I couldn't catch the other:

Then it continues:

And then after 5 minutes, the error message from post #7 is shown.

The CBS.log looks fine:

Code:

2016-09-04 09:45:07, Info                  CBS    TI: --- Initializing Trusted Installer ---
2016-09-04 09:45:07, Info                  CBS    TI: Last boot time: 2016-09-03 21:08:37.492
2016-09-04 09:45:07, Info                  CBS    Starting TrustedInstaller initialization.
2016-09-04 09:45:07, Info                  CBS    Ending TrustedInstaller initialization.
2016-09-04 09:45:07, Info                  CBS    Starting the TrustedInstaller main loop.
2016-09-04 09:45:07, Info                  CBS    TrustedInstaller service starts successfully.
2016-09-04 09:45:07, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart
2016-09-04 09:45:07, Info                  CBS    Startup processing thread terminated normally
2016-09-04 09:45:07, Info                  CBS    Starting TiWorker initialization.
2016-09-04 09:45:07, Info                  CBS    Ending TiWorker initialization.
2016-09-04 09:45:07, Info                  CBS    Starting the TiWorker main loop.
2016-09-04 09:45:07, Info                  CBS    TiWorker starts successfully.
2016-09-04 09:45:07, Info                  CBS    Universal Time is: 2016-09-04 07:45:07.203
2016-09-04 09:45:07, Info                  CBS    Loaded Servicing Stack v10.0.10586.486 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10586.486_none_7640e086266ea227\cbscore.dll
2016-09-04 09:45:07, Info                  CSI    00000001@2016/9/4:07:45:07.219 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ff8931146d9 @0x7ff895bd2150 @0x7ff895bd1d2b @0x7ff70f402ee0 @0x7ff70f4038e1 @0x7ff8c596d533)
2016-09-04 09:45:07, Info                  CBS    NonStart: Set pending store consistency check.
2016-09-04 09:45:07, Info                  CBS    Session: 30541440_1099448250 initialized by client WindowsUpdateAgent, external staging directory: (null)
2016-09-04 09:47:07, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2016-09-04 09:47:07, Info                  CBS    TiWorker signaled for shutdown, going to exit.
2016-09-04 09:47:07, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2016-09-04 09:47:07, Info                  CBS    Ending the TiWorker main loop.
2016-09-04 09:47:07, Info                  CBS    Starting TiWorker finalization.
2016-09-04 09:47:07, Info                  CBS    CbsCoreFinalize: ManifestCacheFinalize
2016-09-04 09:47:07, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2016-09-04 09:47:07, Info                  CBS    CbsCoreFinalize: ComponentAnalyzerFinalize
2016-09-04 09:47:07, Info                  CBS    CbsCoreFinalize: PackageTrackerFinalize
2016-09-04 09:47:07, Info                  CBS    CbsCoreFinalize: CoreResourcesUnload
2016-09-04 09:47:07, Info                  CBS    CbsCoreFinalize: SessionManagerFinalize
2016-09-04 09:47:07, Info                  CBS    CbsCoreFinalize: CapabilityManagerFinalize
2016-09-04 09:47:07, Info                  CBS    CbsCoreFinalize: PublicObjectMonitorFinalize
2016-09-04 09:47:07, Info                  CBS    CbsCoreFinalize: Enter vCoreInitializeLock
2016-09-04 09:47:07, Info                  CBS    CbsCoreFinalize: WcpUnload
2016-09-04 09:47:07, Info                  CBS    CbsCoreFinalize: DrupUnload
2016-09-04 09:47:07, Info                  CBS    CbsCoreFinalize: CfgMgr32Unload
2016-09-04 09:47:07, Info                  CBS    CbsCoreFinalize: DpxUnload
2016-09-04 09:47:07, Info                  CBS    CbsCoreFinalize: SrUnload
2016-09-04 09:47:07, Info                  CBS    CbsCoreFinalize: CbsEsdUnload
2016-09-04 09:47:07, Info                  CBS    CbsCoreFinalize: CbsTraceInfoUninitialize
2016-09-04 09:47:07, Info                  CBS    CbsCoreFinalize: CbsEventUnregister
2016-09-04 09:47:07, Info                  CBS    CbsCoreFinalize: AppContainerUnload
2016-09-04 09:47:07, Info                  CBS    CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2016-09-04 09:47:07, Info                  CBS    Ending TiWorker finalization.
2016-09-04 09:47:07, Info                  CBS    Ending the TrustedInstaller main loop.
2016-09-04 09:47:07, Info                  CBS    Starting TrustedInstaller finalization.
2016-09-04 09:47:07, Info                  CBS    Ending TrustedInstaller finalization.

In the Windows event log I found the following time related error in the Application log:
"Bei der Aktivierung der App „Microsoft.Messaging_8wekyb3d8bbwe!ppleae38af2e007f4358a809ac99a64a67c1“ ist folgender Fehler aufgetreten: Der RPC-Server ist nicht verfügbar.. Weitere Informationen finden Sie im Protokoll „Microsoft-Windows-TWinUI/Betriebsbereit“."

In English this should be like:
"While executing the app "Microsoft.Messaging_8wekyb3d8bbwe!ppleae38af2e007f4358a809ac99a64a67c1" the following error occured: The RPC server is not available. Further information can be found in the protocol "Microsoft-Windows-TWinUI/Betriebsbereit".

Could this be a hint? Where can I find this protocol and was this a proper In-Place-Upgrade?
Thanks for your help so far!

Aura · Sep 4, 2016

The Windows Media Creation Tool you are using is for Windows 10 AU, not TH2, so you are actually trying to do an upgrade from TH2 to AU and not an "In-Place" upgrade. Follow the instructions below please.

Windows Repair All-In-One
NOTE: Before following to step below, please disable your Antivirus software or any other real-time security software that you have enabled.

Boot in Safe Mode with Networking;
Download the portable version of Windows Repair All-In-One;
Move the file (archive) on your Desktop, and extract it there;
Go in the tweaking.com_windows_repair_aio folder, then Tweaking.com - Windows Repair folder, right-click on Repair_Windows.exe and select Run as Administrator;
From there, click on the Next button until you are presented with an Open Repairs button and click on it;
Let the Registry back up complete, and move on to the check-list window;
Click on the Unselect All button at the bottom, then check the following items:
- Repair Windows Update
- Delete Temporary Files
Once done, click on the Start Repairs button and let the scan execute;
If you are being prompted with a Security Warning, allow it to go through;
Once the repair is complete, it'll ask you to restart your computer, please do it;

Martin2 · Sep 5, 2016

You're right, I tried the In-Place-Upgrade again with this mounted ISO:

But with the same result:

Then I followed the instructions of the Windows Repair All-In-One tool in safe mode, rebooted and executed the setup again, and I came to the screen:

So I uninstalled My Image Garden from the dialog, clicked on "Update" and...got the same error as shown above. I tried installing AU afterwards, but again with the same error. Windows Update doesn't find any updates. The CBS.log file is error-free.

Aura · Sep 8, 2016

Can you provide me these two logs?

C:\Windows\panther\setupact.log
C:\Windows\panther\setuperr.log

Martin2 · Sep 8, 2016

See here: http://home.arcor.de/missgadget/Panther.zip
I found them in C:\Windows\Panther\NewOs\Panther

[SOLVED] Windows 10 Anniversary Update installation ends with error message 0x80070003

Member

Attachments

Sysnative Staff, Security Analyst

Member

Sysnative Staff, Security Analyst

Member

Sysnative Staff, Security Analyst

Member

Sysnative Staff, Security Analyst

Member

Sysnative Staff, Security Analyst

Member

Sysnative Staff, Security Analyst

Member

Member

Sysnative Staff, Security Analyst

Member

Sysnative Staff, Security Analyst

Member

Sysnative Staff, Security Analyst

Member