That post is locked and i want to change it but for that i need to first ask a staffmember to unlock the post, when i have time i will ask to unlock it so i can add more info. This is the pinned post: How to upgrade from Home/Home Single Language to Pro (or any other higher SKU) You should be able to do that. It's recommended because for some scenarios with systems containing a MSDM on which disconnecting was needed to have it go thru, Please give us some more info because that should not be caused by not disconnecting but mismatching ISOs or missing upgradepath. For more info about special upgrades: UpgradeMatrix.xml FiX Tool (Very Beta) & https://forums.mydigitallife.net/posts/1846462
Thanks for that. My progress so far: 1. Installed unupdated IoT ISO using gVLK: 2. Tried to activate using KMS38 (Yes. I only saw your reply after having done this ): 3. So what I now have is 4. So to get/convert to IoT, I need to update to 19004.7288 at least (since I'm only at 19044.1288) and reactivate with KMS38 (assuming I want to use KMS38)? Can you advise how to get the necessary updates? I'm kinda lost on what and where to get them. Thanks.
- I think you will need to manually install IoTEnterpriseS gVLK first - see Updates Overview https://forums.mydigitallife.net/th...-20h1-2-vb_release.80763/page-16#post-1571109 just install the LCU
I am used to KMS, and, having read up on the different options, I would prefer KMS38 over HWID if possible.
Please share your ideas on the following weird issue. There is a w10 pro system which is stuck on 1909, on 18363.1556 to be exact! It's user did not care until a few days ago that epic's app could not log him in anymore. How can I upgrade this to 22h2? Windows update just pops an error that it is missing critical updates and nothing more. Upgrading it from the iso of 22h2 leaves the "keep files and apps" option grayed out, so it is not possible to do an inplace upgrade with that iso. The same happens with the iso of 20h1 (2004), in case an upgrade to 19041 is needed first, before upgrading to the other 1904x versions The system's locale is greek (output of get-winsystemlocale), but the user's display language is english, so I used the greek versions of the forementioned isos.
I know. Like I said, it isn't really needed. I was just satisfying my itch.. Sorry to poke you though.
Are you trying to do an in-place upgrade while logged into windows or from the setup (from where you clean install windows)?. Edit: May be try resetting the PC first (Settings > Update & Security > Recovery > Reset this PC) and select the option to keep your files. After this try to do an in place upgrade.
While logged into windows. I do not want to just keep my files, I want to keep the apps as well because they are a lot to reinstall!
Did he use the correct ISO, the correct language and such, did he "tweak" the install in any way? When the correct ISO is used, the correct languae and such and it still doesn't offer to keep all then try to fix the ISO by this MDL tool and try again.
So, using your "FiX Tool," would I be able to migrate from Win 10 Enterprise 22H2, build 19045.4894, to Win 10 IoT Enterprise 21H2 LTSC? Or is that still not possible because the machine to be migrated has an OS newer than the OS to which I want to migrate?