Skip to main content

Bootable Media Builder - boot.wim not found

Thread needs solution

I have some really great Problems with the Bootable Media Builder.

1.)
If I decide to use my own WinPE files, the boot.wim is not found by the Bootable Media Builder. (see brbmb.jpg). When I put "boot.wim" in the filename textfield and press OK I will get an error-message (see brbmb_error.jpg).

2.)
If I decide to let Bootable Media Builder build the WinPE4.0 Image automatically it does very well.
But with a few drawbacks!
I don't want to start Acronis Backup & Recovery automatically on the Bootable Media. No Problem, I can Mount the Image, and correct the "Startnet.cmd" in Windows/System32.
But I need some packages from the ADK for some of my programms to run properly from the bootable media.
But when I add e.g. "WinPE-NetFx4.cab" and "WinPE-NetFx4_en-us.cab" the Bootable Media will quit with a bluescreen and the System reboots.

Need urgent help, because I Need to have the Bootable Media working ASAP.

Attachment Size
brbmb.jpg 166.38 KB
brbmb_error.jpg 87.9 KB
0 Users found this helpful

For Winpe 4.0 you need to point to the folder where 'sources' folder is located, i.e. in your case BitPE4\Media

Fedor Larin wrote:

For Winpe 4.0 you need to point to the folder where 'sources' folder is located, i.e. in your case BitPE4\Media

Sorry, seems to be a nogo (see attachments).

Attachment Size
148507-110440.jpg 164.45 KB
148507-110443.jpg 98.06 KB
Fedor Larin wrote:

Another file that is checked (for WinPE 4.0) is
BitPE4\fwfiles\etfsboot.com
Is it there?

No such file.
From where should this file and the Folder get there?
In the "Windows Preinstalled Environment" x86-folder are only the following Folders:
en-us
Media
WinPE_OCs

I'v looked throu all 3 Folders and no Folder with the Name "fwfiles" and therefore no "etfsboot.com".

Can you send me something showing the right folderstructure and the right filenames?
Have to say the documentation is a little weak for the Bootable Media Builder.

Or the other way round, tell me how I can get the "WinPE32" files working in my WinPE without getting the "Side by Side" error.

I need the following packages in my WinPE:
WinPE-Scripting.cab
en-us\WinPE-Scripting_en-us.cab
WinPE-NetFx4.cab
en-us\WinPE-NetFx4_en-us.cab
WinPE-PowerShell3.cab
en-us\WinPE-PowerShell3_en-us.cab
WinPE-WMI.cab
en-us\WinPE-WMI_en-us.cab
WinPE-Dot3Svc.cab
en-us\WinPE-Dot3Svc_en-us.cab
winpe-hta.cab
en-us\winpe-hta_en-us.cab
winpe-wds-tools.cab
en-us\winpe-wds-tools_en-us.cab
winpe-pppoe.cab
en-us\winpe-pppoe_en-us.cab

When you execute command 'copype' in Deployment and Imaging Tools command prompt, you get the folder structure that is required by bootable media builder. If you select 'use installed winPE automatically' , copype is executed before building media and this folder is used. If not - the builder expects the same folder structure.
It contains three folders - fwfiles, media and mount , and under fwfiles there are efisys.bin and etfsboot.com

OK, got it working with all the other Features I'd like to have on the stick.
Thanks for your help.

Just a few last questions:
- When I want to close Acronis Backup and Recovery, the System shuts down. Is there an easy way to prevent the System from shutting down?
- Is it possible to give Acronis Backup and Recovery the credentials to a connected share, so I don't need to type it every time I want to connect to that share?

I assume that in both questions you mean the product working in WinPE environment, correct? In this case -
1) No. It was implemented as a feature request during 11.5 beta testing (previous versions stayed in cmd prompt). You can open a support case to leave the opinion that this options should be implemented, leave it as feedback form at www.acronis.com/support/feedback.html or wait till version 12 beta campaign.
2) This need clarification - give at what time? What is the time scope you want it to save credentials and how it behaves now? It is expected that credentials to the network folder is reused during one management console session, in WinPE is equals to 'from boot to shutdown'.

I thought of a file containing the credentials and Backup and Recovery will read this file everytime I start it. So I don't have to type the credentials every time I start Backup and Recovery.
With this solution my personal Backup don't Need to know the credentials, and I mustn't remember another Password.

Backup & Recovery was not designed to be operated on regular basis from bootable media environment - it's considered as a recovery environment. When products is running under Windows, credentials are saved across console sessions if 'credentials cache' is checked in console options.