Cant get windows 95 VM to run on windows 10

[liquidcheetos]

I just barely got VirtualBox and have been watching tutorials on how to get a windows 95 VM to run on windows 10 and I've followed all the directions but every time I try to start the VM it gives me a exit code of 0xc0000034. I believe it is a hardening issue but I don't know how to fix it

-VirtualBox version 6.1.18
-Windows version 20H2

[scottgus1]

The error message mentioned that rebooting might help. Have you tried that?

You definitely have something hacking your files. 3rd-party Antivirus and web-safe nanny software like Trusteer Rapport and HP ProtectTools can also hack files. You have BitDefender installed, that could do it too. Try to find and uninstall (not just disable) all 3rd-party security software and reboot, then try Virtualbox again.

For further reading see Diagnosing VirtualBox Hardening Issues, and our 95/98 tutorial: viewtopic.php?f=28&t=9918

[liquidcheetos]

I uninstalled bitdefender and rebooted my host machine and its still giving me the same error code

[multiOS]

Installing a 25+ year-old Windows OS is probably not the easiest first time learning exercise for a 'new' VirtualBox user. Probably easiest to familiarise yourself with the general process using a more modern OS that is still directly supported, which will also help to confirm whether or not the VirtualBox installation is working correctly.

The Windows Blue Screen error code 0xc0000034 has been around for longer than 25 years on real hardware and if it's occurring in the Windows 95 VM it's likely telling you that something went wrong during in the installation and/or there is some incompatible 'hardware' driver or boot setting that Windows 95 simply can't cope with. IMO that should be your starting point; and if you concentrate on the Windows 95/98 Tutorial @scottgus1 already flagged you should get a good grounding in identifying potential issues/possible solutions; and you'll probably also notice that Win98 is often suggested in preference to Win95.

[scottgus1]

The "hacking" is gone now, good.

MultiOS's idea about trying a more modern OS to see if the VM can run is a good idea.

I am not sure the 0xc0000034 is a BSOD in the VM, but rather in the hardening check.

Web-searching "STATUS_OBJECT_NAME_NOT_FOUND site:forums.virtualbox.org" (the error name comes from the hardening log) brought me to this:
viewtopic.php?f=38&t=80820#p379208

Try these ideas, see what happens.

[liquidcheetos]

I just tried to get a windows 7 installation running and it gave me the same error code so I'm wondering if its something with my host machines hardware that's causing it to not boot, I also think it could be a bad installation of the virtualbox program

[scottgus1]

bad installation of the virtualbox program

That is one of the suggested causes in the link I posted, did you read it?

[liquidcheetos]

Yeah i was about to do a clean installation of the program