Salta al contenuto principale

Help with MVPAssistant?

Thread solved

Hello, I would like to create rescue media. I have a Lenovo Legion laptop with an Intel i7 processor running 64 bit Win 10 Pro. I installed ADK for Windows v2004 and Windows PE add-on. I then ran the MVPATIBuilderv186. From the options in the MVP ATI builder, I chose the ADK method, 64 bit rescue media (which is what I thought I needed to do because I have a 64 bit system, so, I assume I have 64 bit drivers?), no wifi or mapped network share, drivers injected from the system, yes to custom drivers but I didn't add anything to the folder so I assume I got the NVME and RAID and that's it, no msiscsi, bitlocker support (even though I turned off bitlocker already), Display choice E which is the closest to my laptop screen... my laptop screen is 2650 x 1600 and E is 1680 x 1050. The MVP ATI Builder asked if I wanted to create a flash drive and I said yes. I then undocked my laptop/unplugged everything, plugged in the USB, went into the boot menu, and selected the USB flash drive. All that happened was a light blue screen for a while, then the system shut down. Does anyone have any suggestions as to what I did wrong? Thank you, Elisa

0 Users found this helpful

Elisa, some comments:

First, the MVP Custom PE Builder tool is no longer being developed and has been superseded by the new MVP Assistant tool which will work with ATI 2017 and later versions.

Next, there is no need to download and install the Windows PE and ADK kits to create WinPE media provided that your Windows Recovery Environment (WinRE) is working correctly - you can take the WinRE option for creating media and it will find all the files needed from the WinRE area.

For this particular issue, I would suggest trying the MVP Assistant in its E-Z Mode (easy mode) which will create WinRE media.

You will need to confirm what BIOS boot mode your Lenovo Legion laptop uses to boot into Win 10 - this can be determined by running the msinfo32 command in Windows then looking at the BIOS mode information shown in the right panel of the report produced.  This will probably be UEFI and if so, this is the boot mode you need to use for the Acronis rescue media too.

MVP Assistant - New 2.0 with Rescue Media Builder (New Version 2.3.2) BETA Version 2.4.0.1 available, see posting below.

KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media

Hello, and thank you... I made progress, but there is still an issue.

Now, using MVP Assistant 2.3.2 in the EZ mode and the RE image, I am able to create a bootable flash drive.  However... there is no Acronis True Image 2017 on the drive.  In the Configuration area of MVP Assistant, the checkbox for Acronis True Image 2017 is checked.  It was queued to install.  It failed to install.  The log file confirms this, it says

12-28-2022 19:25:44  Info Installing Acronis True Image 2017
12-28-2022 19:25:44  Error Failed to install Acronis True Image 2017

I definitely have Acronis True Image 2017 on my computer. 

Do you have any suggestions as to how to install ATI2017 on the boot media created by the MVPAssistant tool?

Thank you, Elisa

Elisa, I remember that there was another user recently who hit a similar problem with ATI 2017 that Bruno (the creator of the MVP Assistant) advised the following work-around for.

First you need to follow KB 59184: Acronis True Image 2017: How to create a WinPE-based bootable media and select the option to create a WIM file rather than either a DVD or USB media.

Once you have created the .WIM file, then you can use this with the MVP Assistant as follows:

Create a New Project.

At Image Source panel, select Local .wim file then click on the Load source button.

In the Explorer window, navigate to where the .wim file is located, select it then click on Open.

The MVP Assistant will show a status message to say it is copying the file then show more detailed information when successful.

You can now continue as before to create the new media.

See the images below showing the above actions using one of my local .wim files (not 2017).