• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Mouse and keyboard don't work on Windows install

V

Vanion

New Member
Joined
Jan 30, 2016
Messages
4 (0.00/day)
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
 
Are they USB? If so, try different usb ports.
 
I have tried multiple usb ports and no luck. I don't think its the usb ports because they work perfectly fine in BIOS but when windows set up comes through they act as if they aren't connected.
 
in bios look for legacy usb enabled
 
I have had this issue before luckily I have and old PS keyboard and mouse to use until windows loads. What version of windows are you trying to load? Like suggested make sure you have usb support on in the bios and you select to load the driver packages in memory when loading windws
 
Is this a new build? Did they used to work correctly and suddenly stopped?
 
Bill_Bright said:
Is this a new build? Did they used to work correctly and suddenly stopped?
Click to expand...
Its a new build i was trying to install my windows os

lonewolf said:
I have had this issue before luckily I have and old PS keyboard and mouse to use until windows loads. What version of windows are you trying to load? Like suggested make sure you have usb support on in the bios and you select to load the driver packages in memory when loading windws
Click to expand...
Thanks for your help my PS keyboard is working unfortunately my usb mouse/keyboard still do not work even after having my OS installed. How would i go about selecting to load the driver packages?
 
Last edited by a moderator:
The fact this is a new build and they have never worked properly suggests a driver problem and not hardware.

Are these wired or wireless? If wireless, one or two dongles?

In any case, the drivers typically are only needed to enable the special features of the keyboard and mouse. All keyboards and mice should work with basic functions without any special drivers installed - and Windows should already know how to make them work using its own native basic drivers. I suspecting this is a USB issue and I would start by ensuring you have them connected in the designated ports pointed out by silentbogo. That should NOT matter - but with this being a brand new build, it might.
 
Bill_Bright said:
The fact this is a new build and they have never worked properly suggests a driver problem and not hardware.

Are these wired or wireless? If wireless, one or two dongles?

In any case, the drivers typically are only needed to enable the special features of the keyboard and mouse. All keyboards and mice should work with basic functions without any special drivers installed - and Windows should already know how to make them work using its own native basic drivers. I suspecting this is a USB issue and I would start by ensuring you have them connected in the designated ports pointed out by silentbogo. That should NOT matter - but with this being a brand new build, it might.
Click to expand...
Ok, thanks ill check out how i installed them on my motherboard. Im in the device managed right now and for my mouse it reads
"This device cannot start. (Code 10)

{operation failed}

The requested operation was unsuccessful"

I tried to plug in my ethernet cable as well to try to go online to get driver updates but the light is glowing yellow/orange rather than green and it also has the same message as my mouse in the device manager.

Bill_Bright said:
The fact this is a new build and they have never worked properly suggests a driver problem and not hardware.

Are these wired or wireless? If wireless, one or two dongles?

In any case, the drivers typically are only needed to enable the special features of the keyboard and mouse. All keyboards and mice should work with basic functions without any special drivers installed - and Windows should already know how to make them work using its own native basic drivers. I suspecting this is a USB issue and I would start by ensuring you have them connected in the designated ports pointed out by silentbogo. That should NOT matter - but with this being a brand new build, it might.
Click to expand...
oh and both the keyboard and mouse are wired

silentbogo said:
1) Make sure you are using USB 2.0 ports, not the 3.0 (see image)
2) Make sure you have legacy USB support enabled

At this point your KB/mouse should already work.

3) Make sure you install the latest USB 3.0 drivers:
http://66.226.78.22/downloadsite/Drivers/Intel/USB/Intel_USB3(v4.0.3.49_PV).zip
View attachment 71739
Click to expand...
I have the legacy usb support enabled in bios and i have my mouse plugged into the usb 2.0 (im using my PS keyboard atm just so i can control the comp so my usb keyboard isnt connected) but the mouse is still not working when i am running windows.
 
Last edited by a moderator:
I had this problem once with a skylake plateform. I was trying to install Windows 7 on it and the issue had to do with Windows 7 setup lacking support for advanced xHCI host controlers. (which is not the case with 8 / 8.1 /10)

Nothing was working past the bios, not even the numlock led.
 
blobster21 said:
I had this problem once with a skylake plateform. I was trying to install WIndows 7 on it and the the issue had to do with Windows 7 setup lacking support for advanced xHCI host controlers. (which is not the case with 8 / 8.1 /10)
Click to expand...

this im banking on it being chipset 100%
 
Solaris17 said:
this im banking on it being chipset 100%
Click to expand...
Except they work just fine in the BIOS Setup Menu, which suggests the Chipset drivers are just fine.
 
Bill_Bright said:
Except they work just fine in the BIOS Setup Menu, which suggests the Chipset drivers are just fine.
Click to expand...

no the drivers dont have anything to do with teh BIOS as im sure you already know. Even wireless mice work fine in most BIOS, this is strictly a driver issue with windows. the BIOS interprets communication of the peripherals on a hardware level.
 
There must be something to activate in the bios (as suggested page 71-72 of user's manual )

I went a totally different route and streamlined the missing driver in my Windows 7 iso using Microsoft's DISM tool

Code: 
DISM /mount-wim /Wimfile:c:\Windows7_wim_file.wim /index:1 /mountdir:c:\local_mounting_directory
DISM /image:" c:\local_mounting_directory " /add-driver /driver:"c:\full_path_to_driver_folder" /Recurse /ForceUnsigned
DISM /unmount-wim /mountdir: c:\local_mounting_directory /commit
 
Last edited:
it may be possible to gain use of the system in safe mode?

Have you tried booting into safe mode too see if the KB and mouse work?

https://support.microsoft.com/en-us/kb/943104

as I'm sure you are already aware the device cannot start because Windows does not understand how to communicate do you have another KB/mouse combo you can use in conjunction? the easiest way out is to probably visit the manufacturers webpage and download the drivers. However if it is an issue with communication to the USB hub itself you will need to rectify this problem first before the Os can properly communicate with the devices.
 
Damn, I just had this exact thing happen to me a few weeks ago... mouse/KB working fine in BIOS, but once Win install started, no more. The lights on the keyboard even went off... now I can't remember what I did to get the mouse and keyboard working :banghead:

It's an
MSI Z97 - with Windows 7. If I can remember maybe I'll come back and post something helpful lol.
 
Solaris17 said:
no the drivers dont have anything to do with teh BIOS as im sure you already know.
Click to expand...
The BIOS is contained in PCH (platform controller hub - formally called the Southbridge) which is part of the chipset.

I am not saying it is definitely not the chipset drivers, I am just saying the symptoms "suggest" it is not. After all, this is something surely well tested before the mobo leave the factory (unless the chipset drivers are corrupt - and I would not suspect that).

Do the mouse and keyboard work in Safe Mode?
 
They both work fine in BIOS but when having to make selections for the windows set-up
Click to expand...

It would be nice if OP could clarify whether he's stuck at the OS installation screen OR at Windows login screen.
 
Bill_Bright said:
The BIOS is contained in PCH (platform controller hub - formally called the Southbridge) which is part of the chipset.

I am not saying it is definitely not the chipset drivers, I am just saying the symptoms "suggest" it is not. After all, this is something surely well tested before the mobo leave the factory (unless the chipset drivers are corrupt - and I would not suspect that).

Do the mouse and keyboard work in Safe Mode?
Click to expand...

I am not sure if I am misunderstanding you or if you are uncertain of the technology.

I am not insinuating something is wrong with his chipset.

I am saying windows has a driver issue preventing his mouse and KB from communicating with them.

the BIOS is not part of the PCH the BIOS is a seprate chip and communicated with the PCH via the SPI

z87-chipset-diagram-3x2.jpg


https://en.wikipedia.org/wiki/Serial_Peripheral_Interface_Bus

The code to communicate with the devices are not "drivers" they are hardware embedded microcode that can communicate with devices attached to the system using a standardized set of firmware/device level communication protocols.

you know this as ACPI

https://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface#Hardware_interface

"Drivers" in the sense we are talking about provide extended characteristics and functionality of a platform to the host operating system.

It does NOT mean that the devices will "work without issue" once an Os is installed. The Os uses the software layer to communicate and translate functions to the hardware device. This requires "Device drivers" to properly convert and transmit this data in such a way as the hardware can interpret and understand.

This is fundamentally different and incompatible to machine code and firmware level instructions used by the devices to communicate with one another.

In this case the Os has been installed but Windows generic drivers which are only provided to give basic functionality are too old (windows 7) to be able to communicate with this and other new hardware based on this technology unless the manufacturer explicitly programs machine code into the devices that allows older software drivers to communicate with the device.

to this end the issue at hand is two fold.

When priority hardware level interrupts are deferred to the Os after initial post the host Os is incapable of communicating with the device at hand and communication with the device is lost or not established.

In this case we need to look at the flow of events required to get the hardware working.

In this case the problem (though we have not seen a snapshot of devman or had a clear enough explination from the OP to draw from) is that the mouse and KB are not working.

this may be a simple driver issue with the parts themselves which is already proven by the (Code 10) established by the OS itself. However further investigation is needed to make sure this works. Downloading the drivers for the KB/mouse itself may not be enough we must also provide the drivers for the devices the commands pass through themselves so that the data from the KB/mouse are interpreted correctly.

In this case it is usually either.

KB/Mouse > USB controller > PCH > windows

or

KB/Mouse > PCH >windows

or in the rare case simply

KB/Mouse > Windows

which means the options are

he needs to install the drivers for the chipset followed by the USB controller (usually needed when run by a separate chip and not controlled by PCH) and finally the KB/mouse if Windows does not pick it up at this point (usually only needed for wireless USB devices are extended function periphs like keyboards that have assignable buttons)

or

he needs to simply install the USB controller bypassing the PCH (usually PCH drivers can be bypassed if other devices are functioning normally as chipset drivers not being installed will show problems with a mirade of devices not just USB specific)

or

he needs to install the drivers for the devices themselves.

I hope this was relatively enlightening though I am concerned that you might just be arguing with me to argue which I would somewhat understand given the amount of flack you get in some threads but to go so far in a thread of this nature is ridiculous. If you would like to be right or believe me wrong you or I can simply state in the most plain way possible that he needs to get his fucking driver disk. put it in the CD drive and install his drivers with a PS2 keyboard (CPU level interrupts)
 
Solaris17 said:
I am saying windows has a driver issue preventing his mouse and KB from communicating with them.
Click to expand...
Yeah, I agree with this.
Solaris17 said:
the BIOS is a seprate chip
Click to expand...
I agree with this too. But the chipset is a "set" of several ICs, one of which is the BIOS chip.

I think we are on the same page.
 
Ok to nutshell this thread it is thought it is a chipset driver issue with the windows install. If this is the case then the OP should be able to load the chipset drivers from the MOBO manufacturer and the issue should be resolved. Am I thinking correctly here?
 
lonewolf said:
this is the case then the OP should be able to load the chipset drivers from the MOBO manufacturer and the issue should be resolved.
Click to expand...
I would rather say, "hopefully" be resolved. 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.
 
You must log in or register to reply here.
Back
Top