Features and support will be added as they are deemed appropriate, and on our own timeline. Asking over and over does not encourage anyone to add anything.
Microsoft released Windows 11 Build 26100.4188 (KB5058499) to Insiders in the Release Preview Channel on Windows 11, version 24H2 (Build 26100). For attention now MAS script failed to activate latest insiders build windows 11/Server 2025 via TSF. So kindly fix/update TsForge accordingly.
It indeed no longer works in 26100.4188. Code: Microsoft Windows [Version 10.0.26100.4188] (c) Microsoft Corporation. All rights reserved. C:\TSforge>TSforge.exe /zcid 6c4de1b8-24bb-4c17-9a77-7b939414c298 TSforge (c) MASSGRAVE 2025 Stopping sppsvc... sppsvc stopped successfully. Writing TrustedStore data... Activation ID: 6c4de1b8-24bb-4c17-9a77-7b939414c298 Installation ID: 652768582096421447545260762377062532636215286455544400263973521 Product Key ID: bd489136-33c8-ecae-20af-a8338b58b771 Depositing fake CID status C004F031 Fatal error: System.InvalidOperationException: Failed to deposit fake CID. at LibTSforge.Activators.ZeroCID.Deposit(Guid actId, String instId) at LibTSforge.Activators.ZeroCID.Activate(PSVersion version, Boolean production, Guid actId) at TSforgeCLI.Program.Main(String[] args) C:\TSforge>
M$ started to fixing things I hope that they don't break anything on OSes before 10 (but these are without support now)
We are aware, fix is being implemented. It's caused by a bug in sppobjs.dll, and there's not much reason for them to backport this to 10. I've TSforged my main, so I will know when any update affects Windows 10.
OSPP based Office: Physical store is stored in the registry in a format that has not yet been reverse engineered (Tsforged). What's a reason?
Something is blocking that, iirc the isp or something else in your environment. I was only asked to test it