Salta al contenuto principale

Acronis Rescue Media Builder vs Bootable Media Builder question when it asks for WAIK or WADK

Thread needs solution

I have Acronis True Image 2017 installed on my windows 10 64bit workstation.  I have installed the WADK kit for windows 10.  When I run Rescue Media Builder and select winpe as my image choice it creates fine and boots fine howerver it is just True Image.  I also have Disk Directore 12 installed along side True Image and it came with a program called Bootable Media Builder.  That program will allow you to create a multi image which allows you to pick 32 bit and 64 acronis true image along with the system reporting tool and adds disk director 32bit and 64 bit all on same flash drive or dvd if you so choose.  From what I can tell the Rescue Media Builder is seeing my kit installation just fine however the Bootable Media Builder that came with DD12 seems to be a bit older and does not.  Is there something else I need to install besides the "Windows Preinstallation Environment" and "Deployment Tools"?  Seems that it works for one and not for the other.  My goal is to make a bootable usb drive with all my tools just like I used to be able to do till I upgraded recently.  I think it might have been broke  in True Image 2016 but for now all I have left installed is True Image 2017.  Here are some screen shots of what I am trying to explain in this wordy statement.  My apologies.

 

 

0 Users found this helpful

Joseph, you are dealing here with two different types of Rescue Media with different capabilities.

The Standard (Linux based) Rescue Media can allow you to combine Acronis True Image with Disk Director and Universal Restore and offer both 32-bit and 64-bit versions.

The Windows PE Rescue Media by default in 64-bit only and does not allow you to combine the other Acronis tools.

If you want to have both 32-bit and 64-bit versions of the WinPE Rescue Media, then you will need to use the MVP Tool - Custom ATI WinPE Builder tool that is linked in my signature below which can do this for you, but as separate builds.

The MVP's are looking to further enhance this MVP Tool to include further options but this is not ready for release to the user community yet.

I have an idea I'm going to play around with to try an automate.  Ultimately, creating a multiboot UEFI and Legacy Flash WINPE flash drive seems do-able - at least manually, but I'd like to find a way to automate it as well and will play around with this after the next update is released.  As long as you have a 32-bit boot.wim and a 64-bit boot.wim, you should be able to do this manually.

Just make sure you're editing the flash drive files and not the local system or you may end up in trouble if not careful. 

For the UEFI menus and booting follow this:  http://www.rmprepusb.com/tutorials/127-make-dual-32-64bit-pe.  Easy UEFI may be another option that I'm going to try soon. http://www.easyuefi.com/index-us.html - doesn't work - only good for the local system I  just can't test if the 32-bit entry I added is working, since I don't have a 32-bit only machine (UEFI will only show the menu for the hardware type that's passed along by the bios).

For the legacy menus and booting, use easybcd. It's really simple. Just "select file store", navigate to the BCD file on the root of the flash drive and then add a new entry for your second .wim file (if you followed the instructions for the UEFI menu, you should have boot.wim (the 64-bit .wim which is already in the BCD store as the default entry) and bootx86.wim - both in the "sources" folder already, which you will be adding as the new / 2nd entry.

Both were pretty easy to do manually.  I've tested the legacy boot menus and can boot 32 or 64 bit after the BCD update.  I have not been able to test the change I made for UEFI since I don't have the 32-bit only system. 

Steve, you might be able to test though.

I added some additional .wim's for some other bootable products - I can successfully boot all f them in legacy mode - both 32-bit and 64-bit.

I can successfully boot all of the 64-bit UEFI ones on my machine.  I see the 32-bit UEFI ones, but of course they error out since it's not 32-bit UEFI capable.  I think it would work on a 32-bit machine though.  

This is sweet!