How to create a custom image with multiple editions – Need Clarification

RobertX

Member

I am planning on making a multi-edition ISO of Windows 11 that has two Windows 11 Pro setups: one that pre-activates and one that asks for a CD key. While reading the above link, I am having trouble understanding the following quote:

– when you’re done with configuring each isolated image to your liking, make sure none is loaded.
Then Export them back into any ISO structure, the exact file location is relative in the target extracted ISO file structure .\Sources\Install.wim
When asked Overwrite or Append, choose No (Append).
Review the current status of images on the Source page, should be obvious how the images are stacking up inside the destination one.
You can right-click Delete any unwanted editions on the resulting image as well, especially unedited ones.

How do I export the WIM files back to the ISO structure?
 
I'm not trying to pirate or anything, this is purely educational.

How do I make a version of Windows 11 that automates activation without me asking, one that does for a CD key and uses that to activate and doesn't use a KMS activator and combine them both for selection in the beginning of setup?

Again, I remind you that I am doing this for educational purposes.

If I am out of line, I apologise and will not ask for help of such things again.
 
Maybe some answer here or use generic key in UnAttended for the Oobe session and user get asked to enter the (CD) license key after install.
 
Discussion of KMS activation borders on piracy, let's be truthful-- anyone who isn't a normal company or org won't have legitimate volume licensing keys. You can find help elsewhere on this topic.

When you create unattended answer files, the default is copying autounattend.xml which is shared by all ISO images. But you can embed a separate unattend.xml inside a image, which overrides the autounattend.xml.

1. Create your customized image. Follow my previous link for instructions on making a cloned copy.
2. Load one of the images. Rename this image to make it easier to identify. Right-menu -> Edit / Name
3. Enabled Unattended mode, and enter a working product key. Under the toolbar, check "Copy to install image".
4. Apply and process the image (which saves this answer file inside our image).

5. To confirm it's been saved, reload the image. Open the mounted image folder, and look for Windows\Panther\unattend.xml.

Capture.PNG

If you want to use autounattend.xml for the other images, make sure to check "Prompt edition selection" and uncheck "Copy to install image". Any images with a local answer file will only use its private copy, instead of the ISO version.
 
To export the WIM files back to the ISO structure after configuring each isolated image in Windows 11 using the Windows Imaging and Configuration Designer (ICD), you can follow these steps:

  1. In the ICD tool, go to the "Images" tab and select the images you want to export by checking the box next to each image.
  2. Click on the "Export" button at the top of the screen.
  3. In the Export Wizard, select "Custom Export."
  4. Choose a location to save the exported images and click "Next."
  5. Choose the option to export the images as WIM files and click "Next."
  6. Choose the location of the ISO file and select the "\Sources" folder, where the "Install.wim" file is located.
  7. Make sure to choose the "Do not overwrite" option when asked whether to overwrite or append.
  8. Review the current status of images on the "Source" tab in the ICD tool to ensure the images are stacking up inside the destination ISO file as expected.
  9. Right-click on any unwanted editions on the resulting image and select "Delete."
  10. Save your changes and build the ISO image.
This should export the WIM files back to the ISO structure and allow you to create a multi-edition ISO of Windows 11 with two Windows 11 Pro setups: one that pre-activates and one that asks for a CD key.
 
NTLite can perform this action without needing ICD. Which is overkill for most users since you need to install ADK to run it.
 
isaac.grifffiths24, I'm interested in hearing more, but I will PM you if I have more questions.

Better to not violate rules and play with fire.

Again, I apologise for the questions and I wish to stay for a long time.
 
He's explaining a different method for cloning images. None of those instructions help you with licensing. You can discuss normal product licensing, just no talk about KMS "activation" scripts.
 
Fine, I'll refrain from asking about activation.

I'll ask it a different way: is there a way to track what SKU a user selects such that SetupComplete.cmd would follow a certain course of action?

I have gotten quite a lot of scripts that are safe and legal, but I need to disable them post-install if a certain Windows version is selected.

Is that a better way to ask?
 
Last edited:
Setup won't record the name of the selected image, but you can tag images using a reg key.

Create your own key under HKLM\Software\RobertX, and have your script query its value. Load each image in turn, and integrate a different reg file holding the ID value into the image. The image is permanently tagged regardless of updates or removals. Repeat for all images.

When your Post-Setup script runs, it can query the embedded value. Since you're defining the values, there's no limit on what identifying info you can pass along to the script.

Code:
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\RobertX]
"Edition"="Pro-Licensed"
"Detail1"="Something"
"Detail2"="Something else"
Code:
reg query HKLM\SOFTWARE\RobertX /v Edition
 
Now, do I have to make a login called "RobertX" too?

Also, how would the installer know what to store depending on the option chosen? Wouldn't that still require keeping track of what the user is choosing?

The query part is easily understood.

EDIT: Let me explain my question:

Also, how would the installer know what to store depending on the option chosen? Wouldn't that still require keeping track of what the user is choosing?

What I mean is that how would each individual option pass the needed keys to the registry if it doesn't keep track of the version chosen?

EDIT: Never mind, I think I know.

Will report back.
 
Last edited:
OK, just two questions:

Should "RobertX" be the name of the registry, or can it be a folder?

If the answer to (1) is the latter, then,
Should the two REG files be the same name?
 
Never mind about that question either.

I just found out that when combining the two Windows 11 versions, the registry file is the same.

Should I implement the registry files when the images were still separated and then merge them?
 
You integrate one registry file to one image. Don't apply the same registry change across all editions, that defeats the purpose.
 
Every time I try to save a different REG file, it does it, but when I load another image, the same REG file that I used for one of the editions remains.

This is what I did:

Say I made two SKUs:

1. WIndows 11 A
2. WIndows 11 B

When I save the REG file for WIndows 11 A, it gets saved, but when I load Windows 11 B, the REG file that I made for Windows 11 A appears at Windows 11 B.

And I did merge the two install.wims to one install.wim.

How do I account for this problem?
 
Last edited:
Basically, what I'm trying to say is that when I merge the two install.wim files, I can't get either SKU to integrate different REG files.

That's all I have to say.
 
Basically, what I'm trying to say is that when I merge the two install.wim files, I can't get either SKU to integrate different REG files.

That's all I have to say.
Regs are directly integrated if using Integrate - Registry page.
If you're using Post-setup, then yes, you need to load install.wim in the isolated mode, more info here.

Regarding activation, Windows 10 and 11 automatically activate previously activated machines, I would not do anything to those editions, just leave them be with an empty product key and they will automatically properly reactivate when the machine is online.
 
Back
Top