Hi,

what is the difference between driver-integration in install.wim or boot.wim?

Can somebody give me an explanation?

Thanks, Thiersee

Edited August 16, 201212 yr by Thiersee

Drivers from boot.wim are needed for the boot of the windows install cd, and for the first phase of windows installation, and those from install.wim are needed for the second phase of windows installation (when devices are properly installedd). So probably you were wondering if you should leave that AIO option intact (drivers also going to boot.wim). So yes, leave it as is, checked.

I'm only wondering because all my drivers are in the install.wim and all the options in AIO to integrate drivers in the boot.wim are unchecked!

My USB-Install is working without problems.

Yeah, however it's very likely that for some USB 3.0 sticks, having those drivers also integrated into boot.wim can be the little difference that permits a succesfull windows install.

The only drivers that should be considered for integration into boot.wim are what M$ classifies as "boot-critical" drivers. Namely Mass-Storage and SOME Chipset drivers. Nothing else.

More info: http://support.microsoft.com/kb/2686316

Driver Limitations:

Please keep in mind that there are some drivers that can be included and/or loaded that may not be functional during WinPE portion of installation. This would include, but is not limited too; video drivers, wireless adapter drivers, and audio drivers. The behavior described in this document is not specific to BootCritical drivers (drivers need during boot-up such as controller drivers for access to hard drive) and is in affect for all drivers loaded during installation/deployment.

The only drivers that should be considered for integration into boot.wim are what M$ classifies as "boot-critical" drivers. Namely Mass-Storage and SOME Chipset drivers. Nothing else.

More info: http://support.micro....com/kb/2686316

Thanks a lot for the explanation!

Yeah, however it's very likely that for some USB 3.0 sticks, having those drivers also integrated into boot.wim can be the little difference that permits a succesfull windows install.

I have an USB 3.0-Stick, but my mainboard can not boot from USB 3, so I boot from USB2.

Thanks you too.

Thread can be closed.

You can try also integrating USB 3.0 drivers to boot.wim and give it a try, alongside the other chipset drivers (and AHCI/mass storage if needed), and see if it works afterwards in your case. Actually I'm very curious...

You can try also integrating USB 3.0 drivers to boot.wim and give it a try,...

No chance, mainboard CAN NOT boot USB3-Medium.

No chance, mainboard CAN NOT boot USB3-Medium.

Mainboard needeth new owner! :dancing:

Mainboard needeth new owner! :dancing:

What do you mean?

Edited August 16, 201212 yr by Thiersee

There are lots of amd mobos that you CAN boot usb 3 with now.

There are lots of amd mobos that you CAN boot usb 3 with now.

Of course, but not the Gigabyte 890GPA-UD3H (USB3-Controller on-board NOT on-chip!).

Of course, but not the Gigabyte 890GPA-UD3H (USB3-Controller on-board NOT on-chip!).

Buy a New board

Buy a New board

Why? Only to have the possibility to boot from USB3 ?

No, thanks.

Why? Only to have the possibility to boot from USB3 ?

No, thanks.

Well, you did bring the subject up!

Well, you did bring the subject up!

You are wrong, I only asked for the difference between integrating in the install.wim or boot.wim.

I only asked for the difference between integrating in the install.wim or boot.wim.

The boot.wim only contains 2 images both are PE-mode framework: Install mode, Recovery mode.

The install.wim contains the actual OS images that are extracted to the target HDD during Install mode.