Windows 10: Windows 10 Setup on Windows 7 fails, error 0x80070005, Failed to mount WIM file

I'm trying to upgrade my Windows 7 PC (Acer) to Windows 10 as admin user


I tried it with Windows 10 Upgrade Assistant, as well as with MediaCreation Tool (direct setup as well as setup from USB).


Setup always fails with error 0x80070005 allthough I even uninstalled my antivirus software before.


I followed all adwices to this error without success:

- fixIt for Winodws Update which fixed all but Windows 10 setup afterwards failed allthough

- checkdsk (no errors found)

- dism:

dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth


and also with sfc /scannow (no errors found)


I have examined the logfiles under C:\$WINDOWS.~BT\Sources\Panther and found the following entries in setuperr.log (see below).


What can I do to fix "failed to mount WIM file" (shown in setuperr.log)?

Do I have to fix the errors from these entries in setupact.log too?


Please help!!!

To install windows 10 new with losing personal data and apps is not an option for me...


Best regards

Johannes


Entries from setupact.log:

...

MOUPG CSystemHelper::CheckConnectedStandby(642): Result = 0x80070057
MOUPG SetupUI::BlockSystemSleep - CheckConnectedStandby failed: [0x80070057]
MOUPG FCAcquirerDCAT: Error on getting CTAC attributes: [0x8007007E]
Error CSI 00000001 (F) STATUS_OBJECT_NAME_NOT_FOUND #10# from Windows::Rtl::SystemImplementation:irectRegistryProvider::SysQueryValueKey(flags = 0, key = 6e4 ('\REGISTRY\MACHINE\SYSTEM\Setup'), vn = [l:7 ml:8]'Compact', kvic = 2, kvi = 2, disp = 0)[gle=0xd0000034]

...

Entries from setuerr.log:


2019-08-14 21:11:49, Error SP Error READ, 0x0000007E while gathering/applying object: post-scan, Action,CMXEPlugin,C:\$WINDOWS.~BT\Sources\ReplacementManifests,Microsoft-Client-License-Platform-Service-Migration\ClipMigPlugin.dll,{6014E67F-2537-48F9-951D-D29D720523E1},Apartment. Will return 2[gle=0x000000cb]
2019-08-14 21:12:02, Error SP Failed to test whether this device is connected standby. Error: 0xD000000D[gle=0x000000b7]
2019-08-14 21:12:02, Error SP Failed to test whether this device is connected standby. Error: 0xD000000D
2019-08-14 21:12:07, Error CSetupAutomation::Resurrect: File not found: C:\$WINDOWS.~BT\Sources\Panther\automation.dat[gle=0x00000002]
2019-08-14 21:12:07, Error SP CSetupPlatform::ResurrectAutomation: Failed to resurrect automation: 0x80070002[gle=0x00000002]
2019-08-14 21:12:15, Error SP CMountWIM:oExecute: Failed to mount WIM file C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim. Error 0x80070005[gle=0x00000005]
2019-08-14 21:12:16, Error SP Operation failed: Mount WIM file C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim, index 1 to C:\$WINDOWS.~BT\Sources\SafeOS\SafeOS.Mount. Error: 0x80070005[gle=0x000000b7]
2019-08-14 21:12:16, Error SP ExecuteOperations: Failed execution phase Pre-Finalize. Error: 0x80070005
2019-08-14 21:12:16, Error MOUPG MoSetupPlatform: ExecuteCurrentOperations reported failure!
2019-08-14 21:12:16, Error MOUPG MoSetupPlatform: Using action error code: [0x80070005]
2019-08-14 21:12:16, Error MOUPG CDlpActionPreFinalize::ExecuteRoutine(579): Result = 0x80070005
2019-08-14 21:12:16, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::Execute(493): Result = 0x80070005
2019-08-14 21:12:16, Error MOUPG CDlpTask::ExecuteAction(3300): Result = 0x80070005
2019-08-14 21:12:16, Error MOUPG CDlpTask::ExecuteActions(3454): Result = 0x80070005
2019-08-14 21:12:16, Error MOUPG CDlpTask::Execute(1631): Result = 0x80070005
2019-08-14 21:12:16, Error MOUPG CSetupManager::ExecuteTask(2574): Result = 0x80070005
2019-08-14 21:12:16, Error MOUPG CSetupManager::ExecuteTask(2537): Result = 0x80070005
2019-08-14 21:12:16, Error MOUPG CSetupManager::ExecuteInstallMode(904): Result = 0x80070005
2019-08-14 21:12:16, Error MOUPG CSetupManager::ExecuteDownlevelMode(392): Result = 0x80070005
2019-08-14 21:12:17, Error SP CDeploymentBase::CleanupMounts: Unable to unmount the directory C:\$WINDOWS.~BT\Sources\SafeOS\SafeOS.Mount. Error: 0xC142011C[gle=0xc142011c]
2019-08-14 21:12:20, Error MOUPG CSetupManager::Execute(284): Result = 0x80070005
2019-08-14 21:12:20, Error MOUPG CSetupHost::Execute(412): Result = 0x80070005


2019-08-14 21:12:17, Error SP CDeploymentBase::CleanupMounts: Unable to unmount the directory C:\$WINDOWS.~BT\Sources\SafeOS\SafeOS.Mount. Error: 0xC142011C[gle=0xc142011c]
2019-08-14 21:12:20, Error MOUPG CSetupManager::Execute(284): Result = 0x80070005
2019-08-14 21:12:20, Error MOUPG CSetupHost::Execute(412): Result = 0x80070005

:)

 

Windows 10 Update to ver 1903 fails

It looks like the Setup failed to mount the WIM File:

2019-06-15 22:16:23, Error SP CMountWIM:oExecute: Failed to mount WIM file C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim. Error 0xC1420121[gle=0xc1420121]

Do you have Windows Assessment and deployment kit installed which usually is why this error gets thrown?

 

System Restore Fails Error 0x80070005


So I try to restore any point and get an error:





I have turned off Malwarebytes and SuperAntiSpyware.

I also did a sfc /scannow with no integrity violations.

Running Windows 10 Pro 64bit... Any suggestions?

 

Windows 10 Creators Upgrade Error Failed to mount WIM file C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim. Error 0x800704FB[gle=0x000004fb]

Windows 10 pro creators upgrade fails with error message " Upgrade Error Failed to mount WIM file C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim. Error 0x800704FB" in setuperr.log. Tried almost everything onDid internet searches with no change-fails after 20%
before even the first boot.

Anyone know what this means, since I do not have a wim file on the installation media (usb thumb drive). Below are things I have tried with no success.

1. Tried installation from ISO /thumb drive and Windows upgrade tool.

2 Tried from clean boot

3. Uninstalled ALL security software except Defender.

Should note that my computer a dual boot system, consisting of one SSD with the PRO and the other with Home version. The update of the home version went flawlessly, while the Pro disk not as described above. During attempted upgrades only the target HD
was installed at one time. Both installation have vertually the same software.

Bbersted