Unable to mount the source .wim file.
Hi
I have just purchased an asus laptop win10 with a ssd drive. I now realise the bios is completely different to those 10 years ago.
one of the first things i decided to do was a drive image. I am trying the 30 day trial and have not backed up yet as when i try to create a recovery usb i get unable to mount wim file. i also tried create iso and same error. i turned off safeboot in bios and the same.
here is the log (i think)
2019-01-13T01:35:06:084+00:00 11868 I00000000: -----
2019-01-13T01:35:06:084+00:00 11868 I00000000: Application started. Version: 23.4.1.14690.
2019-01-13T01:35:06:662+00:00 11868 I00000000: GetDisplayInfo succeeded: DPI: 96, scaling: 100%. Monitors: Resolution: 1366x768, work area: 1366x728, physical DPI: 101.
2019-01-13T01:35:06:662+00:00 11868 W00000000: EnableHiDpiScaling - console doesn't fit monitor resolution with system scaling. Set scale to 1.
2019-01-13T01:35:35:669+00:00 9992 I00180000: Bootable media type: WinPE-based media with Acronis software
Target media: removable disk
2019-01-13T01:35:35:701+00:00 9992 I00180000: Copying source .wim file...
2019-01-13T01:35:36:757+00:00 9992 I00180000: Mounting .wim file...
2019-01-13T01:35:37:305+00:00 9992 E00180000: Error 0x180021: Unable to mount the source .wim file.
| line: 0xaa76ebb96e7153b9
| file: c:\bs_hudson\workspace\646\products\imager\home\builder\logic\impl\utils_winpe.cpp:1767
| function: TrueImage::MediaBuilder::WinpeMediaBuilder::ProceedWithWIM
| line: 0xaa76ebb96e7153b9, c:\bs_hudson\workspace\646\products\imager\home\builder\logic\impl\utils_winpe.cpp:1767, TrueImage::MediaBuilder::WinpeMediaBuilder::ProceedWithWIM
| $module: ti_managers_vs_14690
|
| error 0xfff0: The system cannot find the path specified.
|
| line: 0xaa76ebb96e714e15
| file: c:\bs_hudson\workspace\646\products\imager\home\builder\logic\impl\utils_winpe.cpp:323
| function: `anonymous-namespace'::WIMMounter::MountWIMImage
| line: 0xaa76ebb96e714e15, c:\bs_hudson\workspace\646\products\imager\home\builder\logic\impl\utils_winpe.cpp:323, `anonymous-namespace'::WIMMounter::MountWIMImage
| code: 0x3
| $module: ti_managers_vs_14690
2019-01-13T01:35:50:367+00:00 10976 I00000000: -----
2019-01-13T01:35:50:367+00:00 10976 I00000000: Application started. Version: 23.4.1.14690.
2019-01-13T01:35:50:539+00:00 10976 I00000000: GetDisplayInfo succeeded: DPI: 96, scaling: 100%. Monitors: Resolution: 1366x768, work area: 1366x728, physical DPI: 101.
2019-01-13T01:35:50:539+00:00 10976 W00000000: EnableHiDpiScaling - console doesn't fit monitor resolution with system scaling. Set scale to 1.
2019-01-13T01:36:44:272+00:00 12760 I00180000: Bootable media type: WinPE-based media with Acronis software
Target media: ISO file
Image location: D:\temp\AcronisBootablePEMedia.iso
2019-01-13T01:36:44:303+00:00 12760 I00180000: Adding MS loader...
2019-01-13T01:36:44:303+00:00 12760 I00180000: Copying source .wim file...
2019-01-13T01:36:45:303+00:00 12760 I00180000: Mounting .wim file...
2019-01-13T01:36:45:849+00:00 12760 E00180000: Error 0x180021: Unable to mount the source .wim file.
| line: 0xaa76ebb96e7153b9
| file: c:\bs_hudson\workspace\646\products\imager\home\builder\logic\impl\utils_winpe.cpp:1767
| function: TrueImage::MediaBuilder::WinpeMediaBuilder::ProceedWithWIM
| line: 0xaa76ebb96e7153b9, c:\bs_hudson\workspace\646\products\imager\home\builder\logic\impl\utils_winpe.cpp:1767, TrueImage::MediaBuilder::WinpeMediaBuilder::ProceedWithWIM
| $module: ti_managers_vs_14690
|
| error 0xfff0: The system cannot find the path specified.
|
| line: 0xaa76ebb96e714e15
| file: c:\bs_hudson\workspace\646\products\imager\home\builder\logic\impl\utils_winpe.cpp:323
| function: `anonymous-namespace'::WIMMounter::MountWIMImage
| line: 0xaa76ebb96e714e15, c:\bs_hudson\workspace\646\products\imager\home\builder\logic\impl\utils_winpe.cpp:323, `anonymous-namespace'::WIMMounter::MountWIMImage
| code: 0x3
| $module: ti_managers_vs_14690
Attachment | Size |
---|---|
ti_media_builder.0.log | 3.44 KB |


- Log in to post comments

Hi Steve,
I solved it by using windows reset to go back to factory image. Then when I installed the trial I could create a boot usb and do a back up.
I did try macrium before ATI as it was free, but it fell over so I uninstalled and tried ATI. Maybe this was why. I have now purchased ATI.
Ok just hope if it comes to it it works, as you don't know until it's disaster time.
My previous laptop is over 10 years old, although I have win 10 on that, I was hoping the usb key that boots that would have worked, but these new bioses are a real pain...
- Log in to post comments

David, thanks for the update and glad to read that all is now back to working correctly after doing the factory reset. Your USB boot media should be able to work with both your old & new laptops as it supports both Legacy and UEFI boot modes.
It is always good to test that you can boot from the USB media and that you are able to access both the internal laptop drive and your external backup drive.
- Log in to post comments

Hi again
I tried booting it on my old laptop, it sat there with a blinking cursor.
When I created it I just used the recommended option for your pc (the new one)
- Log in to post comments

The media will take awhile to fully load you must be patient. This can take several minutes in some cases. Since you created the media on a different computer and you used the "recommended for your pc option then you should have a WinRE media rather than a WinPE media. So the WinRE media has drivers for computer it was created on where as the WinPE will not. In any case the media needs to locate the necessary drivers for your hardware and this can take some time so again, be patient.
- Log in to post comments

David, is your old laptop 32-bit or 64-bit - the new media is almost certainly 64-bit which wouldn't work on a 32-bit machine?
- Log in to post comments


David Asbury wrote:Yes 64 and 32. I gave it 15mins.
David, did the above mean the two laptops are different architectures, one 64 bit & one 32 bit?
- Log in to post comments

Hi Steve,
Yes, 1 or each architecture - i believe you answered why it won't work, because of this difference.
- Log in to post comments

David, thanks for confirming. In this case, the older Linux based rescue media version should work for both your laptops as this is 32-bit, and the alternative would be to use the MVP Custom ATIPE Builder tool which is able to make a 32-bit WinPE USB rescue stick which will also work on both laptops.
- Log in to post comments