Windows 10 1809 Upgrade - Black Screen with Cursor for ~2 Minutes (W10 Enterprise)

  • Thread starter Thread starter Sys1809Ko
  • Start date Start date
S

Sys1809Ko

Guest
Hey.


I've been trying to deploy Windows 1809 over my 1709 Clients for quiet some time now, but have encoutered numerous problems.

One of them is that local users face login times of over two minutes, ~30 seconds of "Welcome", ~90 seconds of blackscreen after. After that, the Desktop appears as it should and most things work fine, expect running some setup applications which take roughly 30 seconds to start..

I can open and display the Start Menu during this time, I can open Explorer Windows and so on in the Background, but some stuff like programms are covered, while the start-menu is visible. Ctrl - Alt- Del works as well.

This Issue does not persist for domain users - rapid login times here.

What I noticed is that the sihost.exe seems to be either the culprit or at least a part of it, since I can replicate the problem by restarting said process. Lets say everything has loaded and I hit Run and enter sihost.exe -> 90 seconds of blackscreen..

Another thing I noticed that if I go into the registry and exchange the value explorer.exe with c:\windows\explorer.exe, in the Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell entry, the 30 seconds of "Welcome" stuff is cut to beeing nearly instant.

The error only affects local users, migrated ones as well as newly created ones. I upgraded from 1709 to 1809, this Issue persists every time. 19H1 is also affected, 1803 is not affected.

I tried the usual Dism, SFC /scannow and chkdsk stuff, I even reapplied the Upgrade with the Media Creation Tool, with no changes. No Errors in the Eventviewer, nothing suspicious visible with procmon, tried the Windows Performance Analyzer and so on.

Its not an driver issue as well, as domain users work fine. This also appeared on several different machines, VMs and so on, the list continues.

I tried loads and loads of suggested fixes from this board as well as different sites, but havent yet managed to get any improvement or solution to this Issue.

Any Ideas are welcome!

More...
 
Back
Top