Here is my experience of finding INFCACHE.1 in Win 8.
Share it to anyone who need it.
Posts about corrupted INFCACHE.1 file written by Smokey. Windows Vista / USB device detection problems: How-To-Fix. Author: thedave.ca. During the initial installation of a USB device (most often external drives, although not always), Windows Vista does not locate or install drivers for the device. The INFCACHE.1 file is used to store information about USB drivers, the information in this file may have become corrupted and may cause windows to load the wrong driver or cause a driver not found message to be generated. Deleting this file will force windows to generate a new INFCACHE.1 file. It cannot be an SP2 problem, as this problem has existed since the PC was new, when it was Vista SP1. It is not possible to uninstall Access Connections (or, indeed, most other applications) in Safe Mode, because Windows Installer will not run in Safe Mode. Re: RE: INFCache.1 file Have a look at this article. There is a Vista update available and if that doesn't rectify the problem, there is also a hotfix available by contacting Microsoft. Is there a permanent fix for the INFCACHE.1 problem? - posted in Windows Vista and Windows 7: I'm under Vista Ultimate at the moment and I'm finding this issue pretty annoying yet i think I've found a temporary fix. Infcache doesn't exist in Windows 10, at all, so I cannot delete it, in Windows 7 it works like a charm, delete it reboot the machine and it comes back. I need to have the same operation in Windows 10.
= = = = = = = = = = Dividing line = = = = = = = = = =
First, it's known that:
In the legacy MS OS, such as win 2k(out of our discussion), xp and 2k3, even vista and 2008 (no r2)
%systemroot%infINFCACHE.1 is the driver cache file ( we can also think it as a driver index database).
From win 7 to 2008 r2,
The driver cache file is moved to the following directory, and some new files appeared.
%systemroot%System32DriverStoreINFCACHE.1
%systemroot%System32DriverStoredrvindex.dat
%systemroot%System32DriverStoreinfpub.dat
%systemroot%System32DriverStoreinfstor.dat
%systemroot%System32DriverStoreinfstrng.dat
%systemroot%System32DriverStoredrvindex.dat
%systemroot%System32DriverStoreinfpub.dat
%systemroot%System32DriverStoreinfstor.dat
%systemroot%System32DriverStoreinfstrng.dat
If these driver cache files is missing, corrupted or incorrect, those device based on the default drivers built-in system will not work properly.
= = = = = = = = = = Dividing line = = = = = = = = = =
From win 8 to the latest widows version,
It seems that MS removed the driver cache which existed as files in the past.
= = = = = = = = = = Dividing line = = = = = = = = = =
We've spent some times, and it's not easy to find the new way MS store the driver cache msg in win 8, there has none MS offical explanation.
After win 8.1 is released, we still insist on looking for the driver cache storage location,
Misled by the old version of windows, we think the driver cache should exist as file format as before, and we get nothing from file comparison and tracking.
Then we try to find a new ideas to get new progress, and try to search any helpful msg from MS or Search Engine.
= = = = = = = = = = Dividing line = = = = = = = = = =
Finally, one day I found someone said he believe it's functionality has been moved to the registry as HKLMDrivers, and that the HIVE is loaded on demand.
But I can not find this registry in my win 8.1 or win 8,
After reinstall the os, at the first time while system is ready to use(System Initialization), Press [Shift]key + [F10]key to call the cmd wnd,
Then run 'regedit', okay! the HKLMDRIVERS is exists here! Export it now.
= = = = = = = = = = Dividing line = = = = = = = = = =
Here to share its data structures:
[HKEY_LOCAL_MACHINEDRIVERS]
There are 4 sub-items under HKLMDRIVERS:
[HKEY_LOCAL_MACHINEDRIVERSDriverDatabaseDeviceIds]
[HKEY_LOCAL_MACHINEDRIVERSDriverDatabaseDriverFiles]
[HKEY_LOCAL_MACHINEDRIVERSDriverDatabaseDriverInfFiles]
[HKEY_LOCAL_MACHINEDRIVERSDriverDatabaseDriverPackages]
[HKEY_LOCAL_MACHINEDRIVERSDriverDatabaseDriverFiles]
[HKEY_LOCAL_MACHINEDRIVERSDriverDatabaseDriverInfFiles]
[HKEY_LOCAL_MACHINEDRIVERSDriverDatabaseDriverPackages]
I don't know why it will disappear soon.
= = = = = = = = = = Dividing line = = = = = = = = = =
And there also has a registry:
[HKEY_LOCAL_MACHINEDRIVERSDriverDatabase]
Which has the same data structures as HKLMDRIVERS, but theirs content is different.
[HKEY_LOCAL_MACHINEDRIVERSDriverDatabaseDeviceIds]
[HKEY_LOCAL_MACHINEDRIVERSDriverDatabaseDriverFiles]
[HKEY_LOCAL_MACHINEDRIVERSDriverDatabaseDriverInfFiles]
[HKEY_LOCAL_MACHINEDRIVERSDriverDatabaseDriverPackages]
[HKEY_LOCAL_MACHINEDRIVERSDriverDatabaseDriverFiles]
[HKEY_LOCAL_MACHINEDRIVERSDriverDatabaseDriverInfFiles]
[HKEY_LOCAL_MACHINEDRIVERSDriverDatabaseDriverPackages]
So I export it too.
= = = = = = = = = = Dividing line = = = = = = = = = =
After gather the registry above, I heard someone told me there has another file exists in the OS:
Fix Windows Files 10
%systemroot%system32configdrivers
Well, just extract it from the System Installation Disk now!
= = = = = = = = = = Dividing line = = = = = = = = = =
OK, let' make a summary now.
The '%systemroot%system32configdrivers' can be extracted from System Disk easily, and the registry need to be exported at the System Initialization.
After replace them to your OS, a sysrem reboot is needed to to take effect.