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.
Dunno about S Mode, sounds scary if it is so persistent. Yes, the firmware key matters when clean installing, as Setup reads it and acts accordingly. But outside of clean install, that key is dormant and doesn't do anything by itself. From what I know, you cannot upgrade from non-LTSC to LTSC and vice versa without doing some trickery. Both are different branches and on different media.
What are the installation keys for Embedded 8.0 Industry Pro and Embedded 8.1 Industry Pro? I don't want to destroy the original ISO. Embedded 8.0/8.1 Pro cannot skip input key!
In your case I would use the generic serial that MS gives away, for 8.0/8.1, for installing purposes (search for it). Then when you get to the desktop, permanently activate it with MAS.
8.1 Industry with update series (pro/ent) does not require entering a key during installation. cn_windows_embedded_8.1_industry_pro_with_update_x64_dvd_6052079.iso Spoiler But does the 8.1 Industry Pro RTM version require entering a key during installation? en_windows_embedded_8_1_industry_pro_x64_dvd_2707203.iso
about the missing single product key's in Latest C2R version, even for 2013 always store file's contain Office* cd-key it also work for windows system, some dll hold key's for all MS product's so, i will install, Windows 7, office 2010 and see what can we extract from them edit. nothing, intersting
Where are the files stored after using TSforge/dump in each system? Mainly targeting the retail versions of Windows 8/8.1/2012/2012 r2 and its derivatives, as the retail version cannot skip entering the key at all. Many users are unwilling to modify ISO HASH in order to maintain its integrity!
If just running "tsforge.exe /dump", its stored as dump.dat in the current directory. You can also extract \Windows\spp\store\data.dat (8.0/2012) or \Windows\spp\store\2.0\data.dat (8.1/2012 R2) from install.wim and use "tsforge.exe /dump out_decrypted.dat data.dat" to decrypt it. Usually the data.dat obtained by this method contains some default keys.
See if one of these keys work: https://forums.mydigitallife.net/th...microsoft-products.28669/page-273#post-792313
Where is dump.dat located on drive C? I am looking for retail keys for the following two products: en_windows_embedded_8_industry_pro_x86_dvd_1966344.iso en_windows_embedded_8_standard_image_builder_wizard_x86_dvd_1791542.iso