Thanks for the reply. Unfortunately still does not work I'm really not sure what the problem is. Windows 10 Pro installer boots up fine.
Or use windows 10 pro installer and replace install wim with ltsc Lenovo model please ? With cpu model
Oh what a s**t! It is no more possible to use new Windows 11 icons in versions of Windows 10 LTSC 2021 thanks @M$FT
Thanks - Let me try this! Is it just as simple as creating the installer with the windows media creation tool and copy/pasting the wim with the one from the ltsc iso? It’s a Lenovo 14w (model 81MQ) with an AMD A6 9220C
Really sorry for the late response. All I did was run setup from the IoT package linked in the OP and the results were as described. Perfect, no issues still activated, but as I said IoT was not installed the non-IoT version was installed. I didn't even disable ESET or kill any tasks besides Comodo. I installed on a cloned drive so I really didn't care what happened or if it was successful was just experimenting and it has become my daily driver now. I have no idea how you were in a position where it was requesting a new key. I see others have said you need a key but you def do not. As a suggestion if your still stuck; activate your 2019 install with KMS 8.4 then try to update. Even though everything was working perfectly I stilled played around with activators and tried KMS_ALL which did not enable IoT, then tried the one that starts with an "L" that didn't enable IoT either. I didn't even care about IoT just wanted the challenge to enable it. Which I failed to do lol. So I settled on Mephistoooo2's activator, KMS 9x, and have 2038 enabled on Windows and the 180 day task enabler for Office 2019.
Keys are only needed for upgrade scenarios (when MAK keys are used) and even then it should easily be circumvented by slmgr -ipk Retail or KMS client key or a working ei.cfg. When you did select to install the IoT version then the IoT version was installed, by using a KMS activation it turned into a VL product and the IoT install was turned into non IoT. Only HWID or probably a MSDM will activate IoT as IoT (check my sig for hwid activation tool). To be able to activate office on an IoT install you can use KMS_VL_ALL, it should skip the hwid activated IoT but to be sure set it to only activate office and all should work fine.
I tried this, it didn't work in my case, KMS_VL_ALL did not convert to IoT. I really don't care about IoT over non IoT, as a matter of fact it could become problematic for me being a hardware swapper. Thanks Enthousiast
You mean IoT to non Iot. You mean when hardware swapping the HWID could be gone, that only should happen with exchanging the mainboard/lan.
All new updates: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-668#post-1712134
Updated the 1904x Updates Overview: https://forums.mydigitallife.net/th...-21h1-2-vb_release.80763/page-16#post-1571109
This may be a stupid question, but the Windows 10 Pro bootable USB has install.esd while the 2021 LTSC one has install.wim- can I just delete the ESD and copy the WIM? My understanding is that the ESD is just more compressed than WIM. Thanks!
Microsoft Edge completely removed from image using NTLite. Cumulative update KB5008212 re-installed the bastard.
hmm I'm having a big problem! when installing KB5008212 now in the afternoon this update is not processed correctly accusing the error: "error code 0x800F0984". I don't know what to do... but i found out it's something related to modified iso's has anyone here also observed this problem today? Windows 10 LTSC 2021 x64 ISO modified by myself and without any installation errors... EDIT: PROBLEM SOLVED
I am gonna test with Newest one and I have the Tools that does not need KMS crap, I am using other kind tools...