Windows – How to get the usb devices working in Windows 7 on Asus H110M-K D3

As the comments said, USB 3 drivers are not something that Windows supports natively.

Your main question came about the speed - there will be no difference unless your USB memory stick is USB 3 compatible.

This gets quite advanced, I am assuming you have a working knowledge of the command prompt. I would recommend you add the various Microsoft directories to your path, or run the Windows PE Tools Command Prompt instead of the standard one. If I loose you at any point, please write in comments and I will be happy to help.

What I recommend you do is download the Microsoft Deployment Toolkit, and download your USB drivers.

Once downloaded, load the Deployment Workbench and load the WAIK / Windows Automated Installation Kit.

Once this is downloaded, you can use the "copype" command to copy the required Windows PE files to a staging folder. Assuming you wanted c:\win_pe_32 you would use:

copype.cmd x86 c:\win_pe_32

For 64 bit use:

copype.cmd x64 c:\win_pe_64

(I won't give two versions from now on, simply use common sense and replace 64 with 32!)

This will basically copy the required Windows PE files to the folder above.

Next, we need to mount the boot.wim file (The part that actually loads Windows PE). Do this with the ImageX command:

imagex /mountrw c:\win_pe_32\winpe.wim 1 c:\win_pe_32\mount

This will mount the Wim file to the \mount directory.

To load the driver, have the path to the .inf file and run:

peimg /inf=<path> c:\win_pe_32\mount\Windows

If you explore this folder, you can add additional files if you wish. Personally, I include ImageX so it is available from Windows PE.

Now commit the changes by typing:

imagex /unmount c:\win_pe_32\mount /commit

Now you simply overwrite the default boot.wim file with the winpe.wim you just changed.

copy c:\win_pe_32 c:\win_pe_32\iso\sources\boot.wim

Lastly, we use the Microsoft Mastering tool with the following command:

oscdimg -n -bc:\win_pe_32\etfsboot.com c:\win_pe_32\iso c:\win_pe_32\winpe_32.iso

and congratulations! You now have a new bootable Windows PE iso file with the drivers included.

You can burn this to disk, and hopefully, everything should work - as long as the driver is compatible with Windows PE!

From Wikipedia:

Compatibility of USB 3.0 connectors

• Type A plugs and receptacles from both USB 3.0 and USB 2.0 are designed to interoperate.
• Type B receptacles in USB 3.0 are somewhat larger than would be required for a Type B plug in USB 2.0 and earlier. This is intended to allow connecting an older Type B plug into a newer USB 3.0 Type B receptacle. Accordingly, a USB 3.0 Type B receptacle on a peripheral device can be connected using the corresponding plug end of a USB 2.0 Type B cable.
• Type B plugs in USB 3.0 are somewhat larger; therefore, a USB 3.0 Type B plug cannot enter a USB 2.0 or earlier Type B receptacle. Accordingly, normal USB 3.0 Type B plugs cannot be inserted into normal USB 2.0 Type B receptacles found on peripheral devices (and connect them to a computer).
• A receptacle for eSATAp (eSATA/USB Combo) is designed to accept USB Type A plugs from USB 2.0 and USB 3.0.

In theory, there should not be a problem at the hardware level. However, there may be a problem with the drivers or the underlying controller for the ports.

To determine if this is a hardware or software problem, try booting into a Linux live CD and see if USB 2.0 devices work in the USB 3.0 ports. If they do work, the problem is in the drivers. If not, the problem is in the hardware.

Legacy support in the BIOS only applies to systems that do not natively support USB in general. When this setting is enabled, the BIOS attempts to provide a compatibility layer for very old operating systems such as Windows 95 or MS-DOS, so that storage devices attached to these ports can be used (probably with some restrictions such as no hot-plugging). I'm not sure about this, but USB 3.0 legacy support setting is probably to allow USB 3.0 devices on such operating systems to communicate at USB 3.0 speeds. An operating system that supports USB should not be affected by these settings, as they can communicate with the USB hub controllers directly without having to rely on the BIOS.