Skip to main content


Usbehci.sys is a USB controller driver for Windows XP Service Pack 1. Usbehci.sys is a required file that manages USB ports and Plug-and-Play services. While Usbehci.sys should be included in any Windows Operating System installation, this file is often missing and may prevent the user from installing Windows XP properly. Usbehci.sys runs exclusively on the Windows Operating System and can be found in the Drivers subfolder of the primary hard drive’s System32 folder.

How Usbehci.sys Works

Usbehci.sys is the software component that allows the computer to run its USB ports and recognize USB-based devices that are connected to it. If Usbehci.sys is missing from the computer, the user may not be able to install the Windows Operating System properly, make repairs to it, or use the USB ports. If Usbehci.sys is not included in the Windows XP Service Pack 1 or Windows Operating System installation disc, the copy of either of these services is most likely corrupted or faulty.

Is Usbehci.sys Harmful?

Usbehci.sys is not a harmful program, but rather a critical component of the Windows Operating System. However, if the user downloads Usbehci.sys as a stand-alone file, it may be corrupted or infected with malicious software such as trojans, worms, or spyware. Users should be careful when downloading such files and should always scan the file with an anti-virus software immediately. Users should also note that Usbehci.sys is not a process and, therefore, should never be found running in the Task Manager’s Processes tab. If it is found there, the user should assume the file is a malicious program and remove it immediately with an anti-virus software such as Spyware Terminator, Advanced SystemCare, or Malwarebytes’ Antimalware.

How to Replace Usbehci.sys

If Usbehci.sys is missing from Windows XP Service Pack 1 or the Windows Operating System installation disc, the user can easily replace the file by downloading a copy of it from the computer manufacturer. The computer manufacturer will often have a Downloads section on its website. Usbehci.sys can be found in the Drivers or USB Drivers category. Once the user has obtained a copy of Usbehci.sys, he/she can place it in the Drivers subfolder of the primary hard drive’s System32 folder, which can be found at C:\Windows\System32\drivers. The user can then reinstall Windows XP Service Pack 1.

Popular posts from this blog


The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N