Blank screen after login on 1703

[Sheridan]

We've got a new problem with a previously 'stable' 1703 build. Once a user logs in the screen goes black and all they see is the mouse cursor, which can be moved but they have no desktop.

 

CTR+ALT+DEL and Sign out and then their second login works as normal.

 

I'm guessing an update has now broken the only W10 image we had that worked but has anyone any idea which one? Otherwise I guess I'm stuck with reimaging them

[grahamd22]

Do you have Impero?

[Fazza]

Do you have Impero?

 

If they do that'll be the problem.

[Sheridan]

Nope, no impede here just vanilla Windows!

[Mic_Impero]

Hi all,

 

Just for clarity for anyone else reading, there are many causes for an issue with black screen after windows 10 login. There's a thread on Edugeek about this, and an old version of Impero was in some cases contributing to this, but there are actually many potential causes. Impero was changed some time ago now to ensure that it does not exacerbate this issue. As you're not an Impero user, we know it's not the case that you're running an old version which could be impacting it, but here (completely without warranty) are some notes I scraped from the old thread about this, with the username of the person who posted the information, in case it's useful for you.

 

Post login black screen

 

mic_impero

If the problem is a local profile issue:

Another thought RE post logon which our in house systems manager has seen before here and elsewhere (not running Impero) is that it's a profile issue with the logged on user. He follows these steps to fix (sorry we can't link the original thread as we can't find it, he's typed these out for us):

 

 

1. Reboot the machine

2. Log in to the machine as a local administrator

3. Rename the affected user’s profile folder under C:\Users

4. Launch a command prompt as admin and type

 

wmic useraccount get name,sid

5. Note the affected user’s SID from the command prompt output

6. Launch regedit as an admin and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

7. Look through the keys (left hand side) and find the SID of the affected user

 

file:///C:/Users/MSANDE~1/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png

8. Delete the key named with the SID of the affected user

9. Reboot the machine

10. Log in with the affected user’s credential

11. The issue should now be resolved

12. Clean up the renamed profile under C:\Users if the login was successful.

 

 

 

Steve_layton_sl

First, and the one that had the most impact, was implementing a Microsoft logoff script to tidy the Start Screen Cache. Apparently this was an issue with Windows 8.1. https://support.microsoft.com/en-gb/kb/3161390. As this only prevents new users from being impacted by this and does not address users who have the bloated cache, in conjunction with this we also deleted all local cached roaming profiles off all workstations and cleaned their roaming profiles.

 

Second was we have found a link between the black screen issue and those users who have run out of disk space quote, or those running low. A user had the issue and would consistently have the problem. Increasing his quote by 200Mb (number pulled out the air) allowed him to logon first time.

 

We are still having the occasional occurrence with staff users though, who do not have a disk quota set, so there is still something else occurring.

 

 

 

Alfatec

Has anybody tried disabling the 'Connected User Experience and telemetry service'. I have recently disabled this service and have found that I hardly get any black screens now.

 

 

 

Timbo343

And in GPO, ive changed the following services:

WinDefend | Stop Service | Disabled

wisvc | Stop Service | Disabled

ffsvc | Stop Service | Disabled

wuauserv | No Change | Manual

DiagTrack | Stop Service | Disabled

CDPSvc | Stop Service | Disabled

 

 

newpersn

Just added OneSyncSvc_7e15b to Stop and Disable within services of GPO.

 

 

Stgoodyeara

It's all linked to the same issue. Impero and sophos both inject into dll files. Impero has the facility to exclude files from injection which meant we could improve the issues. I'm lead to believe Impero and sophos have both used the same 3rd party code set to inject the dlls which is why they are both suffering from the same issues.

 

 

 

 

 

Mic @ Impero

[Sheridan]

Yup we've found deleting the profiles helps and we do use Sophos.

 

Most of those services we have disabled as well, apart from wisvc,ffsvc and DiagTrack which don't seem to appear in our services in the GPO.

[ewanc1234]

What versions of Impero are known to cause this? We are having black screen issues and want to rule this out to be the cause.

[Mic_Impero]

Hi @ewanc1234

 

Any version prior to 6.1 running on 1703 upwards could see this issue with Impero. We've got lots of updates and some new features in our later versions and I'd really encourage you to move to the newer version if you're able to, which will for sure rule out Impero, or resolve the issue if Impero is a contributor.

 

Mic

[speckytecky]

Strangely we had the same issue on some W7 machines and had to restart the PC then log in as the same user again and it was okay. Touch wood, it seemed to sort itself out in the end.

[Sheridan]

Just had another 2 - login, get the Welcome screen, then black screen with cursor - one of them was with a fresh profile as well.

[Fazza]

What versions of Impero are known to cause this? We are having black screen issues and want to rule this out to be the cause.

 

There is a very simple and quick fix if it is Impero which is why people ask the question when people report this kind of issue. It's not a fault as such, a quick configuration update on the Imper Server is required and then once the client gets the settings the issue goes away!

[alfatec]

We are running 1709 and have not seen this issue with this. Did on 1703.