Search results

Okay, so i was wrong. Thanks to garlin who found the issue.

Put the new "install.wim" (Win11) into a Win10-sourcefolder. Win10-setup will install Win11 without any trouble.

Das einzige Problem ist, daß die "große" Festplatte (Partition) keinen Laufwerkbuchstaben erhalten hat. Den kannst Du manuell in der Datenträgerverwaltung hinzufügen. “The only problem is that the ‘large’ hard drive (partition) did not get a drive letter. You can add one manually in Disk...

Maybe hard to understand (for me as german either): en-US and en-GB are different languagepacks. You have to integrate both to enable these settings in NTlite. If only one of them is integrated the settings will always fallback to basic language.

Is there an "autounattend.xml" in the root of your ISO? Please show.

Please try out "Ventoy" instead of "Rufus": https://www.ventoy.net/en/index.html

Seems like you integrated the languagepacks only into boot.wim, but not into install.wim.

So mußt Du das einstellen: Configure it like that:

Du hast zwar das Autologon für "ClientADM" aktiviert, aber nicht den User "ClientADM" angelegt. You have enabled autologon for "ClientADM", but you have not created the user "ClientADM".

You got to config unattend-settings in WDS.

I`m setting "Dark Theme" with NTlite. After install dark theme is set (explorer, apps), but the desktop is still "aero" (light). Mostly i install with WDS/MDT, but even installing with ISO (in Hyper-V) the desktop isn`t set to that "dark" desktop picture. Desktop doesn`t change in Audit-Modus...

If you try/want to create a "golden image" for deployment to other clients i would prefer "Hyper-V" to all other VMs. "Hyper-V" is NOT able to pass-trough a lot of hardware - but that`s what we want. We need a "clean" image without any 3-party-drivers. "Hyper-V" has in fact 2 different options...

Use the boot.wim from "Windows 10" in WDS.

After a lot of tries (i´m working in a refurbish company as IT-Admin) i decided not to roll out an "up-to-date" Windows11 24H2. It is possible to enroll an "up-to-date" image, but it`s "old" two times per month due to new updates. I enroll a "basic 24H2" to all clients (including 9 languages)...

It makes no sence to me to integrate different languages and then skip the choice by "autounattend.xml".

Hi Nuhi, i`ll give it a try.

Okay, that`s it. I´m out. Seems like i`m talking to a little child.

Since Windows 11 24H2 i don`t use any "cleanup" (DISM++ or NTlite) anymore. It always brings confusion, WU-errors or other unexpected errors.

Every of your answers is only a short sentence. It`s now Post #26 and we really don`t know what you`re doing or what you want. So i ask a very last time: What do you want or what do you expect? If you integrate some languages and configure an "autounattend.xml" with NTlite the system will have...

And what did you expect? A language choice? Or do you want to configure the disks automated?