Jump to content

Recommended Posts

Posted

Blank screen at startup... welcome to my world. Theres numerous threads on here about black screens after logging on.

 

I've just had 3 this morning and looking in the logs 2 point to the thumbnail cache class factory for out proc server and the other gave no logs in eventvwr. A few other machines report other AppId and CLSID errors which if you look further into, you can stop by denining everyone access but this doesnt solve the problem.

 

Needless to say ive been plagued with this and the start menu / taskbar not working on random machines.

 

The machines with black screens though were running LTSB2015.

 

Ive hacked the registry to bits, again noted my findings on various threads, stopped services running and even disabled IPv6 to see of that had any effect which it doesnt.

  • 2 weeks later...
Posted

I have had the same issue with Windows 10 Machines.

I fixed mine by disabling a specific task so far I have had 100% success rate; no more black screens when logging in to a domain account.

 

Make sure you have joined the domain before you do this.

 

- Login as as a local admin

 

- Go to Task Scheduler

 

- Expand Microsoft > Windows > Work Place Join

 

- In that folders there will be an item called Automatic-Workplace-Join. Disable, restart the machine.

 

That and you you shouldn't have any more issues.

 

hope this helps!

 

Regards

Posted

Well done, youll have to see how it goes across the domain.

 

Pity there isnt a way to delete this via AD as i struggled to delete schedule tasks in the past.

Posted
- In that folders there will be an item called Automatic-Workplace-Join. Disable, restart the machine.

 

We cant see this option on our Windows 10 machines, we do have Automatic-Device-Join - is this the same thing?

Posted
My bad, that is the correct one

 

Regards

 

Thanks! Just wanted to make sure we were looking in the right place! We've made the change on one affected PC so we'll see what happens now :)

Posted

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.

Posted
I have had the same issue with Windows 10 Machines.

I fixed mine by disabling a specific task so far I have had 100% success rate; no more black screens when logging in to a domain account.

 

Make sure you have joined the domain before you do this.

 

- Login as as a local admin

 

- Go to Task Scheduler

 

- Expand Microsoft > Windows > Work Place Join

 

- In that folders there will be an item called Automatic-Workplace-Join. Disable, restart the machine.

 

That and you you shouldn't have any more issues.

 

hope this helps!

 

Regards

 

Didnt work. Blank screen and had to reboot to get it to eventually display.

Posted

This is odd, i guess its not as simple as that. Its a shame microsoft dont seem to be doing anything about it!

 

Its worked for me but i guess it may depend on how you have the GPO setup aswell.

 

I have made sure my roaming profiles dont go any bigger than 5mb. Everything redirects to other folders.

 

Also no scripts for maped drives and printers, everything is done via GPP.

 

 

I think we can all agree its something to do with timeouts but it might be infulenced how we have our networks set up.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...