2. In registry [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing], replace (as TrustedInstaller) Professional with EnterpriseS How can I not find this one？
2. In registry [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing], replace (as TrustedInstaller) Professional with EnterpriseS How can I not find this one？
1. Export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing to 1.reg. 2. Edit 1.reg and replace all Professional string with EnterpriseS. Then save. 3. Import 1.reg.
The fatal factor lies in: Up to RS3: ProfessioanlWorkstationEdition Branding-ProfessioanlWorkstation Editions-ProfessioanlWorkstation ProfessionalWorkstation-License RS4 preview (17083): (License Switch - This is why a RS4 SKU can be upgraded by another SKU. Not magic, simply License Switch.) ProfessionalWorkstation-License How about 1803 RS4 release? unknown. Hint: People know mum/cat are necessary for cheating Windows and thus installing a package to other version. But they nevert know converting a SKU needs the cat being existent in C:\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}. Good luck.
thank you for this trick but could you please tell me what you meant by "1. Install Enterprise LTSB certificates (packages)", which certificates or packages are you exactly talking about ?
[Main package] Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.14393.0 [Sub package] Microsoft-Windows-Branding-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.14393.0 Microsoft-Windows-Editions-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.14393.0 Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Default-Package~31bf3856ad364e35~amd64~~10.0.14393.0 Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-License-Package~31bf3856ad364e35~amd64~~10.0.14393.0 (0ptional) Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-GVLK-Package~31bf3856ad364e35~amd64~~10.0.14393.0
This method of professional workstation upgrade, very helpful！ Validation in my professional workstation(RS3) to do, to achieve the purpose!
For SKU up to RS3, this is the most important: ProfessioanlWorkstationEdition (registry/mum/cat). And remember what I said: "converting a SKU needs the cat being existent in C:\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}."
You need to learn to use Aunty Mel's Cheap And Nasty SxS Package Extractor and capture the packages firstly. Or install directly from install.wim or installed System (This is another topic).
@xinso : could you please take a look at this previous post of mine ? => here i asked some clarification about this scenario but haven't got any response until now so if you could answer it, that would be nice
Q: For example : can we use this trick in this case (win10 home => win10 LTSB N 2016) ? A: Yes. This is good old trick people usually do. And you can do Cross-Language/Cross-SKU (or both) Upgrade and downgrade. e.g. Upgrade from zh-TW Home to en-US Pro: Windows Registry Editor Version 5.00 [-HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\MUI\PreinstalledLanguages] [-HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\MUI\UILanguages] [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\MUI\UILanguages\en-us] "LCID"=dword:00000409 "Type"=dword:00000111 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion] "EditionID"="Professional" e.g. Downgrade from 16299 to 15063 In addition to what mentioned above, replace 16299 ISO\sources\install.wim with the one of 15063. But that old method needs time, and the risk of upgrade failure or system corruption.