Add comprehensive Windows 11 25H2 and 26H1 support plus latest Windows 10 updates #4062
Conversation
Major Updates: - Updated timestamp to 2026-01-25 - Added missing patch code 'mov_eax_1_nop_2' for newer Windows builds - Complete Windows 11 25H2 support (builds 10.0.26100.6899 through 10.0.26100.7623) - Windows 11 26H1 Insider Preview support (builds 10.0.28000.x) - Latest Windows 10 configurations for recent security updates New Windows 11 Builds Supported: - 10.0.26100.6899, 10.0.26100.7051, 10.0.26100.7262 - 10.0.26100.7271, 10.0.26100.7296, 10.0.26100.7309 - 10.0.26100.7344, 10.0.26100.7523, 10.0.26100.7535 - 10.0.26100.7623 (latest January 2026 build) - 10.0.28000.1340, 10.0.28000.1362, 10.0.28000.1371 Fixes: - Resolves 'Not Supported' errors for Windows 11 25H2 users - Addresses issues stascorp#4061, stascorp#4060, stascorp#4059, stascorp#4056, stascorp#4049, stascorp#4042, stascorp#4036 - All configurations verified by community testing Technical Details: - All configurations include proper SLInit blocks - Full x64 support with correct offset mappings - Community-verified configurations from trusted contributors - Future-ready structure for easy addition of new builds Closes: stascorp#4061 Related: stascorp#4060, stascorp#4059, stascorp#4056, stascorp#4049, stascorp#4042, stascorp#4036
|
and the latest is also fixed: |
- Complete step-by-step process for analyzing termsrv.dll - Tool recommendations and setup instructions - Function identification and offset extraction methods - INI configuration creation and testing procedures - Community contribution guidelines and best practices - Troubleshooting common challenges (ASLR, code signing, optimizations) - Advanced techniques for comparative analysis This documentation will help community members contribute new Windows build support more effectively and reduce the learning curve for reverse engineering RDP Wrapper configurations.
- analyse instead of analyze - licence instead of license (when used as noun) - optimisations instead of optimizations - reorganisation instead of reorganization - behaviour instead of behavior Maintains consistency with British English conventions.
|
@binarymaster - please can you review, test and approve this PR? |
|
See the timestamp of the last push into master branch (this is not going to change in near future). The project is officially on the community support, INI sections are provided on termsrv.dll version basis, one GitHub issue per build. |
|
Thx @sjackson0109 |
|
Just for your info. |
|
@kuronekonokuro @binarymaster Requiring one pull request per offset does not reduce risk or improve code quality. It increases process overhead without adding meaningful control. Review effort scales linearly with the number of pull requests, while the technical change remains identical in nature. This creates unnecessary friction and actively discourages contributors from submitting fixes, particularly when the work is repetitive and mechanical. Fragmenting this work across multiple pull requests also weakens traceability. A single consolidated change set makes it easier to understand what is currently supported, what was fixed at a given point in time, and how offsets evolve together. Multiple micro PRs obscure that context and make the project harder, not easier, to maintain. This pull request consolidates all currently missing offsets into one consistent update. The scope is clear. The changes are methodical. Verification is straightforward. If there is a specific technical or long term maintenance concern with merging this as a single PR, please state it explicitly so it can be addressed. Otherwise, I would appreciate a review and decision on the current submission. |
|
The problem is not about pull requests. |
|
if it's been given to the community to support - then why can't we (heavy contributors) take over the ownership role, and progress with PRs. Else an abandoned project should be marked abandoned - so no contributions/issues/discussions etc can then be raised/updated. this seems more half-way abandoned |
|
Massive shame, this tool is really useful. |
It's how it is. I have my own vision for the project future, stuff that I'd want to rewrite in a better way, using CI and covering with tests. But that's not going to happen in near future, there are other priorities.
There are long term community supporters, who participate in the Telegram support chat, and help with issues here. I usually grant moderation permissions to these people, still on my own preference though of course. I'm not planning to transfer ownership to anyone. |
|
I'll just use and advertise my fork, retaining the license and i'll improve it on my own time. thanks for not approving this pr and educating me in the fact it's a dead product. |
4 participants
Overview
This PR adds comprehensive support for Windows 11 25H2 and 26H1 Insider Preview builds, along with the latest Windows 10 updates. All configurations are based on verified community contributions and testing.
Major Changes
Windows 11 25H2 Support (10.0.26100.x)
Windows 11 26H1 Insider Support (10.0.28000.x)
Latest Windows 10 Updates
Technical Improvements
Issues Resolved
This PR directly addresses multiple open issues:
Community Impact
Verification
All configurations sourced from:
Testing Recommendations
Note: This contribution represents months of community effort and addresses the most critical compatibility gaps affecting the majority of current Windows 11 users.