Upgrading to 5.1.11-112094

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Docfxit
Posts: 129
Joined: 23. May 2014, 12:35
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: XP Pro, Win7, Win10

Upgrading to 5.1.11-112094

Post by Docfxit »

I tried installing VirtualBox-5.1.11-112094-Win.exe in Win10 64 bit using a Win7.vdi that was created with VirtualBox-4.3.12-93733-Win.exe in Win7 32bit.

Is there something I can do to get it running?

Thank you,

Docfxit
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Upgrading to 5.1.11-112094

Post by socratis »

I'm sorry, but could you rephrase the question? The "tried installing" throws me a little bit off. Maybe you meant "tried running"?

What's preventing you from running it? Are you getting an error message? Does it abort? Does it even launch?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Upgrading to 5.1.11-112094

Post by scottgus1 »

Be it known that 5.1.11 is a test build (last number odd, test build; even, stable build). It won't be downloadable long. Keep hold of that installer file, you may need it to upgrade if the installer system has a glitch.

The log for your guest shows version 5.1.11 running. this is in the log:

Code: Select all

00:00:02.781293 Shared Folders service loaded
00:00:02.851187 AssertLogRel F:\tinderbox\win-5.1\src\VBox\Devices\Graphics\DevVGA.cpp(6263) int __cdecl vgaR3Construct(struct PDMDEVINS *,int,struct CFGMNODE *): RT_SUCCESS_NP(rc)
00:00:02.851231 PDMDevHlpMMIO2Register(0x10000000,) -> VERR_INVALID_PARAMETER
00:00:02.851241 PDM: Failed to construct 'vga'/0! VERR_INVALID_PARAMETER (-2) - Invalid parameter.
00:00:02.855432 VMSetError: F:\tinderbox\win-5.1\src\VBox\VMM\VMMR3\VM.cpp(363) int __cdecl VMR3Create(unsigned int,const struct VMM2USERMETHODS *,void (__cdecl *)(struct UVM *,void *,int,const char *,unsigned int,const char *,const char *,char *),void *,int (__cdecl *)(struct UVM *,struct VM *,void *),void *,struct VM **,struct UVM **); rc=VERR_INVALID_PARAMETER
00:00:02.855438 VMSetError: Invalid parameter.
00:00:02.855942 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid parameter. (VERR_INVALID_PARAMETER)}, preserve=false aResultDetail=0
00:00:02.856794 Console: Machine state changed to 'PoweredOff'
00:00:02.865868 Power up failed (vrc=VERR_INVALID_PARAMETER, rc=E_FAIL (0X80004005))
00:00:03.071845 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 1920x1040
00:00:03.071882 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={02326f63-bcb3-4481-96e0-30d1c2ee97f6} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0
00:00:03.072108 GUI: Aborting startup due to power up progress issue detected...
00:00:03.358644 OpenGL Error: Render SPU: (MakeCurrent) failed to make 0x58010eec, 0x10000 current with 0x6 error.
Looks like it's trying to start the VGA part of the guest and failing?

Question: why are you using a test build? Is 5.1.11 the first install of Virtualbox on your Windows 10 host? If so, uninstall it and drop back to 5.1.10 or 5.1.6 (not 5.1.8, there's network issues in that version). When installing on Windows you must right-click the installer and choose Run As Administrator form the right-click menu.

Also, did the guest have a saved state when you tried to start in under Windows 10? If so , discard the saved state.
Docfxit
Posts: 129
Joined: 23. May 2014, 12:35
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: XP Pro, Win7, Win10

Re: Upgrading to 5.1.11-112094

Post by Docfxit »

Thank you very much for the great instructions.

I have uninstalled 5.1.11, re-booted and cleaned the temp files.

I have installed 5.1.10 with run as administrator. It installed with no problems.
The Guest is in a powered off state.
When I start Win7 guest I get this error:

Code: Select all

Failed to open a session for the virtual machine Win7.

Invalid parameter. (VERR_INVALID_PARAMETER).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
What can I do to get this started?

Thank you,
Docfxit
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Upgrading to 5.1.11-112094

Post by scottgus1 »

The guest again seems to be dying trying to set up the VGA system, and I noticed there's these lines earlier:

Code: Select all

00:00:02.261487 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_CR_PKCS7_KEY_USAGE_MISMATCH fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume1\Windows\System32\DriverStore\FileRepository\nvltwu.inf_amd64_7abb66182eb8ed83\nvinitx.dll: fKeyUsage=0x0, missing 0x1: \Device\HarddiskVolume1\Windows\System32\DriverStore\FileRepository\nvltwu.inf_amd64_7abb66182eb8ed83\nvinitx.dll
00:00:02.261590 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\WINDOWS\System32\DriverStore\FileRepository\nvltwu.inf_amd64_7abb66182eb8ed83\nvinitx.dll' (C:\WINDOWS\System32\DriverStore\FileRepository\nvltwu.inf_amd64_7abb66182eb8ed83\nvinitx.dll): rcNt=0xc0000190
They refer to a file 'nvinitx.dll' , which seems to be an Nvidia driver file. I don't know if this info is pertinent or not. Try updating your video drivers if possible.
Docfxit
Posts: 129
Joined: 23. May 2014, 12:35
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: XP Pro, Win7, Win10

Re: Upgrading to 5.1.11-112094

Post by Docfxit »

I have updated the video driver. I'm getting the same error.

Could it be one of the settings files is not changing to the current environment?

The last time this Win7 32bit client ran with no errors was when:
The host was Win7 32bit.
Now the host is Win10 64bit.

Thank you,

Docfxit
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Upgrading to 5.1.11-112094

Post by socratis »

  • The Nvidia driver is trying to "inject" itself in every running process.
  • The Nvidia driver is not signed.
  • VirtualBox rejects it.
  • VirtualBox fails to run.
There are two possible outcomes:
  • Get a signed driver.
  • Install the basic drivers without the additional "functionality" that they offer.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Docfxit
Posts: 129
Joined: 23. May 2014, 12:35
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: XP Pro, Win7, Win10

Re: Upgrading to 5.1.11-112094

Post by Docfxit »

I don't know what else to do...

I have downloaded/installed the latest Nvidia driver from Lenovo W550s. Re-booted.

During the install I did not get a message saying the driver is not signed.

The Win7.vdi and Win7.vbox was copied from Win7 to Win10 before installing VirtualBox software.
This same Win7.vdi runs fine in host Win7.
This same Win7.vdi comes up with this error in Win10 dual boot. Same hardware.
Failed to open a session for the virtual machine Win7.

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

Maybe VBox isn't using the correct Interface?
This is a list of my VM's in Win10
C:\Programs\VirtualBox>VBoxManage.exe list vms
"XP" {1f46661d-5b64-47e6-acac-ffd688afd198}
"Win7" {78e3d240-ab46-48bf-b9ef-67197c09e1b5}

In my little knowledge of VBox the interface is not correct. If I'm right how can I correct it?
I have two video drivers on this machine. This is what they look like in Win10.
HTML is not rendering. How can I include the HTML correctly in this reply?

Code: Select all

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
<head>
<title>HTML Report</title>
<style type="text/css">
.theader {background-color: lime; text-align: left;}h3 {font-size:18pt; font-weight:bold; margin-bottom: 2px;}tr:hover td { background: #ddd; }</style>
</head>

<body bgcolor="#FFFFFF" TEXT="#000000">


<a id="Video"></a>
<table WIDTH="100%" BORDER="0" CELLSPACING="0" ALIGN="CENTER">

<CAPTION ALIGN="TOP"><FONT size="5">Video</FONT></CAPTION>

<tr><td><a href="#TOC">Top</a></td></tr>

<tr class="theader">

<th>Property</th>
<th>Value</th>
</tr>
 
<tr bgcolor="#80FFFF">

<td WIDTH="40%">Video Adapter</td>

<td WIDTH="60%">Intel(R) HD Graphics 5500</td>

</tr>

<tr bgcolor="#F0F0F0">

<td>Name [SIW]</td>
<td>Intel Corporation Broadwell-U Integrated Graphics [Lenovo]</td>
</tr>
 
<tr>

<td>Code Name</td>
<td>Not Available</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>Video Processor</td>
<td>Intel(R) HD Graphics Family</td>
</tr>
 
<tr>

<td>Technology</td>
<td>Not Available</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>Adapter DAC Type</td>
<td>Internal</td>
</tr>
 
<tr>

<td>PCI ID</td>
<td>0x8086 / 0x1616 - Intel Corporation / Broadwell-U Integrated Graphics</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>PCI sub ID</td>
<td>0x17AA / 0x2225 - Lenovo</td>
</tr>
 
<tr>

<td>Memory</td>
<td>1024 MBytes</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>Performance Level</td>
<td>Perf Level 0</td>
</tr>
 
<tr>

<td>Adapter BIOS String</td>
<td>Not Available</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>Adapter BIOS Date</td>
<td>Not Available</td>
</tr>
 
<tr>

<td>Video Mode Description</td>
<td>2880 x 1620 x 4294967296 colors</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>Driver Version</td>
<td>20.19.15.4549</td>
</tr>
 
<tr>

<td>Drivers</td>
<td>igdumdim64.dll,igd10iumd64.dll,igd10iumd64.dll,igd12umd64.dll,igdumdim32,igd10iumd32,igd10iumd32,igd12umd32</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>Driver Date</td>
<td>2016-11-10 00:00:00</td>
</tr>
 
<tr>

<td>DirectX</td>
<td>DirectX v12.0</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>Properties</td>
<td> </td>
</tr>
 
<tr bgcolor="#80FFFF">

<td WIDTH="40%">Video Adapter</td>

<td WIDTH="60%">NVIDIA Quadro K620M</td>

</tr>

<tr>

<td>Name [SIW]</td>
<td>NVIDIA Corporation GM108GLM [Quadro K620M] [Lenovo]</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>Code Name</td>
<td>Not Available</td>
</tr>
 
<tr>

<td>Video Processor</td>
<td>Not Available</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>Technology</td>
<td>Not Available</td>
</tr>
 
<tr>

<td>Adapter DAC Type</td>
<td>Not Available</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>PCI ID</td>
<td>0x10DE / 0x137A - NVIDIA Corporation / GM108GLM [Quadro K620M]</td>
</tr>
 
<tr>

<td>PCI sub ID</td>
<td>0x17AA / 0x2225 - Lenovo</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>Memory</td>
<td>2048 MBytes</td>
</tr>
 
<tr>

<td>Performance Level</td>
<td>Current</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>Performance Level</td>
<td>2D Desktop</td>
</tr>
 
<tr>

<td>Performance Level</td>
<td>Default</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>Performance Level</td>
<td>3D Applications</td>
</tr>
 
<tr>

<td>Adapter BIOS String</td>
<td>Not Available</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>Adapter BIOS Date</td>
<td>Not Available</td>
</tr>
 
<tr>

<td>Video Mode Description</td>
<td>Not Available</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>Driver Version</td>
<td>Not Available</td>
</tr>
 
<tr>

<td>Drivers</td>
<td>Not Available</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>Driver Date</td>
<td>Not Available</td>
</tr>
 
<tr>

<td>Properties</td>
<td> </td>
</tr>
 
<tr bgcolor="#80FFFF">

<td WIDTH="40%">Monitor</td>

<td WIDTH="60%">Wide viewing angle & High density FlexView Display 2880x1620</td>

</tr>

<tr bgcolor="#F0F0F0">

<td>Model</td>
<td>VVX16T028J00</td>
</tr>
 
<tr>

<td>Monitor ID</td>
<td>LEN40B5</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>Manufacturer</td>
<td>Lenovo</td>
</tr>
 
<tr>

<td>Manufacturing Date</td>
<td>2013</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>Type</td>
<td>[unknown]</td>
</tr>
 
<tr>

<td>Input</td>
<td>Digital</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>Display Size</td>
<td>15.3" (34 cm x 19 cm)</td>
</tr>
 
<tr>

<td>Brightness</td>
<td>100%</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>Current Resolution</td>
<td>2880 x 1620 @ 60 Hz</td>
</tr>
 
<tr>

<td>Supported Resolution</td>
<td>2880 x 1620 @ 60 Hz - Aspect Ratio 16:9</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>Supported Resolution</td>
<td>2880 x 1620 @ 48 Hz - Aspect Ratio 16:9</td>
</tr>
 
<tr>

<td>EDID Version</td>
<td>1 revision 4</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>DPMS Mode Support</td>
<td>Active Off, Suspend, Standby</td>
</tr>
 
<tr>

<td>Properties</td>
<td> </td>
</tr>
 
<tr bgcolor="#80FFFF">

<td WIDTH="40%">Display Device</td>

<td WIDTH="60%">\\.\DISPLAY1</td>

</tr>

<tr bgcolor="#F0F0F0">

<td>Device Name</td>
<td>Intel(R) HD Graphics 5500</td>
</tr>
 
<tr>

<td>Device Key</td>
<td>\Registry\Machine\System\CurrentControlSet\Control\Video\{21173786-D739-4630-B5A4-FA6A8B9EE302}\0000</td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>Device Flags</td>
<td>DISPLAY_DEVICE_ACTIVE, DISPLAY_DEVICE_PRIMARY_DEVICE</td>
</tr>
 
<tr>

<td>Video Modes</td>
<td> </td>
</tr>
 
<tr bgcolor="#F0F0F0">

<td>Monitor</td>
<td>\\.\DISPLAY1\Monitor0</td>
</tr>
 
</body>
</html>

Code: Select all

Name:            Win7
Groups:          /
Guest OS:        Windows 7 (32-bit)
UUID:            78e3d240-ab46-48bf-b9ef-67197c09e1b5
Config file:     C:\Users\Gary\VirtualBox VMs\Win7\Win7.vbox
Snapshot folder: C:\Users\Gary\VirtualBox VMs\Win7\Snapshots
Log folder:      C:\Users\Gary\VirtualBox VMs\Win7\Logs
Hardware UUID:   78e3d240-ab46-48bf-b9ef-67197c09e1b5
Memory size:     1026MB
Page Fusion:     off
VRAM size:       256MB
CPU exec cap:    100%
HPET:            off
Chipset:         piix3
Firmware:        BIOS
Number of CPUs:  1
PAE:             off
Long Mode:       off
Triple Fault Reset: off
APIC:            on
X2APIC:          off
CPUID Portability Level: 0
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): Floppy
Boot Device (2): DVD
Boot Device (3): HardDisk
Boot Device (4): Not Assigned
ACPI:            on
IOAPIC:          off
BIOS APIC mode:  APIC
Time offset:     0ms
RTC:             local time
Hardw. virt.ext: on
Nested Paging:   on
Large Pages:     off
VT-x VPID:       on
VT-x unr. exec.: on
Paravirt. Provider: Legacy
Effective Paravirt. Provider: None
State:           powered off (since 2016-12-06T22:17:33.275000000)
Monitor count:   1
3D Acceleration: on
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address: 
Teleporter Password: 
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration: 
Autostart Enabled: off
Autostart Delay: 0
Default Frontend: 
Storage Controller Name (0):            IDE
Storage Controller Type (0):            PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  2
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
Storage Controller Name (1):            SATA
Storage Controller Type (1):            IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1):  30
Storage Controller Port Count (1):      1
Storage Controller Bootable (1):        on
IDE (0, 0): C:\Dnload\VirtualBoxConfigure\VBoxGuestAdditions_5.1.10.iso (UUID: 57d067f7-89dd-436f-baf9-d00cef7445e3)
SATA (0, 0): C:\Users\Gary\VirtualBox VMs\Win7\Win7.vdi (UUID: 632c3603-9638-4538-9f75-4485a74103ba)
NIC 1:           MAC: 08002713391C, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 1 Settings:  MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 2:           disabled
NIC 3:           disabled
NIC 4:           disabled
NIC 5:           disabled
NIC 6:           disabled
NIC 7:           disabled
NIC 8:           disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1:          disabled
UART 2:          disabled
UART 3:          disabled
UART 4:          disabled
LPT 1:           disabled
LPT 2:           disabled
Audio:           enabled (Driver: DSOUND, Controller: HDA, Codec: STAC9221)
Clipboard Mode:  Bidirectional
Drag and drop Mode: disabled
VRDE:            disabled
USB:             enabled
EHCI:            disabled
XHCI:            disabled

USB Device Filters:

<none>

Bandwidth groups:  <none>

Shared folders:  

Name: 'Dnload', Host path: 'C:\Dnload' (machine mapping), writable

Video capturing:    not active
Capture screens:    0
Capture file:       C:\Users\Gary\VirtualBox VMs\Win7\Win7.webm
Capture dimensions: 1024x768
Capture rate:       512 kbps
Capture FPS:        25

Guest:

Configured memory balloon size:      0 MB


Please let me know what I can do to get this running.

Thank you,

Docfxit
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Upgrading to 5.1.11-112094

Post by scottgus1 »

The forum doesn't render HTML, as far as I know. The buttons above the textbox for typing new posts are the only markup that the forum uses.

I did just learn that recent updates of Windows 10 have turned on Hyper-v without the user's knowledge. Take a look at that possibility.

I also see that you don't have the Extension Pack installed. Is your guest attempting to use anything that requires the Extension Pack?
Post Reply