Hi,
- What is the make and model number of the Computer?
A file system filter driver intercepts requests targeted at a file system or another file system filter driver.
Assume that you have a Windows 7-based computer that is running on an Intel Atom Z670 processor and on an Intel SM35 Express chipset and you face this issue then run the
Hotfix.
Functionality issues on USB devices that are connected to a Windows 7-based computer that has an Intel platform
http://support.microsoft.com/kb/2528984
For the issue with Windows Vista Computer try these steps.
Windows Vista might report that there is “no driver found for you device” and/or will not display the pre-installed Vista OEM drivers. Even by manually selecting the driver,
you will still get the “no driver found…” error. This is most likely caused by a corrupted INFCACHE.1 file. This file stores the location of drivers and their INF files. This file is hidden, has restricted access, and can be found in “c:\windows\inf”.
Delete the INFCACHE.1 file and it will force Windows to rebuild the INFCACHE.1 file the next time Windows searches for drivers. To delete this file, you have to set the security
permissions of it to allow Full Control for the User Group Administrators or full control for your user account. Please follow the directions below:
1. Open a Windows Explorer window by right clicking on Start and then clicking on Explore.
2. In the address bar, type C:\windows\inf and press Enter.
3. Find and then right click on the file named INFCACHE.1.
4.Select Properties.
5. Click on the Security tab.
6. Click on Edit to edit the permissions of the file.
7. Click on Add to add User Groups.
8. Type Administrators in the User Groups field and click on OK.
9. Set Administrators to Full Control and click on OK.
10. Move or delete the file INFCACHE.1.
11. Reinstall a device to force Windows to rebuild the INFCACHE.1 file (DO NOT reinstall the same external hard drive that you were having issues detecting before. Please connect another USB device other than the one that Vista had an issue detecting).
This detection issue can happen several times in a row, but repeat the steps 1-11 and try again until this works.