Windows Server Essentials Connector An Unexpected Error Occurred
June 28, 2018 2 Comments
Just recently i decided to rebuild my lab setup, which sits on a physical server in my office.
Unfortunately after painstakingly moving VHDs around my system to adjust disk space and rebuild arrays, i managed to format the wrong disk and lost it all! Being a lab setup i had not backed any of it up either.
Not the end of the world of course, more annoyed with myself than worried about the test VMs i lost.
Anyway, i noticed a thread in the TechNet forum (at least two actually) mentioning slow network performance with WIndows 10 after the latest update, and that removing the Essentials connector would remedy it.
So i set about building a Windows Server 2012 R2 Essentials VM and a Windows 10 client. When trying to launch the connector I received this error:
I realised i would need to install a lot of updates on my 2012 R2 system and that would most likely resolve it, sure enough, after installing around 160 updates we have a new Connector file.
This new version launches correctly and installs without any issue.
About Robert Pearman
Title (Required) 
Hi Robert, just read what happened with your VM Lab, feel your pain. Being that Windows Server 2012 R2 Essential is 5 years old I would have ran the updates 1st before deploying the connector but glad you got it all working. I’ve finally started the upgrade process on my Windows Storage Server 2008 R2 Essential Server and moving to Windows Server 2016 Essentials. I’ll let you know how that Pans out.
With 1809 updates for Windows 10 Pro, I have the issue. Is there any news ?
Where I can find the updated client connector ?