Windows 10 - 1809 update Active Directory error/can’t log in!

Hi IT. I'm Greg, an installation specialist and 9 year Windows MVP, here to help you.

I would ask this at our sister forums for IT professionals Technet, as this is strictly a consumer site: https://social.technet.microsoft.com/Forums/en-...

I will add that I would always troubleshoot with only a single monitor, and to check your Display driver is fully updated and working properly.

I hope this helps. Feel free to ask back any questions and let us know how it goes. I will keep working with you until it's resolved.

________________________________________________________
Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

Hey Greg!

Thanks a lot for your reply to my previous post. I followed your tip on troubleshooting with one monitor. Thanks for this tip, it got me further in the process! I have the following update after another day of troubleshooting. Hope someone can help out!

First I tried logging in via Safe mode. The system almost instantly crashed giving me the following error:

sihost.exe 
- 
System Warning Unknown hard error 
<ok>

So that didn't help. Next I logged in reguarly and the screen started flashing again. I waited for an hour to see if anything happened but unfortunately not.

We got to this situation:
 - Local login works (seems fine)
 - AD login crashes
 - Ctrl + Alt + Del works. So I can logout crashed user
 - Loggin in locally again makes the "hi, welcome'  video appear. After this it seems the local user has partly reset.
 - Everything is up to date (double checked). 

What I did next was disconnecting my screens. Suprisingly this helped with the flickering, and so I could log in to my AD profiles, although still there seems to be a problem with the server connection. 
It seemed I had this problem (Edge doesn't have internet connection) https://techcommunity.microsoft.com/t5/Windows-10/Windows-10-1809-Edge-not-loading-pages/td-p/266050 which I could fix by enabeling IPv6 (It is weird this is obligated right? Or is this a driver issue?)
Then it seemed I also had this problem (search bar not working) https://basics.net/2016/12/20/windows-10-cant-type-in-search-field/ which I haven't really been able to fix by following the numerous online tutorials on how to fix this.

Also the following errors occur in the error log:

Faulting application name: sihost.exe, version: 10.0.17763.1, time stamp: 0xafcecc1e
Faulting module name: Windows.Shell.ServiceHostBuilder.dll, version: 10.0.17763.1, time stamp: 0xba54becf
Exception code: 0x80270234
Fault offset: 0x000000000000dd7b
Faulting process id: 0x147
Faulting application start time: 0x01d45c336d7776f5
Faulting application path: C:\Windows\system32\sihost.exe
Faulting module path: C:\Windows\System32\Windows.Shell.ServiceHostBuilder.dll
Report Id: 8fa14fd8-6548-4605-99c0-c424ba82fdf9
Faulting package full name:
Faulting package-relative application ID:

--

The winlogon notification subscriber <Profiles> failed a critical notification event.

--

Faulting application name: svchost.exe_ProfSvc, version: 10.0.17763.1, time stamp: 0xb900eeff
Faulting module name: profsvc.dll, version: 10.0.17763.1, time stamp: 0x2f1e6584
Exception code: 0xc0000005
Fault offset: 0x000000000000eec3
Faulting process id: 0x6d8
Faulting application start time: 0x01d45c3362efb329
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: c:\windows\system32\profsvc.dll
Report Id: 8a758d91-22e3-474a-b3c2-b40a877d28d5
Faulting package full name:
Faulting package-relative application ID:

--

The description for Event ID 0 from source igfxCUIService2.0.0.0 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Service started/resumed
The request is not supported

--

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
 and APPID 
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
 to the user INF\mstoll2 SID (S-1-5-21-4056881438-1123131140-2702252319-1127) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

--

The User Profile Service service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 120000 milliseconds: Restart the service.

So not sure what to do now. Seems everything is very unstable.

Any thoughts?

This would be the type of advanced IT Admin information that they could process better at Technet which is the MS forums for System Administrators: https://social.technet.microsoft.com/Forums/en-...

As I had written earlier these are only consumer forums for individual consumer problems.

I think this is it for now:
https://www.reddit.com/r/sysadmin/comments/9lrq5q/looks_like_win10_1809_has_been_pulled_from/?st=JMYR3WYB&sh=fadb3179

Anyway, rolled back all devices except one. Still experiencing the problems, so I'll just wait for a new update first before seeking technical help. 

Thanks for the replies!

We have experienced the same issue in some computers and finally we discovered that by removing the HOMESHARE value in the AD account settings, the users were able to logon. Maybe it might help you.

Javier

We've experienced the same issue.  This was only experienced by users that, under the Profile tab in their AD account, had a UNC path in the Local path that was not mapped to a drive letter.  Users with a drive letter assigned were fine. Once we changed Local Path to Connect to drive letter users were able to log in successfully.

Here's a quick script I used to find and change the settings.  Probably not the most efficient, but it was quick and worked.

To get the list: 

Get-ADUser {-filter enabled -eq $true} -properties SamAccountName, HomeDirectory, HomeDrive | where {$_.HomeDirectory -like '*\users\*' -and $_.HomeDrive -ne 'D:'} | FT SamAccountName, HomeDirectory, HomeDrive

To make the change:

Get-ADUser {-filter enabled -eq $true} -properties SamAccountName, HomeDirectory, HomeDrive | where {$_.HomeDirectory -like '*\users\*' -and $_.HomeDrive -ne 'D:'} | Set-ADUser -HomeDrive 'D:'

Also, FYI -while looking at Task Manager while the screen flashing was going on we saw the Explorer.exe process starting, hanging, starting, hanging, starting, hanging, etc.

Thankyou!!!!  I have been fighting this for about 3 months on about 6 different computers all using Active Directory from a Synology server.  The symptoms varied slightly but most of them end up with a flashing task bar and or an SIHost error.

Based on your suggestion I checked the Active Directory service on the Synology and each user had a home path set in their profile set to "\\10.1.10.151\home" changing this to use a home path with a drive letter solved the problem.

I am having similiar issue. after clean install of windows 10 pro, i can not connect to synology diskstation. how would you change the profile path 

e.g "192.168.1.41/home" to a drive letter in synology. 

does updating synology solve the log in