update from V4.12 to V4.36

[mm_half3]

Hello,

Have a working 4.12 VirtualBox installation on a Windows 7 host with a few ubuntu guest vm's. Thinking about updating to the V4.34, but my last update to V4.12 had problems, none of my Vm's would startup after the update. Can't remember the error message/code, but searching the forum found similar errors, and a clean reinstall brought things back. One of the posts seemed to think the problem was with not installing with proper admin rights. My update attempt was done in a regular user's desktop, not sure if I ran the app as administrator via right click, or just authenticated with an admin account when the the update tried to install. After reading the post did the reinstall logged into an administrator desktop.

My question is what is the best way to run the update? The administrator desktop shortcut to VirtualBox does not see my Vm's, when VirtualBox is run using it. The VM's were created in a regular user desktop. Concerned that if I run update from there it may muck things up again.

Thanks,

[mm_half3]

Anyone have advice on if I should update to latest version of Virtualbox, and if an update is done, which is the correct way to run update, logged in with an admin desktop session, or authenticate with admin account while logged in with a regular user desktop session.

Thanks,

[noteirak]

The way I always do it and never had an issue : run it as the user who originally installed it, and make sure it "run as administrator" but not under the administrator account (unless that account was the one originally used).
You'll keep your VMs in each user profile, like it is means to be.

In 4.3, Virtualbox checks more strictly about VT-x/AMD-V and if you use the OS Type 32 or 64 bits. You might need to tweak the VM settings around a bit in case they fail to start.

[socratis]

The way I always do it and never had an issue : run it as the user who originally installed it, and make sure it "run as administrator" but not under the administrator account (unless that account was the one originally used).

So, say that you have "Admin", "User1" and "User2" with both User accounts running their VMs. "User1" installed it originally with "Run as administrator". "User2" uses the already installed program. An update comes. User2 cannot upgrade it with "Run as administrator"? Or even the "Admin"?

You'll keep your VMs in each user profile, like it is means to be.

That makes sense and the confusion I think comes that they log in as administrator and then they can't find their configuration.

[noteirak]

You can install it as any user you want, as long as it runs with administrator priviledges. But many people seems to have an issue with the installation. So to keep the issues to minimal, I would suggest to install it the same way it was installed before.

[mm_half3]

The way I always do it and never had an issue : run it as the user who originally installed it, and make sure it "run as administrator" but not under the administrator account (unless that account was the one originally used).
You'll keep your VMs in each user profile, like it is means to be.

In 4.3, Virtualbox checks more strictly about VT-x/AMD-V and if you use the OS Type 32 or 64 bits. You might need to tweak the VM settings around a bit in case they fail to start.

Thanks, just did the upgrade using run as administrator, and it looks to have went without a problem. As I was running the upgrade realized another problem I had on my last upgrade, is that I typically access the system with virtualbox installed using remote desktop, and ignored the warning about losing network connectivity. Caught it this time, stopped the installation, and ran it again without a remote connection.


john