BONNIE BURMAN asked on February 15, 2013. Status: Answered & Closed.
Usbhub.sys NOT DIGITALLY SIGNED
» Since last windows update, all usb ports on my new HP laptop are now disfunctional. Device manager says USB Root Hub driver usbhub.sys is not digitally signed and therefore not loading (code 52). how can microsoft not be able to find the digital signature for it's own driver?
Usbhub.sys with description Default Hub Driver for USB is a driver file from company Microsoft Corporation belonging to product Windows Operating System.
The file is digitally signed from Microsoft Corporation - Microsoft Timestamping Service.
Usbhub.sys problems occur when important operating system files become misconfigured, deleted or damaged. This is a common problem with computers that don't get maintained regularly. Eventually the system becomes overloaded with problems and begins to crash and display errors. Some malware(Exploit:Java/CVE-2012-5076.GAA) camouflages itself as Usbhub.sys, particularly when located in the c:\windows or c:\windows\system32 folder. Therefore, you should check the Usbhub.sys process on your PC to see if it is a threat.
If you're getting Usbhub.sys file missing or not be found errors, it is helpful that you re-install the program, uninstall and re-install a more up-to-date version, and/or check to see if any updates are available for the program associated with the file instead of attempting to copy a new version of the file to the computer. For this purpose, DLL Suite is designed for you to download the required dll file for free. It is a reliable and professional repair tool with a latest library of system files.
What's more, DLL Suite is able to fix BSOD caused by sys extension file error, just because DLL Suite has built-in driver files, and it can replace the failure driver's file which causes the blue screen of death; it can also remove the virus/malware infection at the same time. This specially designed dll file related error fixer has been acclaimed by the users ever since being put into market.
Click DLL Suite's Dashboard menu > Click Scan DLL Errors button > Click Fix DLL Errors button after the scan, and the blue screen of death or any other sys file related error will be repaired automatically. With the help of DLL Suite, it is much easier to fix BSOD and other errors due to the damaged .sys file.
WILLIAM RESLER replied on February 19, 2013
- JOHN GRAY replied on February 15, 2013: » That suggests that the file is corrupt (and SFC can't detect it), or there is some problem with the security catalogs on your system. Consider checking the digital signatures of other Windows binaries - exes in System32, as well as drivers in the drivers folder - to see if others that should be signed do not appear to verify.
- BONNIE BURMAN replied on February 15, 2013: » Well that was enlightening... there are a bunch of unsigned drivers, as you suspected, and I'm noticing other problems now - i.e. windows media files won't open - most likely because it's one of the unsigned files in the pile.
File version is 6.1.7600.16385 (win7_rtm.090713-1255) but I'm starting to wonder if I'm only working to fix a small part of a larger problem? Tried a system restore, but it was unsuccessful. I'm hoping there's a solution other than reinstalling windows.
- JOHN GRAY replied on February 16, 2013: » I assume you're using Win7 x64, correct? If so, perhaps upload to your SkyDrive your copy of usbhub.sys. I've got the same version, and I can diff the files and check the sig on my system. That could help determine if it's the files, or something like the security catalogs.
- MICHAEL SUMNER replied on February 17, 2013: » Now the only problem remaining is a windows live error when trying to run Halo 2 which existed before this anyway. From what I also see in other forums, there is no fix for this yet and it's a known issue with Halo 2 and Windows 7. It was very disappointing I could not restore the system to the point just prior to the update. I'm not sure why it failed, but everything is working now and I've made a fresh backup with this configuration so at least if it happens again, I should be able to bring it back to this configured state, rather than all the way back to factory default.
- JOHN GRAY replied on February 18, 2013: » Good to hear you've got things in a working configuration again. Perhaps, think about monitoring things over time - as sick as it sounds, consider randomly checking the digital signature of various files at various points, etc. to see if the symptoms start returning. Though, I don't know what you would do short of what you already did. I've not encountered a way to restore security catalogs, etc. without reinstalling the OS or restoring from a backup...
DLL Q & A You Might Like:
- BSOD Problems For Example Fltmgr.sys & Mpfilter.sys »
- Meydfv.sys Driver And Win32.Netsky Spyware Alert Trojan »
- Stop 0x0000008e Iomdisk.sys »
- Cannot Find WAB.DLL Error In Outlook »
- Volsnap.sys Or Classpnp.sys Files Blue Screen Errors »
- Windows7 Home 32Bit Jjune.sys Constant Blue Screen 0xD1 »
- Windows 8 BSOD NETIO.SYS »