locked
Windows 10 build 2004 can't connect to a Failover cluster in Windows 2012 R2 RRS feed

  • Question

  • Hello,

    A user from the Russian version of the TechNet forum wrote that after updating Windows 10 to 2004, he cannot connect to a Failover cluster in Windows 2012 R2.

    He received the following error message:

    The cluster to which you are attempting to connect is not a version of the cluster supported by this version of Failover Cluster Manager.

    Has anyone encountered the aforementioned issue or have any information about this?

    Avis de non-responsabilité:
    Mon opinion ne peut pas coïncider avec la position officielle de Microsoft.

    Bien cordialement, Andrei ...

    MCP

    Tuesday, June 2, 2020 8:56 PM

All replies

  • Yes, having the same issue trying to connect to a 2016 based failover cluster after installing 2004 update.
    • Edited by cafdad Tuesday, June 2, 2020 9:05 PM
    Tuesday, June 2, 2020 9:05 PM
  • Same here. 2016 clusters, win 10 2004.
    Tuesday, June 2, 2020 9:25 PM
  • Hi,

    It looks like Win10 2004 does not support server 2016 failover clusters and below,You can try rolling back to Win10 1909 or upgrading the cluster to windows server 2019.

    Best Regards,

    Daniel


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

    Wednesday, June 3, 2020 9:26 AM
  • Hi Danie1zhou,

    Thanks for details.

    Could you please tell me if you have a link to this information, (like FAQ), I would like to send this information to users as the most commonly-encountered problems after upgrading to the 2004 version so that there are no more disappointed users, i.e. . give them a choice before installing this update.

    Avis de non-responsabilité:
    Mon opinion ne peut pas coïncider avec la position officielle de Microsoft.

    Bien cordialement, Andrei ...

    MCP

    • Edited by SQx Wednesday, June 3, 2020 1:47 PM updated
    Wednesday, June 3, 2020 1:32 PM
  • I hope that isn't Microsoft's official stand on this.  I could understand if we were beyond the normal lifecycle for Server 2016 but we aren't even close.
    Wednesday, June 3, 2020 4:58 PM
  • I would like to know Microsoft's official stance on this.
    Wednesday, June 3, 2020 5:00 PM
  • I would like to know Microsoft's official stance on this.

    And I need too :(

    From Hyper-V Manger in MMC console I can connect to HV nodes, but not connect to Failover Cluster...

    • Edited by SlalomJohn Thursday, June 4, 2020 4:18 PM
    Thursday, June 4, 2020 4:17 PM
  • same issue.
    Friday, June 5, 2020 3:45 PM
  • Same issue, any work arounds yet?
    Thursday, June 11, 2020 12:45 PM
  • Same issue here with Windows 10 2004 and Windows Server 2012 R2 cluser.
    Tuesday, June 16, 2020 4:12 PM
  • At 05 jul - no update, not fix, not work...

    It's amazing!

    M$ - forever stop all work!

    Sunday, July 5, 2020 8:03 AM
  • We have the same issue with Win 10 2004 for server 2012 R2 cluster, which is still a supported server version.
    Thursday, July 16, 2020 9:22 PM
  • Already update Win 10 2004 to latest updates, but still cannot connect to windows server 2016's cluster.

    Hope Microsoft Teams could fix this issue soon.

    Friday, July 24, 2020 3:56 AM
  • WFT?!

    unbelievable... same problem here...


    Dario Palermo

    Monday, July 27, 2020 12:47 PM
  • There is an easy fix for this problem.

    Copy the "C:\Windows\Cluster\FailoverClusters.ObjectModel.dll" from a 1909 or earlier to your PC and it wil work again! You have to be the owner of the file, otherwise you can't overwrite it :)

    Tested on 2004 and 2009
    • Proposed as answer by matze19999 Tuesday, July 28, 2020 1:46 PM
    • Edited by matze19999 Tuesday, July 28, 2020 1:47 PM
    Tuesday, July 28, 2020 1:46 PM