VBox 5.1.22 Does Not Start VM after Upgrade from Win7 to Win10

[jkAB]

VM's created with Manager 5.1.22 r115126 were working in Win7. Upgraded to Win10 Enterprise, ver 1703, build 15063.0. VMs will not start. VMs are Ubuntu Xenial 16.04. Tried running the repair VM Manager from the VBox installer. Did not work.

On VM "Start", I get 2 popups. The 1st popup refers to running a cmd 'sc.exe', the results of which are posted. The 2nd popup refers to a file that I pasted below. I could not find a button to attach the file.

COMMAND - SC.EXE

sc.exe query vboxdrv
[SC] EnumQueryServicesStatus:OpenService FAILED 1060:

The specified service does not exist as an installed service.

[jkAB]

I tried following the instructions in the following link, but they did not work. ​https://forums.virtualbox.org/viewtopic.php?f=6&t=66442#p314829

[jkAB]

After running VBoxDrv.inf, the error message in the log file has changed. The last few lines now read:

2c78.2c7c: KnownDllPath: C:\WINDOWS\System32
2c78.2c7c: supR3HardenedVmProcessInit: Opening vboxdrv stub...
2c78.2c7c: supR3HardenedVmProcessInit: Restoring LdrInitializeThunk...
2c78.2c7c: supR3HardenedVmProcessInit: Returning to LdrInitializeThunk...
2c78.2c7c: Registered Dll notification callback with NTDLL.
2c78.2c7c: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\kernel32.dll)
2c78.2c7c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\kernel32.dll
2c78.2c7c: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\KERNEL32.DLL (Input=KERNEL32.DLL, rcNtResolve=0xc0150008) *pfFlags=0xffffffff pwszSearchPath=0000000000004001:<flags> [calling]
2c6c.2c70: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0xc0000005 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 185 ms, CloseEvents);

[Socratis]

1. Do you know how to NOT copy/paste the whole log? As in "attach" the log? It was even in the instructions!

   Attach a (full) log file ("Machine" menu/"Show Log" in the main VirtualBox Manager window) straight away to save time for you and for us. The log file contains a lot of useful information about both the host and the guest systems as well as information about what happened during a particular machine run. Please do not cut and paste it.

2. You do NOT have to hit "Reply", you can simply reply in the form.
3. Even if you hit the "Reply", you can ALWAYS edit your post to delete the parts that are not relevant or repeat themselves. Twice?

Nobody can read a report like that. That's not a report, that's the first three chapters of "War and Peace"...

[jkAB]

ErrorLogFreshVBoxInstall

[jkAB]

Sorry for the long post -- learning curve. I am sure I will make more mistakes. Please be patient.

My latest attempt was a complete removal of VBox 5.1.22 (r115126), and a fresh install, not a repair. My host machine is Win10 Enterprise, ver 1703, build 15063.0. I created a Linux Ubuntu (64-bit) guest and attached the Ubuntu iso file, Ubuntu-16.04-desktop-amd64.iso to the CD virtual drive. I tried to start the VM but got:

Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

I attached the log file (once a ticket is created a button that says Attach File appears).

VBox is completely dead for me.

[Frank Mehnert]

Any AV software installed on your Windows 10 host? If so, which one?

[jkAB]

Not sure. Looking at the Processes list, I am guessing which processes may be AV based on their name. Listed here, my guesses are:

Background Processes

• CrowdStrike Falcon Sensor Service
• CrowdStrike Falcon Sensor Servlet Container
• Cylance Native Agent
• Cylance Protect
• Microsoft Malware Protection Command Line Utility
• Windows Defender notification icon
• Windows Security Health Service

Windows Processes

• Antimalware Service Executable
• Local Security Authority Process (4)
• Secure System
• Windows Security Center