virtualbox.org

Everything was fine until I upgraded to 4.1.18 on the following hardware:MacBook Pro, Mac OS X (10.7.4), 16gb ram which resulted in all VMs inaccessible. NIGHTMARE

After upgrade it took 48hours of back and forth on this forum (viewtopic.php?f=8&t=50184)to get things functional again, at lest the XP_PRO machines.

AT ISSUE is the Windows-7 machine although now it is NOT inaccessible but the the thing will not fire up and fails to launch and will not launch normally.

This virtual box program has worked flawlessly. I have only been a Mac user for less than 3 months and know nothing else but the nightmare of WINDOWS for 30 years;I digress.

This 4.1.18 upgrade needs something? It either needs detailed explicit instructions for people like me to avoid the obvious blind pitfalls that exist;I digress.

Here are 2 screen shots which is the last issue surrounding the 72hours of Heck since the 4.1.18 upgrade...

So does anyone have any ideas about what is going on with this upgrade and the launch failure?

THANKS in ADVANCE.

What happens if you let the repair continue? Any message that are produced needs to be posted.
Assuming that you have installed the guest additions and the wddm drivers you need to set 3D on and increase the vRAM to at least 128MB in the display section of the guest.

Perryg wrote:What happens if you let the repair continue? Any message that are produced needs to be posted.

What I get is the BLACK attachment and the error message that is the first sentence.


Assuming that you have installed the guest additions and the wddm drivers you need to set 3D on and increase the vRAM to at least 128MB in the display section of the guest.

Do I have to reinstall the guest additions? I suppose I need to launch windows-7 to be able to re-install that stuff.....

People should think twice before upgrading .

I said nothing about re-installing. I wanted to know if on your previous install you had installed the guest additions with wddm drivers and 3D enabled. If so that would need to be set in this one as mentioned above. You can complain later but for right now if you want my help lets keep it to the point. I also need to know what happens if you let the repair happen. Does it finish and if not exactly what are the error message/s.

Perryg wrote:I said nothing about re-installing. I wanted to know if on your previous install you had installed the guest additions with wddm drivers and 3D enabled. If so that would need to be set in this one as mentioned above. You can complain later but for right now if you want my help lets keep it to the point. I also need to know what happens if you let the repair happen. Does it finish and if not exactly what are the error message/s.

guest additions were installed.
not sure about 3d; i tried to get some games to run but they wouldn't so the 3d stuff or 2d stuff was just nominal....I ran Photoshop design premium and lightroom primarily. I can't answer this completely about the 3d or 2d. BUT, I did check the 3D as you wanted above.

When I run the launch recovery this is a screen shot of the aftermath, which is essentially nothing and the other option to start windows normally also fails.
this is what happens:

Ok so does it start normally after or does it go back to the repair menu or fail when you try to start normally?

it NEVER leaves the repair menu AND it fails when you try to start normally?

ALL I GET IS THE

Have you tried pressing the enter key instead of waiting for the countdown timer? Also keep in mind that this make take a long time. does the drive activity indicator flicker or show any activity?

Perryg wrote:Have you tried pressing the enter key instead of waiting for the countdown timer? Also keep in mind that this make take a long time. does the drive activity indicator flicker or show any activity?

• ok....after pressing launch startup repair it starts a countdown timer as you can see had 9 secs left, a progress bar appears....does it's thing and then returns to that window.

• I then, I go to the next item and think MAYBE windows might just start normally and make that selection, it got through some gyrations and returns to that same screen

I think I can say I am not seeing any results from this window as WIN-7 will not launch.

SO back to the files...because it is something to do with changes this update made, what about the old files that have the -prev suffix on the file name?

You can compare the old control files with the new ones and see if there is a setting that was different.
Question: Was the Windows 7 guest shut down or in a saved state when you did the upgrade?

Perryg wrote:You can compare the old control files with the new ones and see if there is a setting that was different.
Question: Was the Windows 7 guest shut down or in a saved state when you did the upgrade?

All my machines are always powered off. I shut the acpi or what ever that is when I have one opened ( this usually gave me the least trouble).
I have never had an issue with virtual box.
I opened the VB manager and a notification window opened before I did anything or started anything and all hell broke loose.

Can the guest start in safe mode?
If so look in the device manager and see what it was expecting to see.

Perryg wrote:Can the guest start in safe mode?
If so look in the device manager and see what it was expecting to see.

The WINDOW-7 guest in safe mode? Don't know how to do that?

vdotmatrix wrote:

Perryg wrote:Can the guest start in safe mode?
If so look in the device manager and see what it was expecting to see.

The WINDOW-7 guest in safe mode? Don't know how to do that?

Why the xp log file?

Anyway to start in safe mode you press f8 at boot. You have to be quick though as it gets by really fast.

The error tells you that something has changed from the original to now. Do you have a backup of the original *.vbox (control file) that you can compare with the new one?