virtualbox.org

I wouldn't bother with AV in my own XP VMs. Just make a backup and be prepared to overwrite XP from the backup if it has problems of any kind. And obviously, don't put anything sensitive in there: you'd be nuts to prefer XP for serious work today, so it should be easy to avoid having personal data ...

I have no further ideas why your XP installations are failing when antivirus is installed. If you have another computer that can run Virtualbox you could try copying the VM's folder & files to that computer and see what happens. Also, try to have suitable backups of your host PC so you can reve...

For other readers, the final subjects in Giapo's post above have been discussed here: https://forums.virtualbox.org/viewtopic.php?f=6&t=101037&p=490504#p490487 Giapo, you're posting the same thoughts in multiple places, which is sailing close to triggering the forum's "no duplicate pos...

In the meanwhile, I managed to start Normally Windows 98 SE changing unusually the Graphic options to VboxVGA to VMSVGA; and, above all, in a quite casual way, I found what caused the worst problms on Windows XP. On the VM i had installed Avast Free Antivirus, since the begin. For some reason, after...

Well, this should be a good explanation, but sure is not a Host Antivirus problem, because also without it the VM wasn't still able to start... Indeed, the thing could be connected actually to the last update, with which Windows managed to block some internal file into the VDI file of the VM. As I'v...

Well in the meanwhile, in a quite casual way, I found what caused all of this . On the VM i Had installed Avast Free Antivirus, since the begin. For some reason, after the Windows 10 Update, VirtualBox is unable to load the Avast drivers and goes to BSoD . Now in Safe mode i Uninstalled it and the p...

Windows XP uses very little disk space, Win98 even less. In any case, you could copy the existing vms to external backup and copy them back if you need them in the future. Personally I have had no problems running XP or Win98 under Window 10 20H2, and I have not seen any other users with problems w...

Start the VM again, wait for it to crash. Then Inspect the VM's vbox.log, search for the words: Attempting fall back to NEM If you find them, Hyper-V is still enabled. If the words are not in the log, Hyper-V is off. I did what you told me, and in the Vbox.log file I didn't find anything similar to...

scottgus1 wrote: Did you try the bcdedit command?

Yes, i used the bcdedit command and I have Core Isolation Disabled.

Windows Defender Application Guard is not Windows Defender, it's the additional part of Windows Defender for Microsoft Edge Isolated Exploration. I installed ita few weeks ago and now I just tried to roll back to when it wasn't installed. You told about some third party aggressive AV, so I told you ...

I'm afraid that I see no VM error recorded in the log, so it would seem that the problem is in the guest OS, not in VirtualBox. My own Win98SE VM continues to work normally in VirtualBox 6.1.16, so this is not a universal problem. Since the VM starts in safe mode I believe that indicates that the p...

There still seems to be something wrong with the SVM (a.k.a. AMD-v) feature of the host CPU. Normally this is caused by some other software leaving the VT-x or SVM feature in an invalid state. I would in the first instance treat this as yet another Hyper-v intrusion, but Hyper-v is not the only oth...

Hi everyone, I need help. I write this new post after another one, in which I had initially problems with all the Windows-like VMs since the last Windows 10 20H2 Update, and then I found out that for some unreasonable reason there was the Hyper-V activated (also if it was even checked into the Windo...

Hi everyone, I need help. I write this new post after another one, in which I had initially problems with all the Windows-like VMs since the last Windows 10 20H2 Update, and then I found out that for some unreasonable reason there was the Hyper-V activated (also if it was even checked into the Windo...

Re XP, it is entirely possible that the VM has an internal glitch that happens to coincide in time but not in cause with the host OS update. Try installing a fresh XP in a new VM. You'll have 30 days to test it unactivated. If the new VM runs fine, then the old VM has an issue and needs to be repai...