After Update on 5.0.20 Error

[HeinzL]

Hello

After updating on the latest version I cannot create a VM with Win 7: I get:

Für die virtuelle Maschine Win 7 konnte keine neue Sitzung eröffnet werden.

The device helper structure version has changed.

If you have upgraded VirtualBox recently, please make sure you have terminated all VMs and upgraded any extension packs. If this error persists, try re-installing VirtualBox. (VERR_PDM_DEVHLPR3_VERSION_MISMATCH).

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


The VM with XP works fine and there was a VM with Win 7 before also working ok, but I had it to remove because I need another language version.

Extension has been deleted.

Any idea?

Thx in advance!

Heinz

[scottgus1]

A google search on "device helper structure version has changed site:forums.virtualbox.org" gives posts like this:
viewtopic.php?f=6&t=76242#p354924
Check that extension pack and be sure all guests are completely shut down. If any are save-stated you will need to discard the saved state.

If "Extension has been deleted." means you uninstalled the extension pack, make sure that the guest isn't using anything the extension pack enables.

[HeinzL]

Hi and thanks

That seems not to be the problem:

I have 2 VM running
- Win XP using the extensions and runs
- Win 7 who has the problem and no extension (it didn't even allow me to install the OS)

After restoring the system to version 5.0.14 everything is ok!

It seem to be an issue with the new version of VBox.

[mpack]

No, the issue is that you had the VM in a saved state when you upgraded.

[HeinzL]

I don¨T think so, The XP certainly not and the Win 7 wasn't installed, But ok, I will try this tomorrow and post the result

[mpack]

The reported message, AFAIK, is a saved state version compatibility error. It can't happen if you aren't using saved states.

[HeinzL]

Of course you are obviously the experts, but please cosider:

- the Win XP machine worked always without problems¨
- after having the error message, I completely deleted the Win7 machine and recreated it, when I wanted to install the OS, ther error message came back.

[scottgus1]

- Win XP using the extensions and runs
- Win 7 who has the problem and no extension (it didn't even allow me to install the OS)

This makes me think we have a terminology discrepancy. There is an Extension Pack which goes with Virtualbox on the host OS. This Extension Pack does not go in the guest. The Extension Pack must be upgraded when Virtualbox is upgraded.

There are Guest Additions that go in the guests for further capabilities inside the guest OS. The Guest Additions do not get installed on the host OS. These Guest Additions are what I believe you are referring to when you say "XP using the extensions". Guest Additions normally don't have to be updated when upgrading Virtualbox, unless a new feature is desired.

Note the error message:

please make sure you have terminated all VMs and upgraded any extension packs

In addition to the possibility a guest is save-stated, there is also the possibility that you mistook what you needed to upgrade and did not upgrade the host OS's Extension Pack when you upgraded Virtualbox.

Since you went back to 5.0.14, let's confirm that all of your guests are completely shut down, and then run the upgrade again.

Please right-click each guest you have. If the menu choice "Discard Saved State" is dark print, not grayed out, start the guest and use the guest OS's Shut Down command to completely shut down the guest OS. After this the "Discard Saved State" should be grayed out for that guest.

In the main Virtualbox window, click File, Preferences, then Extensions. Right-click the Extension Pack, then remove it.

Now run the Virtualbox upgrade. Whatever version you upgrade to, there will be a matching version Extension Pack that you will need to download if you want those features. (See the help file for what the Extension Pack gives your Virtualbox.) If you want the Extension Pack, download the correct version to match the version of Virtualbox you're installing, then Start Virtualbox, go to File, Preferences, Extensions, and install the Extension Pack., Remember, Virtualbox and Extension Pack version numbers must match.

You should now be able to start your guests.

[HeinzL]

Hi

You were of course right ! Thx so much!

No I have another problem: I wnat to virtualize my running system, which is an Win 7 pro OEM. It seems to be a problem to start an OEM licence in VB on the system where the "original" is running?

Any workaround? I have also a full version of Win7, but I cannot copy the files into a "blank" OS?

Thanks for all your help!

[scottgus1]

Glad you got it working! Good on ya, mate!

As for Windows OEM, whether it will run in a guest depends on:

the company that provided the OEM disc - Some, like Dell and HP, lock their OEM discs to the BIOS of the physical PC, which prevents the OS from being activated on other PCs, including a Virtualbox guest.

The legality - if you are still running the OEM disc as your host OS, you can't legally run it on another PC, even if you can install it successfully. It all depends on how thorough Microsoft is in tracking Windows activation as to whether you may find your host OS unactivated one day.

Retail versions can be moved to other PCs, or a VB guest, as long as you stop using it on the old PC.

Is your full Windows 7 on a disc or an ISO file? Or is it already installed?

[mpack]

Retail versions can be moved to other PCs, or a VB guest, as long as you stop using it on the old PC.

The same is true of OEM licenses actually, at least in some jurisdictions (i.e. the EU, I can't speak for elsewhere). In the EU a landmark court decision determined that if you obtained the used license legally (e.g. if it was bundled with a PC) then you can dispose of it in any way you see fit, including reusing or even selling it. Ironically I believe it was Oracle which was at the butt end of this decision. Some bloggers say that OEM software is excluded, but they seem to be confusing the license terms (exhausted on first sale), with the law.

[HeinzL]

Hi, yes beside of the OS on my HP PC I have also a CD of OEM Win 7 Pro which I installed on a Notebook, it is not from a manufacturer and can be installed anywhere.

I just want to save my Win 7 installation on the PC before upgrading to Win 10, because I use some older SW (especially Adobe) which is known to have problems with Win 10. I think I read, that Microsoft is allowing to use both OS in parallel.

[scottgus1]

I've actually read that when you do the free upgrade from 7 or 8 to 10, 10 takes over ("consumes") the license for 7 or 8, so the 7 or 8 media is orphaned and can no longer be activated. (See http://answers.microsoft.com/en-us/wind ... e93ab20c74)

Converting a Windows physical PC to Virtual is possible, search "P2V site:forums.virtualbox.org". Also see Migrate existing Windows installations to VirtualBox. Of course you could also just install the OS and the old programs fresh in the guest, as long as you have the install media and you can activate any software that needs activating.

[mpack]

I've actually read that when you do the free upgrade from 7 or 8 to 10, 10 takes over ("consumes") the license for 7 or 8, so the 7 or 8 media is orphaned and can no longer be activated.

If the old product key is still in use then it can't be used somewhere else unless your license allows it - and they generally don't. This is something the activation server should enforce.

There used to be a controversy which you may be remembering, whereby once the Win7 or Win8 product key was upgraded and activated as such on the MS server, there was no option to downgrade again. I believe that position was reversed by MS when news of it stopped people upgrading.