Black Login Page & Multiple Monitor "Fun" o_O - PD 12.2.0 Pro + Win10 Creators Update 1703

[TS-Micah]

Hey guys,

Instead of seeing a login screen on the FIRST boot of my Windows 10 VM, I get a black screen. I have to reset it EVERY time to login!??!!!?!

This has been happening to me since I updated to the Creators Update and upgraded to PD 12.2.0 (41591) a few weeks ago and it has been frustrating to say the least...

I didn't want it so soon because I'm working on some large projects and I don't like doing any upgrades to my system when I'm in the middle of something like this. Due circumstances beyond my control, (no VM snapshot and my time machine backups stopped working - only found out because of this issue) I was unable to rollback my VM.

I thought something broke when the update completed installing when it booted to a black screen. I even reinstalled Windows CU 2x!!! I discovered another app was causing an issue - Bins and disabled it's auto-start. But, I still get the black screen on every FIRST boot of my Windows 10 VM - did I mention how ANNOYING this is?

On another note, I have my primary and secondary monitors configured, Primary on the left, Secondary on the right. EVERY TIME after I log into Windows it now moves ALL my icons to the right monitor... at this point I'm saying "Come on!". I'm getting tired of moving my icons to where I WANT them every time and it FAILING to remember. I have even swapped the connectors on the left/right monitors to see if that could be an issue.

I'll try uninstalling Bins completely to see if this may still have some bazaar seemingly unrelated side effect...

Update: I attached a screenshot of what I get. This seems to happen after the MacBook Pro sleeps between work & home and I startup the VM for the first time since waking it. As Note: I typed in my password and after logging in the "Restart" option becomes available in the Actions menu which means it's there, just not displaying properly.

 

[TS-Micah]

Looking deeper I noticed these errors in the Windows error log:

Log Name: System
Source: Service Control Manager
Date: 5/5/2017 8:42:08 AM
Event ID: 7031
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: ts-dev-vm-01
Description:
The Parallels Tools Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7031</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2017-05-05T12:42:08.326015800Z" />
<EventRecordID>2364</EventRecordID>
<Correlation />
<Execution ProcessID="796" ThreadID="8700" />
<Channel>System</Channel>
<Computer>ts-dev-vm-01</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">Parallels Tools Service</Data>
<Data Name="param2">1</Data>
<Data Name="param3">0</Data>
<Data Name="param4">1</Data>
<Data Name="param5">Restart the service</Data>
<Binary>50006100720061006C006C0065006C007300200054006F006F006C007300200053006500720076006900630065000000</Binary>
</EventData>
</Event>

Log Name: System
Source: Service Control Manager
Date: 5/5/2017 8:42:08 AM
Event ID: 7000
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: ts-dev-vm-01
Description:
The Parallels Tools Service service failed to start due to the following error:
The paging file is too small for this operation to complete.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2017-05-05T12:42:08.388510700Z" />
<EventRecordID>2365</EventRecordID>
<Correlation />
<Execution ProcessID="796" ThreadID="8700" />
<Channel>System</Channel>
<Computer>ts-dev-vm-01</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">Parallels Tools Service</Data>
<Data Name="param2">%%1455</Data>
<Binary>50006100720061006C006C0065006C007300200054006F006F006C007300200053006500720076006900630065000000</Binary>
</EventData>
</Event>

 

[TS-Micah]

Also found this error which maybe related to this link?
https://answers.microsoft.com/en-us...crash-on/e1c83ff6-417a-4e1f-bd3d-5dfb4f34423b

Error:
Log Name: Application
Source: Application Error
Date: 5/5/2017 8:43:19 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ts-dev-vm-01
Description:
Faulting application name: LogonUI.exe, version: 10.0.15063.0, time stamp: 0xccf07184
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.15063.0, time stamp: 0x72781892
Exception code: 0xc000027b
Fault offset: 0x00000000004c3439
Faulting process id: 0x5aac
Faulting application start time: 0x01d2c59d27833749
Faulting application path: C:\WINDOWS\System32\LogonUI.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: 225275de-0303-437f-9c19-b01c35b5e139
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-05-05T12:43:19.206413200Z" />
<EventRecordID>3929</EventRecordID>
<Channel>Application</Channel>
<Computer>ts-dev-vm-01</Computer>
<Security />
</System>
<EventData>
<Data>LogonUI.exe</Data>
<Data>10.0.15063.0</Data>
<Data>ccf07184</Data>
<Data>Windows.UI.Xaml.dll</Data>
<Data>10.0.15063.0</Data>
<Data>72781892</Data>
<Data>c000027b</Data>
<Data>00000000004c3439</Data>
<Data>5aac</Data>
<Data>01d2c59d27833749</Data>
<Data>C:\WINDOWS\System32\LogonUI.exe</Data>
<Data>C:\Windows\System32\Windows.UI.Xaml.dll</Data>
<Data>225275de-0303-437f-9c19-b01c35b5e139</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

 

[TS-Micah]

I submitted a problem report: 186388087 and my support apparently expired so I don't even know if ANYONE would even look into this BUG

Since my previous post I've had to re-install windows as a clean install (after backing up the original VM on another drive) which means I've lost a day or two of much needed productive time.

Why did I have to re-install Windows?
Because the Task Scheduler task database got corrupted. So, how did it get corrupted? Rebooting Windows until there isn't a BLACK LOGIN SCREEN and I can USE my VM.

Since my previous posts, I have also figured out a workaround to use RDP on my Mac to login to the VM and reboot it from there. But seriously, how exactly is that acceptable? I have gone pretty much for a little over a week with out this issue occurring and has just happened to me today after just rebooting my MacBook Pro and connecting it to a Cinema Display (1900x1200 resolution). My instinct tells me that the problem lies in Display drivers and issues with displaying on a high pixel density screen (retina, etc) vs a non high density display

The plus side is that the original Windows image I was using started out as VM import of a physical computer that started since Windows 7 and has been upgraded through 8, 8.1 and 10 - there's a lot of baggage with that. While the performance is much better after a clean install, the issue still remains, I cannot login and use my VM at times and I'm losing time by having to resort to workarounds to get it to do what it should already be doing - just work.

Frankly, I would like this bug to get looked at and resolved. I don't believe I'm the only one experiencing this, or am I???

So, @ParallelsSupport, please look into this. Attached is a screen shot.