I can confirm that Windows 10 runs stable after disabling the Nested Virtualization option. This is an issue that should be look at.
After installing the updated Parallels Tools, I re-enabled Nested Virtualization option, still BSOD on login screen. I'm running the latest build of Windows 10.
Disabled Nested Virtualization; Started windows; Removed Parallels Tools; Restarted to ensure un-installation was finished, Shut down; Enabled Nested Virtualization, Started Windows - No BSOD!!! Installed Parallels Tools; Rebooted; BSOD Loop... sigh, Happy New Year....
Also tried changing number of CPU's, No luck...
In addition to the MEMORY_MANAGEMENT BSOD, I also got CRITICAL_PROCESS_DIED and IRQL_NOT_LESS_OR_EQUAL.
I wanted to downgrade to 11.1.1 (32312), but after attempting to construct a URL for previous versions used in the KB Article 5802 - I got a 404.
Here's the URL I constructed based on the pattern of URLs in KB5802:
Can you please make this version available for download?
How much are these updates really tested? I'm starting to feel like I've paid for the privilege of being a guinea pig the last few updates... I'm really getting frustrated and fearful when updates show pop up for me to install. I don't necessarily have time to test them out especially when they fix some of the minor annoyances I've been experiencing while causing other issues. When things are released, and maybe I'm wrong here, but shouldn't they just work? Where's the QA?
Note to self: Keep previous version installer .dmg.
Last edited: Dec 31, 2015