virtualbox.org

Immediately after a Windows Update my Windows 7 (32-bit) guest will not start on my Mac VirtualBox (v. 5.2.20). It starts, gets to a certain point then shuts down. I have tried all the repair options. Window won't boot into safe mode either. I can get to the command line (get to: X:\windows\system\32), but I have no idea what to try from here.

Is there a way to delete the last Windows Update? Any other options? I'm more a Mac person so my Windows troubleshooting is lacking. I only use VB Windows for Quickbooks and have a backup, so if the quickest solution is reinstalling Windows, that's okay. It would be nice to avoid having to install all the updates, however.

[ModEdit: RTF version of the VBox.log removed]

Thanks for ZIPPING your log. But, please edit your message and replace the RTF zipped log with the actual text version of the log, the original "VBox.log". Not e everyone can read an RTF, but all can read a text file. There's absolutely no need to "ruin" a perfectly fine log by translating it into another format...

Sorry, see attached.

[ModEdit: RTF version of the VBox.log removed]

I'm sorry, but you uploaded the RTF version again. I removed them.

Just right-click on the VM, Show in Finder. You'll be taken into a folder in the Finder. There's a "Logs" folder in there. And in that Logs folder there is a "VBox.log". Simply right-click on it, "Compress". That's what I want to see, not a ZIPPED RTF file.

You can also open TextEdit » Preferences, and make sure that in the "New Document" tab you have "Plain text" enabled and not "Rich text".

See attached. Sorry, it wasn't clear how to find the log file. Thanks for any help.

And a tip, here's simple converter... nowadays there's a converter for anything
https://www.aconvert.com/document/rtf-to-txt/

We're not communicating I'm afraid... I told you to "ZIP"/"Compress" the log...
I'm not going to delete it this time, it's getting boring.

nelslynn wrote:Sorry, it wasn't clear how to find the log file.

I'm sorry, but... what??? The instructions were crystal clear. Which step didn't work for you?

nelslynn wrote:And a tip, here's simple converter... nowadays there's a converter for anything

I'm sorry, but no. We (the users) are doing you a favor already and are trying to help you. Things are simple; you zip the log. If you want to convert the TXT to RTF, ZIP the RTF, and ask the rest of the community to go to an online converter to translate the RTF back to its original TXT format? Not gonna happen... You got to help the volunteers, not make their life more difficult!

Your VM config look pretty standard, nothing major. A couple of minor points that I don't think are going to help you really, but it never hurts to try them out:

• VirtualBox 5.2.22 and 6.0.0 are both out and newer than your current 5.2.20. Please upgrade your installation and your Extension Pack as well.
• You have assigned 1 CPU to your guest. Your host has 4, you can afford a 2nd one to make it smoother.
• 2D and 3D acceleration are disabled. Consider enabling them for better performance.
• Your VRAM is set to 72 MB. I would take it to the max allowed.

That's it. Other than that, it feels and smells like an issue with your guest. Just because an OS/program that runs in the context of VirtualBox has a problem, it doesn't make it a VirtualBox problem necessarily. You're having an issue that has most probably nothing to do with VirtualBox, so my suggestion would be to treat it as such, as a native problem with the OS or the application of the guest.