Skip to content

Konstantinos Tsoukalas

Konstantinos is the founder and administrator of Since 1995 he works and provides IT support as a computer and network expert to individuals and large companies. He is specialized in solving problems related to Windows or other Microsoft products (Windows Server, Office, Microsoft 365, etc.).


  1. Duke
    September 11, 2023 @ 4:17 pm

    Thanks a million! This worked on a 2022 RDS Session based deployment.


  2. Jose Balani
    October 27, 2021 @ 4:17 am

    Please, include the "Remote Registry" enabled and started to work fine.


  3. Troy
    September 23, 2021 @ 6:03 pm

    This worked on a Server 2019 system where WSUS would not install, due to the missing WID role. Was not ever able to add NT SERVICE\ALL SERVICES, but all other accounts were able to add and resolved my issue – thank you!


  4. Andres V
    March 4, 2021 @ 7:57 am

    Awesome, fixed it!


  5. Matthew
    May 8, 2020 @ 4:37 am

    This fix worked for me! Thanks for the help!


  6. Sean John
    October 2, 2019 @ 9:29 pm

    Thank you! Exactly what I needed afted applying DISA STIG's to my SCCM server.


  7. Karthi
    September 11, 2019 @ 3:38 pm

    Hi just restart your remote registry service. It should be work


  8. Dave
    January 31, 2019 @ 6:16 pm

    This fix worked perfectly for my 2016 server. Thanks!


  9. Kiran
    October 29, 2018 @ 7:46 pm

    Still i am getting same error after doing all the configurations as detailed above article. can you suggest any other plan


    • lakonst
      October 30, 2018 @ 10:38 am

      @Kiran: Unfortunately I cannot suggest another workaround to fix this issue. Have you successfully added the mentioned "NT SERVICE" accounts in 'Logon as Service' properties?


    • Usman Ghani
      November 10, 2019 @ 5:59 am

      @Kiran, Please try to start the remote registry service.


Leave a Reply

Your email address will not be published. Required fields are marked *