I Can't run any Windows-like VMs anymore on W10 20H2

[Giapo]

Hi everyone, I need help.
Two days ago I updated my PC to the last Windows 10 20H2 version, and since then I can't run any Windows-Like VMs anymore!
On my computer i have Windows Longhorn Update 4074, Windows XP Professional SP2, OS/2 Warp, Windows 98 SE and OpenSTEP.
Well, all of these VMs worked perfectly at least until 10 days ago, the last time I opened one of them.
Yesterday I tried to start everyone of them, and this is what happened:
- Windows Longhorn Update 4074, after a long boot time period (the screen with the logo and the charging bar), goes on blackscreen and gets blocked
- Windows 98 SE starts only on Safe mode, if I try to start it normally gives to me the message "Windows Protection Error. You must restart your computer."
- OS/2 Warp is blocked on the loading screen after a couple of seconds, loading nothing and blocking the bar a bit after the begin
- Windows XP Professional SP2 gives to me the worst problem. When I try to start it normally or to the Last Good Configuration, after a couple of seconds of boot screen goes to BSoD with the error ISQL_NOT_LESS_OR_EQUAL (0x0000000A) and goes on reboot. If I try to start it in any of the Safe modes, it goes on blackscreen or on BSoD again; so it's actually impossible to start it.

Only OpenSTEP manages to start, also if it's quite slow its boot.
I thought it was a Hard Drive problem, 'cause some of these VMs are saved on an External Hard Drive, but Virtualbox gives the same problems also with the OSes on the Internal Hard Drive. Anyway, I moved all and Formatted the External Hard Drive to be sure, but nothing changed.
I thought it could be a problem given by the antivirus, but also uninstalling it nothing changes; same story thinking it was a VirtualBox problem of some corrupted file, also uninstalling and reinstalling or repairing the installation all the problems remain.
I checked among Windows 10 Funcionalities, and I dont have installed any of Hyper-V or Virtualization tools, so nothing goes in conflict with VirtualBox and its VMs (which worked until now). I found two Virtual Network Adapters of Hyper-V among my Network Cards, and this is strange, but I uninstalled them since Virtualbox has its own Virtual Network Adapter already installed.
What causes all this mess? I can't figure it out!
Someone can help me, please?
I thank for every answer, hoping to get some as soon as possible.
Bye ^_^

[multiOS]

Please 'zip' a copy the VBox.log file for one of the problem VMs and attach the zipped file to your response message using th Upload Attachment Tab and hopefully someone will be able to identify the problem.

[Giapo]

Please 'zip' a copy the VBox.log file for one of the problem VMs and attach the zipped file to your response message using th Upload Attachment Tab and hopefully someone will be able to identify the problem.

Thank you, I attached the ZIP file with alle the logs of the Windows-Like VMs.

[scottgus1]

Hyper-V needs to be disabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active).

[Giapo]

But I don't have Hyper-V enabled, that's the matter...
Do the logs say that's enabled? In that case this is strange, because according to the Funcionalities I've got on Windows Hyper-V and other similar things are not checked.

[scottgus1]

Do the logs say that's enabled?

No, I just haven't typed that response enough this week.

Did you read the linked tutorial? And the link inside that tutorial? Other things besides 'Hyper-V' enable Hyper-V. Also, what is in the log that tells me you do have something that uses Hyper-V enabled is detailed in the tutorial.

[Giapo]

Do the logs say that's enabled?

No, I just haven't typed that response enough this week.

Did you read the linked tutorial? And the link inside that tutorial? Other things besides 'Hyper-V' enable Hyper-V. Also, what is in the log that tells me you do have something that uses Hyper-V enabled is detailed in the tutorial.

LOL, it seems a common issue, isn't it?

Anyway, I foolwed the tutorial, and now Windows Longhorn manages to start; while Windows 98 still goes on Protection Error, and Windows XP now gives anoter BSOD, PAGE_FAULT_IN_NONPAGED_AREA.
It's still a progress, because now I manage to start Windows XP in Safe mode, but the thing is not resolved yet.
I tried uninstalling the Guest Additions, but if I try to boot it normally goes on blackscreen, so I reinstalled it because it's still better than not have it, at least I know the BSoD
Any other advices?

[scottgus1]

Post another log, let's see if Hyper-V is gone.

[Giapo]

Post another log, let's see if Hyper-V is gone.

OK, here you are

[scottgus1]

HM: HMR3Init: AMD-V w/ nested paging

Yup, Hyper-V is gone, good.

now Windows Longhorn manages to start;

Good.

Windows XP now gives anoter BSOD, PAGE_FAULT_IN_NONPAGED_AREA.

XP is set for 3D acceleration enabled. 6.1.x no longer has 3D acceleration for anything Vista and earlier. Either turn off 3D in XP or revert Virtualbox to 6.0.something.

Windows 98 still goes on Protection Error,

See viewtopic.php?f=28&t=9918#p422192. It's for 95, but it may work for 98.

[Giapo]

HM: HMR3Init: AMD-V w/ nested paging

Yup, Hyper-V is gone, good.

now Windows Longhorn manages to start;

Good.

Windows XP now gives anoter BSOD, PAGE_FAULT_IN_NONPAGED_AREA.

XP is set for 3D acceleration enabled. 6.1.x no longer has 3D acceleration for anything Vista and earlier. Either turn off 3D in XP or revert Virtualbox to 6.0.something.

Windows 98 still goes on Protection Error,

See viewtopic.php?f=28&t=9918#p422192. It's for 95, but it may work for 98.

Thank you, I'll try doing what you adviced me.
The strange thing is that Windows 98 never did this problem with the CPU; i mean I had to install it using a computer with a Intel processor but at least after the configuration I always managed to start it also on my PC with an AMD Processor... Anyway, I'll try it.
Talking about Windows XP, instead, also unchecking the 3D Acceleration is unable to start it normally, it manages to start it only in Safe mode. What else can give problem to this VM?

UPDATE:
The patch doesn't work with Windows 98, so nothing changed.

[scottgus1]

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 repaired. Take a good backup of the old VM's files.

98 comes from an era where OS's weren't expected to migrate to new hardware. Try the same thing, a new 98 VM, see if the new one is stable.

I foolwed the tutorial, and now Windows Longhorn manages to start

Since the original problem of not being able to run any Windows-like OS seems to be fixed, please start a new topic, one for each OS, as the fix might be different for each, and forum rules request one subject per topic.

[Giapo]

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 repaired. Take a good backup of the old VM's files.

98 comes from an era where OS's weren't expected to migrate to new hardware. Try the same thing, a new 98 VM, see if the new one is stable.

Since the original problem of not being able to run any Windows-like OS seems to be fixed, please start a new topic, one for each OS, as the fix might be different for each, and forum rules request one subject per topic.

Well, hypotizing that I have time, space in the hard drive and programs to install again Windows XP and Windows 98, I can do it but the problem could show again if i don't find the real cause; so I must find it, either to try to resolve the problems of the existing VMs or to avoid that these glitches could come again and make me waste another giant amount of time and resources to restart it again, maybe at the next update of Windows 10.
So, also if I can use this hard line solution, even if temporary, I still need to find what's the problem, which, I agree, isn't linked to all the Windows-like VMs. OS/2 and Longhorn apparently only suffered the Hyper-V; while Windows XP and Windows 98 are still suffering of something.

[BillG]

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 with that combination.

20H2.PNG

XP-W98.PNG

[Giapo]

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 with that combination.

20H2.PNG

XP-W98.PNG

Well, now my problem remains to manage to start correctly Windows XP, also because I've got installed on it some old PC game of which I don't have the disk anymore, so lose this VM means lose also these games.
What I'm sure is that anything is using Hyper-V anymore, also because I disabled it using the command lines I found here and all of you linked me, also the Vbox.log confirm this.
Now, I have only to understand what makes this problem.