Discussion in 'Windows 10' started by Mr Jinje, Oct 2, 2014.
17763 activates just as 18298 does. So activation is not an issue.
You need to login to view this posts content.
Guys today there is a new release and have crashes the rdpwrap.
any suggestiosn which version to use ?
thank you so much
[CU 10.0.17763.194 uses termsrv 10.0.17763.168]
@Prince_Charles can you give us a patched file (termsrv 10.0.17763.168) ? Thank you in advance !
The patch strings are the same as for the original 17763. Look up the thread a bit.
@Prince_Charles Do we have to add this to the ini file ?
it working thank you
Can anybody provide the patched file for 17763.253? I suppose the file termsrv.dll is the same despite the CU version, am I right?
I've tried to find and replace the hex string, doesn't matter how I try, the result is the same: not found
39 81 3C 06 00 00 0F 84 7F 2C 01 00
I've tried HxD, can't find!
Any help would be highly appreciated.
Thanks in advance!
39813C0600000F847F2C0100 is still there (look at the 17340h row for the start of it), same place. I'm not sure what MS is doing updating the file again, since this isn't what they've done in the past (well, they've updated it between major builds, though very rarely, but when they have, these things actually changed). This new behavior of theirs is very annoying.
There where something wrong with the hex editor, pretty weird.
According to Prince_Charles's post, I've changed only these:
I've find somewhere else a post when i read about one more to be changed but I didn't.
Thanks so much.
LE: Looks like 00EB18488D is only applicable to Windows Enterprise for Virtual Desktops.
Not my case, PRO version here.
I only noticed it later, but there is no 17763.253 for termsrv.dll. Yes, the date changed on it, but the version number is still .168 and its hash matches the one that came with .168. That certainly explains why nothing changed.
I hope MS doesn't make a habit of changing the date on files for no reason, because when they do, I think that means that the previous one is overwritten, even if it's identical. I wonder if this relates to the switch to Express updates from Delta updates in 17763?
The solution is working very well, as long as you wanna open a new connection using one different user account.
In case to connect remotely to the current session already opened, a brand new session is created and you are not able to find all the applications already opened, this is the problem. Basically you got two connections under the same user (the one with what you worked and the new one via remote)
The behavior is totally different comparing with older versions.
What can I do to use the remote server like I haven't applied this patch? Classic way, I mean.
LE: For what I want: remote with a different user account or remote with the main one but not creating a new session You have to replace the first string ONLY (39813C0600000F847F2C0100 ===> B80001000089813806000090) but NOT the second one.
This time, with 17763.292, the DLL actually was updated, not just timestamped, probably to fix this:
"Addresses an issue that causes Remote Desktop Services to stop accepting connections after accepting several connections."
But the string still hasn't changed, which is weird.
"Basically you got two connections under the same user (the one with what you worked and the new one via remote)"
You are logging into the administrator account. The behaviour you are describing is standard: how else would you be able to remotely administer a machine?
Create a normal account:
Either regedit or use RDPWrap's configuration utility to set fSingleSessionPerUser.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server fSingleSessionPerUser (dword) = 0|1
This was asked in Telegram group, and didn't receive any good answers. Maybe people here can offer some input.
Is there any build/sku of Windows 10 that will support concurrent sessions consistently - regardless of windows updates? Does LTSB cumulative updates ever shake of RDP?
Basically, looking for stable W10 for RDP use.
Windows 10 Enterprise for Virtual Desktops supports connecting to multiple user accounts at the same time.
What SKU is that in product.ini ?
ServerRDSH. First install normal Enterprise and then change key to ServerRDSH. If you install it normally you will not be able to create account.
Pretty sure it needs further licensing though after the trial period (90 days?), just like like RDSH does.
This is unrelated to Windows activation.