Acronis Survival Media Kit cannot create
Greetings,
I have a USB SSD thumb drive 256GB when it's creates the partition for the bootable media in progress... I get error..is there a reason why ? I never had any problems before with previous version
Sorry if i posted twice I got and error when trying to submitt
Attachment | Size |
---|---|
ti_media_builder.0.log | 5.98 KB |


- Log in to post comments

Greetings,
When I do a simple survival rescue it starts mounting wim.file and then failed to install driver ignore ignore all..then try again or cancel. below is jpg screen shot
Ancronis 2021 was very easy to create boot disk now this version is totally absurd ... I had the boot format already from before,but the new version said the update drivers will not effect your partition that's already there..and when it tried to update i got a message failed to update drivers....I should of just kept my previous boot disc
I have tried everything u could think of,nothing working :(
Attachment | Size |
---|---|
591449-297048.jpg | 67.14 KB |
- Log in to post comments

Marko, did you try just making the Simple rescue media, not just the Survival Kit?
- Log in to post comments

Yes and Advanced just a searching driver going in circles
- Log in to post comments

Marko, I believe the issue is as described in this topic here by Mustang and being caused by new behaviour introduced by Acronis in the latest ACPHO build 39703 for injecting display device drives into the rescue media.
- Log in to post comments

Greetings,
How do I find out what build I have ? this seems to be very complicated for novice people like me I just want to create a simple boot disk on my USB like i had before.... I should of just left it alone the way it was it worked...now I lost my bootdisk
Sorry I'm not trying to be rude or anything like that,but those instruction are not simple,my head started getting dizzy just reading it :)
- Log in to post comments

Marko, the build is shown on the Account page of the main Acronis GUI and was also shown in the text of the media builder log file you uploaded - you are using ACPHO build 39703..
The way that you can get around this issue is as follows:
First, you will need to use a partition manager tool such as MiniTool Partition Wizard to give a drive letter to the hidden ACRONIS HM 2GB Survival Kit partition.
Once the ACRONIS HM 2GB partition has a drive letter, then you can use the standard Acronis Bootable Rescue Media Builder tool to update it directly using the following steps.
Launch the Media Builder tool.
Select Advanced
Select WinPE based media
Select Windows Recovery Environment
On the next page you will see what drivers Acronis is now trying to add to the media.
If you see something already selected, then you can deselect this!
Select the Media Destination - this is where you can select the drive letter for the ACRONIS HM 2GB Survival Kit partition. Otherwise, you can select to create a WIM file and then copy this manually to the ACRONIS HM partition manually later.
Creating the WIM file will also show you what the size of the new rescue media will be.
The issue created by the changes made by Acronis in build 39703 is that including display device drivers is causing the WIM file to be too large to fit in a 2GB partition on some systems!
Click on the Proceed button to finish the operation.
- Log in to post comments

Ok thanks I'll keep you posted :) I really appreciate your support :)
Question can I make the partition bigger size like say 5GB will that work creating a Survival Media rescue disk ?
- Log in to post comments

Marko Brose wrote:Ok thanks I'll keep you posted :) I really appreciate your support :)
Question can I make the partition bigger size like say 5GB will that work creating a Survival Media rescue disk ?
Yes, you can increase the size of the partition to 5GB and it does fix the issue.
- Log in to post comments

Just wanted to add that I experienced this error for the first time on 11/6/2021 with build 39703. The work around suggested by Steve was successful but Acronis needs to be more proactive helping users avoid the problem in the first place.
- Log in to post comments