locked
Some domain users get "user profile service failed" when trying to login after October Windows update RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    1
    Sign in to vote

    Some of my domain users can't logon on any upgraded Win10 pro machine, whilst other users can logon to the upgraded machine fine.  they see the error - windows couldn't connect to the user profile service service.

    There accounts can also not logon to other upgraded machines - they see the same error on other machines too.

    The 'fix' seem to be rebuild their machine then stop the update happening - but what is the rel cause and proper fix?

    i also on one occasion on one machine saw windows couldn't connect to the System Event notification Service service

    Thanks

    Stuart


    Stuart

    Friday, October 5, 2018 11:07 AM

Answers

  • Question
    Sign in to vote
    3
    Sign in to vote

    I have the same issue on 10 systems now. Admin user can login just fine, but normal domain user gets the same error windows couldn't connect to the user profile service.

    I can add the user to the local administrator group and the can log in, but that is not a solution. I have checked a domain user's rights to access svchost.exe file and the have read and execute rights.

    I am rolling everything back to 1803.



    found something, clearing the home drive path on the active directory user object. It allowed me to login. I then home drive mapping back on the object (it complains that the directory already exists, but I said ok) logged user off and back on again and it seems fine. 
    • Edited by Gov PC Guy Tuesday, October 16, 2018 7:09 PM
    • Marked as answer by Stuart Fawcett Wednesday, October 17, 2018 8:39 AM
    Tuesday, October 16, 2018 6:50 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,
    For error Windows couldn't connect to the System Event notification Service service, I suggest you:
    1、Run SFC /SCANNOW to check if any corrupt system files referring to the following link:
    Use the System File Checker tool to repair missing or corrupted system files
    https://support.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system
    2、Reset the Winsock Catalog:
       a. Open a Command Prompt as an Administrator.
       b. Type netsh winsock reset and press Enter.
       c. Restart the computer.
    3、In some cases, the issue may be caused by faulty Font Cache files.
    Please rebuild Font cache referring to the link below:
    How to rebuild Font cache in Windows 10
    https://www.thewindowsclub.com/rebuild-font-cache-in-windows
    Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    Regards,

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, October 8, 2018 10:12 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,
    For error Windows couldn't connect to the user profile service service, it may be caused by corrupt user profile. Please log in with administrator account and try to delete problematic user profiles.
    You can refer to this link:
    How to delete domain user profile from a computer?
    https://serverfault.com/questions/450389/how-to-delete-domain-user-profile-from-a-computer
    Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
    Then restart PC and re-logon on the machine with domain user account to see if it works.
    If the issue still persists, please rebuild these machines and wait for a while to install Windows 10 October 2018 Update.
    Windows 10 update history
    https://support.microsoft.com/en-us/help/4464619/windows-10-update-history
    Regards,

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, October 8, 2018 11:03 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for your reply, I've tried all the options listed above but they all come back normal and don't fix the issue of just SOME users getting the error "Windows couldn't connect to the user profile service service".  Its only on the 1809 release, the users are fine on the 1803 previous release.

    Stuart

    Monday, October 8, 2018 3:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for your reply, I've tried all the options listed above but they all come back normal and don't fix the issue of just SOME users getting the error "Windows couldn't connect to the user profile service service".  Its only on the 1809 release, the users are fine on the 1803 previous release.

    Stuart

    Monday, October 8, 2018 3:46 PM
  • Question
    Sign in to vote
    3
    Sign in to vote

    I have the same issue on 10 systems now. Admin user can login just fine, but normal domain user gets the same error windows couldn't connect to the user profile service.

    I can add the user to the local administrator group and the can log in, but that is not a solution. I have checked a domain user's rights to access svchost.exe file and the have read and execute rights.

    I am rolling everything back to 1803.



    found something, clearing the home drive path on the active directory user object. It allowed me to login. I then home drive mapping back on the object (it complains that the directory already exists, but I said ok) logged user off and back on again and it seems fine. 
    • Edited by Gov PC Guy Tuesday, October 16, 2018 7:09 PM
    • Marked as answer by Stuart Fawcett Wednesday, October 17, 2018 8:39 AM
    Tuesday, October 16, 2018 6:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    :) Many thanks Gov PC guy - that's the thing for me too - my user can now login if I remove this connect to drive and choose Local path instead its all good. 

    I now need to find out how to let them login and have the mapped drive.



    found something, clearing the home drive path on the active directory user object. It allowed me to login. I then home drive mapping back on the object (it complains that the directory already exists, but I said ok) logged user off and back on again and it seems fine. 

    Stuart

    Wednesday, October 17, 2018 8:42 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Although this update was released, I believe it has since been pulled for deleting user files.

    https://betanews.com/2018/10/04/windows-10-october-2018-update-deleting-documents-photos-and-other-user-files

    The 1809 update is currently unavailable to install from the windows update catalog and can only be installed using the Windows Update/Upgrade Assistant

    Probably worth waiting until it is released to general public once the bugs have been fixed.

    Definitely not something I would be rolling out at present and likely to be the cause of this issue.

    Wednesday, October 17, 2018 8:45 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Gov PC Guy - THANKYOU!

    I've been struggling with this for days! Thought it was a corrupt profile. Went as far as wiping the PC but same error! All I needed to do was remove the home drive mapping. Wow. Now to go and reinstall all the apps back on my wiped PC. 

    Thanks MS.

    Monday, January 21, 2019 2:27 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    I've been struggling with this since since 1809 was released. I've wiped machines and installed a fresh copy of 1809 (no way to go back to 1803) and I STILL have the issue with certain domain users.

    I have verified that clearing the home drive path in Active Directory does allow users to log in. After they log in, and a user profile is built on that computer, I can go back to Active Directory and re-add the home drive path.

    Tuesday, January 22, 2019 7:51 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    found something, clearing the home drive path on the active directory user object. It allowed me to login. I then home drive mapping back on the object (it complains that the directory already exists, but I said ok) logged user off and back on again and it seems fine. 

    This solution works great however this is only a temporary fix.  The problem I am running into is I have users that swap between computers constantly.  With several hundred users, I cannot keep going into AD users and computers, disable the home drive path, allow them to log in and then re-enable the home drive path.  Is there a more permanent solution or is there a way to automate this so the first time a user logs into a new computer the home drive path can be temporarily disabled?
    Wednesday, January 23, 2019 6:15 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    We have the same problem, and found out that our program to update the userprofile in AD didn't write the right value to the homeDrive attribute. The program didn't write a capital letter + ":", but only a capital letter. After we updated the program the problem was gone. I would be grateful to hear if others have the same experience.
    • Proposed as answer by ML2323 Tuesday, March 26, 2019 3:45 PM
    Friday, January 25, 2019 4:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I removed the Windows 10 Update Assistant to resolve the problem.
    Wednesday, January 30, 2019 7:15 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I removed the Windows 10 Update Assistant in Programs and Features to resolve the problem.
    Wednesday, January 30, 2019 7:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Your AD account profile home folder should be set to connect.  This is now an 1809 requirement.

    Monday, March 4, 2019 6:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have been looking at discrepancies between the accounts that's able to log in and the ones who's not. I found that users with the AD-attribute userAccountControl set to ”0x220 = ( PASSWD_NOTREQD | NORMAL_ACCOUNT )”, ”544” in decimal seems to be able to log in. All users who have gotten the error thus far has what I've seen had a different setting. Setting the attribute to 544 solves the issue for the user, however they are prompted to change password :-/'

    I have a premier support case but no help from them so far. The support technician mentioned that they have seen many "similar" issues...


    Thursday, March 7, 2019 11:16 AM
  • Question
    Sign in to vote
    2
    Sign in to vote

    Hi apfselv,

    I've been scratching my head on this. Thanks for your solution, it works!

    We just deployed Windows 10x64 Enterprise to Ring 0 computers. I've all the conf. rom computers are on this version (1809). One user reported problem where he couldn't log-in to this Conf. Room A and I found this topic.

    First, I asked him if he could log-in to another conf. room computers, he couldn't either. I have a test computer is on 1809, where he couldn't log-in either!!

    Contacted our Domain Admin, he suggested to try removing the home drive from first from his AD account and log-in to the computer. After home drive removed, log-in to the test computer, he's able to log-in. Then I added back his home drive to his AD account. Log off then log-in again, it works. Next, he tried to log-in to another conf. room computer where he never log-in before. He could log-in without any problem!!

    Microsoft, would you please fix this bug?

    Reza Prawirasatya


    Tuesday, March 12, 2019 6:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I did the same thing and the only thing that was different was that the clients that were effected had homeDrive set to H and the ones that didn't had H: 
    Friday, March 15, 2019 4:01 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have this problem, too. 

    I have parsed through all my users (300+, which is not so bad) with the "remove home drive (set to local) and then put home drive back" and the problem was resolved.

    Until it reappeared, on some users. I do not have enough information about which PCs (win7 or win10) the user(s) have logged to since I first "fixed" the home drive association. 

    I replaced the H: drive letter to U: and it worked. Reverting back to H: still works. 

    This is annoying. I hope it gets fixed soon. Though I am glad I do not have 5000 + users!

    Thanks to everyone who contributed to this post, it is the only one so far that concerns the problem I am facing, all the others are about corrupted local accounts. 

    Has anyone else tried the windows updata assistant way? Does it work? 

    Thanks again!

    Monday, March 25, 2019 3:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I could only assumed at this point since the home drive is old technology (file server/home drive). Since more companies are going to the cloud (Microsoft) with Microsoft OneDrive (Cloud storage). Is that mean with 1809 they forgot for the companies are still using file server / home drive?

    This is not affected all users but for some (12+) at least.

    No, we use SCCM to deliver Windows 10 updates and patches.

    Reza Prawirasatya

    Tuesday, March 26, 2019 1:25 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We've been having this issue ever since this upgrade came out. After some testing today on the April 2 patch (KB4490481) it appears that this might be finally resolved. I can't seem to get that error to pop up anymore, though it was pretty random as to which users would have a problem and which would not.

    Has anyone tested this patch and noticed any improvements?



    Thursday, April 4, 2019 4:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi! I am also eager to hear if the April 2nd patch or the 1903 build finally fixed this issue.

    The only solution we could roll out was to deploy machines with build 1803 instead of 1809. But we can't do this forever... 

    Thanks

    Sebastien.

    Thursday, June 6, 2019 8:38 PM