Opened 11 years ago
Closed 8 years ago
#11991 closed defect (obsolete)
detected INFACHE inconsistency after VirtualBox update
Reported by: | Helmut Freiwald | Owned by: | |
---|---|---|---|
Component: | network | Version: | VirtualBox 4.2.16 |
Keywords: | INFCACHE | Cc: | |
Guest type: | all | Host type: | Windows |
Description
Hallo,
it is now the second time, that I have for severals days and ongoing days an "detected INFCACHE inconsitency". This first time I have no idea why and from where it comes. But today I checked the date for the first event of this kind in file "C:\Windows\inf\setupapi.app.log". It was the date of installing / updating VirtualBox software (from version 4.2.12 to version 4.2.16). The INFCACHE inconsitency corrensponds with the driver installation of VirtualBox Network Interface(s) ([DIF_PROPERTYCHANGE - ROOT\SUN_VBOXNETFLTMP\0000]]) and the RRNETCAP driver from software "AUDIALS ONE 10" (Build Driver List - ROOT\RS_RRNETCAPMP\0005])
[code]>> [Build Driver List - ROOT\RS_RRNETCAPMP\0005]
Section start 2013/07/18 20:07:30.738
cmd: C:\Windows\system32\svchost.exe -k netsvcs
cpy: Policy is set to make all digital signatures equal.
! inf: Detected INFCACHE inconsistencycode
Uninstallation of RRNETCAP driver and also VB and reinstallation of both, does not repair INFCACHE for all time, just temporarly:
! inf: Attempting INFCACHE repair 20:07:30.741 ! inf: Verify/Fix on INFCACHE complete, status(4) - Fixed 20:07:49.488
on next driver installation the error "detected INFACHE inconsistency" arises again.
I think there are some dependency between drivers of VirtualBox and RRNETCAP, and if I uninstall only one of them for reinstallation, the registry settings under "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\SUN_VBOXNETFLTMP" or "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\RRNETCAPMP" becomes wrong.
I saw in VBOX.log also an error for USB. May USB Driver for VB is also affected by INFCACHE inconsisteny. Symtoms in running VMs are frozen VMs and a 15 minutes work of process "SYSTEM" on startup of OS (Windows 7), which tries to repair driver installation and causes heavy CPU load at startup, so I cannot work with computer for this 15 minutes.
helfrw
Attachments (1)
Change History (2)
by , 11 years ago
Attachment: | VBoxSVC.log added |
---|
comment:1 by , 8 years ago
Resolution: | → obsolete |
---|---|
Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
VBox.log