Device cannot start (error code 10) in WinPE

Hi there, I have tried two different WinPE on my system. And both of them failed to recognize or even start my wifi card. It's Atheros AR9485
In both the cases the issue was the error code 10. This device cannot start. A scan for hardware change suddenly vanished the device altogether, it always does. Trying to update the drivers manually failed (I got the drivers from DRP) and yielded no results either. While updating, it just gave me an error (since I tried updating them through device manager only, in the end it gave me device cannot start error only)

In every case, the device suddenly vanishes out of eyesight and ceases to be available to the windows. Although, there's no issue with the device itself. The card works normally in normal installation of windows. It's just with the WinPE (I think both Bob Omb's 4.8 and Medicat WinPE 19.10 were built using Win10 PESE project, I might be wrong, so pardon me for that)

Either ways, I just couldn't think of any other place for help due to the issue only persisting on WinPE only. They are both windows 10 PE. Any help is appreciated. Thanks a bunch in advance. :)

Hi Raex-D,

If the machine that you want the drivers from, OS matches the PE you are building. You can try to use the Dism Export host drivers and try to Integrate them. plugin is located in -->Win10PESE/Drivers/Driver Integration.

Well, I am not building a new PE but using the prebuilt ones. Integrating them into the winpe would be a little bit of a hassle for me and time consuming. But the old drivers from the PE work fine in the normal windows. I am not even sure if it's an issue from the drivers since the device just suddenly disappears.

Hi Raex-D,

You can find things to add drivers to PE "after boot" around,

 still, the main focus around remains adding driver during the build (creating project)
  and on your case you can not know what are added to iso that may cause troube....

  Normal windows behave different when adding Driver compared to PE ...

@Malok
as written previously on another topic,
 if you create a package with your eg. Malok.cmd (including pecmd.exe with your pecmd.ini etc..)
  http://theoven.org/index.php?board=18.0
    all projects can use and whatever iso/usb created with will work . 

@Malok
as written previously on another topic,
 if you create a package with your eg. Malok.cmd (including pecmd.exe with your pecmd.ini etc..)
  http://theoven.org/index.php?board=18.0
    all projects can use and whatever iso/usb created with will work . 

Forgive my Noobness... I'm not familiar with other projects than PESE and XPE. But Isn't PECmd.exe already included in all projects ?
Not sure if I understand what kind of Package you mean. If PECmd is present. It only needs Drivers in cabinet files. The cmd creates PECmd.ini on the fly.

But Isn't PECmd.exe already included in all projects ?

no,
ms do not include with official winpe 
WimBuilder -> pecmd is default enabled but also optional, one can disable
LiveSystemPro -> pecmd not exists .
Gena (not related to your package but only to give example) -> pecmd optional default disabled
.... and I do not know what people do these days, especially on Chinese, Korean, Japanese and Russian forums...

*
If you write instructions to newbies with a package including your cmd and pecmd ;)
 everybody on the internet can use that easily,
  I guess also the ones that use winpe (boot wim, winre wim) out of box too..... 


**
I hope more clear now.

Hi Raex-D,

You can find things to add drivers to PE "after boot" around,

 still, the main focus around remains adding driver during the build (creating project)
  and on your case you can not know what are added to iso that may cause troube....

  Normal windows behave different when adding Driver compared to PE ...

Hi, thanks Lancelot. The driver removal was the ultimate solution to my issue. I was only looking for a quick and fast resolution. Although, I later learned that it won't be possible due to the driver itself. I think both the WinPE I was using had the same base structure. I think the Medicat just customized Bob Omb's build to their own leisure. Anyhow, I pinpointed the driver which was netathrx.ini (oem19.ini) (driver version 9.2.0.113) . This was an old driver for windows 7. Had to recreate the boot.wim and after which it worked flawlessly. I guess the driver was faulty and caused issues with the hardware.

@Malok
as written previously on another topic,
 if you create a package with your eg. Malok.cmd (including pecmd.exe with your pecmd.ini etc..)
  http://theoven.org/index.php?board=18.0
    all projects can use and whatever iso/usb created with will work . 

Ok it's done http://theoven.org/index.php?topic=3043.msg36388#msg36388