Only thing that would affect Office is TSforge activating it and then doing a unsupported Windows upgrade. Example: TSforge activate Office on Win 11 23H2, upgrade to 24H2, then Office will deactivate.
Should we expect to see new TSForge dll update? Or it's just part of mass project Didn't see new version update of TSForge yet
StaticCID uses code outside of TSforge. /siid option was added ahead of time, so theres nothing to update
Any specific reason for that? Each and any version not having the bug could be perfectly activated offline. That is the big advantage of ZeroCID. StaticCID should only be used for the affected versions, I think.
? Most people have internet access, and using StaticCID guards against the possibility of backporting this bug to Windows 10. The only thing that gets sent is the constructed Installation ID, so only 64 bits of identifiable info is sent.
Just tested on Windows 10. Activating offline with ZeroCID is possible if forced. That's good, please don't hard-block it. By default, it uses KMS4K if offline. The matter is worse with ESU activation on offline systems. StaticCID doesn't work offline, and KMS4K is not supported for ESU. Forcing ZeroCID is the only option.
Idk why you think we would hard-block it lol, this is just a measure to prevent a hypothetical backported patch from wiping out ESU licenses for users. If you really hate internet-based activation, ZCID will always be available.
Lots of people use MAS to activate ESU on other users' systems. It wouldn't be good if all those machines were to deactivate in the future if Microsoft decides to backport that update to 10. That's why we are somewhat forcing the use of StaticCID, but users still have the option to change the method from the menu manually.
This is no criticism, I just wanted to understand it. And even in the Force menu, it outright states "Will only work with builds below 19041" which is not entirely correct. "Not guaranteed to work with 19041 builds or higher" would be more appropriate. I'm just glad that I don't have to keep two MAS versions. And in hindsight, even if they correct this bug, it's better to leave StaticCID as default if it's more stable.
after check your code + explain here >> From now on, the script will use StaticCID method (requires Internet) on build 19041 and later. >> Because of this, ZeroCID does not work in any Windows 11/Server 2025 Insider Canary builds released afterwards, or any Windows 11/Server 2025 retail/release preview builds newer than 26100.4188. so my question is 19041 no have problem with zeroCid, so problem start from 26100 ? so .. why start from 19041
Probably off topic, but would KMS4K soon replace KMS38 in the future once we are in the year 2038 aslong as its stable enough?
The TSforge menu of MAS 3.0 version The TSforge menu of MAS 3.3 version Suggestions for the next version of the TSforge module in MAS: For the auto mode of TSforge activation: In offline mode, it is recommended to change the priority to ZeroCID (if supported by this version) - KMS4K. In online mode, it is recommended to change the priority to ZeroCID - StaticCID (if this version does not support it).