Thank you! Who would have thought the CMDShell GOAT is also a PowerShell ninja!! The first more complex code is perfect for the Inbox key (System apps) The second simple code gathers it all up, Inbox & Deprovision keys and UWPs. Super comprehensive. Very cool.
@Enthousiast I'm having the same issue with update KB5044384, I did tried a lot of fixes, but no go. Could you please explain a bit the possible cause you mentioned in this post and how to fix it? Windows 11 IoT Enterprise LTSC Version 24H2 Build 26100.2033, no third party AV. Thank you for your time and help.
I am not able to reproduce the errors, so i can't test fixes either. Maybe run W10UI with the 2 needed updates (1742 and 2033, or try 2161 instead of the 2033 one) and see what the error is, when it doesn't work run W10UI in debug mode and maybe @abbodi1406 can make some sense of it.
You must be doing something wrong... Switching license between IoT Enterprise 2024 LTSC and Enterprise 2024 LTSC should work, updated or not. https://forums.mydigitallife.net/posts/1833792 Plese show screenshot of the cmd window in which you ran the slmgr command.
I installed the normal version, not the "N". Now it worked, using the CMD command. But in my previous installations I always inserted the key on the Settings not on the CMD, strange!!!!
License switching can be done by the Settings > activation > change product key but it's mainly done by using the cmd,
i am running win 10 pro on i5 6600, is it a good idea to run window 11 iot ent ltsc? as tpm 2.0 is not required in this built , or my system will get slow after some time ? should i stick to 10 pro only ? pls guide