After installing Windows Fundamentals for Legacy PCs on VMware, you might encounter the 0x0000007B blue screen. Actually this happens because you chose the wrong SCSI controller and virtual disk type in the VM creation wizard.
This happened to me, and after doing some reconfigurations, I found the fix.
To fix this, you need to create a new VM again. Leave everything that aren't mentioned here as is to prevent further issues after installing.
On the "install from" section, choose "I will install the operating system later". DO NOT choose the installer disc image option, as this will lead to the same BSOD.
On the guest operating system version, choose Windows XP Professional.
On the I/O controller selection, use BusLogic.
On the virtual disk type selection, choose IDE. DO NOT use SCSI as this also leads to this BSOD after installation.
As I said before, leave everything else on the VM creation wizard, to prevent further issues. After you've finished configuring, mount the ISO into the VM and just do the installation. If you do these correctly, you should be able to boot WinFLP without problems.
Hope this helps, and good luck installing it.
Side note: I've searched the whole forum to see if this has already been posted and I found none of them, which is quite surprising.
How to fix 0x0000007B BSOD after installing WinFLP on VMware
- EnclosedPriority
- Posts: 5
- Joined: Mon Apr 11, 2016 1:57 am
Re: How to fix 0x0000007B BSOD after installing WinFLP on VM
IDE is recommended for any XP-based operating system, in my honest opinion.
Virtual machines just happen to perform better on an IDE-based virtual disk than on an SCSI one, when using VMware.
Anyway, thanks for your appreciated suggestions.
Win7
Virtual machines just happen to perform better on an IDE-based virtual disk than on an SCSI one, when using VMware.
Anyway, thanks for your appreciated suggestions.
Win7