Windows 10, version 1903 kills Essentials Connector

[German]Administrators using the Essentials Connector should be careful with upgrading to Windows 10 May 2019 Update (Version 1903). The update will prevent you from connecting to a Windows Essentials server afterwards. However, there is a workaround to fix the Essentials Connector again.

I became aware of this topic through Woody Leonhard. Leonhard, who runs the Askwoody.com platform, pointed out the problem on Twitter..

Windows Server Essentials broken? Lots of reports of problems, especially with Win10 1903. #PatchLady https://t.co/80udJi5rcu

— Woody Leonhard (@AskWoody) 14. Juni 2019

Susan Bradley, who is active on askwoody.com and runs the patchmanagement.org platform, has posted this short article.

For those of you still using the Windows Server Essentials 2012 or Windows Server Essentials 2016 platforms in your client base that provides the ability to backup the client workstation as well as provide storage, just a heads up.  Every feature release there is a constant battle with the connector software on the clients.  In the past we've been able to tell people to reboot the pc several times and the connector "wakes" back up again. Peter Perry reports that this time with 1903 you'll need to totally uninstall the connector and reinstall it to get it to hook back into the console.

So if you are still using Windows Server Essentials 2012 or Windows Server Essentials 2016, you have to rely on the Windows clients and the Essentials connector. The solution offers the possibility to backup the client workstation as well as to provide storage space. According to this Technet forum post, the connector must be uninstalled and then reinstalled. 

Windows 10 Feature Update 1903 disables Essentials Connector

I have begun testing the Windows 10, version 1903 Feature update.  In the three clients on which I installed the update, they were unable thereafter to connect to the Essentials Server.  The only way I was able to resolve the issue was to manually uninstall and reinstall the connector.

The bad side of the story: Users had been reporting this to Microsoft for months, and a Microsoft moderator had already mentioned the Uninstall/Install solution there.