I remember one time, one of the guys I was working with was working on a PC. He has done some things with it and when he plugged it in and turned it on, there was an actual flame jet shooting out of one of the chips. I never saw anyone unplug a PC faster than that LOL. Of course the customer ended up just buying a new PC at that point. They had the option of getting a new motherboard but chose not to.
24H2 Official ISO Don't support custom wim file
Solved
Windows
-
@DownPW Very odd indeed - particularly as it works with the previous version without issue. My only thoughts at this stage in the absence of any sane log file for examination is a compatibility issue, or the inability to access the EFI partition.
-
It’s incomprehensible and I’ve been wasting my time on this for 2 days: thanks Microsoft…
Personally I think that Microsoft has changed something on its installation ISO (the graphical interface is different) which means that the customized Wim file does not work and it does not seem to be properly documented.
It is specified that the ADK of May 2024 is compatible with 24H2
Or the way I capture the image or the way to make the ISO with ADK is different for a 24H2 maybe, but likewise, I have not found anything on that.
The capture of the PC that I made is the capture of an OS in 24H2 and I use an official ISO of a 23H2 to make the ISO with the captured Wim file.
I have test with secure boot Enable and Disable on BIOS and same result
It’s a hybrid operation but it’s the only thing that works for now because I have a hundred machines to deploy soon and that’s how I worked before.
Unless I have another method of deploying 24H2 that would work I don’t see.
-
@DownPW said in 24H2 Official ISO Don't support custom wim file:
It’s a hybrid operation but it’s the only thing that works for now because I have a hundred machines to deploy soon and that’s how I worked before.
Are you deploying this image to new machines, or upgrading existing ones?
-
@phenomlab said in 24H2 Official ISO Don't support custom wim file:
Are you deploying this image to new machines
deploying this image to new machines (same machines)
-
@DownPW sorry. Same machines, or new machines? You seem to have specified both
-
Sorry, I have 100 machines, same model, same material = New machines
-
@DownPW Whilst this sounds kinda dumb, the hardware is supported, yes?
-
@phenomlab said in 24H2 Official ISO Don't support custom wim file:
@DownPW Whilst this sounds kinda dumb, the hardware is supported, yes?
affirmative no problem !
-
@DownPW thought that would be the case, but wanted to check. I guess the only “real” way (temporarily) around this issue is to issue 23H2 version to the machines, and upgrade them to 24H2.
Not ideal, but a “workaround” for the time being.
-
undefined phenomlab forked this topic on
-
So in fact there is a new installation interface (GUI) with the new ISO of 24H2.
A custom.wim doesn’t work with this one.
On the other side, I hadn’t seen it because it’s not very visible but we have a link to activate the old interface and there it works without problem with her !!
In short, thank you Microsoft & f**k you !
-
undefined DownPW has marked this topic as solved on
-
@DownPW said in 24H2 Official ISO Don't support custom wim file:
In short, thank you Microsoft & f**k you !
That’s typical! I’ve seen this before with Office365 actually - the new admin GUI doesn’t work properly, but the older one does. Really frustrating, and I feel your pain with this one. I must admit I couldn’t stop laughing when I read the line above. That’s exactly how I feel on almost a daily basis with Micro$oft.
-
@phenomlab said in 24H2 Official ISO Don't support custom wim file:
I must admit I couldn’t stop laughing when I read the line above. That’s exactly how I feel on almost a daily basis with Micro$oft.
I believe we are all in the same boat on this subject!!
they are tiring
-
@DownPW Very tiring. Seems to happen more often than not.
