ITT

Itechtics staff is a team of technology experts led by Usman Khurshid. We verify everything we write so that our users can be sure to trust us in everything we write. You can reach out to us for further help and support.

29 Comments

  1. Thomas
    March 13, 2021 @ 9:49 PM

    Help!

    Like others, a recent update has removed rdp listening.
    (can no longer connect from a remote machine)

    Tom

    Reply

    • Luke
      April 11, 2021 @ 8:56 PM

      I would like to second this help request.

      The ‘Remote Desktop’ feature on System Properties is gone and the RDP Wrapper Configuration displays ‘Not Listening’.

      Reply

  2. Corky
    February 27, 2021 @ 11:31 AM

    Error with the installer. Won’t install. i don’t know why.. still says can’t use rdc. Event viewer is unhelpful.

    Reply

  3. Laura
    February 23, 2021 @ 3:14 AM

    I found the fix!
    After 11 months of using the “Remote Desktop Connection” feature, a recent security update left this feature blocked with a prompt to upgrade to Windows Pro for a cool $99.

    I went to the Microsoft App Store, downloaded “Microsoft Remote Desktop” (orange >< logo)
    https://www.microsoft.com/en-us/p/microsoft-remote-desktop/9wzdncrfj3ps?activetab=pivot:overviewtab

    installed the app, added my PC (had to make sure my VPN was connected first).

    VIOLA!!! I have my remote connectivity back!

    Reply

  4. Alex Tafarrodi
    October 31, 2020 @ 12:54 AM

    I wasn’t able to even open the 1.62 MSI file: https://github.com/stascorp/rdpwrap/releases/tag/v1.6.2
    It says “could not open the file. contact vendor to make sure it’s a valid installation package”
    Win 10 does not give me the option of opening as administrator.
    Tried the zip file: https://github.com/stascorp/rdpwrap/releases/download/v1.6.2/RDPWrap-v1.6.2.zip
    and error says: “the archive is either in unknow format or damaged”
    Same error for zip file for version 1.6.1

    Reply

    • Usman Khurshid
      October 31, 2020 @ 5:45 AM

      Please run the MSI file instead of opening and extracting it. I can confirm that the MSI file runs on my computer.

      Reply

  5. RCP
    August 11, 2020 @ 7:15 PM

    Win10 Home 19041.388 not “listening” says [not supported]

    Reply

  6. Mike
    August 2, 2020 @ 11:13 PM

    I have 2 Lenovo laptops that I was able to log into remotely from my phone.
    Both have windows 10 home. I can no longer log into 1 of them. It shows offline and last seen online may 3, 2020.
    the other laptop is rarely used. I turned it on last week and I can log into it.
    Is there some bug or update that caused this?

    Reply

  7. Jon Biddell
    July 28, 2020 @ 3:06 AM

    Interestingly I don’t get the Remote Desktop portion of the System Profiles dialog after following this – I’m trying to RDP TO a Surface Go running Windows Home (not in S mode either).

    Reply

  8. B.A.
    July 18, 2020 @ 9:16 PM

    Thank you for this article. RDC just vanished off my Windows 10 Home after the most recent update. It’s like the only Windows feature I use, so my ass was pretty chapped when I noticed it was gone. I tried a bunch of the fixes suggested in articles prior to finding this one. Obviously, none of them worked. After reading this page, I had RDC up and running in less than 2 minutes….and I’m not the least bit computer savvy. Thanks again for the clear, concise, and accurate info!!!

    Reply

  9. FlyingDutchman
    May 22, 2020 @ 4:31 PM

    The STASCORP repo on GitHub has now been disabled. Apparently this is probably due to the fact Microsoft now owns GitHub, so updates to the .ini file will be hard to find.

    Reply

    • Latindorito
      May 27, 2020 @ 7:28 AM

      It would be really nice if the article could be updated with the latest version of the code uploaded to gitlab, in order ro reinstate the discussion and the updates to the .ini file, out of Microsoft hands

      Reply

  10. Clark
    May 1, 2020 @ 2:41 AM

    Since this has recently become very topical please correct a large mistake in your article. Win10Home DOES support outgoing remote desktop connections and allows you to connect to other PCs. Win10Home does NOT support other PCs connecting TO it.

    Probably most people looking at RDP for the first time now are Win10Home users trying to connect to their work Win10Pro machines which should work just fine.

    Reply

    • Usman Khurshid
      May 1, 2020 @ 12:11 PM

      Hi Clark, I can’t open RDP by going to Run –> mstsc on Windows 10 Home. I have to make it work by using the method in this article. Can you explain how you are able to connect to other PCs using RDP on Windows 10 Home?

      Reply

      • Ekkehard
        February 1, 2021 @ 12:45 PM

        1. Connect to another remote with RDP enabled.
        Win-Button -> write remotedesktopverbindung (german)(english?) -> then use the remotelink as ever.
        2. Let other Computer connect to you or you to another
        Win-Button -> write remotehilfe (german)(english?) -> in this app there are two option: ask for help and give help
        This works for between two Win10home Laptops
        Reagards Ekkehard

        Reply

  11. Calvin Lai
    April 27, 2020 @ 8:26 AM

    was able to get remote desktop working on my cheapo HP stream 7 (which comes with win10 home), thanks!

    Reply

  12. TechMage
    March 19, 2020 @ 3:11 AM

    If not working for you, you may need to update the ini file which hasn’t officially been updated for awhile. Here are 2 posts where you can update the INI file after installation:

    As Mishniak posted (download of updated ini, instructions)
    https://github.com/stascorp/rdpwrap/issues/928#issuecomment-555456887
    Before installing/updating ini, add this to the downloaded ini:
    https://github.com/stascorp/rdpwrap/issues/928#issuecomment-586759251

    After that it worked for me for Windows 10 Home 1909 18363.720 with termsrv.dll 10.0.18362.657. If it’s a later version, then may need some additional ini info. Good luck! And thanks to all who helped me get it running.

    Reply

  13. Gucio
    March 16, 2020 @ 10:04 PM

    Windows 10 1909 – Listener state: Not listening (not supported)…

    Reply

  14. Mike
    February 28, 2020 @ 4:02 AM

    This is not working as of 2-27-2020. I get “RDC not listening”.

    Reply

  15. Tom the Toolman
    February 24, 2020 @ 11:01 PM

    As of 2/24/20, this does not work on my Windows 10 Home version 1903 (May 2019).

    Reply

    • Usman Khurshid
      February 25, 2020 @ 8:54 PM

      I will check and confirm by tomorrow.

      Reply

      • J
        March 30, 2020 @ 6:14 PM

        Any update on this? Having the same issue.

        Reply

        • TechMage
          April 1, 2020 @ 6:44 PM

          If you scroll up a few comments to the one I left (on 2020-03-19), there are some instructions on how to do this while we await it getting updated. In the discussion thread on Github, it’s been updated by others, and after I figured it out, I came back here and noted that info. It’s an .ini file that needs an update and is pretty easy to do.

          Reply

  16. Anthony Ramirez
    January 1, 2020 @ 4:55 AM

    I successfully installed the RDP Wrapper. When I run the rdpconf.bat program I see exactly what is described in the figure in Step 5. However when I run the rdpcheck.bat prog and enter my Microsoft password I get the “Access Denied” message. In addition, I do not see the Remote Desktop information on the System Properties box. I only see the top part (“Remote Assistance”). Any ideas?

    Reply

    • Mishniak
      January 4, 2020 @ 10:52 PM

      Have you tried logging in with a local account (not your Microsoft one)?

      If you are running a very recent version of Windows 10, you may need to update a settings file manually. See this post here: https://github.com/stascorp/rdpwrap/issues/928#issuecomment-555456887 . This solved it for me. To check your OS version, press Windows key, type “About my PC” and look for section titled OS build.

      Reply

  17. Bonghwan
    December 20, 2019 @ 1:29 PM

    The GitHub link of ‘RDP or remote desktop protocol’ is identified as either a virus or dangerous file. Any idea?

    Reply

    • Usman Khurshid
      December 21, 2019 @ 4:42 PM

      It’s an executable file. If you are downloading it using Chrome or Vivaldi, it’ll show a warning when downloading any executable file including the RDP Wrapper.
      Otherwise, the RDP Wrapper Library is a remote admin tool which should be identified as a threat by default but it is marked as safe by the community largely because it doesn’t hinder any Operating System functionality. Here’s the virustotal result:
      https://www.virustotal.com/gui/file/9899ffecf141ab4535ec702facbf2b4233903b428b862f3a87e635d09c6244de/detection

      Reply

    • Carlos
      December 30, 2019 @ 7:09 PM

      It probably is marked as a dangerous file because Microsoft doesn’t want you to enable features you didn’t pay for. Same thing happens with KMSPico for example, which is a way to run unlicensed Windows copies as if they were legitimate.

      Reply

  18. Viktor
    December 18, 2019 @ 3:17 PM

    For Home version of Windows I use LiteManager for remote desktop monitoring

    Reply

Leave a Reply

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