Salta al contenuto principale

Bootable Rescue Builder WinPE 5.0

Thread needs solution

According to this site http://www.acronis.com/support/documentation/ABR11.5/index.html#23980.h… WinPE should be supported by the Bootable Rescue Builder.
I just unistalled Assessment and Deployment Kit (ADK) for Windows 8 (PE 4.0) and then installed Assessment and Deployment Kit (ADK) for Windows 8.1 (PE 5.0).
Now I am not able to build a new Image.
Do I have to install the Bootable Rescue Builder again?
And if yes, why is there no possibility to point the BRB to the Installation-Folder of ADK??

0 Users found this helpful

What build do you have installed ? ADK for windows 8.1 is supported in builds 38350 and later. If it's so, you don't have to reinstall media builder, it should detect new ADK automatically. What steps do you perform and what error you get?

What build number do you mean?
If I look in Acronis Backup & Recovery 11.5 Agent under Help -> About I see Build 11.5.37975.
I let the Agent search for an update, but it didn't find any.

Yes, the build # you can see in help->about. The one you have installed doesn't support ADK 8.1 , you can download the last update from http://www.acronis.com/support/updates/

Please extract content of attached .zip file to any folder on the machine with media builder and run media_builder.exe from it. It contains improved error reporting - error message will be different, please copy-paste it here.

Allegato Dimensione
160935-111133.zip 2.66 MB

Details:
Code: 1.572.894(0x0018001E)
LineInfo: 0xA0A7FA0A4449F583;

Module: media_builder_vs_38645
Message: Failed to create WIM image.

Code: 1.572.890(0x0018001A)
LineInfo: 0xA0A7FA0A4449FAC9;

Module: media_builder_vs_38645
Message: Internal error.

This error may occur if you specify to use existing folder with WinPE files and it has other bitness (32/64) than bitness of media you want to create. The error occurs when additional font packages are added to the media. You can check DISM log in C:\Windows\Logs\DISM\dism.log
- there will be an error like
DISM DISM Package Manager: PID=3044 TID=2584 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error

Bitness should be the same, 32.
I use 32Bit packages, and I don't set RBR to use 64Bit.

I don't add additional font packages. But I realized that the RBR does. Any possibility to prevent him from adding WinPE-FontSupport-JA-JP-Package?

These are the packages I need in my Image:
- WinPE-Dot3Svc.cab
- WinPE-HTA.cab
- WinPE-NetFx.cab
- WinPE-PPPoE.cab
- WinPE-Scripting.cab
- WinPE-WDS-Tools.cab
- WinPE-WMI.cab

- WinPE-Dot3Svc_en-us.cab
- WinPE-HTA_en-us.cab
- WinPE-NetFx_en-us.cab
- WinPE-PPPoE_en-us.cab
- WinPE-Scripting_en-us.cab
- WinPE-WDS-Tools_en-us.cab
- WinPE-WMI_en-us.cab

>Any possibility to prevent him from adding WinPE-FontSupport-JA-JP-Package?

No. You need to find out why it's not working on your machine.

I know that I need to find out how to get this ..... to work.

Thought I might get some help from Acronis .....

You can post relevant fragments of dism.log here or contact non-free support at http://www.acronis.com/support/contact-us.html . More crazy approach is to replace WinPE-FontSupport-JA-JP package directly in ADK installation folder with one of packages that you need (e.g. WinPE-WMI_en-us.cab ) before running media builder. Don't forget to revert it. May the problem won't occur with this package.

Hi,
I'm French and I can't create a fresh WinPE media boot with the same problem of WinPE-FontSupport-JA-JP-Package
The error in the dism.log is :
2014-03-19 08:34:43, Info CBS Exec: Processing complete. Session: 2356_336166, Package: WinPE-FontSupport-JA-JP-Package~31bf3856ad364e35~amd64~~6.3.9600.16384 [HRESULT = 0x80070005 - E_ACCESSDENIED]
And I'm logged with the local administrator account.

I tried to rename the C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-FontSupport-JA-JP.cab to C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\Ludo_WinPE-FontSupport-JA-JP.cab
and copy the C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-DismCmdlets.cab to C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-FontSupport-JA-JP.cab
But it create another error ...

Did you find a solution ?
Thank you for your help.

Ludovic.

Bonjour à tous,

après avoir rencontré exactement le même problème sous Windows Server 2012 avec la version English ABR 11.5 build #38573 (sur laquelle nous avons été obligés de passer suite à l'incompatibilité entre WinPE 5.0 -que nous souhaitions absolument utiliser- et notre précédente version en Français build #37975), nous avons enfin réussi à créer sans erreur avec Bootable media Builder, un "WinPE Boot media" intégrant ABR 11,5, ceci après avoir désinstaller notre antivirus (solution peut-être un peu trop radicale et à affiner... ! ) : peut-être une piste à suivre pour certains d'entre vous... je l'espère en tout cas.

Cordialement. Christian / Hubert.

Ludovic ,
Some people reported similar errors (with 'access denied' in DISM log for no apparent reason) that were caused by antivirus activity
http://social.technet.microsoft.com/Forums/windows/3544dcab-2aeb-4629-a…

Merci.
Thank you.

Really, McAfee is the bad boy of this story !
And when I read your answer I thought it was the right answer because I found already this problem ans this answer. But did not remind it !

Thank you.
Merci.

Ludovic.

Fedor Larin wrote:

Ludovic ,
Some people reported similar errors (with 'access denied' in DISM log for no apparent reason) that were caused by antivirus activity
http://social.technet.microsoft.com/Forums/windows/3544dcab-2aeb-4629-a…

This was our problem as well. Disabling McAfee Enterprise temporarily allowed the Bootable Media Builder to complete successfully.