Update from 4.2.8 to 4.3.4 Trashed my Windows7 VM
-
PeterNosko
- Posts: 19
- Joined: 7. Dec 2013, 02:49
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Win7-64
Update from 4.2.8 to 4.3.4 Trashed my Windows7 VM
My Windows7 VM was working without issues on OS X 10.7.5 using 4.2.8. After installing 4.3.4, I'm unable to keep the VM running. It will crash shortly after startup and attempt to fix the problem on restart, saying a bluescreen occurred. Rinse, repeat.
-
PeterNosko
- Posts: 19
- Joined: 7. Dec 2013, 02:49
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Win7-64
Re: Update from 4.2.8 to 4.3.4 Trashed my Windows7 VM
I deleted the VM and started creating a *completely new* Win7-64 Pro VM. A few minutes into the install (asking me for a user name and computer name), it crashed. I'm dropping back to 4.2.8.
-
socratis
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Update from 4.2.8 to 4.3.4 Trashed my Windows7 VM
It's nice to see the reminder ignored. Please read the following: Minimum information needed for assistance.
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.
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.