Discussion in 'Windows 10' started by Mr Jinje, Oct 2, 2014.
With Hex editor. Find=>Replace
You need to login to view this posts content.
Can someone make a patch for Server 2019, 17763.771 ?
original file is here -> h ttps://mega.nz/file/zNFWjYbY#4L4PKKPReO8nnFwzKgVDtfLGerZ_bsNoW8SQmIAX9Fg
-----------------NOT WORKING multisession----------------------
with this settings working only multiuser...
For Server just make it RDS Host
Try this alone without any other patchs.
Offset 17425h B80001000089813806000090
Offset 12899h 00
with RDS Host settings works great... thx @sebus
Тhank you both, will try later only with @wyxchari offered offsets
What are the pros and cons of using a straight hack of termsrv.dll vs the rdpwrap approach?
From what I have gathered so far it seems that RDPwrapper has some advantages that straight patching does not, but does lack some printing functionality.
I was curious about some remarks that were made about server: why would one want to use a k'd termsrv.dll on Windows Server 2019 with RDS and CALs from eBay at an affordable price? Are there reasons and what are they if so?
Also why do we have 2 forks?
https: github.com asmtron rdpwrap (last commit 11 days ago and from 2014 edtrejo)
https: github.com sebaxakerhtc rdpwrap (last commit dec 2018 and from stascorp)
It's open source and it's GitHub, If you have a GitHub account you can fork it too with the click of one button
I'm not asking what this is, I'm asking why are there two forks from what appears to be the same member of the forum but with two different GitHub accounts. I have no problem with this being done, I simply am trying to understand why it's being done since I've seen both being referred to......
Is there a reason? What's the reason? What do we need to be aware of so we use the right version? And so forth.
stascorp is the original, some people fork it just to have a backup. Just recently the stascorp rdpwarp github got locked but reopen as of now.
Please help file termsrv.dll windown 10 32bit 10.0.18363.. thanks
Thanks you verymuch
Q1, I still have 18363.900, why is the version 2004 not available for my system?
Q2, my patched "termsrv.dll" has been working fine, just today it starts to reject remote multi-user. The "termsrv.dll" has patch B80001000089813806000090 and 58000000FF15F7. Anything wrong?
Hi! What about one for Win10 2004 19041.329 version ? There is nothing so far ..
When we talk about versions, it is made from the versions of termsrv.dll, we are not talking about the windows versions.
- termsrv.dll x64 10.0.19041.84 11.05.2020 is the version in Windows 10 x64 v2004 10.0.19041.329
IDA: ?Query@CDefPolicy@@UEAAJPEAH@Z proc near
Write : B80001000089813806000090
Offset file: 172D5h Write: B80001000089813806000090
IDA: ?IsSingleSessionPerUserEnabled@CSessionArbitrationHelper@@UEAAJPEAH@Z proc near
Write : ----00----------
File offset: B412h Write: 00