ender_'s Accepted Solutions

Try disabling hardware acceleration (either for Edge in the guest, or for the VM in general) – there are similar problems with all Chromium-based browsers (the most common one is that message boxes are transparent and nearly invisible).

Modern CPUs are too fast for Win9x, which leads to problems like you're seeing (I see a similar Explorer crash when starting my Win98 VM that I installed years ago). The certificate errors you're seeing are due to certificate revocation lists either not existing any more, or using protocols that aren't supported by the ancient OS.

> Also, on Device Manager, there is only Microsoft Basic Display Adapter listed, shouldn't there be an SVGA 3D adapter or something like that as well? That's likely your problem – the VMWare SVGA driver did not get installed for some reason. Try double-clicking the Basic Adapter, go to Driver tab, click Update driver button, then Browse computer for drivers and Let me choose a driver. If the next page shows VMware SVGA 3D option, choose that, otherwise click Have disk and browse to c:\Program Files\Common Files\VMware\Drivers\video_wddm\Vista, which should give you VMware SVGA 3D.

Have you tried updating the SVGA driver in VM? I'm not sure if it'll help, but Windows Update should have a version that's newer than shipped with VMWare Tools in 16.1 (you can get this same version by downloading VMWare Tools 11.2.5 manually).

I used VMWare Workstation with Hyper-V on a Xeon E5 1620 (v1) - Sandy Bridge EP. Though if you're buying a CPU, buy the newest one your motherboard supports (if you have a LGA2011 socket, that means go for E5 v2).

I don't understand Chinese, but is the message saying that nested AMD-V/RVI can't be enabled? If that's the case, Windows 10 probably enabled Hyper-V on the host (it gets enabled automatically if you use Core Isolation/Memory Integrity, Credential Guard or WSL2), and Workstation is using that instead of its native virt to run VMs. Hyper-V doesn't support nested virtualisation, so you will have to disable it - see KB2146361 for more info.

Bridge with VPN almost certainly won't work. NAT mode should work, since that makes VMWare share your host's IP address (basically your computer acts as a NAT router for the VM). Check the virtual gateway IP with ipconfig - at least for me, it's not .1, but .2; ping from the VM should also work for any host that you can ping from the host (note that traceroute does not work in my experience - you only see the first and last hops).

If you're not planning to run nested VMs (VMs inside your VMWare VM), just disable the "Virtualize Intel VT-x/EPT or AMD-V/RVI" checkbox in VM Settings→CPU, and the message will go away; if you do plan to run nested VMs, you will have to disable Hyper-V on the host.