-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for 10.0.17763.194 #611
Comments
Yes, rdpwrapper is blow up after update yesterday. Any things? |
@ @mbowers3, @artemmen , @binarymaster bInitialized.x64 =ECAB0 |
thank you very much hajubu it's working for me on build 17763.194 |
Thank you Aliqalavi! I finally got this working on Windows 10 (1809). 😊
From: aliqalavi <[email protected]>
Sent: Wednesday, December 12, 2018 4:46 AM
To: stascorp/rdpwrap <[email protected]>
Cc: Subscribed <[email protected]>
Subject: Re: [stascorp/rdpwrap] Add support for 10.0.17763.194 (#611)
@ @mbowers <https://github.com/mbowers> , @artemmen <https://github.com/artemmen> , @binarymaster <https://github.com/binarymaster>
10.0.17763.194 - CU KB4471332 - keeps/lifts the termsrv.dll to its file version 10.0.17763.168.
Therefore since .165, .167, .168 use the data-offset, which are the same, we have to add to the rdpwrap.ini dated 2018-10-10 ( last.ini in the repository - code: res\rdpwrap,ini).
Ensure you have the correct ini file with two ini-sections [10.0.17763.1] , [10.0.17763.1-SLInit]
and add then the two sections [10.0.17763.168], [17763.168-SLInit]
Keep an eye on Acces Rigths and at least use "stop net termservice" before you exchange the
rdpwrap.ini (2018-10-10) with your newly edited ini file.
After the successful replacing you have to start the termservice again ("start net termservice")
Just a short remark there are more stumbling stones with system privileges if plan to change termsrv.dll on your own. ! ( see also #606 <#606> -hajubu posts)
.Good Luck with this task
( You also may wait till we get an updated rdpwrap.ini from binarymaster in the repository )
;---------SNIP part1-----goes just behind the section of 10.0.17763.1 ---
[10.0.17763.168]
LocalOnlyPatch.x86=1
LocalOnlyOffset.x86=AFC74
LocalOnlyCode.x86=jmpshort
LocalOnlyPatch.x64=1
LocalOnlyOffset.x64=77AF1
LocalOnlyCode.x64=jmpshort
SingleUserPatch.x86=1
SingleUserOffset.x86=4D665
SingleUserCode.x86=nop
SingleUserPatch.x64=1
SingleUserOffset.x64=1322C
SingleUserCode.x64=Zero
DefPolicyPatch.x86=1
DefPolicyOffset.x86=4BE69
DefPolicyCode.x86=CDefPolicy_Query_eax_ecx
DefPolicyPatch.x64=1
DefPolicyOffset.x64=17F45
DefPolicyCode.x64=CDefPolicy_Query_eax_rcx
SLInitHook.x86=1
SLInitOffset.x86=5B18A
SLInitFunc.x86=New_CSLQuery_Initialize
SLInitHook.x64=1
SLInitOffset.x64=1ABFC
SLInitFunc.x64=New_CSLQuery_Initialize
;--------------end snip part1-----------
;
;-----------snip part2 --------goes just at the bottom of the file behind 10.0.17763-SLInit Section------
;.
[10.0.17763.168-SLInit]
bInitialized.x86 =CD798
bServerSku.x86 =CD79C
lMaxUserSessions.x86 =CD7A0
bAppServerAllowed.x86 =CD7A8
bRemoteConnAllowed.x86=CD7AC
bMultimonAllowed.x86 =CD7B0
ulMaxDebugSessions.x86=CD7B4
bFUSEnabled.x86 =CD7B8
bInitialized.x64 =ECAB0
bServerSku.x64 =ECAB4
lMaxUserSessions.x64 =ECAB8
bAppServerAllowed.x64 =ECAC0
bRemoteConnAllowed.x64=ECAC4
bMultimonAllowed.x64 =ECAC8
ulMaxDebugSessions.x64=ECACC
bFUSEnabled.x64 =ECAD0
;---------end snip part2 --------------
thank you very much hajubu it's working for me on build 17763.194
but i havent [10.0.17763.1] section i only have [10.0.17763.1-SLInit] section but its works!
anyone need help just follow these steps from above from hajubu
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#611 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/Ap7Gxypo9kZZPTNUNyBRpC61AEMM03vWks5u4Ox6gaJpZM4ZOt2_> .
|
That is odd.
Have a look to the „official“ rdpwrap.ini in the repository ( see CODE : res\rdpwrap.ini)
Or better Code : res\rdpwrap-ini-kb.txt
Normally, For each „Version“ does exist a proper Section pair.
But I also see some singular cases. There might be some „default“ cases,
which gaves us this Advantage. – We should not Always Count to be lucky like this.
I will add an template (only structures explained) also.
(
Details see in the repository
{ Code: res\rdpwrap.ini or more details in res\rdpwrap-ini.kb.txt}
)
@waltw1207 - High Five !
@aliqalavi wrote:
@ @mbowers3, @artemmen , @binarymaster
10.0.17763.194 - CU KB4471332 - keeps/lifts the termsrv.dll to its file version 10.0.17763.168.
Therefore since .165, .167, .168 use the data-offset, which are the same, we have to add to the rdpwrap.ini dated 2018-10-10 ( last.ini in the repository - code: res\rdpwrap,ini).
Ensure you have the correct ini file with two ini-sections [10.0.17763.1] , [10.0.17763.1-SLInit]
and add then the two sections [10.0.17763.168], [17763.168-SLInit].Good Luck with this task
thank you very much hajubu it's working for me on build 17763.194
but i havent [10.0.17763.1] section i only have [10.0.17763.1-SLInit] section but its works!
anyone need help just follow these steps from above from hajubu
[rdpwrap-ini_template_17763.zip](https://github.com/stascorp/rdpwrap/files/2672063/rdpwrap-ini_template_17763.zip)
|
hajubu ?( You also may wait till we get an updated rdpwrap.ini from binarymaster in the repository ) is this going to be done around 18 December 2018 you think. |
>> @starfighter asked for „official“ update release date
….. I just have a „Feeling“, when the OS win10 1809 update Story is calming down ,
we will be lucky getting an update.
Probably @binarymaster knows more & better.
…. Meanwhile we may live with this intermediate solution.
a) Os update CU 1809-17763-194 (KB4471332) using
b) the suitable data for 10.0.17763.168 (termsrv.dll file version)
Von: StarfighterJ
Gesendet: Mittwoch, 12. Dezember 2018 20:18
hajubu ?( You also may wait till we get an updated rdpwrap.ini from binarymaster in the repository ) is this going to be done around 18 December 2018 you think.
|
Thank you very much ! @hajubu and @RobertSpir ( #601 ) |
Hello. |
The latest Windows update seems to have an issue with the INI provided by @hajubu. Following all the above tips and tricks, I am still unable to get it working. System Info: Here are my findings after about an hour of testing:
I'm at a complete loss here so any help would be much appreciated. |
It works on 10.0.17763.168. I also struggled but if you follow the steps above you'll see it can work |
Sorry Team - But here my cooking recipee and all the detail incl. the ini for
ALSO I rechecked just now the snipping data above in #611 Here the best description I meanwhile could make.
c) Install rdpwrap.ini - ensure to have the latest d) Edit rdpwrap.ini to add the relevant section
e) To replace the data
---- and more details in my zip file - |
hola, gracias @hajubu seguí sus instrucciones y funciono con la versión w10 10.0.17763.168 |
I've followed all the instructions given including those from the 17763-templates.zip file given by @hajubu but I am still unable to get it working. I have gone as far as uninstalling and reinstalling RDP Wrapper and have even replaced the termsrv.dll file in System32 with an older one (10.0.17763.1) to no avail. Curiously enough, now instead of TermService crashing on launch, it is just in a perpetual state of "Starting." Seeing other having success makes me think that this is an isolated issue with my computer alone. Are there any other services, programs, permissions, etc that affect the usage of RDP Wrapper? Besides the standard installation and modification of the INI file, is there anything else I should take a look at? |
Hello Kasim Ahmic –
there is normally no need to tackle manually with the termsrv.dll.
Did you go straight forward first with the KB4471332 (10.0.17763.194)
which does an update from termsrv.dll.001 or dll.165 or dll.167 to dll.168
( …but keeps in case you had been already updated to .168
( e.g. done with the windows10.0-kb4469342-x64_7290815610ac4c3d657eb5ed6e4e92421fa8c29a.msu
, "Package_for_RollupFix" version="17763.168.1.10") which leads also to an Termsrv.dll.168 )
The same happens when you update the OS from .168 to .194 (KB4471332) {keeps the termsrv.dll.168)
I do assume you are on win 10x64-1809-17763-194 at this time
and you had seen the termsrv.dll.168 and validated the Version
( see my crc-listing 3-17763_rdpRule.CRC.txt in the Zip-file)
and for now are on termsrv.dll.001 ( manually)
As you did so –
I assume you solved the elevated privileges ( manually or either by a „Tool“).
To circumvent the stumbling Stones of the „System“ Access Rights.
Did you also Keep an eye on your „Virusscanner“ as some of these “good Boys“ are sensitive and reluctant for exchanging/touching System Files and also registry data. (win-defender is not reluctant).
Now It is time Change the termsrv.dll.001 back to „Normal .168“
Ensure the correctness with following elevated cmd:
„Certutil -hashfile C:Windows\system32\termsrv.dll -md5“
(-md5 , -sha1 – doesn’t matter in the „3-17763_rdpRule.CRC.txt“ are known crc-data in)
You may also verify the property data of
C:Windows\system32\termsrv.dll :: Props:: 10.10.17763.168 - size: 1019392 - date:2018-12-04
Another file(s) of interest is/are
C:Windows\system32\rfxvmt.dll :: Props:: 10.10.17763.1 - size: 40960 - date:2018-09-15
C:Windows\syswow64\rfxvmt.dll :: Props:: 10.10.17763.1 - size: 32768 - date:2018-09-15
Remark:
BUT the syswow64\rfxvmt.dll may be added by your RDP Wrapper V.1.62 with an older date
(Up till now this was not conflicting with the RDP wrapper Function,
„one“ rfxvmt.dll (32-bit) should be in this folder. It must exist only !
If you like you can now take my Template
1-17763_rdpwrap.168.194.txt renaming it to „%program files%\RDP Wrapper\rdpwrap.ini“
( this folder is the „Default“ for the first Install.)
Follow my short instruction :
To replace the data in "%program files%\RDP Wrapper"
I recommend to use a batch file with „Pause“:
1:: "net stop termservice" , 'PAUSE',
2:: delete old "%program files%\RDP Wrapper\rdpwrap.ini"
3:: and copy the „new-ini-168“ to "%program files%\RDP Wrapper\rdpwrap.ini"
4:: and then 'CONTINUE' , "net start termservice" , 'PAUSE' again.
Keep an eye on the Messages in the ‚PAUSE‘-Phases !
This should help to ensure that the service has stopped and restarted without errors
Also you may Restart your "magic-machine"
before you test the RDP Wrapper with RDPconf.exe
and (or) with RDPcheck.exe to see the settings and function.
This concludes the easy test steps.
It should work in General.
If there are other termservices products installed , it has Always worked fine.
b.r. Hajubu
update: to ease the Job ,added a small Batch , to stop and Restart the Service
.Good Luck
Von: Kasim Ahmic
Gesendet: Donnerstag, 13. Dezember 2018 21:19
..:..... it is just in a perpetual state of "Starting."
Seeing other having success makes me think that this is an isolated issue with my computer alone. Are there any other services, programs, permissions, etc that affect the usage of RDP Wrapper? Besides the standard installation and modification of the INI file, is there anything else I should take a look at?
[net-stop-and-start_termsrv.zip](https://github.com/stascorp/rdpwrap/files/2678955/net-stop-and-start_termsrv.zip)
|
#611 (comment) - working. |
Hey guys, I had the same issue as @KasimAhmic. Adding both snippets breaks TermService start. My ini was just the last update from 2018.10.10, but I guess there must have been some differences. |
I confirm. Works |
Thank you @ventsislav-georgiev, that worked for me as well! Also, big thanks to @hajubu and everyone else for the help! I greatly appreciate it! :) |
So this is a duplicate of #606 too. |
1809-17763.1 -.55 -.107 -.134 has Always had the termsrv.dll.001 version
Termsrv.dll with Version -.165 -.167 -.168 (CU_KB4469342_v5.10) have different CRC
but same Offset Values – see my template.zip in ^# 611.
Therefore Data Sections 10.10.17763 for .1 and .168 ought to be sufficient in most cases.
Cu 4471332 does not touch termsrv.dll.168 only in cases less then .168 !
OK?
^# 606 611 refer to These Facts ! and a little bit also in ^# 601 ( .165)
10.0.17763.194 - CU KB4471332 - keeps/lifts the termsrv.dll to its file version 10.0.17763.168.
So this is a duplicate of #606 too.
|
Thanks very much for posting rdpwrap.ini edit for 17763.168. Works excellent for me. |
@hajubu Please refrain from mentioning all kinds of codes, details, KB article numbers, as this confuses most people more than it clarifies things. I as a technician find it hard to understand your posts... To be clear to everybody: First find the version of your termserv.dll file. BTW a big thank you goes to @hajubu and @RobertSpir for providing the details which need to go into the ini files. This is the real hard work. The correct command to stop the service is NB it would be most welcome to have the rdpwrap.ini file updated at the source more frequently with validated contents for each new build of termsrv.dll, that would help a lot of people... @binarymaster please?? |
@ andrePKI wrote:
Please refrain from mentioning all kinds of codes, details, KB article numbers, as this confuses most people more than it clarifies things. I as a technician find it hard to understand your posts...
➢ „as a technician it is …“ : what ever your full background might be, I have also one.
We should stop here and stay cool.
|
Thank you all !!! works fine with the attached rdpwrap.ini |
Windows 10 Pro x86 17763.194 not work with section from .ini for 10.0.17763.168 (the user is not included into system). |
@vibaaa wrote
X64 :: Windows 10 Pro x64 17763.194 worked.
… OK
X86:: Windows 10 Pro x86 17763.194 not work with section from .ini for 10.0.17763.168
… works in my Testbed: VM/Vbox
?? which data sections did you implement ??
17763.1 , 17763-SLinit and also 17763.168, 17763.168-SLInit
?? Which file Version do you see in the properties for the termsrv.dll ??
|
@vibaaa wrote:
1) property Info: Termsrv.dll .168
2) I copy section [10.0.17763.1] -> [10.0.17763.168] and [10.0.17763.1-SLInit] -> [10.0.17763.168-SLInit]
… Be Aware [10.0.17763.1] is not equal to [10.0.17763.168]
Therefore you need both sections, each with seprarate data Content .
… The SLinit Data for [10.0.17763.1-SLInit] is equal to [10.0.17763.168]
Therefore copying is fine
… If you wants to have os(x64 and x86) in one rdpwrap.ini , Combine them in one Header.
I add a small sample to help you to clarify the data sections.
rdpwrap-light_for_vibaaa.txt in rdpwrap-light_for_vibaaa.zip
[rdpwrap-light_for_vibaaa.zip](https://github.com/stascorp/rdpwrap/files/2691051/rdpwrap-light_for_vibaaa.zip)
|
Which ini file is the right one to grab? It seems Microsoft have been messing with the file a lot lately? |
All works. Thanks. |
Ok THAT zip file works - thank you! |
One more problem: in approximately 20 minutes the session of a remote desktop is disconnected, how it is possible to correct? It will be connected it is possible right after switching-off, in gpedit.msc switching-off time is not set. |
@Vibaa wrote:
One more problem: in approximately 20 minutes the session of a remote desktop is disconnected, how it is possible to correct? It will be connected it is possible right after switching-off, in gpedit.msc switching-off time is not set.
… this seems MS Windows behaviour depending on your „Remote Desktop Session Host“ , which features no given timeout by Default.
… found some Infos – BUT Think of RISKs , with Time-Out settings
• OPEN A COMMAND-PROMPT AND TYPE GPEDIT.MSC TO LAUNCH THE LOCAL GROUP POLICY EDITOR SNAP-IN.
• IN THE LEFT PANEL, EXPAND THE COMPUTER CONFIGURATION NODE OR THE USER CONFIGURATION NODE, DEPENDING IF YOU WANT TO CHANGE THE RDS BEHAVIOUR ON SYSTEM-SCOPE (RECOMMENDED FOR THIS SCENARIO) OR ON USERS-SCOPE (SEE BELOW FOR THE DIFFERENCES).
• NAVIGATE TO ADMINISTRATIVE TEMPLATES > WINDOWS COMPONENTS > REMOTE DESKTOP SERVICES > REMOTE DESKTOP SESSION HOST > SESSION TIME LIMITS.
• IN THE RIGHT PANEL, DOUBLE-CLICK THE SET TIME LIMIT FOR ACTIVE BUT IDLE REMOTE DESKTOP SERVICES SESSIONS POLICY: IN THE MODAL WINDOW THAT WILL APPEAR, ACTIVATE IT BY SWITCHING THE RADIO BUTTON FROM NOT CONFIGURED TO ENABLED, THEN SET THE DESIRED AMOUNT OF TIME IN THE DROP-DOWN LIST RIGHT BELOW.
|
Hi Everyone, I have tried with this .ini file and it worked for me, it's for 10.0.17763.167 version x64 First, stop the service running CMD as administrator, then run net stop termservice |
new updates broke it I tried my old termserv.dll but then remote desktop services will not start anymore.
The text was updated successfully, but these errors were encountered: