Failed to open a session for the virtual machine Win7.

[kb1376]

Failed to open a session for the virtual machine Win7.

The virtual machine 'Win7' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\ronald.benefield\VirtualBox VMs\Win7\Logs\VBoxStartup.log'.

Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

It errors out when getting to the dciman32.dll, fatal error on virtualbox.dll

1e58.7a4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\ddraw.dll
1e58.7a4: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status -22900 (0xffffa68c)) on \Device\HarddiskVolume1\Windows\System32\dciman32.dll
1e58.7a4: Error (rc=0):
1e58.7a4: supR3HardenedScreenImage/NtCreateSection: cached rc=Unknown Status -22900 (0xffffa68c) fImage=1 fProtect=0x10 fAccess=0xf cHits=1 \Device\HarddiskVolume1\Windows\System32\dciman32.dll
1e58.7a4: supR3HardenedDllNotificationCallback: Unload 000007fede830000 LB 0x00875000 C:\Program Files\Oracle\VirtualBox\VirtualBox.dll [flags=0x0]
1e58.7a4: supR3HardenedDllNotificationCallback: Unload 000007fee3740000 LB 0x0011d000 C:\windows\system32\OPENGL32.dll [flags=0x0]
1e58.7a4: supR3HardenedDllNotificationCallback: Unload 000007fee3880000 LB 0x000f1000 C:\windows\system32\DDRAW.dll [flags=0x0]
1e58.7a4: supR3HardenedDllNotificationCallback: Unload 000007fee6460000 LB 0x0002d000 C:\windows\system32\GLU32.dll [flags=0x0]
1e58.7a4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\Program Files\Oracle\VirtualBox\VirtualBox.dll'
1e58.7a4: Fatal error:
1e58.7a4: supR3HardenedMainGetTrustedMain: LoadLibrary "C:\Program Files\Oracle\VirtualBox/VirtualBox.dll" failed, rc=1790
1ff4.1104: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 2520 ms, the end);
18e4.1034: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 3664 ms, the end);

[scottgus1]

dciman.dll seems to be a Windows dll, and likely you're getting the error because a recent Windows update has been hosing the trust certificates again. Virtualbox won't run with that issue - see viewtopic.php?f=6&t=66639

Try hunting through your most recent Windows updates for one that affects dciman.dll and uninstall it. Perhaps KB3045999 or KB3004394.

[kb1376]

dciman.dll seems to be a Windows dll, and likely you're getting the error because a recent Windows update has been hosing the trust certificates again. Virtualbox won't run with that issue - see viewtopic.php?f=6&t=66639

Try hunting through your most recent Windows updates for one that affects dciman.dll and uninstall it. Perhaps KB3045999 or KB3004394.

I'm not a hundred percent sure that the issue is with the dciman32.dll file. I only noticed it as an error, then the system crashes. I don't have either KB3045999 or KB3004394 installed on the system. I'm not familiar with the VBox logs, so need some other eyes.

[kb1376]

Reinstalled the 4.3.26 again, and now I'm getting a new error.

1514.1b30: supR3HardenedDllNotificationCallback: load 000007fefd790000 LB 0x00036000 C:\windows\system32\CFGMGR32.dll [fFlags=0x0]
1514.1b30: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\cfgmgr32.dll
1514.1b30: supR3HardenedDllNotificationCallback: load 000007fefe6d0000 LB 0x000d7000 C:\windows\system32\OLEAUT32.dll [fFlags=0x0]
1514.1b30: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -22900 (0xffffa68c)) on \Device\HarddiskVolume1\Windows\System32\oleaut32.dll
1514.1b30: Error (rc=0):
1514.1b30: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -22900 (0xffffa68c) fImage=1 fProtect=0x0 fAccess=0x0 cHits=3 \Device\HarddiskVolume1\Windows\System32\oleaut32.dll
1514.1b30: Fatal error:
1514.1b30: supR3HardenedDllNotificationCallback: supR3HardenedScreenImage failed on 'C:\windows\system32\OLEAUT32.dll' / '\??\C:\windows\system32\OLEAUT32.dll': 0xc0000190
136c.1a44: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1888 ms, the end);
3bc.1084: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 3076 ms, the end);

[kb1376]

Updated logs

[kb1376]

Updated logs, still no resolution.

[kb1376]

Still no resolution. updated logs.

[scottgus1]

Still looks like the same issue to my inexperienced eyes. Throughout the log files, you'll find the words "lacks WinVerifyTrust" next to Windows & Virtualbox dll's. Apparent cause - Microsoft messed up the certificates. Try uninstalling all Microsoft updates since this issue began, and let them get re-installed one at a time until the issue returns.
If you really have to get going, you could try version 4.3.12, which doesn't have the security hardening. All but the most recent Linux guests should run. Just have to make sure your host doesn't have & doesn't get malware on it.

[kb1376]

Still looks like the same issue to my inexperienced eyes. Throughout the log files, you'll find the words "lacks WinVerifyTrust" next to Windows & Virtualbox dll's. Apparent cause - Microsoft messed up the certificates. Try uninstalling all Microsoft updates since this issue began, and let them get re-installed one at a time until the issue returns.
If you really have to get going, you could try version 4.3.12, which doesn't have the security hardening. All but the most recent Linux guests should run. Just have to make sure your host doesn't have & doesn't get malware on it.

Thanks, problem is my computer is managed by GPO. While I may have local administration on the machine and can remove the updates, the updates will get reinstalled at the end of the night. I'll give the 4.3.12 a shot and see what happens.

[frank]

Please could you try the latest Windows test build (>= r100091? It contains a fix which should allow you to install the Microsoft hotfix which is highly recommended as they contain important security fixes. Though I don't know if this build will fix your issues as they might not be related to this fix.