Open test2a opened 4 years ago
in task manager, if i try to start RemoteAccess, the operation could not be completed. the services cannot be started, either because it is disabled or because it has no enabled devices associated with it
This version of LTSC is not supported at this time, we need new jump points for the patch.
any ETA on that, secondly, any way i can start the remote access service?
1809 LTSC (and no LTSC) build 17763 version 771 is supported here : https://github.com/stascorp/rdpwrap/issues/945#issuecomment-573673428
i am in a mind now. as i said, i had stopped the remote desktop services in the services. now i got it to start but in task manager, "RemoteAccess" is still stopped and starting it says " the operation could not be completed. the service cannot be started, either because it is disabled or because it has no enabled devices associates with it".
rdpconf says service state: unknown. previously it was "stopped" until i started the service. doing "net stop termservice" in cmd says "the service name is invalid".
i am in a mind now. as i said, i had stopped the remote desktop services in the services. now i got it to start but in task manager, "RemoteAccess" is still stopped and starting it says " the operation could not be completed. the service cannot be started, either because it is disabled or because it has no enabled devices associates with it".
rdpconf says service state: unknown. previously it was "stopped" until i started the service. doing "net stop termservice" in cmd says "the service name is invalid".
You need to pun old rdpwrap.ini file and follow news solution.. If you need a file, ask to me.
Has perhaps TrendMicro, ESET interfered? Both of these take out Windows registry components for RDP as well as taking out rdpwrapper.dll ... :(
Perhaps even Windows Defender?
You need exceptions in place, even then TM still seems to kick in randomly and destroy RDP again. I use ssh via a Tor hidden service to get back in and "fix" things whenever it gets taken out. If TM keeps taking it out, then I'm going to try real hard to get the client to stop using TM and just use built-in products.
@affinityv ok. made an exception to defender and uninstalled rdpwrap and installed it again. @lucassssmi the latest update put me on 17763.1012 version 1809. where can i get the ini file as rdpconf is now showing wrapper state: installed [1.5.0.0] service state: running [ver. 10.0.17763.771] listener state: listening [not supported]
@test2a
[10.0.17763.771-SLInit]
bInitialized.x86 =CD79C
bServerSku.x86 =CD7A0
lMaxUserSessions.x86 =CD7A4
bAppServerAllowed.x86 =CD7AC
bRemoteConnAllowed.x86=CD7B0
bMultimonAllowed.x86 =CD7B4
ulMaxDebugSessions.x86=CD7B8
bFUSEnabled.x86 =CD7BC
bServerSku.x64 =ECAB8
lMaxUserSessions.x64 =ECABC
bAppServerAllowed.x64 =ECAC4
bInitialized.x64 =ECAB4
bRemoteConnAllowed.x64=ECAC8
bMultimonAllowed.x64 =ECACC
ulMaxDebugSessions.x64=ECAD0
bFUSEnabled.x64 =ECAD4
[10.0.17763.771]
LocalOnlyPatch.x86=1
LocalOnlyOffset.x86=AFEB4
LocalOnlyCode.x86=jmpshort
SingleUserPatch.x86=1
SingleUserOffset.x86=4D7F5
SingleUserCode.x86=nop
DefPolicyPatch.x86=1
DefPolicyOffset.x86=4BFF9
DefPolicyCode.x86=CDefPolicy_Query_eax_ecx
SLInitHook.x86=1
SLInitOffset.x86=5B30A
SLInitFunc.x86=New_CSLQuery_Initialize
LocalOnlyPatch.x64=1
LocalOnlyOffset.x64=77AD1
LocalOnlyCode.x64=jmpshort
SingleUserPatch.x64=1
SingleUserOffset.x64=1339C
SingleUserCode.x64=Zero
DefPolicyPatch.x64=1
DefPolicyOffset.x64=18025
DefPolicyCode.x64=CDefPolicy_Query_eax_rcx
SLInitHook.x64=1
SLInitOffset.x64=1ACDC
SLInitFunc.x64=New_CSLQuery_Initialize
i am on windows 10 enterprise ltsc version 1809 os build 17753.973 yesterday, after some update, rdp access stopped working. i had tried to use ini files from here but nothing changed. i somehow managed to stop remote desktop services in services and after restart, that is refusing to start back again thowing a error 1067. the processs terminated unexpectedly. windows could not start the remote desktop service on local computer.
RDP check used to show wrapper state: installed ver 1.5.0.0 service state: started ver. 10.0.17763.771 listener state: not listening {not supported]
now after stopping the service, service state: stopped