Windows 10: 'Remote Desktop Services' Services keeps setting itself to 'Automatic'

The 'Remote Desktop Services' service (under Services.msc) keeps setting itself to 'Automatic'.

Does anyone know how to stop this? I've set it to 'Disabled' and turned off the service multiple times but it seems to automatically set itself to 'Automatic' and activate itself. This even happens without restarting the computer.

Is this indicative of malware/virus activity?

How can I ensure this service remains disabled?

I've long suspected this computer is hacked and this activity could be associated with remote access of one form or another. If this indicates known malware please inform me of the usual suspects.

Much appreciated.

:)

 

Remote desktop problems

What remote desktop services need to be started, or do they start upon demand? I have looked at services and there are about 4-5 remote desktop services none of which are starting automatically.

David

 

Disbale Remote Desktop Services

How do I completely, and permanently, disable Remote Desktop Services both in Windows 10 Pro and Windows 10 Home?

When first booting my PC, the service is set for Automatic, but not running. When I connect to the Internet, the service is starting. I have both Remote Assistance and Remote Desktop unchecked and turned off under System Properties, but the service is still
running. I am able to stop and disable it, but I have to do this every time I boot the PC.

I've searched for the Terminal Server, but it's not under HKEY_LOCAL_MACHINE\Software\Microsoft, per directions from a MS article.

Thanks.

 

It is definitely not normal, especially for this service. Pick 2-3 scanners and check for malware.

10 Free and Portable Offline Antivirus Scanners

Try this, run CMD as admin and copy/paste:
Code: reg add "HKLM\Software\Policies\Microsoft\Windows NT\Terminal Services" /v "fAllowToGetHelp" /t REG_DWORD /d "0" /f reg add "HKLM\Software\Policies\Microsoft\Windows NT\Terminal Services" /v "fAllowUnsolicited" /t REG_DWORD /d "0" /f reg add "HKLM\Software\Policies\Microsoft\Windows NT\Terminal Services" /v "fAllowUnsolicitedFullControl" /t REG_DWORD /d "0" /f reg add "HKLM\Software\Policies\Microsoft\Windows NT\Terminal Services" /v "fDenyTSConnections" /t REG_DWORD /d "1" /f reg add "HKLM\Software\Policies\Microsoft\Windows NT\Terminal Services" /v "TSAppCompat" /t REG_DWORD /d "0" /f reg add "HKLM\Software\Policies\Microsoft\Windows NT\Terminal Services" /v "TSEnabled" /t REG_DWORD /d "0" /f reg add "HKLM\Software\Policies\Microsoft\Windows NT\Terminal Services" /v "TSUserEnabled" /t REG_DWORD /d "0" /f schtasks /Change /TN "Microsoft\Windows\RemoteAssistance\RemoteAssistanceTask" /Disable schtasks /End /TN "Microsoft\Windows\RemoteAssistance\RemoteAssistanceTask" sc config TermService start= disabled net stop TermService /y[/quote]

 

A few years ago, a Norton user was ranting about the security software resetting the Service to 'Automatic'. No one in the Norton Support Forum volunteered to prove the user wrong/right.

My own experience, and I use Norton, says a reboot resets the Service to 'Automatic'. When I had the occasion to check, it usually shows it as previously set, 'Disabled'. Only after a reboot does it show the Service running.

It's an inconvenience, the reflexive checking, I've learned to live with.