Hmm... You could try making a reg add runonce to modify the protected reg key. Example: make a script that has the exact reg mod. call that script regmod.cmd or something. then do a reg add runonce to run regmod.cmd The effect would be to elevate the permissions since it's run by the system and not the user.
...you have no idea what kernel protected means for this key. try to change and you will see it will be restored instantly. there is no chance for simple editing,
I see. Well then, why are you bothering with an online conversion effort if you cannot modify the files post-install?
So... may I missed some Info... If you convert your edition the ProductPolicies will be updated to the final/last SKU you want. If you type in your ProductKey than you get your regular Windows Edition and therefore your updated ProductPolicies. It's flexible to the SKU. It's not a/the fixed Value from your initial Edition, but some features like WMC have a license entry and are declared as restricted. There are possibilities to even 'break' the protected system but than you lose some regular funcationalities like applying updates that contain xrm-ms files. They will fail (that's all I know so far). @Tito ... this converter only switches the EditionID registry. I read that you can reinstall your windows over your old/eval edition but this is a complete reinstall. This is way different as you only switching 1 Packages and adding about 2-3 important ones.
Hm... this relates to another issue. The resources are included but the packages seems to be unstaged. Now we have to figure out how to (re)-stage it again.
Hehe. won't go that deep I took a deeper look and found some interessting information in "Component Based Servicing\Packages" there is a Subkey for each superior Package (offline loaded Reg-Hive) called "Owners" . While runtime this Subkey does not exisit and also with alle permissions it's hidden for me (so far). I don't understand how this is possible as I also can create while runtime this subkey with the same name. Unconfirmed guessings: Every superior Package has a entry Owner for which Windows-Edition the Packages get applied (CoreEdition, ProfessionalEdition,ProfessionalWMCEdition) If a entry is not found (CoreEdition) for the Package, than it won't be applied as it's not bound as the Package is not realted to the Edition (Core). Now the Idea is to insert the Edition (Core) into the Owners Subkey and than reapply (entering ProductKey (again)) the SKU to get the features / Package alive. My interpretation of "CurrentState" for each superior Package is 40 = unstaged, 70 = staged.
I think there are to ways for adding gpedit.msc and so on to core edition.. One easy (with overhead - files you already have) and one pretty difficult (no files, just some kind of complex script) But anyway... this relates to the point that my compares aren't good enough to fully qualify / convert any SKU into another. Therefore I need some testers! My compares are based on physical non-existing files, not disabled features. This also excludes so far (easy way) to enable them instead of reappying them as a seperat redundant package (not tested yet). ATM my recommendation would be anyway Enterprise as a basement and than adding the license informations from PRO/VL/CORE.