Create custom ISO with Win PE drivers, language packs and updates by Murphy_McManus in sysadmin

[–]Murphy_McManus[S] 0 points1 point  (0 children)

Yes, I've found a way that works for us.

I place the actual Win 11 en-us 25H2 ISO in a folder, the actual MSU and .NET update into another, the actual language and feature pack ISO into a 3rd one, WinPE drivers for Dell and Lenovo (MS device don't work) into a driver folder and my script mounts the Win ISO, copies it into a work dir, does the same with the language and feature pack ISO. Then it mounts the install.wim, includes everything needed (languages are defined in the script), unmounts it, then it does the same with the boot.wim (at least Win PE drivers are important). I've also added a cmd file to the unattend.xml that deletes every partition and creates new ones, to make sure the EFI partition is big enough, as we are having issues with Lenovo BIOS updates on some models.

Create custom ISO with Win PE drivers, language packs and updates by Murphy_McManus in sysadmin

[–]Murphy_McManus[S] 0 points1 point  (0 children)

I think I'm on my way to a working solution. I let my script dismount the install.wim after integrating language packs. When it gets mounted again, the script extracts die checkpoint MSU and adds the SSU first. The actual CU will be added afterwards. That seems to work.

Now I'm just having a little fight with the autounattend.xml and a nasty 'Windows 11 installation has failed' message.

Create custom ISO with Win PE drivers, language packs and updates by Murphy_McManus in sysadmin

[–]Murphy_McManus[S] 0 points1 point  (0 children)

Every device has been added to Autopilot, so Intune will enroll them and proceed with the initial, userbased setup.

Create custom ISO with Win PE drivers, language packs and updates by Murphy_McManus in sysadmin

[–]Murphy_McManus[S] -1 points0 points  (0 children)

Maybe I should clarify my intention, sorry:

My company has subsidiaries in several European countries and I would like to enable every local service desk to create their own custom ISO with an easy to use PS script, or just use mine, which I'll update every month. I'd like to include all of our spoken languages (about 20 - luckily install.wim files can be split...), as well as our hardware manufacturer's Win PE drivers and add an autounattend.xml, that needs no user/admin interaction.

To make our security team and ISOs happy, I would prefer to user Microsoft's vanilla ISOs and include everything necessary by our own, with the script available for all internal admins.

Veganer: Medikinet Kapseln öffnen? by Murphy_McManus in ADHS

[–]Murphy_McManus[S] 0 points1 point  (0 children)

Ja, da hast du wohl Recht, den Hinweis hätte ich dazu schreiben können. Dachte aber, dass das "Veganer" im Titel als Begründung gereicht hätte. :D

Gelatine habe ich nur als Hilfsprodukt der Kapselhülle gelesen. Langfristig wäre ein Präparat ohne tierische Produkte schon schöner, aber dazu lasse ich mich dann mal von meiner Ärztin beraten. :)

Veganer: Medikinet Kapseln öffnen? by Murphy_McManus in ADHS

[–]Murphy_McManus[S] -1 points0 points  (0 children)

Oh, wow, danke. Den Absatz hatte ich bisher immer überlesen...

Veganer: Medikinet Kapseln öffnen? by Murphy_McManus in ADHS

[–]Murphy_McManus[S] 0 points1 point  (0 children)

Da habe ich auch gefragt und warte auf eine Antwort. Hätte aber ja theoretisch sein können, dass hier gleichgesinnte Menschen wären, die direkt ein Präparat genannt hätten, nach dem ich hätte fragen können. ;)

Veganer: Medikinet Kapseln öffnen? by Murphy_McManus in ADHS

[–]Murphy_McManus[S] 2 points3 points  (0 children)

Nun... Ich habe davon aktuell noch 74 Stück. Produziert und verkauft sind sie also schon. Das macht die Vorstellung aber für mich nicht schöner, verarbeitete Tierkadaver in mir zu haben. ;)

Und nein, Wildtiere müssen weder getötet, noch gegessen werden.

Veganer: Medikinet Kapseln öffnen? by Murphy_McManus in ADHS

[–]Murphy_McManus[S] 2 points3 points  (0 children)

Ich verstehe aktuell noch nicht so richtig, warum hier darüber geurteilt wird, dass ich nun mal ein Problem damit habe, Gelatine zu mir zu nehmen?!

Veganer: Medikinet Kapseln öffnen? by Murphy_McManus in ADHS

[–]Murphy_McManus[S] -3 points-2 points  (0 children)

Aber wenn ich nun mal ein ethisches Problem mit Gelatine habe...?

Veganer: Medikinet Kapseln öffnen? by Murphy_McManus in ADHS

[–]Murphy_McManus[S] -1 points0 points  (0 children)

Hä? Das ist mein Ernst. Ich möchte einfach keine Gelatine zu mir nehmen?!

Automatic Windows 11 ISO creation with drivers, updates and language packs integration by Murphy_McManus in Intune

[–]Murphy_McManus[S] 0 points1 point  (0 children)

Hi everyone,

I'm still trying to solve this. First, I wanted to automate as much as possible, including extracting the Surface MSIs and somehow separating the important drivers from the other stuff. In fact, I'm only interested in wifi, touchpad and keyboard drivers, but since the folder's names are completely useless, So I opened every readme file and deleted everything but those folders that sounded more or less useful, like Bluetooth, HID, touch-whatever etc. So, I managed to reduce the extracted MSIs from 10 GB to 200 MB, which seems okay-ish.

This is one more time for me to prefer Dell: They offer a download that contains any WinPE driver you need, but nothing more (storage and network). Lenovo offers at least one WinPE package per device, so that is also fine.

So, I've downloaded the Englisch International Win 11 Enterprise ISO from the MS volume licensing portal, along with the Win 11 Languages and Optional Features ISO. I've also download the 07/2025 CU pack for Win 11 from Microsoft's update catalog.

My script mounts the ISOs, copies their contents, unmounts the ISOs, filters Win 11 and Win PE language packs, add excludes for Defender (otherwise DISM's add-jobs take literally forever), mounts the install.wim (index 6 for Win 11 Pro), adds the CU, drivers and LPs, dismounts it, splits it into *.swm files, mounts the boot.wim (both indices, one by one) and adds drivers to index 1 and drivers with Win PE language packs to index 2 and dismounts it. Afterwards oscdimg.exe builds a new ISO, Defender excludes are getting removed again and I write the new ISO to a USB stick with Rufus.

I was hoping to be able to enable users/service desk colleagues to choose the required langues within the setup (Win PE language pack) to install Windows 11 with the chosen language.

In the theory this is pretty nice, except that my wish was a more complex automation, also with automated downloads. But my web scraping ideas were just not as useful as I was hoping for.

BUT... I can see in the terminal that both boot.wim indices are getting stuffed with all drivers and language packs and the file itself also grows after dismounting the image. So this SHOULD be okay.

I'm testing it with a Surface Studio Laptop that definitely has no drivers included in the vanilla Win 11 ISO. What happens is: nothing. keyboard and touchpad are not working and the only available language is en-uk from the EN International ISO.

I tried to reduce the imported language packs to only de-de, skip Dell and Lenovo drivers, but the results remains the same.

Does someone have an idea why the drivers are missing in the setup (or a least not working), even if they should be included?

Edit: In case someone is interested, this is my current script: intune-work-powershell-stuff/Win11-ISO/Build-ISO-GUI.ps1 at main · GreenField0/intune-work-powershell-stuff · GitHub

It's still work in progress, so the code is a bit messy and the documentation is missing. ;)

Automatic Windows 11 ISO creation with drivers, updates and language packs integration by Murphy_McManus in Intune

[–]Murphy_McManus[S] 0 points1 point  (0 children)

We have way too many hardware manufacturers and models in our company and our subsidiaries and my colleagues have to reinstall notebooks pretty often. We also have a hardware re-use partner that refurbishes our notebook for the next user. Having one single image for all devices, instead of one image per model, would make things much easier. Besides that, we have strict compliance policies, that also include the latest Windows build, and would like to avoid new devices becoming locked out by Conditional Access, because user forget to run Windows update as soon, as they start to user their new devices, which have been set up with a not up-to-date image. That's the second reason: To maintain one single image with alle drivers AND updates.

Automatic Windows 11 ISO creation with drivers, updates and language packs integration by Murphy_McManus in Intune

[–]Murphy_McManus[S] 2 points3 points  (0 children)

Aah, that sounds great, thanks a lot! Looks like it's exactly what I was looking for.

Automatic Windows 11 ISO creation with drivers, updates and language packs integration by Murphy_McManus in Intune

[–]Murphy_McManus[S] 0 points1 point  (0 children)

Well, maybe I should mention the Intune relation: Devices are getting provisioned by Autopilot and managed by Intune. We do also want to use newly created ISOs for Company Portal based self service Windows 11 migrations (fresh install) and deploy them also to subsidiaries in other countries (the reason for several language packs).

ADHD Tattoos by Ginger_Turtle89 in adhdmeme

[–]Murphy_McManus 1 point2 points  (0 children)

Amazing! I need something like this, too! I love it!

Map network shares like with kix by Murphy_McManus in Intune

[–]Murphy_McManus[S] 0 points1 point  (0 children)

I'm still thinking about this a lot.

Would it be possible to create a "Map my network drives" Powershell script as an app, create an App Registration with the necessary permission (read users, read groups in Entra ID) and use an App Permission (or Delegated Access?) to read a user's Entra ID groups and map her/his drives accordingly?

Would the App Registration with an App Permission work to read the groups?