Cannot open a new task for the virtual computer

This is for discussing general topics about how to use VirtualBox.
happyliang
Posts: 1
Joined: 25. Oct 2020, 08:33

Cannot open a new task for the virtual computer

Post by happyliang »

Dear friend, I encountered an unsolvable problem when installing virtualbox. I tried all the methods I could think of, but failed. I hope God can help me solve it. Thank you very much.
Below are the errors that occurred when starting the virtual host. Number, but, I don’t know how to solve it. My computer is a 4-screen monitor. I don’t know if there is a conflict.

I installed virtualbox on my laptop and started the new virtual host. Everything is normal. This problem occurs on the desktop. Please help. solve

I use windows 7 ultimate and install the VirtualBox 6.1.16 version



Failed to load R0 module C:\Program Files\Oracle\VirtualBox/VMMR0.r0: Signature #2/3:

Expected at least 2 valid paths, not 1.: \Device\HarddiskVolume2\Program Files\Oracle

\VirtualBox\VMMR0.r0 (VERR_SUP_VP_UNEXPECTED_VALID_PATH_COUNT).

Failed to load VMMR0.r0 (VERR_SUP_VP_UNEXPECTED_VALID_PATH_COUNT).

返回 代码: E_FAIL (0x80004005)
组件: ConsoleWrap
界面: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Cannot open a new task for the virtual computer

Post by scottgus1 »

This error appears to be very unusual.

Uninstall Virtualbox's Extension Pack, then uninstall Virtualbox. Restart your computer.

Right-click the Virtualbox installer and choose Run As Administrator. Let the installation complete. Do not install the Extension Pack for now. Restart your computer again.

Now try Virtualbox. Let us know what happens.
GillP21
Posts: 5
Joined: 26. Oct 2020, 17:30

Re: Cannot open a new task for the virtual computer

Post by GillP21 »

I also had this problem. I did what the other reply recommended and still got the same error.

Failed to load R0 module C:\Program Files\Oracle\VirtualBox/VMMR0.r0: Signature #2/3: Expected at least 2 valid paths, not 1.: \Device\HarddiskVolume2\Program Files\Oracle\VirtualBox\VMMR0.r0 (VERR_SUP_VP_UNEXPECTED_VALID_PATH_COUNT).
Failed to load VMMR0.r0 (VERR_SUP_VP_UNEXPECTED_VALID_PATH_COUNT).


Result Code:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

This is the VBox Log
00:00:03.772686 VirtualBox VM 6.1.16 r140961 win.amd64 (Oct 16 2020 16:33:17) release log
00:00:03.772691 Log opened 2020-10-26T15:16:16.391609800Z
00:00:03.772692 Build Type: release
00:00:03.772695 OS Product: Windows 7
00:00:03.772696 OS Release: 6.1.7601
00:00:03.772699 OS Service Pack: 1
00:00:03.817800 DMI Product Name: To be filled by O.E.M.
00:00:03.822586 DMI Product Version: To be filled by O.E.M.
00:00:03.823023 Firmware type: BIOS
00:00:03.823032 Host RAM: 7368MB (7.1GB) total, 1168MB available
00:00:03.823035 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
00:00:03.823036 Process ID: 2508
00:00:03.823037 Package type: WINDOWS_64BITS_GENERIC
00:00:03.823719 Installed Extension Packs:
00:00:03.823821 Oracle VM VirtualBox Extension Pack (Version: 6.1.16 r140961; VRDE Module: VBoxVRDP)
00:00:03.824875 Console: Machine state changed to 'Starting'
00:00:03.825074 Qt version: 5.6.2
00:00:03.827647 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:04.017824 PDMLdr: pdmR3LoadR0U: pszName="VMMR0.r0" rc=VERR_SUP_VP_UNEXPECTED_VALID_PATH_COUNT szErr="Signature #2/3: Expected at least 2 valid paths, not 1.: \Device\HarddiskVolume2\Program Files\Oracle\VirtualBox\VMMR0.r0"
00:00:04.017900 VMSetError: F:\tinderbox\win-6.1\src\VBox\VMM\VMMR3\PDMLdr.cpp(733) int __cdecl pdmR3LoadR0U(struct UVM *,const char *,const char *,const char *); rc=VERR_SUP_VP_UNEXPECTED_VALID_PATH_COUNT
00:00:04.017905 VMSetError: Failed to load R0 module C:\Program Files\Oracle\VirtualBox/VMMR0.r0: Signature #2/3: Expected at least 2 valid paths, not 1.: \Device\HarddiskVolume2\Program Files\Oracle\VirtualBox\VMMR0.r0
00:00:04.017925 VMSetError: F:\tinderbox\win-6.1\src\VBox\VMM\VMMR3\VM.cpp(563) int __cdecl vmR3CreateU(struct UVM *,unsigned int,int (__cdecl *)(struct UVM *,struct VM *,void *),void *); rc=VERR_SUP_VP_UNEXPECTED_VALID_PATH_COUNT
00:00:04.017929 VMSetError: Failed to load VMMR0.r0
00:00:04.018332 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Failed to load R0 module C:\Program Files\Oracle\VirtualBox/VMMR0.r0: Signature #2/3: Expected at least 2 valid paths, not 1.: \Device\HarddiskVolume2\Program Files\Oracle\VirtualBox\VMMR0.r0 (VERR_SUP_VP_UNEXPECTED_VALID_PATH_COUNT).
00:00:04.018388 Failed to load VMMR0.r0 (VERR_SUP_VP_UNEXPECTED_VALID_PATH_COUNT)}, preserve=false aResultDetail=-5660
00:00:04.018599 Console: Machine state changed to 'PoweredOff'
00:00:04.170420 Power up failed (vrc=VERR_SUP_VP_UNEXPECTED_VALID_PATH_COUNT, rc=E_FAIL (0X80004005))
00:00:04.670969 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600
00:00:04.671017 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0
00:00:04.671201 GUI: Aborting startup due to power up progress issue detected...

VBoxHardening.log

9cc.700: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume2\Windows\System32\wbem\fastprox.dll
9cc.700: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume2\Windows\System32\ntdsapi.dll
9cc.700: supR3HardenedDllNotificationCallback: load 000007fef6830000 LB 0x00027000 C:\Windows\system32\NTDSAPI.dll [fFlags=0x0]
9cc.700: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume2\Windows\System32\ntdsapi.dll
9cc.700: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=000007fef68f0000 'C:\Windows\system32\wbem\fastprox.dll'
9cc.700: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=000007fefe8f0000 'C:\Windows\system32\OLEAUT32.dll'
9cc.700: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=000007fefe9d0000 'C:\Windows\system32\ADVAPI32.dll'
9cc.700: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume2\Windows\System32\winmm.dll
9cc.700: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\system32\WINMM.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=00000000008cbfd0:C:\Program Files\Oracle\VirtualBox;C:\Windows\system32;C:\Windows\system;C:\Windows;C:\Program Files\Java\jdk-11.0.8\bin;C:\Program Files\Java\jre1.8.0_261\bin;C:\Program Files\Oracle\VirtualBox\; [calling]
9cc.700: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=000007fef6ac0000 'C:\Windows\system32\WINMM.dll'
9cc.9dc: \Device\HarddiskVolume2\Program Files\Oracle\VirtualBox\VBoxVMM.dll: Signature #1/2: info status: 24202
9cc.9dc: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=000007feff340000 'C:\Windows\system32\setupapi.dll'
9cc.9dc: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcr100.dll'.
9cc.9dc: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'vboxrt.dll'.
9cc.9dc: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume2\Program Files\Oracle\VirtualBox\VBoxVMM.dll) WinVerifyTrust
9cc.9dc: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume2\Program Files\Oracle\VirtualBox\VBoxVMM.dll
9cc.9dc: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'vboxrt.dll'...
9cc.9dc: supR3HardenedWinVerifyCacheProcessImportTodos: 'vboxrt.dll' -> '\Device\HarddiskVolume2\Program Files\Oracle\VirtualBox\vboxrt.dll' [rcNtRedir=0xc0150008]
9cc.9dc: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcr100.dll'...
9cc.9dc: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcr100.dll' -> '\Device\HarddiskVolume2\Program Files\Oracle\VirtualBox\msvcr100.dll' [rcNtRedir=0xc0150008]
9cc.9dc: supR3HardenedMonitor_LdrLoadDll: pName=C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=00000000008cbfd0:C:\Program Files\Oracle\VirtualBox;C:\Windows\system32;C:\Windows\system;C:\Windows;C:\Program Files\Java\jdk-11.0.8\bin;C:\Program Files\Java\jre1.8.0_261\bin;C:\Program Files\Oracle\VirtualBox\; [calling]
9cc.9dc: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume2\Program Files\Oracle\VirtualBox\VBoxVMM.dll
9cc.9dc: supR3HardenedDllNotificationCallback: load 000007fed3480000 LB 0x0037e000 C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL [fFlags=0x0]
9cc.9dc: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume2\Program Files\Oracle\VirtualBox\VBoxVMM.dll
9cc.9dc: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=000007fed3480000 'C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL'
9cc.b04: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=000007feff340000 'C:\Windows\system32\setupapi.dll'
9cc.1b2c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=000007fefe8f0000 'C:\Windows\system32\OLEAUT32.dll'
9cc.b04: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=000007fefe8f0000 'C:\Windows\system32\OLEAUT32.dll'
9cc.700: supR3HardenedDllNotificationCallback: Unload 000007fefb240000 LB 0x0000e000 C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxPuelMainVM.DLL [flags=0x0]
9cc.700: supR3HardenedDllNotificationCallback: Unload 000007fef68f0000 LB 0x000e2000 C:\Windows\system32\wbem\fastprox.dll [flags=0x0]
9cc.700: supR3HardenedDllNotificationCallback: Unload 000007fef6830000 LB 0x00027000 C:\Windows\system32\NTDSAPI.dll [flags=0x0]
9cc.700: supR3HardenedDllNotificationCallback: Unload 000007fef6480000 LB 0x00014000 C:\Windows\system32\wbem\wbemsvc.dll [flags=0x0]
9cc.700: supR3HardenedDllNotificationCallback: Unload 000007fefa6f0000 LB 0x0000f000 C:\Windows\system32\wbem\wbemprox.dll [flags=0x0]
9cc.700: supR3HardenedDllNotificationCallback: Unload 000007fef6ba0000 LB 0x00086000 C:\Windows\system32\wbemcomn.dll [flags=0x0]
9cc.700: supR3HardenedDllNotificationCallback: Unload 000007fed4710000 LB 0x000ef000 C:\Program Files\Oracle\VirtualBox\VBoxProxyStub.dll [flags=0x0]
9cc.700: supR3HardenedDllNotificationCallback: Unload 000007fed4350000 LB 0x003c0000 C:\Program Files\Oracle\VirtualBox\VBoxC.dll [flags=0x0]
9cc.700: Terminating the normal way: rcExit=0
137c.1b38: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 6111 ms, the end);
688.9b0: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 6503 ms, the end);
GillP21
Posts: 5
Joined: 26. Oct 2020, 17:30

Re: Cannot open a new task for the virtual computer

Post by GillP21 »

scottgus1 wrote:This error appears to be very unusual.

Uninstall Virtualbox's Extension Pack, then uninstall Virtualbox. Restart your computer.

Right-click the Virtualbox installer and choose Run As Administrator. Let the installation complete. Do not install the Extension Pack for now. Restart your computer again.

Now try Virtualbox. Let us know what happens.
This one didn't worked
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Cannot open a new task for the virtual computer

Post by scottgus1 »

Could be a new problem with Windows 7 and 6.1.16.
Can you uninstall the Extension Pack and Virtualbox, reboot, then install 6.1.14 with Right-click run As Administrator? (Just Virtualbox, not the Extension Pack, please.)
GillP21
Posts: 5
Joined: 26. Oct 2020, 17:30

Re: Cannot open a new task for the virtual computer

Post by GillP21 »

scottgus1 wrote:Could be a new problem with Windows 7 and 6.1.16.
Can you uninstall the Extension Pack and Virtualbox, reboot, then install 6.1.14 with Right-click run As Administrator? (Just Virtualbox, not the Extension Pack, please.)
I did this exactly
GillP21
Posts: 5
Joined: 26. Oct 2020, 17:30

Re: Cannot open a new task for the virtual computer

Post by GillP21 »

scottgus1 wrote:Could be a new problem with Windows 7 and 6.1.16.
Can you uninstall the Extension Pack and Virtualbox, reboot, then install 6.1.14 with Right-click run As Administrator? (Just Virtualbox, not the Extension Pack, please.)
I did the exact same thing and yet I got the same problem. I've been trying a lot of suggestions from forums and yet it still doesn't work. It's shortening my patience.
GillP21
Posts: 5
Joined: 26. Oct 2020, 17:30

Re: Cannot open a new task for the virtual computer

Post by GillP21 »

GillP21 wrote:
scottgus1 wrote:This error appears to be very unusual.

Uninstall Virtualbox's Extension Pack, then uninstall Virtualbox. Restart your computer.

Right-click the Virtualbox installer and choose Run As Administrator. Let the installation complete. Do not install the Extension Pack for now. Restart your computer again.

Now try Virtualbox. Let us know what happens.
This one didn't worked
This time It worked. I tried installing an older version of virtual box. The latest version didnt worked. But the 6.0.24 worked.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Cannot open a new task for the virtual computer

Post by scottgus1 »

GillP21 wrote:
scottgus1 wrote:Could be a new problem with Windows 7 and 6.1.16.
Can you uninstall the Extension Pack and Virtualbox, reboot, then install 6.1.14 with Right-click run As Administrator? (Just Virtualbox, not the Extension Pack, please.)
I did the exact same thing and yet I got the same problem. I've been trying a lot of suggestions from forums and yet it still doesn't work. It's shortening my patience.
Regrettably, I can't help, because there's no log to see what happened with 6.1.14 to compare with 6.1.16, or with 6.0.24. No logs = no help, unfortunately, there's no data to deduce from.

What was the last version, if any, that your Virtualbox did work on? Or did you start off fresh with 6.1.16?
RussianIvan
Posts: 1
Joined: 31. Oct 2020, 10:56

Re: Cannot open a new task for the virtual computer

Post by RussianIvan »

GillP21 wrote:
GillP21 wrote:
scottgus1 wrote:This error appears to be very unusual.

Uninstall Virtualbox's Extension Pack, then uninstall Virtualbox. Restart your computer.

Right-click the Virtualbox installer and choose Run As Administrator. Let the installation complete. Do not install the Extension Pack for now. Restart your computer again.

Now try Virtualbox. Let us know what happens.
This one didn't worked
This time It worked. I tried installing an older version of virtual box. The latest version didnt worked. But the 6.0.24 worked.
Thanks guys! I also had this problem in latest VB 6.1 version, and the downgrade to 6.0.24 solved the issue for me as well. I use Windows 7 x64 Ultimate. :)
otrees2
Posts: 2
Joined: 5. Mar 2021, 08:08

Re: Cannot open a new task for the virtual computer

Post by otrees2 »

Hi, I also started to have this problem when 6.1.16 appeared. When after installing 6.1.16 I got that error I just rolled back to 6.1.14. Now, when 6.1.18 released, after upgrade to it I still cannot run any VM with the same error. Tried to install with Admin etc. as suggested didn't help also. Machine is Windows 7 Home Premium.

But I have dualboot Windows 7 Home Premium one the same machine, and in another instance of Windows on the same machine the version 6.1.18 has installed and worked correctly. So, then it is not a hardware and/or Windows itself, it is something with the environment in general, other installed software etc. Maybe even some VirtualBox configuration, amount of VMs... For example in the instance of Windows where it is not working, there is no Java installed, although in the other one it is... Also I'm guessing maybe there is some library missing of cpp or dotnet... or wrong version of it..

Also in the error message there is a backslash and a slash in it before VMMR0.r0 part, maybe this is the cause? See the error below:
Failed to load R0 module C:\Program Files\Oracle\VirtualBox/VMMR0.r0: Signature #2/3: Expected at least 2 valid paths, not 1.: \Device\HarddiskVolume6\Program Files\Oracle\VirtualBox\VMMR0.r0 (VERR_SUP_VP_UNEXPECTED_VALID_PATH_COUNT).
Failed to load VMMR0.r0 (VERR_SUP_VP_UNEXPECTED_VALID_PATH_COUNT).
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Cannot open a new task for the virtual computer

Post by scottgus1 »

FWIW I have since learned that Windows 7 is no longer a supported host OS: https://www.virtualbox.org/manual/ch01. ... tossupport

Maybe it will run on some Windows 7's and not others. Perhaps other host drivers might interfere.
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Cannot open a new task for the virtual computer

Post by fth0 »

AFAICS, the error code means that VirtualBox could not find all certificates needed to verify the code signature(s) of the VMMR0.ro file. If this assumption is correct, there will be at least one intermediate or root certificate that is only available on one of your hosts.
otrees2
Posts: 2
Joined: 5. Mar 2021, 08:08

Re: Cannot open a new task for the virtual computer

Post by otrees2 »

Could you please be more specific where to check for certificates and how to learn what possible certificates are missing? And, if so, where to obtain those? I've got not enough knowledge on this topic unfortunately.
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Cannot open a new task for the virtual computer

Post by fth0 »

otrees2 wrote:Could you please be more specific where to check for certificates and how to learn what possible certificates are missing? And, if so, where to obtain those?
In Windows Explorer, navigate to C:\Program Files\Oracle\VirtualBox\, right click on VMMR0.r0, choose Properties, and open the Digital Signatures tab. I'll try and summarize what you can discover when opening several further dialogs from this starting point:

On the Digital Signatures tab, there will be a number of signatures displayed, usually 2 or 3 for a VirtualBox executable. Each signature involves 2 certificates, one for code signing and one for timestamping. Each certificate will be signed by an intermediate certificate, and each intermediate certificate will be signed by a root certificate. In consequence, there will be (up to) 6 intermediate certificates and (up to) 6 root certificates involved (*).

The root certificates should be available in the Windows Certificate Stores. Press the Windows key, enter "cert" and select the Certificate Manager. Search for the necessary root certificates in both of your hosts. If you find one of the certificates on one host but not on the other, you can export the certificate to a file, and import the file into the other Windows installation (e.g. by double clicking in Windows Explorer). If that doesn't help, note all differences between your hosts from all visited dialogs and tell us about them.

(*) There is a possibility that it is even more complicated. In Windows 10, under certain conditions additional Microsoft cross certificates are needed, which sign the root certificates from other companies (e.g. VeriSign), and those certificates are ignored by the the Digital Signatures tab dialogs ...
Post Reply