So far, I have tested other system versions that can be successfully activated with TSforge: WIN11 24H2 、23H2、LTSC2024 WIN10 1507、1607、1709、1809、1909、22H2、LTSC2019、LTSC2021 WIN8.1 ENT EMBEDDED 8.1 ENT
it have intersting file in the package, PidGenX.dll can it help somehow generate one ? i think i have an idea to get an retail word key don't know if it will work, but i will give it a shot
pidgenx is also in windows, it can only validate keys, not generate one. all key data like public key/ranges is stored in pkeyconfig.
I don't want to modify the ISO, I just want to provide the Win8/8.1/2012/2012r2 retail version KEY and all CSVLKs on the TSforge official introduction page. Only by doing so can one feel at ease. @Windows_Addict
I strongly disagree!!!!! All retail versions of Win8/8.1/2012/2012r2 do not support GVLK and must enter a Key during installation.
Hello all, this topic is all about TSForge! Any talk about HwID, Ohook and other MAS-related stuff does not belong here. As you know, advertising MAS and talking about it in general (apart from the occasional mention) is not allowed, for not drawing unwanted attention. In short, the more you advertise it, the more that certain company will be arsed to fix the underlying issues.
Partially. There are pure Retail versions of Windows 8.x (all Core SKUs, ProWMC and maybe some Embedded ones) which are not officially KMS-capable. But they take lab KMSC keys (not listed on website) and an Emulator can activate it for a shorter period (30 days for 8.0 and 45 days for 8.1).
I am wondering if with TSforge on a OEM PC if you would need to disable secure boot so that the new serial key doesn't conflict with the serial key embedded in the UEFI? Or is the TSforge serial key an upgrade key that takes precedence over the embedded UEFI serial key. I am just wanting to avoid a serial key conflict. ... Also on a OEM PC, if you use the MAS method to upgrade from 10 home or pro to IoT, should you disable secure boot to avoid a serial key conflict in that scenario. Or would you possibly not even get to IoT during the upgrade if not disabling secure boot first?
The embedded firmware key applies to OEM:DM channel and will not interfere with TSForge (which usually uses MAK, Retail or OEM:NONSLP). No need to disable anything. Upgrading Home or switching Pro to IoT Enterprise should work likewise (but will have to be reactivated). Please note that IoT Enterprise is just a worse Enterprise SKU, Enterprise is preferred. The version everyone praises is called "IoT Enterprise LTSC", with the LTSC part being important.
@Carlos Detweiller Thanks for all the info. Yeah I'm using the IoT LTSC versions of 10 & 11 on several PCs, so I have that part straight. ... I was just asking the 2nd part of my question b\c several yrs ago I went to clean install 10 IoT LTSC on a 10S Mode laptop and I ended up with 10 IoT LTSC in S Mode (I kid you not), until I disabled secure boot and clean installed a 2nd time and then the laptop was unshackled from the serial key in the UEFI and I then finally ended up with 10 IoT LTSC not in S Mode.