Trouble injecting network drivers into WinPE Bootable media build -- Acronis B&R 10

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 2

Hello,

Trying to create a WinPE-based bootable media image in Backup and Recovery 10. AIK is installed and I'm able to build the image no problem using either WIM or ISO, however when I try to inject network drivers into the image build, it kicks back with the following error:

Failed to create the file: Error code 0x180000

Again, no issue creating the bootable image if I just do a vanilla creation without specifying any drivers to inject. Unfortunately Acronis seems to take a long time to update their online boot media builds, so my system's NIC hardware (Dell Vostro 360) apparently isn't currently supported, thus my need to build the image myself. The last time I had this issue (Dell Latitude E6420) they were able to create a custom image for me that functioned with the NIC in that model, unfortunately that's no longer an option since my support contract ran out. Anyone have any suggestions on how to proceed?

Thanks!
-Jeff

Fri, 06/01/2012 - 14:49
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 2

Over 50 views so far -- someone has to have some recommendations? Any Acronis support people on here? I know it builds OK because it'll create the image no problem if I don't specify any drivers to add, but that doesn't help me out with newer computers. Alternatively, anyone from Acronis interested in perhaps updating their year old boot disc image image?

Tue, 06/12/2012 - 13:01
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 31
Comments: 1272

Hello Jeff,

Thank you for using Acronis software.

The issue can be resolved, by using the correct drivers for your NIC. Please be aware, that your driver matches this conditions:

  • It have to be 32 bit driver
  • You should unpack the driver. As a result, you can see .inf, .sys and .dll files then
  • The driver should match the Operating System, used to build the AIK
  • Use every time the latest Version of your Acronis Product.

This article shows you, how to build a WinPE Media in Acronis Backup & Recovery 10. And this article shows you, how to add the Acronis-Plugin into an existing WinPE Media.

If there is anything else, we can do for you, please let me know.

Thank you.

Mon, 06/18/2012 - 08:57
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 2
Comments: 14

I'm having similar issue using ABR11, current build (but it's worse because) my SATA controller on Intel type X79 motherboard (with 2 SSDs in RAID 0) don't get seen. I'm running Windows 7 Professional 64-bit. I can manually add the drivers once booted to a 'vanilla' Acronis-created Win PE based bootable CD, and then add the Intel RST drivers manually but I want to "inject" them ahead of time into the ISO that Acronis will build. So far this is what I seem to discern, can anyone verify this?? -

A) Using Win7 AIK on a 64-bit OS, the AIK installs as 64-bit thus matching the OS on the system being used to build the bootable WinPE media.
B) The AIK will not allow a 32-bit driver to be added, only 64-bit versions when Acronis bootable media creator is used to add drivers.
C) Acronis runs as 32-bit, and when booted to WinPE media, all drivers must actually be 32-bit. If 64-bit drivers were added in the build, they will fail (and/or perhaps the WinPE will fail to even boot up.)

---> Conclusion (please someone confirm and comment) ?
D) To add the necessary 32-bit drivers to WinPE media, the machine being used to build the media via Acronis and AIK MUST be running Windows 32-bit operating system. It cannot be running a 64-bit OS.

I am sure there are 3rd party utilities to accomplish what we need, but what is the *simplest* way, second to building the WinPE on a machine actually running Windows 32-bit?

Wed, 06/20/2012 - 16:59
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 2

Howard -- you hit onto the same thing I believe is affecting me. It didn't even occur to me that I'm trying to inject these drivers (32-bit) into the image using Acronis, which is installed on a 64-bit machine.

Any suggestions from Acronis?

Wed, 06/20/2012 - 17:11
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 2
Comments: 14

Update:  I installed the latest ABR11 and Windows AIK on another Win7 system, this system with 32-bit version of Windows.  I was able to use the Acronis bootable media creation tool to make a WinPE based ISO, and had no problems adding my needed 32-bit SATA controller drivers.  I tested the final ISO created (using GRUB4DOS bootable USB stick drive) and it worked fine.  The SATA controller drivers I added during WinPE creation worked automatically and all hard drives could be accessed.

This seems to validate my post earlier today (2 posts prior) that Acronis running with WinPE bootable media uses 32-bit drivers, but you cannot add 32-bit drivers using Acronis (along with Windows AIK installation,) if you are building that WinPE media on a 64-bit version of Windows! 

Acronis, could you comment on workarounds? 

Thu, 06/21/2012 - 00:05
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 31
Comments: 1272

Hello Howard, Hello Jeff,

when using an 64bit Windows you only can add 64bit drivers. When using Windows 32bit, you can only add 32bit drivers.

You cannot mix 32bit and 64bit drivers in this situation.  Find more information about MS WinPE here.

If there is anything else, we can do for you, please let me know. 

Thank you.

Thu, 06/21/2012 - 12:17
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 3
Comments: 2

Hi,

I have WAIK 3 (2008 R2/Windows 7 codebase) installed on an R2 server and have no issue creating x86 Acronis boot media with ABR 11. The boot media creator automatically grabs the x86 files from WAIK and injects the x86 lan drivers (from DriverPacks).

The only time I have personally experienced "Failed to create the file Error Code: 0x180000" was when using RDP. Using the actual console is fine.

Whether this is related to your problem or not, I don't know. Just thought it might help - and wanted to assure you that x86 wims can be made on x64 OSs.

Sat, 08/04/2012 - 14:29