Parallels Tools Kills Windows 10 Insider Preview Build 15042

It's Deja vu time as once again, Parallels Tools install once again kills the virtual machine with a blue screen of death on every boot-up attempt. As before with build 14926, did a workaround to 'fix' by booting up using low resolution mode - "Enable low-resolution video" on repair option. Hope this helps others but the Parallel Tools needs to be fixed to prevent this kind of thing.

 

Confirmed here as well. I killed the Parallels Tools' installation as soon as it booted and it stay working. As soon as I let Parallels install it, it reboots into blue screen.

 

also, if you don't want to go through the repair option on every boot, enable the Boot option "Base video" in msconfig

 

Hello Guys, please check this article and keep us posted.

 

Has nothing to do with using expired builds - 15042 is the newest insider build. It's clearly a video driver problem as changing the video resolution to low or base video will workaround the problem.

 

Are you sure you have the right link? If yes, then please read this thread again. This has nothing to do with an expired build. 15042 is the latest build that came out yesterday, it is an issue with the graphics subsystem caused by the installation of Parallels tool. This has happened before and Parallels fixed it with an update. This is 100% an issue within Parallels, not Windows or Insider Builds.

We have no problem using the VM without installing Parallels tool or booting into the base video mode. Please pass this onto your driver engineering teams.

 

Same as everyone above. Low resolution mode allows boot up. Watching this for further developments.

 

Same for me ... and it boots up fine to do the Parallel Tools install, then is dead unless you boot in Low Res Mode (and networking does not work)

 

+1, sorry can't upload the error code as I've rolled back to the previous version.

 

Here is a screenshot of it. As you can see, it works fine before Parallel Tools install and then bluescreens afterwards.

 

I get the same thing. In fact, I was unable to upgrade to the latest build (15042) because of this problem. The process would get to about 75% and do the final reboot and then would blue screen and roll back to the previous build (15031 iirc) and there it was. Uninstalling Parallels Tools allowed the upgrade to Build 15042 to complete. Installing Parallel Tools in Build 15042 causes it to blue screen and not boot. Without having Parallel Tools installed it boots just fine. Here is a screen shot of the blue screen. In my case it seems to be related to dxgkrnl.sys which deals with MS Direct X system. Hope this might help in diagnosing what's going on.

 

Yes, as MarkBryn pointed out, the remedy is the same as with the BSOD booting build 14926 (different error, though: now it's exception not handled in dxgkrnl.sys insted of in kmdd.sys):

Reboot the VM containing build 15042 with reinstalled Parallel Tools; this causes BSOD, but system enters Repair Mode after an iteration or so. Now select Advanced Options | Troubleshoot | Advanced Options | Startup Settings | Restart, and subsequently choose "Enable low-resolution video". The system duly boots in lo-res, but the proper resolution kicks in as soon as the logon screen appears; after this, the system will run stably. If you enable the Boot option "Base video" in msconfig, you can restart the system at leasure from then on--with Parallel Tools installed.

UPDATE. Build 15046 (well, Redmond, that was quick!) has the same problem--which can be remedied by the same measure: boot in "base video"

 

Just installed Build 15048, the trick with "base video" doesn't work anymore for me. Only starting into safe mode and disable the parallels services via msconfig enable to start windows again...

 

Solid advice. On my system, I could actually combine steps 2 thru 5 into one. And of course: run MSCONFIG.exe in Admin mode (everyone has renamed user Admin, right ;-)

 

Just to add I'm having the same issues as everyone else. As soon as I install the Parallels Tools I get a blue screen and the machine won't boot anymore. I have to set the system to Base Video and No Gui Boot (as per above) to fix the issue.

Parallels - when can we expect a fix for this ?

 

Probably only after Microsoft fixes the moving target these "Insider Preview Builds" present... And BSoD caused by dxgkrnl.sys seems to occur with other environments than Parallels VM too.

 

I have just trashed multiple VMs because of the above. I reverted on one to April, and now get a security exception that winload.exe is signed improperly. How do I recover from that?
The update installed after I uninstalled parallels tools, but after I reinstall them, it reverts again on reboot. How do I get high-res video?

 

I set my system to Base Video and No Gui Boot, but it still reverts unless i uninstall Parallels tools. Help!
Parallels, the whole purpose of using VMs is to try new OS versions, and it is up to you to support them!