Cannot Start VM after Update 5.0.10 or 5.0.12

[gerhardgt]

Hallo,
I'm using virtualbox since the beta's of v5, because only with V5 there was no problem to install from a windows host - in my case Win8.1Pro - windows 10.
So i went through 5.0.4 and 5.06 and everthing was fine.
I missed update 5.0.8. When I installed 5.0.10 the first time - weeks ago - i could not start the client any more ...
I tried many thing but i did'nt get it run. The client starts and when the spinning wheel from W10 normally comes on the screen, there is nothing, and i can wait and wait forever. I killed the client with power off, and the next time - the same.
So i installed back version 5.0.6 and everthing was fine until today when i installed v 5.0.12. Same symptom when the client starts no spinning wheel from W10 and i can wait forever ... Once more V 5.0.6 installed and everything is O.K.
What i was wondering, when I installed an older version from virtualbox i was never prompted to install the older version of the extension pack. So i now have Virtual Box V 5.0.6 with extension pack V 5.0.12 installed. Since I was never able to start VB 5.0.10 or 5.0.12 the Guest Addition is v 5.0.6.
So what can I do?
Configuration:
Host: W8.1 Pro, 16 GB Memory, 120 GB SSD (60 GB free), Intel Grafik.
Guest: W10.Pro 8 GB Memory, 25GB HD - and EFI enabled.
On both guest and host standard MS Antivirus installed. No special Software just plain Win8.1Pro and Win10Pro ...
I have tried to read the log, but because of the reinstall of another version and many try and error - i do not know which log file i should append.
Can anyone please help - thanks in advance
Gerhard

[socratis]

Well, since we're trying to troubleshoot something that is not working for you, here is what you do:
- Shut down all your VMs. I'm not talking pause, save or anything like that, I'm talking shut down the guest.
- Uninstall VirtualBox.
- Install VBox 5.0.12.
- Install the matching Extension Pack.
- Start the VM.
- Shut down the VM, if it hasn't aborted by itself, or you were forced to kill it.
- Right-click on the VM in the VirtualBox Manager.
- Select "Show Log..."
- Save it, ZIP it and attach it in your response.

[gerhardgt]

@socrates
Thank you for your reply.
I did it as you listed. Deinstall all incl. Extenstion Pack and installation Folder.
New install of version 5.0.12r104815 and Extension Pack. Here i have one question: I'm always logged in as an user. When i install VirtualBox i am prompted for an Admin account password. When i try to install the extension pack the program aborts saying i have to be logged in as administrator - why?

Here is the text of the message:
Das Zusatzpaket C:/GT/Temp/Oracle_VM_VirtualBox_Extension_Pack-5.0.12-104815.vbox-extpack konnte nicht installiert werden.
The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Membership in the Administrators group is required to perform this action.
Fehlercode:E_FAIL (0x80004005)
Komponente:ExtPackManagerWrap
Interface:IExtPackManager {edba9d10-45d8-b440-1712-46ac0c9bc4c5}

Then I started virtual Box and the guest - and the same as before - no spinning wheel and no action on hd an taskmanage. I waited about 2 to 3 minutes and then i ended the program via the x in the MenuBar.
Find attached the log file.

Thank you in advance for an answer
Gerhard

[socratis]

When i install VirtualBox i am prompted for an Admin account password. When i try to install the extension pack the program aborts saying i have to be logged in as administrator - why?

Because VirtualBox, like any other program that gets installed, modifies the "Program Files" directory. On top of that, it installs kernel drivers, which only an administrator can do.

My favorite installation method on Windows is to log in as an administrator, right-click on the installer and choose "Run as administrator" (yeah, I know, it's twice the admin, but it does make a difference), install the ExtPack and then log back in as your everyday (simple, restricted) user.

Now, from the log:

rejecting 'c:\gt\gtprogs\sizer\sizerhook64.dll'

It seems that the "Sizer" program tries to hook itself to VirtualBox, something that is not allowed since version 4.3.12. You need to get rid of it unfortunately, or look if they have an update where their program is digitally signed.

00:00:05.258593   CpuExecutionCap   <integer> = 0x0000000000000050 (80)
00:00:05.258605   NumCPUs           <integer> = 0x0000000000000004 (4)
00:00:16.631996 CPUM: Physical host cores: 4

You have 4 cores on your host and you've assigned all of them to your guest. True, you've set an 80% execution cap, but it would be wiser to assign a maximum of 3 to your guest.

00:00:05.259028 [/Devices/efi/] (level 2)

Can you give me one good reason for switching EFI on? I don't believe that this is what the default template has.

00:00:05.259186 [/Devices/ich9pci/] (level 2)

Can you give me one good reason for switching to ICH9? I don't believe that this is what the default template has. Mind you, as the tooltip over the control to change it says "support is experimental".

See if taking care of the above helps.

[gerhardgt]

@socratis

Because VirtualBox, like any other program that gets installed, modifies the "Program Files" directory. On top of that, it installs kernel drivers, which only an administrator can do.

I know that Administrator privileges are needed to install the program. I only mentioned that i am forced to enter admin credentials at installation of the program and NOT at installation of the expansion pack.

It seems that the "Sizer" program tries to hook itself to VirtualBox, something that is not allowed since version 4.3.12. You need to get rid of it unfortunately, or look if they have an update where their program is digitally signed.

I can't believe that, since the program is loaded after windows 10 is loaded. But nevertheless i removed that program (via install v5.0.6 - remove it - install v.5.0.12) and the same happens - no spinning wheel, the screen with the ms windows (or sometimes in addition the message: trying to repair windows ... but nothing happens - for hours !!

You have 4 cores on your host and you've assigned all of them to your guest. True, you've set an 80% execution cap, but it would be wiser to assign a maximum of 3 to your guest.

I tried this too - with 2 Prozessors and 100% or 2 prozessors and 80% - but the same: no start of windows and no spinning wheel.

Can you give me one good reason for switching EFI on? I don't believe that this is what the default template has.

The first reason that you have an option to go from the OS (Win) directly to bios, the second is that the format of partition table in enhanced and many more. But for me the mentioned two are important. We have now for year (U)EFI Support on newer motherboards and there you have even troubles when trying to install an OS without EFI. And last but not least MAC has (U)EFI support for years ...

Can you give me one good reason for switching to ICH9? I don't believe that this is what the default template has. Mind you, as the tooltip over the control to change it says "support is experimental".

As I understood PIIX3 is the older one so i selected ICH9.

Since nothing seem to get me out of this situation i tried to make a new VM. But when i try to attach the existing Virtual disk (either the original or a copy made with the built in option of VirtBOX i receive 2 error messages. (See appended Screenshots)

So the only solution seems to do a complete new installation, but then i think i will loose my key for windows 10. I also searched the net for converting an efi image to an normal image but i did not find any hint for that.

The thing which is for me totally unexpected, is that whatever i change in the VM and does not work on v5.0.107v5.0.12 is working without any issue on v5.0.6. (And beside all previous version since the beta's of v5. It was mainly the reason why i gave up any older versions, an only used VirtualBox V5x with the windows 10 installation).

So it looks like that i have to use v5.0.6 until the next release and maybe it is then fixed - maybe!

Regards Gerhard

[gerhardgt]

@all
Installed today the new version of Virtual Box (v5.0.14)
My problem still exists. When starting under v5.0.14 the guest starts with the windows logo and no spinning wheel - and that forever .... nothing more.
One more i changed back to my latest running version v5.0.6 - and voila - everthing works as before.
One change seemed to be implemeted. Now if you have v5.0.6 installed you are requested to install the expansion pack with the same version. Before the update i can also use Expansion Pack v5.0.12 under v5.0.6 !

So the result seems to be to stay on version v5.0.6 - maybe forever ....

Regards
Gerhard