ADK to burn ISO doesn't work.

[AlterNate37]

What is the bug about?
Please describe the bug you're experiencing. Examples:

I've finished removing what I wanted to remove, and integrating drivers.
I committed and unmounted.
I used the ISO creation tool, looked for the unmounted image, selected it, chose the architecture, and the destination.
I clicked on create and there was an error saying Property AdkInstallation does not exist at path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount
I went in Regedit, looked for the WIMMount folder, right clicked on it, created the string "AdkInstallation", given it as a value the path of the ADK folder, or of the oscdimg folder, or of the oscdimg exe, and nothing worked. This time the error message was that ADK is not present.
Yet, it is.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

[CodingWonders]

ADKInstallation is not a string value, but a DWORD. You set it to 1. Also, could you provide a bit more info regarding your ADK installation?

[AlterNate37]

Fuck COPILOT for telling me that it had to be a string.
But anyway why is this even so complicated in the first place?
When I install the ADK from the link you provide at the bottom left of the ISO creation window, this should automatically create a registry entry.
Is this the "expected behavior"? Having to create the registry entry manually?

What else can I tell you about my ADK installation?
I followed your instruction, which aren't very detailed tbh. I clicked on the link, downloaded, left the default selections but added the compatibility one just in case on Copilot's recommendation.
Error.
So I also downloaded the PE, but still error.
I uninstalled them both and reinstalled them "as an administrator" and this time in ADK I selected ALL options.
Still error.

I will try with DWORD and let you know.
I really shouldn't do this at night, it makes me more angry than usually when I lose hours while I'm already so tired.
Damn.

[CodingWonders]

this should automatically create a registry entry.

The program is supposed to detect the registry value at startup and create it automatically. Included with it is a registry file that you can import:

Windows Registry Editor Version 5.00

; Set registry to let DISMTools detect Windows ADKs from Windows 11 onwards (ADK MUST BE INSTALLED BEFORE MERGING THIS KEY!!!)
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount]
"AdkInstallation"=dword:00000001

The link simply redirects you to the ADK download page.

Keep this issue open for any advancements.

[AlterNate37]

Please define "is supposed to detect the registry value at startup and create it".
If it detects it, it means it exists? So, why does it have to create it?
Anyway, it didn't.

New error now, see attachment...

[AlterNate37]

In case it plays any role: it's Win11 Pro 64, EN US, 24H2 (10.0.26100.1742) downloaded directly from Microsoft.
If I should use an ISO from UUP Dump instead, please tell me.

[CodingWonders]

Please define "is supposed to detect the registry value at startup and create it". If it detects it, it means it exists? So, why does it have to create it? Anyway, it didn't.

New error now, see attachment...

This new error is caused by this PE Helper not being compatible with your ADK.

You see, your installed ADK (which I presume is 10.1.26100.2454) changed some things around in order to add support for new boot binaries that contain new certificates. Rather than sticking to what worked, they did the following:

• Boot binaries are no longer in a folder called fwfiles, but they're now in bootbins
• Another environment variable is created by CopyPE (which is the bit that is failing in the screenshot you attached) because DISM is now called simply to extract boot binaries

DISMTools 0.6.1 Preview 3 added support for this ADK. Try with that version.

Do note that this version has an issue with the PE Helper that occurs if you have an earlier ADK, but since you have the latest one, it should work fine.

I spent an entire day working on the PE Helper to add support for this ADK and the new boot binaries.

Now, your initial question. It is supposed to detect the registry value and ask you if you want to create it. I admit that the message that is shown is a bit vague - I need to work on that.

[AlterNate37]

I see, it's a chain of fuck-ups :)
Shame on the Big Bang, after all that's where it all started. It could have stayed as void forever but no, it had ambitions.

Which message do you mean is vague?
If you mean a message about if I want to create the detected registry value (I still don't get why somethign whih has been detected still needs to be recreated), there never was such a message.
I simply installed ADK and then I started creating the ISO and it only gave me the "Property AdkInstallation does not exist at path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount".
AAAAHHH, you mean THIS.
Yes, it's very vague, nervingly vague (dword play).
It would be better if it says "the DWORD AdkInstallation in the path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount does not exist. Do you want to create it or do you prefer to give up on the ISO and go to sleep?".
And then it should also explain that the value of such dword has to be 1.
This would have been a time saver and nerves savior. IF the ADK dudes hadn't decided to mess with your day and my night.

I'll try the preview and keep you posted.

[AlterNate37]

Hombre, I don't find the pre-release 3.
I did find your "post" about it with the timeline of what you did, but I don't find the download...

Ah, I see, it's called v0.6.1_pre_2521 but it's actually the 3, I was expecting it to be called 0.6.1 Preview 3 (or 0.6.1_pre_3).
Thanks God there is still coke left. (the beverage)

[CodingWonders]

Hombre, I don't find the pre-release 3. I did find your "post" about it with the timeline of what you did, but I don't find the download...

https://github.com/CodingWonders/DISMTools/releases/tag/v0.6.1_pre_2521

[CodingWonders]

I see, it's called v0.6.1_pre_2521 but it's actually the 3, I was expecting it to be called 0.6.1 Preview 3 (or 0.6.1_pre_3)

That's the release tag. Anyway, did it work?

[AlterNate37]

No.
There's no entries in the Architecture drop list of the ISO creation tool, so I can't choose an architecture and the creation fails immediately.

[CodingWonders]

No. There's no entries in the Architecture drop list of the ISO creation tool, so I can't choose an architecture and the creation fails immediately.

That's weird. Can you check the directory structure of \Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment? I'm interested in everything inside that directory