Windows Server 2016 application crash popup - "Host process for setting synchronization has stopped working"

I have a Windows Server 2016 XenApp server, and every so often, I get an a standard application crash popup saying "Host process for setting synchronization has stopped working".  In the event logs I get this...

Log Name:      Application
Source:        Application Error
Date:          23/03/2018 14:40:58
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xenprawf03.domain.local
Faulting application name: SettingSyncHost.exe, version: 10.0.14393.1198, time stamp: 0x590280cf
Faulting module name: SettingsHandlers_nt.dll, version: 10.0.14393.2125, time stamp: 0x5a9907cb
Exception code: 0xc0000005
Fault offset: 0x0000000000010893
Faulting process id: 0x2b4c
Faulting application start time: 0x01d3c2b43eab8535
Faulting application path: C:\Windows\system32\SettingSyncHost.exe
Faulting module path: C:\Windows\System32\SettingsHandlers_nt.dll
Report Id: 4265a47f-2759-4546-a1b3-c60121cf85bc
Faulting package full name:
Faulting package-relative application ID:

I can't seem to pin point exactly what I'm doing to cause this - and it'll only happen once per session (presumably the process in question doesn't re-open after the first crash), and I can't tell whether it'll happen after a few minuets or after a couple of hours, so it's not really feasible to run ProcMon on it either.  Closing the popup doesn't seem to affect anything with how the session runs, though, but I'd still like to prevent this from happening because I'm just going to get calls to the helpdesk from people who clearly don't have enough work to do!

Does anyone have an idea where I can start looking for this?

A few months ago I ran an optimization script on this machine which disables apparently unnecessary services, to improve performance.  I'm guessing there is a possibility that the disabled state of one of the services is causing this. Just in case, I've attached screenshots of all the Disabled services on my machine.

meirionwylltSenior Desktop EngineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Gwyn, since very few people disable windows' internal services at all, there is little experience around. I would enable all the services again and see if that changes anything. If it does, maybe use the black viper list for win10 and take the "safe" configuration and apply it to 2016 for a test, rather than mess with such an amount of services.
meirionwylltSenior Desktop EngineerAuthor Commented:
Windows Server 2016, in terms of performance, is dreadful, so the only option is to disable unwanted services, or change it for an OS that is already 5 years old, which I'm not prepared to do.

As for the list of services safe to disable, the script I ran was compiled specifically for Windows Server 2016 used as a XenApp server, so I can't imagine that Black Viper's Windows 10 list would be more suitable here.

Anyway, after a bit more digging I've found the solution myself.  The error I was getting was pointing to the Settings Sync service, which synchronizes settings like wallpaper, theme, Mail app settings, from one machine to the next.  Why anyone would want this service on a Windows Server machine is beyond me, so obviously the best way to go is to disable this too.  I was unable to disable it from Services.msc, so I had to follow this in order to do it in the registry instead.

Now the error popup no longer appears.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Great, thanks for sharing.
"the script I ran was compiled specifically for Windows Server 2016 used as a XenApp server" - please consider to share that source, too, as this question will be archived and others might be interested :-)
meirionwylltSenior Desktop EngineerAuthor Commented:
meirionwylltSenior Desktop EngineerAuthor Commented:
found the answer myself.  error popup is no longer appearing.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 10

From novice to tech pro — start learning today.