unexplained error code 262,158(0x0004000E) while preparing a Dell Laptop with Bootable Media Builder
I'm using Acronis 2016 to try to build the Bootable Media for a Dell Inspiron 15 7547-4020 laptop.
While preparing the CD-Rom, I used the Windows setup option and when it got to the LOAD DRIVERS page I pointed it to the existing Drivers folder on my Dell. I'm running latest update of win 10 on a 64bit machine, 8 GB RAM.
It eventually populated a page full of drivers and I then went to the NEXT screen. Then it got to the "ready to start the media creation process.." at which point it stopped and presented this error info:
==================================
Code: 262,158(0x0004000E)
LineInfo: 0x6983D207431790EE;
Module: universal_restore_media_builder_vs_3900
==================================
Below that is a long list of driver names and I'm stuck at this screen.
I queried the Acronis site for that error code and found nothing. What do I do now?


- Se connecter pour poster des commentaires

Good Idea I'm the Admin and the only one logged in but worth a try
- Se connecter pour poster des commentaires

Nope, it didn't help. Everything looks fine until I hit PROCEED on the tool that's trying to create the CD-ROM.
I still get the same error message.
BTW, I'm choosing to load the DD and TI apps onto the CD-ROM. I selected the 64-bit versions only because my target system will be (is) 64 big.
I'm trying to check all this functionality out before disaster strikes. My Dell is new. My Source PC is 7 years old. I'm trying to set things up so that IF I must recover from a H/W failure on that older system, I can restore it to the new DELL. Both are now running the same versions of Win 10 Home. Both are 64 bit
The Dell (target) has DD, TI and Universal Restore folders present. I can't imagine what is the issue
- Se connecter pour poster des commentaires

Alwaysfixing, does this error occur only when trying to include drivers into the bootable media? If you try creating the bootable media without drivers, are there any issues? Could you share a screenshot of the error?
- Se connecter pour poster des commentaires

Yes, Dmitry, the error ONLY occurs if I attempt to load drivers to the rescue media. The rescue media creates just fine when I do not attempt to load drivers and I actually have now succeeded in accomplishing my goal (migration) useing that more simple media. I was able to access all the external drives connected to my PC by USB.
You will find the exact information on the error message that appeared at the very start of this post. I can't repeat the process now without creating another rescue media, which is not necessary for me to do now.
Thanks,
Gene
- Se connecter pour poster des commentaires

Alwaysfixing, thanks for the additional info. The issue has been reported to the development team.
- Se connecter pour poster des commentaires

Thx Dmitri. I appreciate that and I hope they will get it fixed and send out an update after they check it out.
Or, of course, if it's something I did wrong, I'll be grateful for the instructional fix.
Gene
- Se connecter pour poster des commentaires

For what it's worth, I found the same problem first time I tried to create a Universal or Rescue disk with Dell. Attempted to add the NEC USB 3.0 drivers, the NIC drivers (BroadCom Extreme), and the WiFi (WLAN half-mini 1501) drivers. All of which are stock Dell for this machine (XPS 8300 running Win7 SP1).
And as with Alwaysfixing, works fine without the drivers, but then I can't get all my hardware to run during a full restore.
Thanks fellows.
MP
- Se connecter pour poster des commentaires

Hello Phlipster,
Unfortunately there is no solution at the moment, as workaround I would suggest creating the WinPE bootable media on the different machine. Could you please send us Acronis System Report from your PC and applied drivers as feedback.
Thank you,
- Se connecter pour poster des commentaires

AlwaysFixing,
Two possible workarounds..
1) don't inject the drivers during media creation. Instead, see if the default media can find your OS and if it can, inject the drivers through the booted UR media at that point in time.
2) if you want the drivers in your UR media already (or need them because UR can't detect your drive or Raid controller already)... After your WinPE media is created, you can use Windows ADK offline to inject the drivers into your boot.wim (you'll need to extract this from your iso if you have made a bootable iso instead of a bootable usb).
Add and Remove Drivers to an Offline Windows Image
Alternatively, try DISMGUI which is a GUI based tool that makes the DISM ADK commands a little more user friendly.
- Se connecter pour poster des commentaires

Bobbo_3C0X1,
Thank you for the workarounds to this issue!
- Se connecter pour poster des commentaires