Unable to Start VM, get a small window no Splach screen.

Discussions about using Windows guests in VirtualBox.
Post Reply
DocBrown
Posts: 43
Joined: 2. Feb 2010, 09:42
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows 7 Pro, 10 Pro, 10 Ent, 11 Pro; MacOS (Mac Host).

Unable to Start VM, get a small window no Splach screen.

Post by DocBrown »

I have a VM that I created as a clone years ago. I have successfully Started it less than a week ago. Now when I attempt to start it all I get is the initial window which stays black. I don't even see the Virtual Box Splash screen. Here is what I have tried:
  • Restored the VM from a backup. When that didn't work I restored the VM from a backup taken 2 months ago.
    Detached the virtual disk and attached a newly created one.
    Attached a bootable Windows 10 CD.
    Tried to Start it from another Windows User.
    Deleted the VM (leaving the files) and added it back.
Nothing has worked.
I did also try to clone another Win 10 VM (without it's disk attached) and attach the disk of the failed one and couldn't boot that because of bad boot parameters. The Windows ISO wanted to clean install which I didn't want to do. I haven't tried to solve that, yet.
All other VM I have are booting fine.

I have looked at the logs but don't recognize any error message.

Host:
Windows 11, 25H2
Asus P670-Pro MB, Intel i7-12700K,
w/ 32GB main memory.
VM configured to run on a 2 TB SSD. About 10% free.
What are my options for using the vDisk or recovering the VM.

Guest: Windows 10 22H2, I think.
DocBrown
Posts: 43
Joined: 2. Feb 2010, 09:42
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows 7 Pro, 10 Pro, 10 Ent, 11 Pro; MacOS (Mac Host).

Re: Unable to Start VM, get a small window no Splach screen.

Post by DocBrown »

I solved the issue. When I restored the VM, I forgot to account for the vDisks and Snapshots that VB was tracking and then somehow the TPM setting was incorrect. So once I cleaned up the vDisks in Media manager, and set the TPM setting to 2.0, the VM booted correctly.
Post Reply