SingleUserOffset.x64 is different

[davidcao2000]

I found that one of the values obtained by your tool for termsrv.dll for Windows 10 (I only tested Windows 10) is SingleUserOffset.x64 Its value is different from the value in the rdpwrap.ini version of sebaxakerhtc.

Only the most recent versions of termsrv.dll (from 10.0.19041.4239 to 10.0.19041.4355) have exactly the same data.

Earlier than version 10.0.19041.4239, the value of SingleUserOffset.x64 is different from the sebaxakerhtc version.

For example, termsrv.dll version: 10.0.19041.3636 (Win10 22H2 03-2024), with your tool, I get: SingleUserOffset.x64=182FB But sebaxakerhtc version: SingleUserOffset.x64=11E12

For example, termsrv.dll version: 10.0.19041.789 (Win10 21H1 10-2020), with your tool, I get: SingleUserOffset.x64=8107 But sebaxakerhtc version: SingleUserOffset.x64=0CA4C

I guess only one side is right. So which side is right?

sebaxakerhtc version: github.com/sebaxakerhtc/rdpwrap.ini

[loyejaotdiqr47123]

I found that one of the values obtained by your tool for termsrv.dll for Windows 10 (I only tested Windows 10) is SingleUserOffset.x64 Its value is different from the value in the rdpwrap.ini version of sebaxakerhtc.

Only the most recent versions of termsrv.dll (from 10.0.19041.4239 to 10.0.19041.4355) have exactly the same data.

Earlier than version 10.0.19041.4239, the value of SingleUserOffset.x64 is different from the sebaxakerhtc version.

For example, termsrv.dll version: 10.0.19041.3636 (Win10 22H2 03-2024), with your tool, I get: SingleUserOffset.x64=182FB But sebaxakerhtc version: SingleUserOffset.x64=11E12

For example, termsrv.dll version: 10.0.19041.789 (Win10 21H1 10-2020), with your tool, I get: SingleUserOffset.x64=8107 But sebaxakerhtc version: SingleUserOffset.x64=0CA4C

I guess only one side is right. So which side is right?

sebaxakerhtc version: github.com/sebaxakerhtc/rdpwrap.ini

Can you upload termsrv.dll？ sebaxakerhtc is not right.

[davidcao2000]

Great! you know someone is wrong. Attached is the dll mentioned. Thanks ! termsrv.dll.19041.3636.zip termsrv.dll.19041.789.zip

[loyejaotdiqr47123]

Offsets have been edited https://github.com/sebaxakerhtc/rdpwrap.ini/commit/807f0c6cd183cf36fde65d444831b2ee5dd13eed

[davidcao2000]

I noticed that in recent Windows 10 versions, the value of SingleUserOffset.x64, generated by llccdr's RDPWrapOffsetFinder, is different from sebaxakerhtc's.ini. Is the former right and the latter wrong? I will provide more termsrv.dll version files.

[loyejaotdiqr47123]

我注意到在最近的 Windows 10 版本中，由 llccdr 的 RDPWrapOffsetFinder 生成的 SingleUserOffset.x64 的值与 sebaxakerhtc s.ini不同。前者是对的，后者是错的吗？我将提供更多termsrv.dll版本文件。

You're right.

[davidcao2000]

我注意到在最近的 Windows 10 版本中，由 llccdr 的 RDPWrapOffsetFinder 生成的 SingleUserOffset.x64 的值与 sebaxakerhtc s.ini不同。前者是对的，后者是错的吗？我将提供更多termsrv.dll版本文件。

You're right.

这么说，有相当多的版本中， SingleUserOffset.x64 的值要按 llccdr 工具所给的值来纠正了。至少数十个。这个工作量很大。请教一下，这个SingleUserOffset.x64的用途是什么？若使用了错误值，会有什么不良结果？

[davidcao2000]

以前我用的是sebaxakerhtc的版本，如果说他的ini中的SingleUserOffset.x64是错的，但似乎也没发现有糟糕后果。

[loyejaotdiqr47123]

以前我用的是sebaxakerhtc的版本，如果说他的ini中的SingleUserOffset.x64是错的，但似乎也没发现有糟糕后果。

第一个登录的用户可能会被踢出而已，其他不受影响

[loyejaotdiqr47123]

这个我跟sebaxakerhtc早就在研究了

[loyejaotdiqr47123]

我注意到在最近的 Windows 10 版本中，由 llccdr 的 RDPWrapOffsetFinder 生成的 SingleUserOffset.x64 的值与 sebaxakerhtc s.ini不同。前者是对的，后者是错的吗？我将提供更多termsrv.dll版本文件。

You're right.

这么说，有相当多的版本中， SingleUserOffset.x64 的值要按 llccdr 工具所给的值来纠正了。至少数十个。这个工作量很大。请教一下，这个SingleUserOffset.x64的用途是什么？若使用了错误值，会有什么不良结果？

几百个吧，从10.0.17063.1000(已知)开始都是错误的

[adream100]

几百个版本的SingleUserOffset.x64 值要修正，是否得收集这几百个版本的dll？

[loyejaotdiqr47123]

几百个版本的SingleUserOffset.x64 值要修正，是否得收集这几百个版本的dll？

是的

[adream100]

我去全力收集，大概有几十个。改天打个包发上来。

[loyejaotdiqr47123]

我去全力收集，大概有几十个。改天打个包发上来。

不需要，我这边都有，issues不一搜就到，我有空就会更新

[adream100]

好的，有劳了，等待你的更新