massgrave/TSforge
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
WitherOrNot 2025-02-17 13:00:57 -05:00 committed by GitHub
parent c4919da1e7
commit 8aa1f9078d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -75,7 +75,7 @@ You can use the `/igpk` and `/zcid` options with the activation ID of the KMS Ho
### Why is Windows Vista not supported by any activation methods? ### Why is Windows Vista not supported by any activation methods?
Windows Vista contains a driver which holds a permanent [handle](https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/object-handles) to the physical store, even when SLSvc is not running. This prevents TSforge from writing new trusted store data while the system is booted without abusing access to another kernel driver. Although the physical store can be modified offline, this would require hosting TSforge in a [WinPE](https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/winpe-intro) image, which lacks many of the tools and APIs required by both MAS and TSforge. As of yet, this has prevented us from implementing Vista support. Windows Vista contains a driver which holds a permanent [handle](https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/object-handles) to the physical store, even when SLSvc is stopped after initial startup. This prevents TSforge from writing new trusted store data while the system is booted. There are theoretical workarounds to this issue, but they require an extraordinary amount of bug-prone, specialized code specific to Vista. For these reasons, we do not plan to support Vista/Server 2008.
### How do I prevent de-activation due to WAT on Windows 7? ### How do I prevent de-activation due to WAT on Windows 7?