About 3/4 the way through the install process it completely hangs the virtual machine.Įxecuting "C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxDrvInsta.exe" dri. I was able to add an optical drive to the virtual machine and get the guest additions iso mounted. In this case necessary not only cause I couldnt copy/paste between host/guest but because I use a 4k display and so my image was stuck in a little 1024/768'ish square in the center of my screen. Naturally everything I have running on my main pc murders a VM so after waiting a good long while for it to start up and calm down, I closed and disabled everything.Īt this point I wanted to install the Guest additions as I assume thats virtualbox's equivalent to Vmware tools. At that point it all goes downhill though. Getting the image started was easy enough. Since viboot doesnt support vmware I figured nows a good time to see how virtualbox is as I wasnt interested in enabling Hyper-V. I'm seasoned enough with vmware but thats just new OS's installed from an clean iso. I had never used viboot in the past as I never had a reason to.
Part of my solution should I decide to go the clean install route was to have my final windows 10 macrium image bootable via viboot so I could use it to pull whats going to amount to a zillion registry modifications and programdata/appdata folders to restore application settings and reference my start menu layout etc. So with windows 11 looming I'm starting to weigh the whole "upgrade vs clean install" conundrum.
0 kommentar(er)
