Black screen problems with Windows 10 at login

[timbo343]

{7006698D-2974-4091-A424-85DD0B909E23} is the Windows Insider Service - could try setting that to Disabled (GPP setting)?

 

Hats of to you for knowing this. Ive searched and searched this to no end and found nothing. How do you know its the Windows Insider Service? Needless to say, ill be disabling this service across the domain.

[Ephelyon]

I didn't. I googled for that GUID, first hit took me to a Microsoft Answers discussion, first post on its second page mentions looking under HKEY_CLASSES_ROOT\AppID for the GUID in question to find out what it relates to...

 

Edited October 19, 2016 by Ephelyon

[timbo343]

I didn't. I googled for that GUID, first hit took me to a Microsoft Answers discussion, first post on its second page mentions looking under HKEY_CLASSES_ROOT\AppID for the GUID in question to find out what it relates to...

 

[ATTACH=CONFIG]39317[/ATTACH]

 

Well, my google-fu failed me on countless times then. Ive trolled google with various searches for this id and i've searched the registry multiple times which gave very little in the way of a result.

[sturgeo]

Have you got any impero error log files on the C drive that match up timewise?

We had to remotely browse to the C$ (whilst the machine had the post login black screen) and saw some timestamped errors, they had miraculously been overwritten by less useful information upon the next boot.

 

Still, 2+ weeks of being free of impero software and not a single reported black screen.

We're currently setting up an entirely new impero server and will be deploying it to just a single IT room, time will tell!

[timbo343]

Have you got any impero error log files on the C drive that match up timewise?

We had to remotely browse to the C$ (whilst the machine had the post login black screen) and saw some timestamped errors, they had miraculously been overwritten by less useful information upon the next boot.

 

Still, 2+ weeks of being free of impero software and not a single reported black screen.

We're currently setting up an entirely new impero server and will be deploying it to just a single IT room, time will tell!

 

In which folder were the errors, so i can check for the future. Are they in the Root of C or buried deep within program files.

[sturgeo]

In which folder were the errors, so i can check for the future. Are they in the Root of C or buried deep within program files.

 

Pretty sure everything was in the root of C:

[timbo343]

{7006698D-2974-4091-A424-85DD0B909E23} is the Windows Insider Service - could try setting that to Disabled (GPP setting)?

 

Hmmm, just to come back to this. Windows Insider is on my machine as im using EDU however we have LTSB2015 deployed out to the school and those machines don't have the Windows Insider Service listed so im wondering if something is calling that service and crashing as it doesn't exist.

 

We are looking at deploying LTSB2016 out soon.

[timbo343]

Just looked at LTSB2016 and the Windows Insider Service is there. I wonder if killing dll would solve this issue on LTSB2015

[timbo343]

Still grasping at straws with this problem and still continuing to run Impero but ive seen something on our machines in Task Scheduler which might point us in the right direction. Ive checked the machine which had the problem yesterday and seen the attached image. Is it a coincideace that the logs from event viewer marry up with the User Feed Synchronisation task?

 

Ive checked a few other machines around school and some machines have loads of entries of this user feed sync service.

[timbo343]

Just had another machine with the black screen problem.

 

Got hold of the local Impero folder on Program files and checked the event log and the schedule tasks to find the attached.

[Ephelyon]

I suppose it's conceivable that could be linked to the Windows Insider service. There are some suggestions for resolving it here: Microsoft Feeds Synchronization - Microsoft Community

[BarryBKS]

Timbo343,

 

Thanks for directing me towards this post.

 

I have only seen this issue on 1607.

We are also running Impero, but I don't think it is related as it often happens on machines before Impero is installed and I have seen the problem occur on brand new home builds, including my own!!

The problem seems to occur after Windows Updates has been run or while they are being applied.

The DCOM event errors are written to the event viewer during the black screen state.

 

Hardware seems to be irrelevant. HP, Dell, Intel CPU usually. Intel or ATI graphics. Often Intel chipset.

 

I have asked Microsoft for some explanation / fix here, but I am yet to hear anything.

 

As this is such an unpredictable issue, I get classrooms as well as IT suites with unusable PCs for over two hours!! Not a very practical working environment for a school, or any other corporate business for that matter.

 

Looking forward to seeing anyone's solution as this is turning into one very big headache.

 

Cheers,

[k-strider]

We see this across our estate too, either either Pro or Edu and either 1511 or 1607 we do use impero

[timbo343]

Do you see anything out the ordinary in the event logs when this happens. Edited October 21, 2016 by timbo343

[k-strider]

next time i see it i'll have a look

[timbo343]

so ive not found the cause of the problem however i can replicate the problem in a room of 30 machines.

 

We have 7 ICT suites and if i do a mass logon on each room at least one machine will fail logon with a black screen. Looking at the event viewer i cannot see any thing out the ordinary and i've cleared out all the errors that were relating to the DCOM messages. I created a new GPO which changed the security permissions of %windir%\systemapps so that SYSTEM and ITADMIN had full control over this folder. Within the same policy, i created 2 entries to delete ContactSupport and WindowsFeedback. This GPO is working as these folders have now been deleted however we are still getting the black screen issue.

 

To those of you who have removed impero from a suite of machines, have you still been getting the black screen issue or does this problem no longer exist in those rooms?

[steven_layton_sl]

@timbo343 We're having the black screen issue. We're running Windows 10 Education, 1511. We have not found one single magic bullet, but have found two things that have massively reduced the occurrence of the issue.

 

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.

[FragglePete]

@timbo343 We're having the black screen issue. We're running Windows 10 Education, 1511. We have not found one single magic bullet, but have found two things that have massively reduced the occurrence of the issue.

 

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.

 

Looks interesting. You state Log Off Script, but the article says Logon. Can you clarify where you are using it?

 

Thanks

 

Pete

 

PS. On a different note, I've been getting reports on Black Screen issues happening on our Macs - all of which have Impero installed but I haven't clarified anything yet as it could just be the Macs being, well, Macs.

[timbo343]

@timbo343 We're having the black screen issue. We're running Windows 10 Education, 1511. We have not found one single magic bullet, but have found two things that have massively reduced the occurrence of the issue.

 

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.

 

The Start Screen Cache (aka TIleDataLayer i think it's called) was the deciding factor for us to go to LTSB as this was having a massive impact on our users. I might re-visit this issue again as we have a delprof script that runs when a machine is restarted or powered off.

 

We get the issue even with our domain admin account which has hardly anything in the userarea. If it was happening on users who had their user areas full, it would be happening to most staff. Instead, it happens to students rather than staff.

 

As for the MS fix, we have mandatory profiles for students, the key listed in the link you gave is already deleted from the Mandatory Profile when we set it up. I honestly think it's something to do with Impero. @stgoodyeara was going to remove impero from a room over half term to see if that made any difference.

 

We are looking at deploying LTSB2016 but hitting some sticking points at the moment.

[steven_layton_sl]

I may have linked to the wrong article, sorry. This is a copy of the logoff script that runs to clear the Start Menu Cache.

 

On Error Resume Next

Dim objShell,strKeyPath

strKeyPath = "HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\UFH\SHC"

Set objShell = WScript.CreateObject ("WScript.shell")

objShell.RegDelete (strKeyPath)

[Danp]

Have you got any impero error log files on the C drive that match up timewise?

We had to remotely browse to the C$ (whilst the machine had the post login black screen) and saw some timestamped errors, they had miraculously been overwritten by less useful information upon the next boot.

 

Still, 2+ weeks of being free of impero software and not a single reported black screen.

We're currently setting up an entirely new impero server and will be deploying it to just a single IT room, time will tell!

 

How was it? Did it come back in that room?

[timbo343]

Looks interesting. You state Log Off Script, but the article says Logon. Can you clarify where you are using it?

 

Thanks

 

Pete

 

PS. On a different note, I've been getting reports on Black Screen issues happening on our Macs - all of which have Impero installed but I haven't clarified anything yet as it could just be the Macs being, well, Macs.

 

Hah! that is interesting if it turns out to be the same issue on the macs as well as on the windows machines.

 

We're now in a position where we are going to deploy LTSB2016 to a room, just need to wait for WSUS to download the latest updates tonight / tomorrow and then we are ready to roll with impero 5.4.36 and LTSB2016 in a room of 17 machines.

[paulr522]

I just came across this thread. We have been experiencing the black screen on 1511 Edu since first roll out and we do not use Impero. However we've never had to manually power off a machine, the desktop will eventually appear after anything up to a minute or so.

[timbo343]

I just came across this thread. We have been experiencing the black screen on 1511 Edu since first roll out and we do not use Impero. However we've never had to manually power off a machine, the desktop will eventually appear after anything up to a minute or so.

 

We can be waiting longer, someone waited an hour and no desktop displayed.

[timbo343]

So, that's one room deployed with LTSB2016 and impero 5.4.36 installed. Another room tomorrow.