[ARCHIVED] Windows Editions Reconstruction Project

@acer-5100 I don't understand. I thought you indicated it was better to use 25398 IoT Enterprise LTSC That's why I'm trying to get this to work. I already did a test with 26100 and it installed and activated fine.

 

I mean use 25398 but activate it as 26100. It' easier, solves the hyper-v problem, and you gain multiple rdp connections in one stroke, and 5 minutes of work.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

So what's the point, you're telling me that NOT doing what I suggested didn't work?

Use the SKU you like, THEN use the corresponding key from 26100 !!!!, not the one for 25398, then use massgravel

Is that a valid reason to have it broken? You may not need HV now, but you likely need it in the future, everything is based on HV nowadays, WSL2, WSA, VBS, Containers and so on

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Take your time and read what's already explained. Hyper-V is broken when you install updates, enabling it or not is up to you. But if you enable it after updating with CUs it doesn't work, that's all

Come on!! It's tree steps and you missed at least one.

What would you do if you had to to something complicate like 15 steps?

So reread my instructions.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Test 25398.830 Windows 11 IoT Enterprise LTSC amd64 en-US (for Volume-MAK)

Code:

------------------------------------------------------------
Set IoTEnterpriseS key
------------------------------------------------------------

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.25398.830


Error: 0x8a010001

The specified product key could not be validated.
Check that the specified product key is valid and that it matches the target edition.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

============================================================

Test 26100.461 Windows 11 IoT Enterprise LTSC (Volume-MAK with Edge without Store) amd64 en-US

Code:

Deleted for uncertain if it is genuine key

[Credits]
Sum_Ting_Wong

 

You need to login to view this posts content.

 

So I was right they are just 3 steps, and you managed to skip one

 

Yes confused people tend to do things like that. I'm bad at connecting the dots.
Now that the activation problem seems resolved for me, will this reconstruction work with Windows Update or are more hacks needed?
The reason I ask is only

Code:

Windows Malicious Software Removal Tool x64 - v5.123 (KB890830)
Update for Windows Security platform antimalware platform - KB5007651 (Version 1.0.2402.27001)

are offered. I don't see a CU for April.