Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's true that VNC is a disaster, but RDP still feels miles behind thrid-party tech like TeamViewer. And doesn't MSFT stil cripple RDP on Home editions?


Is it actually miles behind?

I've used RDP to work remotely and also to play some games inside Hyper-V VM and I didn't felt big difference between native


I haven't used it much lately, but a few years back I was working on a Windows Server system (whichever was the version that was basically Windows 8) and remember it being really janky (latency spikes, image artifacts, etc.) over my pathetic DSL Internet connection. Then I noticed some other admin installed TeamViewer on it so I gave it a try and it was way faster and smoother so I switched to it permanently, despite the constant annoyances because we were too cheap to pay for a license.

Admittedly, it's been almost a decade since Windows 8 (!?!), so this is a very dated experience.


Technically MSFT disabled the RDP server feature in Home edition, meaning you can't use Windows Home as RDP host (I am not sure the proper terminology for this). The software still in there, you only can use RDP client in Win Home, not the server aspect. It is just disabled without official way of enabling it (w/o upgrading to Pro). However there is way to get it enabled in Windows Home, it need rdpwrap by stascrop. Just download the file and run it. It will get the server aspect running.

Rdpwrap by stascrop (GitHub) https://github.com/stascorp/rdpwrap/releases


There is an official way to get RDP connections to Windows Home edition systems, Windows Quick Assist: https://community.windows.com/en-us/stories/windows-quick-as...

Obviously it has far more restrictions than enabling RDP on Pro systems, but that's because it's clearly designed with Home users (average consumers) in mind.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: