Usb ports stopped working windows xp sp3

However, sometimes this feature may not correctly wake up the USB device. Therefore, the USB device is unresponsive when you try to use it. You might want to disable this feature for server products where power management is not important or required.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:.

If the DisableSelectiveSuspend registry entry is present, double-click it. If it is not present, create the entry. To create the entry, follow these steps:. Now go to the " Did this fix the problem? This problem may occur because of a timing issue that prevents the computer from detecting the USB device.

Microsoft and the hardware vendors that manufacture the chips that are used for USB have investigated the problem. However, the results were inconclusive because of the intermittent nature of the problem. Microsoft is researching this problem and will post more information in this article when the information becomes available. Need more help? Expand your skills.

Get new features first. Was this information helpful? Yes No. Thank you! Thanks for your feedback, it helps us improve the site. Carolina Calling. In reply to kaymejia's post on August 29, Have you gone to the Latitude D support site , downloaded and installed the Dell Latitude D laptop drivers, utilities and firmware updates?

In particular, have you installed the Dell Notebook System Software? Note, during production, Dell feels free to substitute hardware as it sees fit and you need to determine which downloads actually apply to your laptop.

Additionally, check for undocumented substitutions. I found a Fujitsu hard drive in an Inspiron laptop where Dell never even listed it as an option and the service tag showed a Samsung was installed. Good luck! This will help other find this solution in the future. I'm sticking my neck out a bit here but others can shoot me down in flames if I am wrong. We are getting the same issue here with some Dell USB mouse. Out of or so PC's that we released SP3 on for a trial we have about 3 that the mouse have failed on.

Have no idea why at the moment. It was working fine until I installed Service Pack3. Now the computer won't even see it. I have scaaned for hardware, and reinstalled Kensington's drivers. Kensington tech support said the mouse was not compatible with Service Pack 3. I am responsible for over computers not to mention servers. I am looking into what does and does not work with SP3. Does anyone have a list put together or is it all hit and miss? No one, not even MS has been able to determine why this affects some but not others.

Yet SP3 still remains available for download. I haven't installed mouse software in over five years now for this reason out-dated or buggy.

Most settings are configurable through the default MS drivers and mouse properties, anyway. Roll-back to SP2, uninstall the Kensington drivers and software, make sure the mouse is using the default MS drivers, check for any out-standing updates by going to Windows Update website in your browser, then try installing SP3 again.

There is no "Mice and other pointing devices" section and I cannot seem to get it to use moucalss. It will not reinstall on any new port. In addition to some Logitech drivers , I'm showing mouclass. It's been a while since I posted this, but the knowledgeable techs at Microsoft have provided me with a solution that worked for us at any rate. Backup and delete these files:.

Open a command line and run Net stop Cryptsvc 4. Reboot the computer to make sure the information was clean up. Uninstall all HID devices than "Scan for new hardware". My experience at home has been that I have too many USB connections to the machine - SP3 is able to handle it, but the mobo itself doesn't seem to be able to. I had issues with my mouse or keyboard when I had too many USB devices plugged in, it was resolved by removing un-needed devices.

Microsoft has admitted problems with these installers. And issued hot fixes for this installers before installing Sp3. Of course people by now know that Sp3 leaves. And other internet reports indicate that more reliable installs can be had using the ISO image of Sp3. Usually includes the latest security releases. I have not looked into the ISO yet. But at least can reasonably assume there is something fixed inside WI 3. Not only does this eliminate the older Installer issues. But instead of being inside the UAC account, at least program associations, and settings are preserved.

But avoids the recognition problems of USB. And using the seperate image and the proper WI seems to reduce the usb recognition problem. And also stopping the anti-virus programs from interfering with Sp3 installs, and of course the dreaded lack of SATA drivers. Reducing the environmental problems. So a solution is to install WU 4. Microsoft recommendation of WU 4. But seems to recognize certain raid 0 issues. Rollback of drivers in my testing seems to respond properly, and works out better then past roll backs; 3.

Seems WI4. Prepping people for Vistas UAC image. Partly to get people used to UAC. And to reduce the support requirements for Sp3. Inside Fireware we have the associations of wnaspi, storage management and a few other things.

Time to get the debugger out. Where is WinFS when you need it? Of course leaving you to do the research on this. This Almost Worked! Other steps that "helped" - I updated to latest Windows Installer as noted in a later post on this thread - that helped a little with some devices - seemed to make the storage class of devices work better, and CardScan Pro seemed to work after that - also the Belkin 7-port HUB no longer seemed to be a problem before this it was an "unknown device" despite needing no drivers.

So I swapped the Revolution device for the Nano device in the same port and it worked fine - didn't even report a "new device found" - just silently worked as advertised. Thank You MVanZee - thanks also to the person who pointed me to the latest windows installer. After the above success, I decided to test things further so I plugged in an MP3 device and it did not complete installation as a storage device, then I tried a logitech camera and it ALSO did not install - both seemed to hang with "Windows Service Pack Installer" running update.