none
Windows Server 2012 R2 Essentials Connector Update won't install on Windows 10

    Question

  • I tried to install the update Windows10.0-KB2790621-x64.msu for connecting the windows 10 pro x64 clientto the windows server 2012 R2 essentials server, but the msu package always fails on the client.

    any idea how to solve that or manually install the connector software ?

    i already tried to copy the files "system32\essentials" from a working client to the client with the installation problems

    but the deploy.exe wont work. do i have to register all the dlls ?

    Saturday, April 23, 2016 6:26 PM

All replies

  • Why are you downloading that?

    Open IE on the client and surf to servername/connect  The page does not list Win10 and never will, but it works.


    Grey

    Sunday, April 24, 2016 12:02 PM
    Moderator
  • I was having issues as well with the connector software. I think since I had cancelled an installation (multiple times), it would just turn itself off during the "installation phase" (right before you have to enter your credentials). What I did was just did a system restore to a point in time before I tried to use the connector software for the first time, and started all over following the proper steps and it worked great for me. I literally just got it to work a few minutes ago.

    I also followed the steps here to not join a domain as well: https://tinkertry.com/how-to-make-windows-server-2012-r2-essentials-client-connector-install-behave-just-like-windows-home-server#comment-1705687227

    Monday, April 25, 2016 4:09 AM
  • Hi,

    Make sure that you have installed KB 3105885 - Update to support auto-redirection of Windows Server 2012 R2 Essentials for Windows 10 client connector – on your Essentials Server:
    https://support.microsoft.com/en-us/kb/3105885

    Then, follow the official document to download Connector from Essentials(via accessing http://<server name or IP address>/connect):
    https://technet.microsoft.com/en-us/library/jj713510.aspx

    Also, make sure that your client meets the prerequisits for connecting to the server.

    If the problem persists, any error prompt? And, on which step does this wizard prompts error? Please provide the screenshot if possible.

    Besides, have you confirmed that if any other client(with same and different OS version) can connect to the server successfully?

    Best Regards,
    Eve Wang

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

    Monday, April 25, 2016 10:42 AM
    Moderator
  • My previous comment was for Server 2012. I am now trying to connect to Server 2012 R2 Essentials and the connector is not working. Error message: "Windows Server Essentials Connector has not be installed because: Packing installation did not succeed. Try to install the Windows Server Essentials Connector again. If the issue persists, contact your network administrator."

    The solution given here: https://technet.microsoft.com/en-us/library/jj635102.aspx  states to "Complete all other updates or application installations. Restart the computers if prompted."

    This does not work. I think the reason is because every time I restart, the server dashboard gives me an alert that I must restart my server to apply the updates. I keep restarting and shutting down, and the message persists. I tried to delete the warning as well. My guess is that this warning is prohibiting the connector from working as it may think there are pending updates.

    The update you listed above was installed earlier today in a round of 231 updates installed. Updater shows no new updates available.


    • Edited by FittyFrank Thursday, April 28, 2016 3:13 AM
    Thursday, April 28, 2016 3:12 AM
  • It may be the client that needs updating/rebooted.  I would should down/restart the server again anyway.  It may still be installing updates if it just did 200

    Grey

    Thursday, April 28, 2016 10:26 AM
    Moderator
  • Here are the details of the Windowsupdate.log when installing the required update.

    without this update the client is missing the configuration wizard and the complete essentials folder under %windir%/system32

    2016.04.28 16:52:11.9952891 2880  2608  Handler         CBS called Initiate
    2016.04.28 16:52:12.0081634 2880  2608  Handler         CBS called Progress with state=2, ticks=10, total=1000
    2016.04.28 16:52:16.2558026 2880  2608  Handler         CBS called Progress with state=2, ticks=101, total=1000
    2016.04.28 16:52:16.2591786 2880  2608  Handler         CBS called Progress with state=2, ticks=111, total=1000
    2016.04.28 16:52:16.2638759 2880  2608  Handler         CBS called Progress with state=2, ticks=121, total=1000
    2016.04.28 16:52:16.2671247 2880  2608  Handler         CBS called Progress with state=2, ticks=131, total=1000
    2016.04.28 16:52:16.2712266 2880  2608  Handler         CBS called Progress with state=2, ticks=141, total=1000
    2016.04.28 16:52:16.4699028 2880  2608  Handler         CBS called Progress with state=4, ticks=205, total=1000
    2016.04.28 16:52:16.4706067 2880  2608  Handler         CBS called Progress with state=4, ticks=217, total=1000
    2016.04.28 16:52:16.4712892 2880  2608  Handler         CBS called Progress with state=4, ticks=229, total=1000
    2016.04.28 16:52:16.4720098 2880  2608  Handler         CBS called Progress with state=4, ticks=240, total=1000
    2016.04.28 16:52:16.4725929 2880  2608  Handler         CBS called Progress with state=4, ticks=252, total=1000
    2016.04.28 16:52:16.4731251 2880  2608  Handler         CBS called Progress with state=4, ticks=263, total=1000
    2016.04.28 16:52:16.4737479 2880  2608  Handler         CBS called Progress with state=4, ticks=275, total=1000
    2016.04.28 16:52:16.4743579 2880  2608  Handler         CBS called Progress with state=4, ticks=287, total=1000
    2016.04.28 16:52:16.4748848 2880  2608  Handler         CBS called Progress with state=4, ticks=298, total=1000
    2016.04.28 16:52:16.4753569 2880  2608  Handler         CBS called Progress with state=4, ticks=310, total=1000
    2016.04.28 16:52:16.4757257 2880  2608  Handler         CBS called Progress with state=4, ticks=322, total=1000
    2016.04.28 16:52:16.4760731 2880  2608  Handler         CBS called Progress with state=4, ticks=333, total=1000
    2016.04.28 16:52:16.4764145 2880  2608  Handler         CBS called Progress with state=4, ticks=345, total=1000
    2016.04.28 16:52:16.4767731 2880  2608  Handler         CBS called Progress with state=4, ticks=356, total=1000
    2016.04.28 16:52:16.4771312 2880  2608  Handler         CBS called Progress with state=4, ticks=368, total=1000
    2016.04.28 16:52:16.4774731 2880  2608  Handler         CBS called Progress with state=4, ticks=380, total=1000
    2016.04.28 16:52:16.4778166 2880  2608  Handler         CBS called Progress with state=4, ticks=391, total=1000
    2016.04.28 16:52:16.4781580 2880  2608  Handler         CBS called Progress with state=4, ticks=403, total=1000
    2016.04.28 16:52:16.4785181 2880  2608  Handler         CBS called Progress with state=4, ticks=415, total=1000
    2016.04.28 16:52:16.4788600 2880  2608  Handler         CBS called Progress with state=4, ticks=426, total=1000
    2016.04.28 16:52:16.4792211 2880  2608  Handler         CBS called Progress with state=4, ticks=438, total=1000
    2016.04.28 16:52:16.4796183 2880  2608  Handler         CBS called Progress with state=4, ticks=450, total=1000
    2016.04.28 16:52:16.5392699 2880  2608  Handler         CBS called Progress with state=4, ticks=463, total=1000
    2016.04.28 16:52:16.5399695 2880  2608  Handler         CBS called Progress with state=4, ticks=476, total=1000
    2016.04.28 16:52:16.5406270 2880  2608  Handler         CBS called Progress with state=4, ticks=490, total=1000
    2016.04.28 16:52:16.5412938 2880  2608  Handler         CBS called Progress with state=4, ticks=503, total=1000
    2016.04.28 16:52:16.5418412 2880  2608  Handler         CBS called Progress with state=4, ticks=517, total=1000
    2016.04.28 16:52:16.5423881 2880  2608  Handler         CBS called Progress with state=4, ticks=530, total=1000
    2016.04.28 16:52:16.5428959 2880  2608  Handler         CBS called Progress with state=4, ticks=544, total=1000
    2016.04.28 16:52:16.5434135 2880  2608  Handler         CBS called Progress with state=4, ticks=557, total=1000
    2016.04.28 16:52:16.5439555 2880  2608  Handler         CBS called Progress with state=4, ticks=571, total=1000
    2016.04.28 16:52:16.5444633 2880  2608  Handler         CBS called Progress with state=4, ticks=584, total=1000
    2016.04.28 16:52:16.5449726 2880  2608  Handler         CBS called Progress with state=4, ticks=598, total=1000
    2016.04.28 16:52:16.5454642 2880  2608  Handler         CBS called Progress with state=4, ticks=611, total=1000
    2016.04.28 16:52:16.5459955 2880  2608  Handler         CBS called Progress with state=4, ticks=625, total=1000
    2016.04.28 16:52:16.5465013 2880  2608  Handler         CBS called Progress with state=4, ticks=638, total=1000
    2016.04.28 16:52:16.5471461 2880  2608  Handler         CBS called Progress with state=4, ticks=652, total=1000
    2016.04.28 16:52:16.5476749 2880  2608  Handler         CBS called Progress with state=4, ticks=665, total=1000
    2016.04.28 16:52:16.5481812 2880  2608  Handler         CBS called Progress with state=4, ticks=679, total=1000
    2016.04.28 16:52:16.5486954 2880  2608  Handler         CBS called Progress with state=4, ticks=692, total=1000
    2016.04.28 16:52:16.5492257 2880  2608  Handler         CBS called Progress with state=4, ticks=706, total=1000
    2016.04.28 16:52:16.5498029 2880  2608  Handler         CBS called Progress with state=4, ticks=719, total=1000
    2016.04.28 16:52:16.5503357 2880  2608  Handler         CBS called Progress with state=4, ticks=733, total=1000
    2016.04.28 16:52:16.5544048 2880  2608  Handler         CBS called Progress with state=7, ticks=743, total=1000
    2016.04.28 16:52:16.8879365 2880  2608  Handler         CBS called Progress with state=7, ticks=768, total=1000
    2016.04.28 16:52:16.9024735 2880  2608  Handler         CBS called Progress with state=7, ticks=784, total=1000
    2016.04.28 16:52:16.9229446 2880  2608  Handler         CBS called Progress with state=7, ticks=800, total=1000
    2016.04.28 16:52:16.9281820 2880  2608  Handler         CBS called Progress with state=7, ticks=816, total=1000
    2016.04.28 16:52:16.9899641 2880  2608  Handler         CBS called Progress with state=7, ticks=832, total=1000
    2016.04.28 16:52:17.1459923 2880  2608  Handler         CBS called Progress with state=7, ticks=842, total=1000
    2016.04.28 16:52:17.2159685 2880  2608  Handler         CBS called Progress with state=7, ticks=852, total=1000
    2016.04.28 16:52:17.2785128 2880  2608  Handler         CBS called Progress with state=7, ticks=862, total=1000
    2016.04.28 16:52:17.3125793 2880  2608  Handler         CBS called Progress with state=7, ticks=872, total=1000
    2016.04.28 16:52:17.3407019 2880  2608  Handler         CBS called Progress with state=7, ticks=882, total=1000
    2016.04.28 16:52:17.3662827 2880  2608  Handler         CBS called Progress with state=7, ticks=892, total=1000
    2016.04.28 16:52:17.3898275 2880  2608  Handler         CBS called Progress with state=7, ticks=902, total=1000
    2016.04.28 16:52:18.2248475 2880  2608  Handler         CBS called Progress with state=7, ticks=927, total=1000
    2016.04.28 16:52:18.4556387 2880  2608  Handler         CBS called Progress with state=7, ticks=937, total=1000
    2016.04.28 16:52:18.5359400 2880  2608  Handler         CBS called Progress with state=7, ticks=947, total=1000
    2016.04.28 16:52:18.6109623 2880  2608  Handler         CBS called Progress with state=7, ticks=957, total=1000
    2016.04.28 16:52:18.6996382 2880  2608  Handler         CBS called Progress with state=7, ticks=967, total=1000
    2016.04.28 16:52:23.8767753 2880  2608  Handler         CBS called Progress with state=7, ticks=970, total=1000
    2016.04.28 16:52:24.1110115 2880  2608  Handler         CBS called Progress with state=7, ticks=980, total=1000
    2016.04.28 16:52:24.4080932 2880  2608  Handler         CBS called Progress with state=7, ticks=990, total=1000
    2016.04.28 16:52:26.5107412 2880  2608  Handler         CBS called Progress with state=7, ticks=990, total=1000
    2016.04.28 16:52:26.8908223 2880  2608  Handler         CBS called Error with 0x800f0922, <NULL>
    2016.04.28 16:52:26.8909710 2880  2608  Handler         CBS called Progress with state=7, ticks=1000, total=1000
    2016.04.28 16:52:26.8920922 2880  2608  Handler         CBS called Terminate
    2016.04.28 16:52:27.2471130 2880  8672  Handler         Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x800f0922
    2016.04.28 16:52:27.2855749 2880  8672  Handler         * END *   CBS Install
    2016.04.28 16:52:27.2929555 652   1108  Handler         Loaded state: cCompleteIterations: 1, pt: SelfContainedNoExpressPayload, nNextRequestID: 1.
    2016.04.28 16:52:27.3108793 652   1108  Agent           LogHistory called. idUpdate={37EADE32-ADE2-4764-B7CC-6066D2B9EAC0}.501, resultMapped=800F0922, resultUnMapped=800F0922
    2016.04.28 16:52:27.3173690 652   1108  Agent           Installing updates CallerId = wusa
    2016.04.28 16:52:27.3175060 1248  8596  ComApi           Install ClientId = wusa
    2016.04.28 16:52:27.3175084 1248  8596  ComApi          Install call complete (succeeded = 0, succeeded with errors = 0, failed = 1, unaccounted = 0
    2016.04.28 16:52:27.3175755 1248  8596  ComApi          Reboot required = False
    2016.04.28 16:52:27.3175764 1248  8596  ComApi          Exit code = 0x00000000; Call error code = 0x80240022
    2016.04.28 16:52:27.3175769 1248  8596  ComApi          * END *   Install ClientId = wusa
    2016.04.28 16:52:27.3176273 652   9200  Agent           WU client calls back to install call {E8E4D4C6-D323-4D99-8384-E91ACDB064B2} with code Call complete and error 0
    2016.04.28 16:52:28.0706353 1248  9088  ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C

    Thursday, April 28, 2016 3:17 PM
  • When using the connectorsoftware https://servername/connect the error is the same.

    Eventlog says "Installationsfehler: Die Installation des folgenden Updates ist mit Fehler 0x800F0922 fehlgeschlagen: Update für Windows (KB2790621)"

    Thursday, April 28, 2016 3:34 PM
  • Can you go into iis admin and make sure that the wss cert site is started

    Grey

    Thursday, April 28, 2016 6:44 PM
    Moderator
  • Yes, WSS Certificate Web Service is started. Still doesn't work...
    Thursday, April 28, 2016 10:37 PM
  • I just got it work. Solution is found here: https://blogs.technet.microsoft.com/sbs/2015/11/17/client-connector-availability-with-windows-home-server-small-business-server-and-windows-server-essentials-for-supported-client-os/

    You have to download the connector manually for Windows 10. Download links will be found under " Resolution (Updated on 29/07/2015):" There will be a download x64 and x86 bit Windows 10 clients.

    Friday, April 29, 2016 12:13 AM
  • Well if you read farther down it says if your server has all the windows updates applied you do not need to manually down load a connector

    Update (21/10/2015):

    - There will be a Windows Update released on 17th,November 2015 for Windows Server 2012 R2 Essentials.

    - This Windows Update will enable the Windows 10 clients to be joined to the Windows Server 2012 R2 Essentials. In current scenario, the user has to download and install the client connector   manually on the Windows 10 client, this manual process would not be required after applying this Windows Update to the Server.

    - This Windows Update will not affect any of the existing Windows 10 clients connected to the Windows Server 2012 R2 Essentials.


    Grey

    Friday, April 29, 2016 12:20 AM
    Moderator
  • I think you misunderstood me. It's a 100% client update problem.

    The Server works fine, other clients show correctly in the essential dashboard.

    Only the kb2790621 patch which is a prereq for the client connector software cant be installed on a specific client.

    So do you have any idea what prereqs or dependencies the patch has ?

    the exit code is 0x800f0922

    Friday, April 29, 2016 7:41 AM
  • yes the prereqs for kb2790621  are listed in the details on the download page.

    System Requirements
    Supported Operating System

                        Windows Server 2012 R2                

                          Windows Server Essentials Connector is designed to be installed on Windows 7 Service Pack 1 (SP1), Windows 8, Windows 8.1, and Mac OS X 10.6 -10.8.

      .

    The connector you got to work was an interim fix.  It is no longer required.  You need to make sure https://support.microsoft.com/en-us/kb/3105885 is installed on the server which is offered in Windows updates.

    About this update
    This update enables the Windows 10 clients to be joined to the Windows Server 2012 R2 Essentials. Currently, you have to download and install the client connector manually on the Windows 10 client. This manual process will not be required after you apply this update to Windows Server 2012 R2.

    I notice you are not installed in English.  If your server does have 3105885 installed perhaps there is a bug in your language?


    Grey

    Friday, April 29, 2016 10:43 AM
    Moderator
  • Sorry the patch you mentioned is already applied on the server.

    The interim fix is the same its nowadays just included inside the connector "software".

    because when i check the eventlog the problem while the connector software skips installation is the same.

    KB2790621 failed with error 0x800F0922

    so any idea how to fix that specific update problem ? any registry prereqs for that patch ?

    i already reset the software distribution cache on the client and run sfc scan.

    Other windows 10 updates works fine.

    Friday, April 29, 2016 11:01 AM
  • ITEvolution - Have you had any luck resolving this problem?  I've got the same issue. 

    Bottom line is that Windows 10 Pro won't install the Windows Server Essentials Connector available from:

    • Servername/connect result is error window that "Package installation did not succeed" and a number of Event ID 1001 are generated.  (The Windows Server 2012 R2 Essentials is up-to-date, including KB3105885 installed 11/19/2015.)

    • Standalone Windows10.0-KB2790621-x64.msu fails with window stating it was not installed. WindowsUpdate.log says CBS called Error with 0x800f0922 (looks like your log posted Apr 28).  BTW, even though KB3105885 on the server is supposed to make the server-supplied connector software work, I haven't seen any advice to not use KB2790621, and it has worked well on all my other Win 10 Pro clients.

    Background: I upgraded the last of six Windows 7 & 8.1 computers to Windows 10 Pro last week, and it is the only one that I haven't been able to install the WSE 2012R2 Connector in.  I've had all six computers connected to this server for years with no problem when the clients were Win 7 & 8.1, and now five of them running Win 10 Pro are connected with no issue.  

    Action to date:

    • I learned that Error 800f0922 can mean that there's not enough room on the System Reserved partition. Although the problem computer doesn't have a System Reserved partition like most of my other computers, I do have another laptop that upgraded from Windows 7 Ultimate to Windows 10 Pro and connected okay to the server -- it doesn't have a System Reserved partition either. But just in case, I restored Windows 8.1 Pro to the problem computer and used EasyBCD to create a 100MB System Partion like the other computers and move the boot files accordingly.  Then I upgraded again to Windows 10 Pro.  Same issue. 

    • Thinking that maybe the newest Windows 10 Pro upgrade (Build 10586.318) had introduced a problem, I restored Win 8.1 again and re-upgraded with the Nov 2015 version of Win 10 Pro.  Same issue, so I again went through all the steps to get back to the latest Windows 10 Pro.

    I know this thread stalled at the end of April, but maybe this post will reactivate it.  Otherwise, I'll post elsewhere.  The standalone WSE Connector for Windows 10 clients, KB2790621, is not working as advertised and intended for some Windows 10 computers.  This is a real problem in need of a solution.




    Monday, June 06, 2016 7:50 AM
  • Is windows update working on the problem PC?  /connect actually goes online to fetch it.

    for giggles try the fixit https://support.microsoft.com/en-us/kb/971058


    Grey

    Monday, June 06, 2016 11:06 AM
    Moderator
  • Is windows update working on the problem PC?  /connect actually goes online to fetch it.

    for giggles try the fixit https://support.microsoft.com/en-us/kb/971058


    Grey

    Thanks for the question and tool tip. Yes, Windows Update is working - see screenshot. (I don't think the standalone installer for KB2790621 goes online, though, does it?)

    I tried the fixit WindowsUpdateDiagnostic.diagcab, KB971058 that you suggested, and it said it found and fixed one problem.  However, no dice: Both the standalone and server provided connector installations failed afterward.

    Monday, June 06, 2016 4:36 PM

  • Moderator, I have the same problem. I had various machines running 7 and 8.1 all happily backing up to Window Server 2012 R2 Essentials. I had installed Windows10.0-KB2790621-x64.msu when I had issues restoring from Windows Server. I've since upgraded 5 of these machines to Windows 10, installed Windows10.0-KB2790621-x64.msu and they've all been humming along. These were all upgraded several months ago. Today, I try to upgrade my last windows 7 machine (which was backing up perfectly well) to Windows 10. Windows Connector was of course obliterated by the upgrade, so  I ran Windows10.0-KB2790621-x64.msu and was mildly stunned when it failed with a 0x800F0922. I followed up and performed what various sources reported as the solution to the issue, enlarging the system reserved partition. Absolutely no help. I can only conclude that since this update worked on several other systems upgraded to Windows 10 at earlier dates, some update to Windows 10 in the last few months is the culprit.
    Thursday, June 09, 2016 5:16 AM
  • In all of these cases, have the Windows 10 machines been upgrades from Windows 7?

    Any fresh installs of Windows 10 failing? / Upgrades from Windows 8?


    Robert Pearman Cloud & Datacentre MVP
    @titlerequired | LinkedIn | Google+
    Facebook | Windows Server Essentials.com

    Thursday, June 09, 2016 8:52 AM
    Moderator
  • In all of these cases, have the Windows 10 machines been upgrades from Windows 7?

    Any fresh installs of Windows 10 failing? / Upgrades from Windows 8?


    Robert Pearman Cloud & Datacentre MVP
    @titlerequired | LinkedIn | Google+
    Facebook | Windows Server Essentials.com

    My problem occurred after upgrading from Windows 8.1 Pro to Windows 10 Pro, as described above. I have upgraded other machines to 10 from 8.1 and directly from 7 with no problem.
    Thursday, June 09, 2016 9:38 AM
  •  I can only conclude that since this update worked on several other systems upgraded to Windows 10 at earlier dates, some update to Windows 10 in the last few months is the culprit.
    Paget Hite, see my first post above: I went back to the Nov 15 Windows 10 version and still had the same issue. What I haven't tried yet is a clean install, but that will mean a lot more work reconstructing my HTPC (which was my last holdout because of the loss of WMC in Windows 7, but now MDL has a viable WMC for 10).
    Thursday, June 09, 2016 9:50 AM
  • Mick,

    Sorry I got an email with your post but it did not have the pics and I did not look online.  I will try to find out.  You would think if it failed to download from windows updates manually downloading would work, but I am not sure they are the same package.

    The download is dated before the "fix"  https://blogs.technet.microsoft.com/sbs/2015/11/17/client-connector-availability-with-windows-home-server-small-business-server-and-windows-server-essentials-for-supported-client-os/

    Look in all programs windows server essentials  on the win 10 box and see if you have the program WSE Configuration.  If so run that and see what happens


    Grey

    Thursday, June 09, 2016 11:08 AM
    Moderator
  • In all of these cases, have the Windows 10 machines been upgrades from Windows 7?

    Any fresh installs of Windows 10 failing? / Upgrades from Windows 8?


    Robert Pearman Cloud & Datacentre MVP

    I went back and checked.  All my other machines were upgrades from Windows 8.1 (which had been upgraded from 7). Only the most recent upgrade from Windows 7 Pro to Windows 10 Pro had issues with the Windows10.0-KB2790621-x64.msu update. So in my case, the answer is yes.
    Thursday, June 09, 2016 3:28 PM
  • Look in all programs windows server essentials  on the win 10 box and see if you have the program WSE Configuration.  If so run that and see what happens


    Grey

    I don't have any WSE programs listed in All Programs and none in Programs and Features.
    Thursday, June 09, 2016 8:31 PM
  • Can you look and make sure this update is installed on the server?

    https://support.microsoft.com/en-us/kb/3105885

    You do not have any 3rd party AV or proxy running do you?


    Grey

    Thursday, June 09, 2016 9:27 PM
    Moderator
  • Yes, I have KB3105885 installed and there is NO 3rd party AV or proxy running on the machine.
    Thursday, June 09, 2016 9:57 PM
  • Welp, dats all I got.  I don't have one to duplicate it.  Prob have to run process monitor to see why it is failing


    Grey

    Thursday, June 09, 2016 10:12 PM
    Moderator
  • Can you look and make sure this update is installed on the server?

    https://support.microsoft.com/en-us/kb/3105885

    You do not have any 3rd party AV or proxy running do you?


    Grey

    My server does have kb3105885. On the Win 10 client, I've got Norton Security Suite (Norton 360).  I'll turn it off and give kb2790621 a whirl. However, Norton wasn't a problem on any other machines I updated to Win 10 and connected to the server.
    Thursday, June 09, 2016 10:35 PM
  • Nope, turning off Norton AV didn't help.
    Thursday, June 09, 2016 11:27 PM
  • When Norton is the problem disabling does not help.  It has to be uninstalled.  No clue if it is worth your effort to try that.

    You should be using servername/connect not the download

    If that does not work you might try this approach:

     Resolution (Updated on 29/07/2015):

    The Client Connector for Windows 10 to connect to Windows Server 2012 R2 Essentials has been released. 

    For x64 bit Windows 10 Client download it from here.

    For x86 bit Windows 10 Client download it form here.

    Note:

    The Client Connector needs to be manually downloaded and installed on the Windows 10 Client OS. Once the installation is completed follow the steps listed below,

                – Click on Start, All Apps

                – Scroll down till “Windows Server Essentials”, expand and run “Windows Server Essentials Connector Configuration Wizard”.

    This is a known issue and the fix on the server is being targeted to be released tentatively in October 2015.

    Once the fix is patched, then there will be no user intervention required, all the downloading, installation and configuration will be automatically carried out


    Grey

    Thursday, June 09, 2016 11:48 PM
    Moderator
  • Thanks for the Norton info. I think I'd just be spinning my wheels to uninstall it, given it's been no problem for any of my other computers when upgrading to Win 10.  Note that the "Resolution (updated on 29/07/2015)" is actually and simply the download, Windows10.0-KB2790621-x64.msu (or the 32-bit version as appropriate).

    I think I'll try a clean install and find out if my issue is hardware based. (Not likely, since it's the same motherboard as two other computers that had no problem.)  The beauty of WSE 2012 R2 is that I can easily restore 8.1. But similarly, it's unacceptable not to be able to connect a Win 10 machine to WSE for backup, restore, and other features.


    Friday, June 10, 2016 12:24 AM
  • well for giggles if you are going to wipe and reload you might go ahead uninstall Norton>reboot> and try server/connect

    I suppose sfc /scannow could not hurt either


    Grey

    Friday, June 10, 2016 12:27 AM
    Moderator
  • well for giggles if you are going to wipe and reload you might go ahead uninstall Norton>reboot> and try server/connect

    I suppose sfc /scannow could not hurt either


    Grey

    True. Okay, I will give the Norton uninstall a shot first.  But, BTW, I've used SFC early on which found no problems with the files. There seem to be few answers out there for the apparently unique situation that ITEvolution, Page Hite, and I have.
    Friday, June 10, 2016 12:37 AM
  • Dunno, I just connected a win 10 that had done a win10 update and it did fine an says KB2790621 installed in windows updates.

    clean out program files \windows server

    windows\system32\essentials

    registry

    windows\temp\clientdeploymentfiles

    or just say done, wipe and reload :)


    Grey

    Friday, June 10, 2016 12:59 AM
    Moderator
  • Dunno, I just connected a win 10 that had done a win10 update and it did fine an says KB2790621 installed in windows updates.

    clean out program files \windows server

    windows\system32\essentials

    registry

    windows\temp\clientdeploymentfiles

    or just say done, wipe and reload :)

    Update from 7 or 8?  Did the PC already have Network Connector before the upgrade?

    When you say registry, do you mean clean the registry with something like CCleaner?

    And you're doing all this after the Win 10 update but before KB2790621 update?

    Inquiring minds need to know.

    Friday, June 10, 2016 2:07 AM
  • No to CC Cleaner.  I meant dig to the essentials stuff

    hklm\software\Microsoft\windows server

    servername/connect installs kb2790621 It was a win10 update from 10xxx to 14361

    the upgrade removes the previous connector and it has to be reinstalled


    Grey

    Friday, June 10, 2016 3:14 AM
    Moderator
  • Mick, is your upgrade from 7 to 10 or from 8 to 10? Grey described steps he used, but he was only going from one level of 10 to another. MY confidence level is extremely low at this point.

    Friday, June 10, 2016 6:41 AM
  • My problem PC that won't connect to WSE is an upgrade to Win 10 Pro from 8.1 Pro. But I've got other computers from both 7 and 8.1 That I upgraded to 10 without that issue. You're right, Grey installed the latest Insider build which is major enough to wipe out the WSE connection, similar to the Nov 2015 update.

    You know, this really is a Windows 10 issue, since the connector - even standalone - won't install on the Win 10 client, rather than a Server issue. So there could be better answers if posted in another MS forum than this one for the Server.  However, Google does search bring posts from many sources together, so maybe it doesn't matter.

    I did uninstall my AV program, Norton, just to see, and installation of the connector still fails. (I know 3rd party AV isn't part of your problem). Currently, I'm taking inventory of installed programs before doing a clean install.

    Friday, June 10, 2016 7:14 AM

  • I did uninstall my AV program, Norton, just to see, and installation of the connector still fails. (I know 3rd party AV isn't part of your problem). Currently, I'm taking inventory of installed programs before doing a clean install.

    Any luck? Or did you just scrape down to bare metal and reinstall?
    Tuesday, June 14, 2016 7:38 PM

  • I did uninstall my AV program, Norton, just to see, and installation of the connector still fails. (I know 3rd party AV isn't part of your problem). Currently, I'm taking inventory of installed programs before doing a clean install.

    Any luck? Or did you just scrape down to bare metal and reinstall?

    Page,

    Yeah, I gave up on the upgrade. I couldn't resolve the connector issue.  Apparently, my existing HTPC Win XP Media Center . . . to Win 7 . . . to Win 8.1 was carrying too much baggage which then put it into our 1% WSE connector failure issue.  So I wound up deleting all partitions and installing Win 7 Ultimate SP1 and upgrading to 10 Pro from there. Multiple times, in fact, until I had it the way I wanted. WSE 2012 R2 connector installed and worked fine with a clean install or a "clean" upgrade. But it's unfortunately a PITA to reinstall all the programs I want.

    The reason I installed 7 and upgraded to 10 multiple times was because I wasn't getting the Windows DVD Player with 10,  and I wanted the partitioning to fit current MS concept (350MB system reserved). Also, I ran into the error, "We couldn't create a new partition or locate an existing one," when installing Win 7 fresh. To solve that error, I unplugged my external USB drive and, in my BIOS, removed references to anything but my primary HDD in the boot order. It's possible that might have been a cause of the original connector problem, subject of this thread. However, I didn't have a problem connecting to the server when I upgraded from 7 to 8.1 a couple months ago with the same BIOS config and the USB drive plugged in.

    Extraneous to the original subject here are a few unsolicited tips on installing 10 clean or upgrade through a clean installation of 7:

    1. Even though it will be digitally activated, you won't get the free Windows DVD Player with a clean install because the Windows 10 setup program won't see any WMC being upgraded from. (Regardless of whether people think the Win DVD Player app is any good or the fact that you can buy it for $20, I want to get it as offered for free when upgrading from a version of Win with WMC.)

    2. You won't get the DVD Player with your 10 upgrade unless you take the time after installing 7 to actually run WMC the first time. Otherwise, it's as if Win 7 didn't even have WMC.

    3. You won't get a System Reserved partition unless you delete all the partitions and install 7 into unallocated space. Win 7 will then make a 100MB system reserved partition. You can enlarge that to 350MB using EaseUS Partition Master or another tool before the Win 10 upgrade.


    Tuesday, June 14, 2016 11:25 PM
  • 3. You won't get a System Reserved partition unless you delete all the partitions and install 7 into unallocated space. Win 7 will then make a 100MB system reserved partition. You can enlarge that to 350MB using EaseUS Partition Master or another tool before the Win 10 upgrade.
    Hmm, that brings up an interesting thought. After my initial upgrade from W7 to W10, when I attempted to install the connector, I got the 0x800f0922. The message was related to a lack of space in the system reserved partition, so I enlarged mine but continued to get the error. I've now gone back to W7. I wonder if somehow W10 didn't recognize the additional space in the expanded partition. Since I've gone back to 7 and the enlarged partition is still there, I wonder if it would be worth trying the upgrade to 10 to attempt the connector install again.

    • Edited by Page Hite Wednesday, June 15, 2016 12:20 AM
    Wednesday, June 15, 2016 12:19 AM
  • I know exactly what you mean. Originally, my problem PC had no System Reserved partition (which, BTW, the latest Windows versions seemed to have wanted to shorten the name to just "System") so I went through the motions to make one and use EasyBCD 2.3 to transfer the boot files to (I went back to 8.1 then upgraded again to 10). That didn't work -- WSE connector still failed to install. Plus, I looked at all my computers that I'd moved to 10, and two of them had no system reserved partition but were successfully connected to WSE.

    I think it has to be some complex interference involving long-term installation of the version being upgraded -- the "baggage." Am I right to suppose your 7 has been around the block with lots of programs installed? If you've got it backed up well to WSE (or an Acronis or other image), then you can experiment at will and always get back to where you are easily (especially with a NIC boot into WSE full restore). I bet you'll find, like I did, that a clean install of 10 or clean install of 7 then upgrade to 10 will bypass the WSE connector issue. Of course, the other problems introduced are loss of your entire comfortable Windows environment of existing programs and, in the case of clean install of 7 or 8.1, license keys (or potential phone MS complications) to activate in order to get the valid 10 upgrade.


    Wednesday, June 15, 2016 3:41 AM
  • I wasn't real happy with PCMover when I used it in the past, but the thing I remember about it was that basically it backed up applications and data then restored them into the new Windows version. Therefore, if you're going to do that, you can save to another drive now, take advantage of the free upgrade (doing a clean install, because MS has her machine digitally licensed from the previous upgrade), and restore via PCMover now rather than with a new machine. Data is no problem anyway - it's easily transferred system to system.

    Wednesday, June 15, 2016 5:01 AM
  • I wasn't real happy with PCMover when I used it in the past, but the thing I remember about it was that basically it backed up applications and data then restored them into the new Windows version. Therefore, if you're going to do that, you can save to another drive now, take advantage of the free upgrade (doing a clean install, because MS has her machine digitally licensed from the previous upgrade), and restore via PCMover now rather than with a new machine. Data is no problem anyway - it's easily transferred system to system.


    I used it not long ago. It moved everything over in real time from one machine to another) and got about 90% of the apps. MY beef is that you get one try and if it doesn't work, you're screwed. I had to call them and complain to get another license key.
    Wednesday, June 15, 2016 5:06 AM
  • Not sure how my last reply got posted ahead of yours.
    Wednesday, June 15, 2016 5:11 AM
  • Not sure how my last reply got posted ahead of yours.

    I tried to delete one of my entries, so it probably bolluxed up the works.
    Wednesday, June 15, 2016 5:40 AM
  • I wasn't real happy with PCMover when I used it in the past, but the thing I remember about it was that basically it backed up applications and data then restored them into the new Windows version. Therefore, if you're going to do that, you can save to another drive now, take advantage of the free upgrade (doing a clean install, because MS has her machine digitally licensed from the previous upgrade), and restore via PCMover now rather than with a new machine. Data is no problem anyway - it's easily transferred system to system.


    I used it not long ago. It moved everything over in real time from one machine to another) and got about 90% of the apps. MY beef is that you get one try and if it doesn't work, you're screwed. I had to call them and complain to get another license key.
    There's a version that lets you save an image then restore it to a new pc - other than real time. Still one shot unless you want to pay a lot more for multi-use.
    Wednesday, June 15, 2016 5:54 AM
  • There's a version that lets you save an image then restore it to a new pc - other than real time. Still one shot unless you want to pay a lot more for multi-use.
    I wasn't aware of that. I'll have to check it out. The only issue would be that much of the data is dynamic, so I would have to move pretty quickly. But I do like the sound of that. Thanks for the info.
    Wednesday, June 15, 2016 6:23 AM
  • There's a version that lets you save an image then restore it to a new pc - other than real time. Still one shot unless you want to pay a lot more for multi-use.

     I did a little research and now PCMover will only go from one machine to another in realtime.  Todo PC Trans will let you use a image as you described.

    Wednesday, June 15, 2016 6:43 AM
  • Well, guess what? Just did the W10 anniversary update and it killed a working connector and now fails on the install as described on all the various post above. My disgust know no bounds.

    Wednesday, August 10, 2016 5:01 AM
  • As I understand, the major Win 10 updates wipe out the connector. The same thing happened with the update to version 1511. I'm in the midst of updating my clients to 1607 also.  http://servername/connect "worked" on the first one to reinstall the connector software for me so far.  But after finding and signing into the server and saying the computer name already exists and do I want to connect anyway, it informs me that I need to restart in order to connect.  Then on restart, I get a freeze before the logon screen.  No more time tonight, but I see others are having problems too:  http://homeservershow.com/forums/index.php?/topic/11492-windows-10-anniversary-update-and-the-connector/

    Wednesday, August 10, 2016 7:04 AM
  • Eve Wang

    Tried to install KB 3105885 but it reported that not applicable to my system.  Running Server 2012 R2 Essentials. Cannot connect Windows 10 Pro computer via the connector from my http:/server name/connect.

    Suggestions    Updates are current.

    Thanks,

    Bill Funk

    Friday, February 03, 2017 4:04 PM
  • Eve,

    I have 4 clients running Windows 10 Pro 64bit connected to Windows Server 2012 R2 with all of the latest updates including KB3105885.  Every time there is a Windows 10 feature update one of the clients does not automatically connect to the server.  The other clients are fine.

    To solve the problem I run xxserver/connect on the problem client and it then connects to the server until the next feature update.

    Any idea as to what might be the problem on the one client?

    John Poindexter

    Saturday, August 12, 2017 3:40 PM
  • Hi,

    More information is necessary in order to have an further identification, such as:
    1. Error message.
    2. Relate event in Event Viewer.
    3. Relate log files on client, such as ClientDeploy.log and ComputerConnector.log - %programdata%\Microsoft\Windows Server\logs.

    In general, one thread focuses on one problem for specific customer, as environment and confirmation are different. Also, in order to obtain more suggestion from other Essentials professional, I would recommend you to post a new thread on this forum, provide more detail information such as I had mentioned above.

    Thank you for your understanding.

    Best Regards,
    Eve Wang

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

    Monday, August 14, 2017 2:05 AM
    Moderator