It is in ATI2016 build 6559, and an error occurs.
It is in ATI2016 build 6559, and an error occurs.
I refer to the following links.
http://ameblo.jp/office-itou/entry-12153985220.html
Hello Steve Smith,
Firstly, please allow me to be a funny sentence because it is machine translation.
I installed ATI2016 after I performed clean install of Windows.
I customize AcronisBootablePEMedia.wim in MkWinPE.cmd made.
I use adksetup.exe build 10.1.10586.0.
winpe is ver.10.0.10586.0.
It occurs in build 6027.
Hello Jun,
Thank you for the additional information - if I understand correctly, it seems that you are building Windows PE Rescue Media but using MkWinPE to do this?
With ATIH 2016 you can create the Windows PE Rescue media directly within the application using the Bootable Rescue Media Builder utility found in the Tools folder - this will automatically include the necessary media add-ons and download the latest Windows 10 ADK if these are needed provided you have installed ATIH 2016 Build 6559. There is no need to use other PE builder commands such as MkWinPe.cmd.
If you want to customise the Acronis WinPE Rescue Media, please see the Guide to Add Drivers to WinPE Recovery Media in the Best Practices Forum
Hello Steve Smith,
Thank you for advice.
1.I made AcronisBootablePEMedia.wim in ATI2016 build 6559.
・"ツール"->"レスキューメディアビルダ"->"Acronisプラグインを含むWinPEベースのメディア"->"WIMファイル"->"保存"->"実行"
2.MkWinPE.cmd is additional handling of lack driver & Japanization.
I watched guide, but think that I do the same thing.
Hello Jun,
Can you test the Acronis Bootable PE Media as created by the Acronis media builder before customising it, to prove whether it works in the default configuration.
If it does, then you will need further help with doing further customisation, but perhaps again, you can separate this into smaller changes, i.e. to add in additional device drivers first, test if that works, then add in the changes for Japanization and test again. This would allow you to better isolate where the problem is coming from.
Hello Steve Smith,
It was for WinPE before the customization and tested it.
An error reproduced the result.
An abnormal partition appears in hdd when I carry out the linux 64bit version.
Hello Jun,
Please can you give more details of the steps that produce the error?
Are you booting from the WinPE media on DVD or USB stick?
Do you have an UEFI or MBR BIOS system?
Are you booting in the same mode as your Windows OS boots?
If Windows boots using UEFI, then you must boot the WinPE media also using UEFI.
Does the WinPE media boot to an Acronis desktop view with a CMD Window before launching the ATIH Rescue application?
Do you get the error during the boot process or after the ATIH application has launched?
If after the ATIH application has launched, what actions were you performing (Backup, Restore?).
Hello Steve Smith,
I added the hard copy of the practice example in VMware to the following links.
http://ameblo.jp/office-itou/entry-12153985220.html
It becomes in the same way in P5K-E.
The media does not change for the ISO image in the USB memory either.
Hello Jun,
Have you tried booting the Acronis WinPE media on a physical computer system instead of using VMware?
The error references a memory issue and VMware operates mainly in memory so this could be connected.
If I understand the issue correctly, you are attempting to run the Acronis DriveCleanser utility from the bootable WinPE rescue media running under VMware to wipe an 8GB (unallocated space) virtual drive and this is giving an application error for TrueImage.exe - The instruction at 0x00007FFDA83C9E7 referenced memory at 0x00000000857AA200. The memory could not be written.
I am not sure that this is a valid test environment for DriveCleanser especially as there is no actual define drive partition to be wiped.
If you can reproduce this error on a physical computer system with a real hard drive, then I would recommend submitting an Acronis System Report with details of the error to Acronis Support using the Feedback Tool in the ATIH GUI with reference to this forum post.
Hello Steve Smith,
Even a physical PC confirms that the same symptom comes out.
I feed back for support.
Thank you very much.
Because support was expired, an investigation request was not possible.
If the person whom an obstacle was able to reproduce in DriveCleanser comes, I investigate it, and would you depend?
http://ameblo.jp/office-itou/entry-12153985220.html
Even a physical PC reappears in us in the virtual environment.