5 Replies Latest reply on Aug 31, 2017 10:15 AM by cwinning

    Protect not starting remote registry in Server 2016/Win 10 with default of Automatic (Trigger Start)

    Keschnei42 Rookie

      Is anyone else finding that Protect fails with Windows 10/Server 2016 because of remote registry not starting when configured with the default of Automatic (Trigger Start)?  If we start the service manually it works.


      We are on build 9.3.0 4440.