* Whether you have installed Guest Additions and/or Host Extensions (this solves 90% of the problems we see) * Whether you have enabled VT-x/AMD-V (applicable to all hosts running 6.1 and above) and disabled HyperV (applicable to Windows 10 Hosts) * The version of VirtualBox you are using This is just a friendly reminder in case you missed it. I’ve tried doubling the memory of the virtual machine to no success, I’ve made two more XP virtual machines, each with new virtual hard disks, but neither of them work, and I’ve reinstalled Virtualbox entirely, but the XP virtual machines still don’t work. So far, I’ve tried running different ISOs of the XP installer, but none of them work, as they also blue screen as soon as they reach the splash screen. I don't know what VT-x or AMD-V are, but virtualization is enabled in my BIOS, and while I have Hyper-V enabled, it's likely not the problem since every other virtual machine except XP is working Guest Additions is not installed, it can't get past XP's splash screen Please ask questions, I know it's not a very detailed post, I just can['t think of anything to add It's not from changing any virtual hardware, since I haven't changed memory, the only thing I've changed being making three different. It reaches the Virtualbox screen, the Safe Mode start up screen, and it tries to reach the XP boot screen, only for it to be in weird colors for a split second before going to a blue screen Then go into the vm settings and change the image then power back up to use it.Hi, I made an XP virtual machine in the past, however, it has stopped working One other oddity is that you have to power the vm down to change cd ISOs. After the restart you can access the share and no problem. The odd things is that it appears to be only the first instance that triggers a restart. I mapped an network share to the vm, accessed it and after a few minutes the vm restarted. For the moment I can live with 1024 x 768 res. Its only a partial success because when you start changing or messing with drivers it wants to reboot after a couple of minutes.įor instance, I changed the vm display from the default 1024 x 768 to 1600 x 1200 ( 32 " monitor ) and after a few minutes the system just abruptly Restarted. That was the only change I made and it let me install windows. The key factor being the network connection is disabled before you install Win. I wanted to share my partial success installing Win 10 and booting it up. Knowing / Guessing it's a driver issues from seeing the point of failure and seeing some successful youtube "how to's", it occurred to me to disable the vm's virtual network driver before attempting to install win 10. I thought I would update the forum on my partial success It seems to be ok above this version but there is none from Terramaster. virtualbox up to 6.1.18 (which is the one from Terramaster) with newer CPUs (Intel 10th gen and up) I searched some foruns and it seems that it has to do it doesn`t even boots completely one time it reboots again and then shows up another error (about the same thing but a white box), then reboots and does the same thing over and over after the reboot, W10 boot the first time where it starts again setting everything up and comes always to a BSOD with KMODE_EXCEPTION_NOT_HANDLED W10 has no issues doing the first part of the install (file copy + some settings) > then it normally reboots I tested with dozens of different combinations, lets say virtualbox default + 2-core CPU + 4 GB RAM assigned to the VM I installed the latest available virtualbox over the store (6.1.18) and tried to install a W10 22H2 64-bit (the latest) image. I bought my new F4-423, fully updated (TOS 5.1.33) and updated with terramaster`s extra 4 GB RAM (total 8 GB RAM)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |