Microsoft activation

[wx69wx2023]

**MAS 3.3 ** ������

**The Empire Strikes Back**
### **TSforge:**
- In Windows 11 build 27802, Microsoft introduced a bug that causes Confirmation ID cache validation to always fail, forcing validation directly from the stored Confirmation ID each time the license status is checked.
- To circumvent this bug, TSforge is used to set the current Installation ID to that of a known key that can be used to generate valid Confirmation IDs.
- For more information on StaticCID, check https://massgrave.dev/tsforge#staticcid
- From now on, the script will use StaticCID method (requires Internet) on build 19041 and later.
- KMS4k activation option is now added in the script.
- Thanks a lot to <@370676311653482497> for working on this.
### **Change Office Edition:**
- Added the option to switch the Office update channel between VL and non-VL.
### **All:**
- Various other fixes and improvements.

https://massgrave.dev/changelog

[Kerlingen]

I think it is a good guess that this is not some accidental "bug" introduced by Microsoft, but something done deliberately in order to break this type of activation.

It should also be noted that this "bug" does not only exist in some future "beta preview" version which most people will likely never install anyways, but has already been rolled out on all up to date Windows 11, Server 2022 and Server 2025 systems.