Windows 10 Black screen with white cursor intermittent after network logon

[sk1d00]

Hi,

 

I have recently upgraded many of our 3 year old HP and Zoostorm PCs with 8GB RAM and an SSD drive, but am getting this annoying intermittent issue when staff logon they either have a very fast logon to desktop or the dreaded Black screen of death. The PCs all have fresh builds with nothing more than Windows 10 pro (anniversary edition), Office 2016, VLC, Adobe Reader and 7zip. SCCM pushes MS endpoint and we also push MalwareBytes. All drivers are up to date but still this happens about 5% of the time - enough to be a pain as staff either give up or turn the PC off and on which generally fixes it.

 

Drive mappings seem okay and we don't use roaming profiles.

 

Logon servers are Windows 2008r2. We have tried all both original and anniversary edition of Windows 10.

 

Some brand new PCs with the same standard build are okay 99.9% of the time so I thought it might be graphics drivers on the older machines but it is so intermittent we don't know what it is. We have tried turning off SCCM connectivity with one or two of the machines but as the issue happens not all the time we finding it hard to diagnose. Nothing in the event logs.

 

The one thing it seems to be is explorer.exe not starting as if we ctrl+shift+escape and manually start explorer.exe we generally get the desktop.

 

I have googled this plenty of times and it is not the Windows+P fix so many mention, plus as this was an upgrade issue to Windows 10 a lot of the searches point to that and not my issue.

 

Thank you in advance for any suggestions.

[daflibble]

We have been seeing this intermittently in our environment too. We did update the intel graphics drivers on our Ergo (zoostorm by another name) PC and it occurred less. We are currently trying out disabling windows fast start via gpo to see if it makes an improvement.

We use impero and there is another thread on here relating to it causing this behaviour. We've not tried any testing on the new version though as got a few dependencies to tidy up before we can roll out the new version of impero client for other reasons.

[ricki]

We get this a lot on older machines while they apply settings Richard

[Mic_Impero]

We have been seeing this intermittently in our environment too. We did update the intel graphics drivers on our Ergo (zoostorm by another name) PC and it occurred less. We are currently trying out disabling windows fast start via gpo to see if it makes an improvement.

We use impero and there is another thread on here relating to it causing this behaviour. We've not tried any testing on the new version though as got a few dependencies to tidy up before we can roll out the new version of impero client for other reasons.

 

Hi @dafibble Just a heads up that our current release 6.0.45 will not impact this issue. We've found that there are many causes of this, but a change to Impero can reduce occurrences of it. The change I'm speaking of us currently in a closed Beta phase and will be included in the next build of Impero, subject to successful testing.

 

Mic @ Impero

[sk1d00]

Hi,

 

Cheers for the reply, we have Impero but not on the machines in question. I'm pretty sure we turned off fast start also, but I'll go check and come back to this post.

[Craisin]

We are having similar issues on new HP hardware. Windows 10 LTSB 2015. Very very occasionally when a machine is logged on to, the screen will go black as mentioned, then turn to a solid grey.

The machine shows up on the Impero console, but if you view the screen, it is grey.

Only way around it is a reboot. I did read that applocker might cause the issue, but when testing & applocker removed, it still happens.

Very frustrating.

 

Also looking to roll out the latest version of Impero over the Easter hols.