Add support for 10.0.17763.165 #601
Comments
|
Thanks RobertSpir, adding your lines from above to And it is working again. (Showing supported below and I can do multi-login)
I also recompiled the project from source at master, but that was likely not needed. |
|
I tried adding these lines to the end of the file but the service didn't come up at all. Any ideas what shall be changed? |
|
Just for all users a short remark: Thanks to @RobertSpir [10.0.17763.165] // LocalOnlyOffset.x64=xxxxx // all other x64-ini-data for 1809rs517763.1 to .134 are the same as .165-data hint: SingleUserOffset.x64=132F9 may be also ==1322C as in the original-ini from 2018-10-10 x86 data not yet fully tested if identical with the base data 17763.1 ( suppose NO!) |
|
Ok, i found my mistake, i didn't change the date of the file :) Now it works flawlessly .. Many thanks guys. |
|
Hallo - here my findings for 1809_1773.165 ;[Main] ;--------snip------------- ;------------------------use as batch / cmd -------------------------------------------- |
|
termsrv.dll was updated to 167, offsets seems to be the same |
|
termsrv.dll was updated meanwhile to .167 (18-11-27) and .168 (18-12-04), offsets seems to be the same.
|
|
These offsets don't seem to work for me on 168 x64. |
|
@DHaak93 : the offsets I contributed above are tested against x64/x86 in VM and check per IDA |
|
@JeffPeters on my current .ini file i see those lines Do i have to replace them with the lines of @RobertSpir and also Replace termsrv.dll he posted ? |
|
@Julien-nl ; Hello , for each build , a need for the two ini-Section [10.0.17763.nnn] and [10.0.17763.nnn-SLInit] / nnn= (1 , 165, 167, 168 ) is given, which contains both (.x64 and .x86) offset-values.
Therefore in x64 you have several choices to circumvent the stumbling stones. |
|
Despite the description of @hajubu I don't seem to get it working in 17763.168 So I got the 2018-10-10 rdpwrap.ini, added two sections for .168 and .168-SLinit, copying the data from the 165 and .165-SLInit respectively. and … termservice crashes.. I did not fiddle with the dlls. (BTW still fighting with virusscanner too -- maybe this disturbes things as well?) |
|
@andrePKI wrote :: Despite the description I don't seem to get it working in 17763.168
…... „I did not fiddle with the dlls.“
…… BTW still fighting with virusscanner too … maybe this disturbes Things
> (!yes may be!)
> ?? ( Which one do you use ?
> !! Some do strictly forbid
making changes in surveyed/observed (System) areas.
! – use $MS Defender only , I had never a Problem with it – but with others
! Try to Keep it Simple (K.I.S.S.) at least for the implementation phase
….. and … termservice crashes..
> ?? ‚When‘ and ‚What‘ is the message or Event id ?
There is no „fiddling“ necessary , except If you really want to test manually several builds of “termsrv.dll“, which is not the normal workflow.
- So I did it just straight „Forward“
- Use at the first time install or update Win10 and
- use the „Install.bat“ ( only once, with Option -o) to get the updated Version of rdpwrap.ini of the repository {2018-10-10), otherwise you receive with rpd-wrap 1.62 the ini-file 2017-12-27
- net stop termservice (elevated) and watch Messages in the admin-console (see my batch cmd proposal)
- edit rdpwrap.ini with the updated [section-version] according to your termsrv.dll in system32.
- net start termservice (elevated) and watch Messages in the admin-console
just see my result at last post (hajubu- 18-12-09) in #606
----------------
|
|
Yep, @hajubu, I did exactly that. my termserv.dll is .168, the appcrash event in the eventviewer shows P2: 10.0.17763.1 (.1, not .168?) (2 events were logged on each crash, 1000 from Application Error and 1001 from Windows Error Reporting - but this is not relevant anymore - please read on) So, with 10-10-18 file (no modifications) I can RDP into the machine, but only 1 session at a time. Then, when adding the entries for .168 (just above the [SLInit] section) and .168.SLInit (the bottom of the file) I have several possibilities: either the service doesn't start at all, or it starts then crashes when attempting to open an RDP session.
#Happy. Now, the only thing I have to do is to convince McAfee that they show a false positive on rdpconf.exe, so I can use that tool as well. |
|
andrePKI wrote ….in the eventviewer shows P2: 10.0.17763.1 (.1, not .168?)
>> HIGH-FIVE! For your success an Explanation
>> my Observation was in the past form time to time net stop / net start Needs a while for finilazing the Task. Therefore I’m used to take an elevated Batch.cmd with „pause/wait“cmds to have a Chance to see the stopping/starting Messages of the net termservice. ( A clean „Restart“ is Always the best solution !)
>> „McAfee“ -> RDPCfg.exe ( As far I know McAffee observes registry Entries !?!)
Just a short remark : to [Main] updated=yyy.mm.dd i.r. to rdpwrap.ini
Updated=yyyy.mm.dd .GE „last.ini in repo“ prevents regular update with update.bat i.r. to DATE
Update=yyy.mm.dd .LT pulls the „last.ini“ from repo
>> taking only x64 offset values works for your x64-Environment fine.
Other may Need both x64 and x86
>> The two Section [OS.build.no] and [OS.build.no-SLInit]
should positioned acc. to the given logic in the origial rdpwrap.ini
|
Unfortunately doesnt work for me. heres what i get in event logger : |
|
@Scr34mik::18-12-10 Another Msg part hold " Fault offset: 0x00000000000029fc" and the "TermService, version: 10.0.17763.1" Therefore make sure that you did a "sober" OS-Update to "new" 17763.168 ( I suppose you wanted that) |
|
@hajubu got the same error as @Scr34mik. I've used the snippet from @hajubu: As soon as I remove this from the .ini the service starts without problems. Updates were installed in the right order. Also, I've tried to disable anti-virus as well. Seems to be that the old version of the TermSerivce is causing the problem as @hajubu suggested. Any ideas how to register the new version? Update: in the meantime I’ve overwritten termsrv.dll with version .165 and it works (thanks for the snippet @hajubu). This is a workaround for now. The termsrv.dll in the first comment is good, thanks for that @RobertSpir. To overwrite, the owner of the file has to be changed to admin and permissions has to be granted for writing. Stop/start of termservice is needed at the end of the process. |
|
@hajubu, @ But the version in the eventlog refers to svchost.exe, which is .1, not .168, so nothing strange there. This process runs as local system, hence the error 5 (0xc00000005) is odd. |
|
@andrePKI
---------------------------
….. [Hajubu wrote '''
Another Msg part hold " Fault offset: 0x00000000000029fc" and the "TermService, version: 10.0.17763.1"
points to an effect that at the time the error occurred, the "older" version of 17763.1 is still registered.
''''
>>> Thanks andrePKI ,
but I believe there is a little misunderstanding:
If the OS-Update from.1 to .168 was done right and „sober“ before,
I’d never observed a message with „the old Version I had before“ the update of the rdpwrap.ini.
Exchanging „termsrv.dll“ on-the-fly needs a knowledge of handling privileges ( or a tool )
….. Running the …process as local System, hence the error 5 (0xc00000005) is odd …“
>>>> quite clear, but nevertheless we have to accept that the „update“/„replacing“ -Errors are based on on a handling with wrong privileges ( „access-rights“) anything in the registry or file System, in most cases.
……I am not sure about the order of the section in the ini file (normally it should not matter)
>>> You may be right, but for a simple comparison ( simplier reading), I do prefer the way with the „Two“ part as described ( „part1.xxx“ in the middle bevor the [SLInit]-section and „part2xxx-Slinit“ at bottom of the ini file.
-------------------
@creatoro wrote in the update to your post you said: [10.0.1773.165]…[10.0.17763.165-SLinit] data works with now with termsrv.dll.165 which is the way it should.
For any other Version of win10.1809_17763.xxx-termsrv.dll.xxx you need an seperate section-pair.
17763.1 , as set in the rdpwrap.ini in the repository)
17763.165 , as you used it.
17763.167 and / or 17763.168 as I explained :
Add the data from the [10.0.1773.165]…[10.0.17763.165-SLInit] Section pair
in a new pair of sections with each Header(s)
for [10.0.17763.167] and [10.0.17763.167-SLInit]
and / or
for [10.0.17763.168] and [10.0.17763.168-SLInit]
just below the above discussed and referenced positions in the ini file.
--------------------------------------------------------------------------------
Remark : a) From termsrv.dll.1 to termsrv.165 is a difference in the ini-sections data.
Rdpwarp.ini in the repository (Code:res\rdpwrap.ini) used
b) When you do a "normal" update.bat call and may overwrite your just edited
"new" ini-file depending of the Update=yyyy.mm.dd in the [Main]-section "is Less"
then the actual one in the repo [i.e. 2018-10-10]
containing only the 1809-build with 10.0.17763.1.
c) To avoid to overwrite the already updated rdpwrap.ini you may edit update.bat and
delete the option { -o } in the line3 just behind (... RDPWinst" -i) from (RDP-Wrapper V1.62).
JUST To Ease The Job: I do recommend to test the workflow always in a VM/Vbox Environment.
I explained, for those who are not familiar with handling „System Privileges“ exceptions
To do "FIRST" a „sober“ – Standard - „ OS-Update to "new" 17763.168 (…. If wanted …)
with // last CU KB4469342 (v168.1.10 i ) and SSU KB4470788 both from 2018-12-04 --
and "THEN" use the workflow to add the [.168 ini-Section] where you need these.
-- see my post from 18-12-09 in #606 for more detail
-- or follow the post of andrePKI 18-1210 in #601
--------------------------------------------------------------------------------
|
|
just a short note: |
|
Hi, you people are awesome, but there may be some n00bs like me (relatively speaking) out there getting a bit lost. Here are some streamlined instructions based on hajubu, RobertSpir, Scr34mik, et. al., which worked for me. This is for those who have already installed 1.6.2 using the install.bat file and RDPWInst.exe. edited 12/22/2018: I used the code from rcheung81 in the next post, which worked on a Win 10 Pro build 17763.195.
That should work. Thanks for keeping this going! edited 12/22/2018: |
|
Hello, I followed the instructions from gitgotgone exactly but when I try to restart the service with "net start TermService" I get A system error has occured I rebooted the computer and still same issue. Anyone have any thoughts? edit I uninstalled and reinstalled the whole thing and started over. Now the Wrapper state is installed and the service state is green but the Listener State is still not listening. I finally got it working. The lines to add were different on my version of windows 10 (17763.194). I read another post by hajubu for my version. You can follow the rest of the instructions from gitgotgone with the exception of which lines to add in the rdpwrap.ini file Below is what I had to do. Please note you cannot put these snippets at the end of the file and it needs to be followed exactly. ;---------SNIP part1-----goes just behind (above) the section of 10.0.17763.1 --- bInitialized.x64 =ECAB0 |
|
I tried everything they said there, it did not work here what I'm going to do, unfortunately, is to leave the 1803 version with the updates blocked until a version that already works with the 1809 termserv .168 thanks |
|
Instruction from andrePKI worked for me for version 17763.168. Make sure to follow them to the letter, including uninstalling and reinstalling: |
|
I noticed that it is very important that you have a newline at the end of the file. |
|
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 |
|
I'm really sorry but I can't get this to work and I think I've ended up in a muddle with my dlls. I thought I had a recollection of having to copy termsrv.dll and rfxvmt.dll into my system32 folder from my system running Win 10 Pro (also .168) so I did this before running uninstall.bat then install.bat. Looking at the instructions and problems it seems that is not required, just to change the .ini file. So now I'm not sure I have the correct dlls. Could someone send the correct versions I need to work for Win 10 Home x64 10.0.17763.168 with instructions on where they need to be copied to? Apologies for being an idiot. |
|
rfcxvmt.dll 10.0.16063.0, 37376 bytes, timestamp Nov. 10th, 2018 |
|
There is issue #606 for build |
|
tell it to cmhowarth ;) |
New CU KB4470788 for win10 1809 was released that updated termsrv.dll.
It seems that offsets are the same as for 17763.1 version
termsrv_x64.zip
The text was updated successfully, but these errors were encountered: