Win10XPE - Build Your Own Rescue Media

I have tried the new iso, but it refuses to boot - just the spinning circle.

I do not think is the iso but a driver issue I have with my hardware. I always have an issue Windows on my amd device since 1803 not selecting the amd sata controller rather choosing the default Sata controller. I always use Macrium Reflect Redeploy and it sorts out the driver. I just know no way of doing that to a Winpe environment.

PC boots fine from a Macrium Reflect Boot drive though. I somehow need to combine the two isos I think. Still, the old iso version works fine, and I know how to customise it.

Macruim uses WinPE 10 environment - When you create your macruim boot media - it pulls up a driver list..
What is in that list that is not already supported in PE???

Kyhi said:

Macruim uses WinPE 10 environment - When you create your macruim boot media - it pulls up a driver list..
What is in that list that is not already in PE???

Actually I use WinPE 5 as my bios is not 100% WinPE 10 compatible which leads to inability of Macrium Reflect to display in anything but 640x480 resolution when booting from a flash drive (MR have promised a fix in V7.2).

I will post a list of the MR drivers to see if anything obvious. In the end, not a big deal as my case is very specific to me, and I doubt it is worth a lot of effort to fix.

Any, you will find those drivers in > "C:\boot\macrium\Drivers"

Kyhi said:

Any, you will find those drivers in > "C:\boot\macrium\Drivers"

Just looked - only network drivers.

The driver list in c:\boot\macrium\drivers do not list all the drivers, only those that get added that are not in the base setup..

I know what the issue is in terms of hardware.

I replaced by DVD drive with an HDD caddy so I could have two hard drives. I have just tested the iso REMOVING the HDD caddy, and then it booted fine.

This issue started with Windows 1803 - when ever I clean installed, it used the standard SATA Controller, I could not see the drive in the HDD, and I had to update the SATA Controller in Device Manager to the AMD Sata Controller and then I could see the HDD in the HDD caddy.



However, I found the Insider versions would not even boot after a clean install using the standard SATA controller, just hanging with the spinning circles. I found they would boot if the HDD caddy was removed.

I then used the Macrium Redeploy Option on the Insider installation, getting it to search my 1803 installation as it had the AMD drivers in place, and then it replaced the standard SATA controller with the AMD one, and then the Insider versions now boot fine (I have repeated this many times).

I mounted boot.wim from your iso, and as far as I can tell it actually has the AMD Sata Controller drivers available in C:\windows\system32\drivers but I do not think they get automatically picked up i.e. I think it defaults to the standard MS SATA controller. I did not try and run device manager to see what drivers it uses (Does that even work?)

As I said, this is an issue really with my hardware more than an issue, but if you have any idea how I can change the SATA driver automatically that would be interesting. However, I do not think you should waste any significant time on this as the issue is more academic really as I do not need to use the 1803 version.

Cheers

C.

I did not try and run device manager to see what drivers it uses (Does that even work?)

In XPE - Yes..

As long as driver does not require a reboot.....
Must of the time the new driver is loaded and we just deny the reboot..

Or you can try to reload the drivers by using the "System Tools" shortcuts

Although booting is your issue...

Can I also suggest booting with caddy removed - after PE loaded - plug in caddy and refresh/reload drivers..

Not sure it will work - and you seem to have a handle on the issue...

Kyhi said:

In XPE - Yes..

As long as driver does not require a reboot.....
Must of the time the new driver is loaded and we just deny the reboot..

Thanks.

Also if both drivers are installed and the generic one is always chosen - remove the generic driver - keeping just the one you need..

By finding the driver file in the "Target" directory and deleting it.
then recreate the ISO

Kyhi said:

Also if both drivers are installed and the generic one is always chosen - remove the generic driver - keeping just the one you need..

Ah that is a good idea. I will try that.

Watch this space.....

I will provide a little hint for you so you can Boot directly from the Win10XPE folder...
Thus no need to keep burning/coping ISO files to USB..


Hit the "Create Batch File" button - that will create a batch file to add the Boot Menu option for XPE to boot from the Win10XPE directory

Note: If your selected build is to USB the Y drive is not created (As Y Drive is the Root of the drive)
Selecting the "Run All Programs From Ram" option will work no problem..