detected INFACHE inconsistency after VirtualBox update
Posted: 24. Jul 2013, 23:17
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]
Uninstallation of RRNETCAP driver and also VB and reinstallation of both, does not repair INFCACHE for all time, just temporarly:
on next driver installation the error "detected INFACHE inconsistency" arises again.
I think there is some dependeny 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.
Any help available for this issue? I want not to reinstall my whole operating system and all applications again, to repair this error in INFCACHE, because it make more than 4 weeks work and if I have again an update from VB the error comes again.
helfrw
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: Select all
>>> [DIF_INSTALLDEVICEFILES - ROOT\NET\0000]
>>> Section start 2013/07/18 20:01:47.311
cmd: C:\Windows\system32\MsiExec.exe -Embedding 1FDC03DC91FC96D96E63DBB24DA7793C M Global\MSI0000
! sig: Verifying file against specific (valid) catalog failed! (0x80096002)
dvi: Committing file queue...
flq: CopyFile: 'C:\Windows\system32\DRIVERS\VBoxNetAdp.sys'
flq: to: 'C:\Windows\Temp\OLDE7CF.tmp'
flq: CopyFile: 'c:\program files\oracle\virtualbox\drivers\network\netadp\VBoxNetAdp.sys'
flq: to: 'C:\Windows\system32\DRIVERS\SETE7DC.tmp'
flq: MoveFile: 'C:\Windows\system32\DRIVERS\SETE7DC.tmp'
flq: to: 'C:\Windows\system32\DRIVERS\VBoxNetAdp.sys'
<<< Section end 2013/07/18 20:01:47.991
<<< [Exit status: SUCCESS]Code: Select all
>>> [DIF_PROPERTYCHANGE - ROOT\SUN_VBOXNETFLTMP\0001]
>>> Section start 2013/07/18 20:01:47.516
cmd: C:\Windows\system32\svchost.exe -k netsvcs
<<< Section end 2013/07/18 20:01:47.519
<<< [Exit status: SUCCESS]Code: Select all
[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 inconsistencyUninstallation of RRNETCAP driver and also VB and reinstallation of both, does not repair INFCACHE for all time, just temporarly:
Code: Select all
! inf: Attempting INFCACHE repair 20:07:30.741
! inf: Verify/Fix on INFCACHE complete, status(4) - Fixed 20:07:49.488I think there is some dependeny 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.
Any help available for this issue? I want not to reinstall my whole operating system and all applications again, to repair this error in INFCACHE, because it make more than 4 weeks work and if I have again an update from VB the error comes again.
helfrw