Mouse and keyboard don't work on Windows install

[Ferrum Master]

I would like to remind you all... it ain't a no more such thing as plain BIOS... it is dead. It is a small OS. EFI running atop firmware driver image(located in dedicated SPI flash from cold boot, afterwards it resides in PCH's memory), basically an independent OS usually running from in PCH located ARM microcontroller. So inside the EFI GUI everything will work as it has a precompiled binary driver blobs to ensure it works. On the next OS level the OS uses their own, if there are not present it won't work, it doesn't magically carry somewhere over in ram stack.

And yes, that's it. PE boot environment problem you cannot add such drivers to it, the kernel doesn't know it. Had this with few newer laptops too for those dorks wanting to downgrade... I always blame those idiots, it is a laptop full of specific HW and drivers, nobody will support you and ensure your damn device even is properly idling at lower currents, not mentioning some basic drivers, but still they cry and buy things without checking the compatibility. Don't use EOL/Legacy OS with latest hardware, it ain't Linux, M$ won't do recompiles for their golden code, nada won't happen - simple as that.

 

[R-T-B]

This would really have to be some unique problem with this computer and not bad drivers or it would be affecting many users of that same chipset.

For a Windows 7 install at least, as the Intel notice above (thanks @blobster21) describes, it is.

 

[Bill_Bright]

For a Windows 7 install at least, as the Intel notice above (thanks @blobster21) describes, it is.

Good point. But, in looking back through this thread, do we even know what OS the OP is using? I just did a quick scan and all I saw was,

Its a new build i was trying to install my windows os

 

[R-T-B]

Good point. But, in looking back through this thread, do we even know what OS the OP is using? I just did a quick scan and all I saw was,

I'm going to have to return your "good point." It could be either thing then!

 

[Bill_Bright]

I'm going to have to return your "good point."

Nope! Once I give them away, you can't give 'em back!

@Vanion - what OS are you using here?

 

[TheDookie]

This is a (now) fairly common problem with new builds using the Skylake CPU family and Z1750 MOBO's when trying to install Windows 7. Like many here, my devices work fine in the BIOS and even at the beginning of the install process. This ends after the initial 2 reboots. In other words, I can go so far as to choose my language etc., choose drive options, and choose to "Restart Now" in lieu of waiting 10 seconds after all the file copying, getting ready for install, install, install updates. After it allows that it's making registry changes, the devices cease to work. For me the pointer jumps to the top left of my screen and stays, no more input from mouse/KB registers.

I'm using a unified Logitech mouse/KB by the way, not that it matters. I've already jumped through several of the hoops suggested through searching, such as patching the installation ISO (didn't work), added USB 2.0 ports to my MOBO (didn't work), and now I'm here. My next attempt has me manually editing the “boot.wim” and “install.wim” files. I'll update this thread with my results if anyone is still following it and check back to see if maybe someone has solved it definitively yet.

 

[Jetster]

This is why you keep a PS2 keyboard around

 

[basco]

set xhci from smart auto to auto--that helped me

XHCI Mode = Disabled - The on-board USB 3.0 port function like a 2.0 port
XHCI Mode = Enabled - The on-board USB 3.0 port function like a 3.0 port
XHCI Mode = Auto - The on-board USB 3.0 port function like a 2.0 port before OS USB 3.0 driver load. If you reboot the OS, the on-board USB 3.0 port again function like a 2.0 port during this reboot BIOS phase before OS USB 3.0 driver load.
XHCI Mode = Smart Auto - The on-board USB 3.0 port function like a 2.0 port before OS USB 3.0 driver load. If you reboot the OS, during this reboot BIOS phase, BIOS is "Smart" enough to avoid downgrade the USB 3.0 port back to 2.0 functionality before OS USB 3.0 driver load. So Smart Auto is faster than Auto on 2nd boot onward, but Enabled is fastest once you are sure the OS has the USB 3.0 driver installed, because it avoid the switching. Making the on-board USB 3.0 port function like a 2.0 port is mainly to support OS installation or to support OS that does not have build-in USB 3.0 driver, so that the USB keyboard would still work if the user plug-in a USB keyboard or any other USB devices into the USB 3.0 ports before the OS is installed with the USB 3.0 driver come with the motherboard.​

 

[simpletruth]

win7 has no usb3 drivers and it can happen that the usb2 ports also are in need for xhci drivers etc.
to get keyboard and mouse win7 needs the drivers
you need the system running with mouse and keyboard on other hardware then:
1. get the drivers for the new hardware (usb3, hub, xhci) and copy them on the harddisc were you find them
2. use that trick to preinstall the drivers on the old hardware BEFORE needing them on the new https://blogs.technet.microsoft.com/mspfe/2013/03/25/how-to-add-a-driver-to-the-driverstore/
3. insert the win-system into your new hardware (maybe using legacy-boot mode or win7 uefi, depending on your win7 install)
in my case on a zbox ci543 it worked and the usb3 drivers got installed after reboot
for rescue and migration tools (e.g. paragon) you need to slipstream the drivers into the bootmedium when creating it.
hope that helps others to get skylake win7 systems

 

[eidairaman1]

Sometimes unplugging and replugging is needed

 

[lelenlelen]

Just created an account here to help some poor guy facing this problem.
I did make it work...without creating usb3 compliant USB installer or side loaded any usb3 driver.
The trick....just set xhci hand off to disable!!!

Hope this helps out someone stuck at windows 7 installation.

 

[arabdream24]

Hi there, i seem to have found the issue. I don't believe Windows 7 Pro x64 has XHCI drivers readily available for the new boards.

I was working on a Lenovo M700 today, and having my OCD, wanted to put in a fresh install of Windows 7 Pro 64 bit. Bios could see the keyboard and mouse fine, but get to windows install screen, no response... After screwing around with BIOS settings, updating firmware on BIOS, and clearing the CMOS using the Jumper, i seem to have found a solution.

Under USB settings of your board, if you see a feature called USB KBC or something like that, that creates virtual drivers for limited use of keyboard and mouse, enable it. This will allow the keyboard and mouse plugged in via USB to work as if they're plugged into the PS/2 port (in this units case, they had PS/2 ports, but i'm using a Microsoft Wireless Comfort 2000 desktop set - so was using USB).

It's working fine now, and once windows is installed, i'll disable the feature, as the windows updates will have the XHCI drivers needed to support this set. Good luck!

 

[7Black]

As the title says my mouse and keyboard stop running as soon as windows comes into the equation. They both work fine in BIOS but when having to make selections for the windows set-up nothing is responding even my caps lock and num lock lights go out.

Motherboard: Asrock z97 anniversary
Power supply: corsair CX600M
Video card: GTX 960 Gaming 4G
Processor: i5

This is a USB port issue. From what I can tell any Windows OS 7 & earlier requires USB2. So, to rectify this you need to plug in mouse & keyboard to a USB2 port & not USB3. My PC case, the front port are USB2 so I plugged into those for the install then once motherboard software was installed I moved mouse & keyboard back to USB3 ports at the rear. If your PC case doesn't have USB2 perhaps a case with USB2 ports in needed?

 

[kobeg]

Just created an account here to help some poor guy facing this problem.
I did make it work...without creating usb3 compliant USB installer or side loaded any usb3 driver.
The trick....just set xhci hand off to disable!!!

Hope this helps out someone stuck at windows 7 installation.

I am having the same problem with the OP, and this solution does work.

 

[jboydgolfer]

PS2. Native support ftw