Opened 12 years ago
Closed 8 years ago
#11185 closed defect (obsolete)
Virtual Box install hangs - appears to be conflict with VPN network driver
Reported by: | bitbucket | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.2.4 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description
When trying to install Virtual Box on my Dell Win7 64-bit laptop, the install process got near the end and just hung. I checked Process Explorer and the hung thread call stack was the below.
ntoskrnl.exeKeWaitForMultipleObjects+0xc0a ntoskrnl.exeKeAcquireSpinLockAtDpcLevel+0x732 ntoskrnl.exeKeWaitForMultipleObjects+0x26a ntoskrnl.exeNtWaitForSingleObject+0x41f ntoskrnl.exeIoReportTargetDeviceChange+0xe6d ntoskrnl.exeKeSynchronizeExecution+0x3a23 wow64cpu.dllTurboDispatchJumpAddressEnd+0x6c0 wow64cpu.dllTurboDispatchJumpAddressEnd+0xf5 wow64.dll!Wow64SystemServiceEx+0x1ce wow64.dll!Wow64LdrpInitialize+0x429 ntdll.dllRtlUniform+0x6e6 ntdll.dllRtlCreateTagHeap+0xa7 ntdll.dllLdrInitializeThunk+0xe ntdll.dllZwWaitForMultipleObjects+0x15 kernel32.dllWaitForMultipleObjectsEx+0x8e msi.dll!MsiEnumProductsW+0x2bf0 msi.dll!MsiReinstallFeatureW+0x2a4 msi.dll!MsiInstallProductA+0xcc VirtualBox-4.2.4-81684-Win.exe+0x1fcf VirtualBox-4.2.4-81684-Win.exe+0x27f4 kernel32.dllBaseThreadInitThunk+0x12 ntdll.dllRtlInitializeExceptionChain+0x63 ntdll.dllRtlInitializeExceptionChain+0x36
I killed the installer and rebooted. I checked device manager and noticed my VPN client network adapter in the list, "NCP Secure Client Virtual NDIS6 Adapter". This is the adapter created by my VPN client.
I tried disabling that adapter in device manager and rebooted. After the reboot I tried again to install Virtual Box and this time it worked without hanging. After installing, I re-enabled the VPN network adapter and rebooted again and all appears to be working now.
Change History (2)
comment:1 by , 12 years ago
comment:2 by , 8 years ago
Resolution: | → obsolete |
---|---|
Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
ok, the call stack didn't come through right above. Here it is again.