Important stuff that the OS needs to read and write is probably in completely different places now than it was before, so when drivers write to what they think is the correct location, and it's not the correct location, it ends up corrupting the OS in memory, forcing Windows to do a BSoD and then reboot.
I'm not sure, but I'm guessing that the issue is that the driver accesses kernel memory (the layout of memory for the OS itself), and the layout is probably much different now than it was when MSVPC2007 was released. I figured it probably was that there was a driver that it installed that was incompatible with the current version of Windows. It gave me a BSoD, something VERY RARE in Windows 10. So after that I was able to install MS Virtual PC 2007. I carefully blanked out that entry with 0x00 bytes (not removing the bytes from the file as that would change the offsets for other entries and corrupt the file, which could cause other issues). I bypassed this by hex editing one of the files Windows uses to determine the compatibility of various software (and blocks installation of known incompatible software). It says it's not compatible with the current version of Windows. Unfortunately it won't even install in Windows 10.
I have Virtual PC 2007, the last version made by Microsoft.
0 kommentar(er)
