It sounds like the users cannot access this key to make Kereberos work. Make sure that all client computers have this key enabled that you are testing on.If you have uncommented the debugging statements you may also wish to look in the Application event log to verify that the script is running.If the script is running then Edge is not running for other reasons. It is possible that either your Windows user profile or your Windows build is now corrupt.
So far, I have established a strict dependence of SSO work of the directory name for the synchronization on a server.
The profile on the local machine is marked as Roaming (Type= Roaming, Status=Roaming) When the new user log of form the Windows XP client the user is not ...
— Update 2017-12-15 — I think Roaming Profiles are now deprecated.
While it seems absolutely incredible that Microsoft would launch Windows 10 with this key feature broken they seem to have done so and this is a widely reported problem with no official solution (2016-02-10). #New-Event Log –Log Name Application –Source “Logon Script” #Write-Event Log -Log Name Application -Source Logon Script -Entry Type Information -Event Id 1 -Message "In Login Script to fix roaming profiles" if ([Environment]:: OSVersion. Major -eq 10) You will see the this script can write to the Application Event Log for debugging purposes but I have commented it out on production.
The root cause seems to be that when a user logs out Windows 10 sets essential registry keys to read only. Create a group policy for your domain users called “User-Windows10Roaming Profile Fix”.