Infcache.1 Windows Xp

by

Apr 18, 2019  March 17, 12:09 - date of INFCACHE.1 file modification (c:WindowsSystem32DriveStore) March 17, 13:07 - installing of 4th update -failure. I personally have never had an OS break via MS updates while running Avast since xp through W8-8.1 and W10 19 years.just lucky I guess. Windows XP: The INFCACHE.1 file can be found in the C:Windowsinf directory. Simply right click the file and click delete. Once deleted simply restart your.


I ran into an issue with my Windows XP installation recently, and Google turned up a lot of questions exploring the area but no answers, unfortunately. So here's how I fixed things, maybe some poor soul will find this of use:
In a nutshell, I've upgraded the BIOS for my motherboard and the external USB hubs stopped working. The computer would prompt about 'New Hardware Found' whenever I logged in, but it could not install the drivers - so the HUBs just sat there, doing nothing. Very strange, especially because I dual-boot XP and Vista on this machine, and Vista detects and uses the HUBs perfectly.
The usual, obvious things (try to unplug, re-plug, reboot, delete infcache.1, reinstall chipset drivers in as many possible combinations as I could bear to try) did not help, so I decided to tell Windows what to do with the HUBs manually. After all, it knows perfectly well how to handle an USB hub, all I have to do is tell it what drivers to load, right? Turns out this was easy to do, and seems to work perfectly.
First, plug in the hub and ignore the 'New Hardware Found' message. Go to Device Manager, and look for the device with the yellow questionmark. Right-click and select Properties, then choose the Details tab. You will see something like this:

Device Instance Id
(click to enlarge)

Note the 'Device Instance Id'. Open up Regedit and navigate to HKLMSystemCurrentControlSetEnumUSB. There will be a bunch of subkeys starting with 'Vid_'. Select the one that corresponds to the Device Instance Id. It will have a subkey with a seemingly random name, such as '6&1b4ffbf&0&1'. Select this subkey, like this:

The Registry - before
(click to enlarge)

Right-click the selected key in the treeview and select 'Permissions'. Check 'Full Control' for 'Everyone' and click OK.
Enter the following missing registry values on the right-hand side:
  • 'DeviceDesc' is a string value and should be 'My Favorite USB Hub' or something similarly descriptive.
  • 'Mfg' is a string that should be set to the manufacturer name, like 'My Favorite Hardware Company'. You can be creative, it doesn't matter.
  • 'Class' is a string and should be 'USB'.
  • 'ClassGUID' is a string and should be '{36FC9E60-C465-11CF-8056-444553540000}'.
  • 'Driver' is yet another string and should be '{36FC9E60-C465-11CF-8056-444553540000}0015'.
  • 'Service' is the last string and must be 'usbhub'.
  • Finally, 'ConfigFlags' is a DWORD and should be 0.
    Like so:

    The Registry - after
    (click to enlarge)

    While you're typing the above values, Windows will suddenly decide that it has *some* info but not enough and the 'New Hardware Found' prompt will disappear. You'll get a balloon tip instead telling you that the hardware you're installing has malfunctioned. Just ignore this and finish adding the entries.
    When you're done, unplug then re-plug your HUB. If everything goes well, Windows will detect your hardware and start using it absolutely silently. (Well, save for the usual USB ding.)
    At this point you will also want to take away the 'Full Control' checkbox from 'Everyone' and leave the permissions on 'Read'.
    This doesn't fix the overall problem; the fact that Windows is not able to automatically detect HUBs that you plug in is still there. You're done with this particular device but if you attach a new HUB to your machine you will have to go through this painful process once more.
    I very warmly recommend that you do not change other registry values that might belong to this key or its subkeys. As you add or remove hardware Windows will insert other entries, and, for example, having a duplicate 'ParentIdPrefix' value will result in bluescreens.
    Note: If you have a device with nested HUBs (such as a Dell monitor with USB ports and integrated card readers) you will need to perform the above steps twice. First you will get the 'Add New Hardware' prompt for the internal HUB itself. When you fix it according to the above instructions, you will gain full use of your memory card reader but the USB ports are still useless because you have a new 'Add New Hardware' prompt for the external HUB. Go through the process once more and all will be well.

PROBLEM


The following error is encountered in a VIPRE Business Agent's installation logs:


Drivers HP Compaq 6515b/6715b/6715s Ethernet Driver 1.00 A Windows XP x32 was collected from HP official site for HP Notebook. Brand:HP, Product:Notebook, Model: Compaq 6510b, Driver: 1.00 A, OS: Windows XP x32.

Note: The Microinstaller and AgentMSI Logs can be located in the Agent's Volatile Data folder:

Arturia Download arturia jupiter 8v VST for mac for free. Audio & Video tools downloads - Jupiter-8V by Arturia and many more programs are available for instant and free download.

  • C:ProgramDataVIPRE Business Agentlogs (Other OS/Version Locations)

ENVIRONMENT

  • VIPRE Business
  • VIPRE Business Premium
  • VIPRE Endpoint Security
  • All Supported Environments

SOLUTION


This is a generic installation error and can have multiple potential resolutions.
Prior to troubleshooting, check the following:
  • Remove the VIPRE Microinstaller from the Control Panel if it's present
  • Navigate to 'C:Windowsinf' and clear any 0kb *.inf files present
  • Open Regedit and open the following key:
  • x86:HKLMSOFTWAREMicrosoftWindowsCurrentVersion
  • x64:HKLMSOFTWAREMicrosoftWindowsCurrentVersion
  • Append 'devicepath' to: 'c:Windowsdrivers; %systemroot%inf'

If any changes were made, reboot the system and retry the installation.

Should the issue persist, a corrupt infcache or drivers from a previous install may be the cause:
Rename the infcache:
  • Windows XP/2003:
  • Navigate to: C:WINDOWSinf
  • Rename 'infcache.1' to 'infcache.old'
  • Windows Vista and later:
  • Navigate to: C:WindowsSystem32DriverStore
  • Take ownership of 'infcache.1' and rename it to 'infcache.old'

Purging any present orphaned VIPRE drivers:
  • Navigate to: 'C:WindowsSystem32drivers' and purge any of the following:
  • sbfw.sys sbfwim.sys sbapifs.sys sbhips.sys sbredrv.sys sbwtis.sys
On Windows Vista and later, there can be a cached folder for the firewall driver:
  1. Navigate to: 'C:WindowsSystem32DriverStoreFileRepository'
  2. Locate the folder beginning with sbfwim (if present)
  3. Take ownership of and delete this folder
If any changes were made, reboot the system and retry the installation.
If the issue persists, Contact Support.

CAUSE


This is a generic installer error that could be due to not being able to overwrite previously installed components or being unable to load the drivers.