Black screen problems with Windows 10 at login

[timbo343]

Blank screen after login here this morning.. in the event logs under system seeing a DCOM error with the error:

 

The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.

[Danp]

We are still seeing this, maybe one an hour or so.

[MrKJLS]

We are also having this issue with this! I wonder if v6 will fix this?

[timbo343]

We are also having this issue with this! I wonder if v6 will fix this?

 

When you say V6, you mean a V6 profile? The error this morning came from a staff machine which all run LTSB2015 which creates a v5 profile and LTSB2016 creates a V6 profile.

 

We did have one staff member who constantly had trouble with their office machine that was running LTSB2015. We moved the machine over to LTSB2016, since then we haven't heard anything. Ive just been to see them and they said its been alright since so touch wood. Their teaching machine still runs LTSB2015 but not heard anything about this.

 

The number of black screens too on the student machines running LTSB2016 as pretty much gone too. It's just the random sticking start menu now on LTSB2016 that we have issues with.

[MrKJLS]

When you say V6, you mean a V6 profile? The error this morning came from a staff machine which all run LTSB2015 which creates a v5 profile and LTSB2016 creates a V6 profile.

 

We did have one staff member who constantly had trouble with their office machine that was running LTSB2015. We moved the machine over to LTSB2016, since then we haven't heard anything. Ive just been to see them and they said its been alright since so touch wood. Their teaching machine still runs LTSB2015 but not heard anything about this.

 

The number of black screens too on the student machines running LTSB2016 as pretty much gone too. It's just the random sticking start menu now on LTSB2016 that we have issues with.

Impero V6

 

Staff what primarily use Windows 10 have mandatory profiles with uev to roam there settings.

 

I've only seen it on the student machines. All the kids also use mandatory profiles.

Edited February 10, 2017 by MrKJLS

[timbo343]

Just had the black screen.. again on a machine that's done it before.

 

The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.

 

I wish i know how to solve this! It happens on both LTSB2015 or LTSB2016.

 

This key relates to RunTimeBroker.

Edited February 14, 2017 by timbo343

[newpersn]

Any ideas? Looking at recreating our main image and may look at going LTSB 2016.

 

Seems to be happening more and more over the last few days. The only thing i can think of it of the regedits i got my GPP.

[ITGURU]

I'm running Windows 10 EDU x64 both the anniversary edition and the latest November release. Had no issues with a black screen. Only random issue occasionally is the machine gets stuck 'signing out'

[newpersn]

I'm running Windows 10 EDU x64 both the anniversary edition and the latest November release. Had no issues with a black screen. Only random issue occasionally is the machine gets stuck 'signing out'

 

Are you running impero?

[ITGURU]

Are you running impero?

 

Nope and never will - I don't like this kind of software running on top of systems. Your best off going to Impero with the issues for them to sort - not a Microsoft issue.

[forkies]

Nope and never will - I don't like this kind of software running on top of systems. Your best off going to Impero with the issues for them to sort - not a Microsoft issue.

 

What are you using for safeguarding and prevent out of interest?

[timbo343]

Impero think they have fixed the black screen issue but unsure when its to be released. We've had it a few times and mysteriously it always happened on a tuesday to a specific machine on LTSB2015 so swapped the HDD out with LTSB2016 and soon found out the startmenu (custom xml) and tiledatalayer become an absoltue PITA, to a point where i had to redirect the tiledatalayer back to the roaming profile and only for staff with V6 profiles - i had to create a gpo WMI filter to only work with 10.0.14393 otherwise it caused issues with V5 profiles on 10.0.10240. I do wish MS would sort this problem out. We have to use roaming profiles for staff as some use outlook. We have to add Authenticated users to the profile on the server share so that the v6 profile can be loaded. Yes, i could use mandatory profiles for staff who dont use outlook i guess. Ive been tempted to look at UEV too but it means using offline files which ive spent a lot of time stopping the services and processes via gpo.

 

I have seen the error message critical error - cortana isnt working. Im not too sure why this didplats, again this is completely random.

 

I had a meeting with Mic at impero a few week ago and have another one on the 20th march and will ask again how they are getting on with the black screen problem.

 

Windows 10 is giving me sooo much of a headache that im ready to throw the towel in at work. It feels that any adjustmemts that i do will end up breaking it. It isn't well built for domains and if i could i'd go back to windows 7 tomorrow. Moving from xp to 7 had no major issues but 7 to 10 has been a nightmare.

[Arthur]

Windows 10 is giving me sooo much of a headache that I'm ready to throw the towel in at work.

Microsoft have deprecated Tile Data Layer in the Creators Update so it might not be worth throwing in the towel just yet.

 

https://support.microsoft.com/en-us/help/4014193/features-that-are-removed-or-deprecated-in-windows-10-creators-update

[newpersn]

Impero think they have fixed the black screen issue but unsure when its to be released. We've had it a few times and mysteriously it always happened on a tuesday to a specific machine on LTSB2015 so swapped the HDD out with LTSB2016 and soon found out the startmenu (custom xml) and tiledatalayer become an absoltue PITA, to a point where i had to redirect the tiledatalayer back to the roaming profile and only for staff with V6 profiles - i had to create a gpo WMI filter to only work with 10.0.14393 otherwise it caused issues with V5 profiles on 10.0.10240. I do wish MS would sort this problem out. We have to use roaming profiles for staff as some use outlook. We have to add Authenticated users to the profile on the server share so that the v6 profile can be loaded. Yes, i could use mandatory profiles for staff who dont use outlook i guess. Ive been tempted to look at UEV too but it means using offline files which ive spent a lot of time stopping the services and processes via gpo.

 

I have seen the error message critical error - cortana isnt working. Im not too sure why this didplats, again this is completely random.

 

I had a meeting with Mic at impero a few week ago and have another one on the 20th march and will ask again how they are getting on with the black screen problem.

 

Windows 10 is giving me sooo much of a headache that im ready to throw the towel in at work. It feels that any adjustmemts that i do will end up breaking it. It isn't well built for domains and if i could i'd go back to windows 7 tomorrow. Moving from xp to 7 had no major issues but 7 to 10 has been a nightmare.

 

What version of impero are you on?

 

Microsoft have deprecated Tile Data Layer in the Creators Update so it might not be worth throwing in the towel just yet.

 

https://support.microsoft.com/en-us/help/4014193/features-that-are-removed-or-deprecated-in-windows-10-creators-update

 

When the release date of this?

[timbo343]

Microsoft have deprecated Tile Data Layer in the Creators Update so it might not be worth throwing in the towel just yet.

 

https://support.microsoft.com/en-us/help/4014193/features-that-are-removed-or-deprecated-in-windows-10-creators-update

This is possibly the best thing ive heard since windows 10 has been released!! I wish the next LTSB version (1707) would get released.

[timbo343]

What version of impero are you on?

 

 

 

When the release date of this?

Im on 5.4.38 and looking at doing the V6 upgrade in easter but will be ralking to Mic on monday about it. I think 6.1 has the black screen fix.

[Arthur]

When the release date of this?

11th April 2017 apparently.

 

I wish the next LTSB version (1707) would get released.

Isn't the next LTSB version going to be in 2-3 years time?

 

... LTSB is only due to receive revisions every two or three years. Our assumption is that, in practice, LTSB releases will be paired with Windows Server releases; the back-to-back 2015 and 2016 LTSB builds are a one-off due to Windows 10 being released more than a year before Windows Server 2016.

[ITGURU]

What are you using for safeguarding and prevent out of interest?

 

Our filter has image filtering and reports by website category . For screen viewing we use vnc.

[newpersn]

Im on 5.4.38 and looking at doing the V6 upgrade in easter but will be ralking to Mic on monday about it. I think 6.1 has the black screen fix.

 

Is it impero making the black screen problem? or is a mix of windows and impero?

[timbo343]

Isn't the next LTSB version going to be in 2-3 years time?

 

Oh for gods sake!! :banghead: So it means we have to put up with 1607 or get education to work! Really losing faith and confidence in MS now.

[timbo343]

Is it impero making the black screen problem? or is a mix of windows and impero?

 

I honestly don't know - but im starting to get really frustrated with the OS! We have a version that works to a point but staff roaming profiles don't always work and the start menu breaks, along with black screens (1511) and we have 1607 where the start menu / taskbar doesn't work (only on random machines), staff who use the V6 profile have to have an extra policy that copies the tiledatalayer to the profile and a vbs that runs at startup to populate the icons however if we change the start menu for what ever reason we would have to delete all the profiles on the server. We also set the cache copies of profiles to delete meaning the logon has to look at the profile share for the profile and the V6 staff profiles have to have authenticated users added to the folder with full permission as this isn't added when the profile is created.

 

Appologies if this is going slightly off topic but the list of possibilities on why the start menu / black screen problems is scraping the bottom of the barrel now.

Edited March 16, 2017 by timbo343

[steven_layton_sl]

Guys. I've had a ticket logged with RM about the black screen issues for quite a while as I thought the issue might have been with the CC4 stuff. They stated that they were working with Impero to try to identify the issue, as they were clearly seeing it at other CC4 schools. At the time I was still in support with Impero. Knowing that I was going to have to drop support with them for budget reasons, I logged the ticket with Impero, and specifically asked them whether they would allow me to update to a future version of Impero, even if I was out of support, if it was known that that update would fix the black screen issue. Impero agreed to this via email, just before Christmas.

Fast forward to a week or so ago, RM updated my support call with them, stating that Impero had identified an issue, and would be fixing this in a future v6 release. I contacted Impero, who have said they'll honour their agreement with us, so in April (or when the v6 version is released), I'll be updating to that version.

We're still seeing a couple of instances a day, so it'll be immediately obvious if the updated version of Impero fixes the issue or not.

Edited March 16, 2017 by steven_layton_sl

[newpersn]

I honestly don't know - but im starting to get really frustrated with the OS! We have a version that works to a point but staff roaming profiles don't always work and the start menu breaks, along with black screens (1511) and we have 1607 where the start menu / taskbar doesn't work (only on random machines), staff who use the V6 profile have to have an extra policy that copies the tiledatalayer to the profile and a vbs that runs at startup to populate the icons however if we change the start menu for what ever reason we would have to delete all the profiles on the server. We also set the cache copies of profiles to delete meaning the logon has to look at the profile share for the profile and the V6 staff profiles have to have authenticated users added to the folder with full permission as this isn't added when the profile is created.

 

Appologies if this is going slightly off topic but the list of possibilities on why the start menu / black screen problems is scraping the bottom of the barrel now.

 

eek. We us classic shell. I could never get the start menu working to they way i wanted it to. (works fine for kids but not for staff)

 

I'm going to hold by moving to ent or ltsb to see if the update next month fixes anything.

[samb56]

Hi All,

 

I have been working closely with Impero to have this issue resolved it is Impero and only effects 1511 verision of Windows. They are testing a service pack for the new release which they believe has fixed the issue.

[mattpant]

Hi All,

 

I have been working closely with Impero to have this issue resolved it is Impero and only effects 1511 verision of Windows. They are testing a service pack for the new release which they believe has fixed the issue.

 

I have the Black Screen after logon issue with Windows 10 Education Edition - 1607 and using Impero! We are using a fairly old version of Impero - I was fed up of all the broken promises they gave us about fixing things and never getting them and so we didn't renew our support with them - one of the issues that should have been fixed was promised to us no end of times whilst we were still supported, but magically it came out after we were out of contract and they didn't honour it for us to get the update!