Recent content by arrowflash

Just giving my two cents. What I can tell OP is that in terms of legacy software compatibility, even very old software from Windows XP and Windows 9x days, Windows 11 24H2 is pretty good. Better than I expected, basically on the same level as Windows 10 22H2. I'm talking only app software...

Okay, I got it! Here's what I did: >Mounted boot.wim using dism >Loaded <path_to_mounted_image>\Windows\System32\config\SYSTEM hive file into regedit >Added the Labconfig registry entries >Unloaded the hive from regedit >Saved changes to the image with dism /commit-wim...

I'm perfectly willing to use this approach. The only problem, is that I'm a bit of a noob when it comes to editing offline registry files, and I don't know what registry file I should edit in the mounted boot.wim. If you could guide me through this or point to some tutorial, I'd be grateful...

By the way, a bit of googling shows other people who had the same issue in the past, as far back as with Windows Server 2008 R2. No clear answers or solutions in any of the cases. I kind of give up and going to look for another workaround. Since the only thing I really need autounattend.xml for...

Yes, I've seen and even bookmarked this. This is the biggest head-scratcher. According to MS's documentation, this shouldn't be hapenning.

I managed to enable the legacy setup, using the winpeshl.ini in boot.wim method. Unfortunately, using the legacy setup didn't fix any of the issues I'm having. The issue is definitely related to the setup process, though. When the image is ready for deployment (after running sysprep...

Good to know. As for the standard place, unless it's supposed to have been changed, I thought it was \Windows\Panther? At least that's how it's set up in my working install.wim images. When you point an answer file somewhere else in sysprep (like /unattend:c:\deploy_win.xml), it automatically...

I see. Looks like I'll have to mess with the boot.wim to force legacy setup then? Bummer. Wonder if using legacy setup can fix the other issues?

Update: It really was a parsing or formatting error! Windows is really finicky about this. I decided to use SIM to recreate the answer files, with exactly same config, and the boot issues ceased! Now I can get into Windows 11 Setup with the hard requirements (TPM, Ram, Secure Boot, etc)...

I have tried using the legacy Setup (loading it before the other commands in load order), but same thing happened: Either way, I'm also beginning to suspect some formatting or parsing error...

When I meant reboot loop, I thought I had explained pretty clearly: I mean when booting from a newly created .iso with the autounnatend.xml in its root dir, and the sysprepped install.wim. After the system completes the BIOS checks and boots the .iso, as soon as WinPE starts, a command prompt...

Thanks, but this is exactly one of the things I already tried, as I detailed in step 3: The only thing I haven't tried is moving it to \Windows\Panther\unattend.xml instead of autounattend.xml. I'll give this a try, who knows.

Since the Windows 8 days and with multiple Windows 10 builds up to 22H2, I've always been building custom sysprepped, generalized install images using answer files and copyprofile feature, always with the same method. Clean install in a VM, enter audit mode with Ctrl+Shift+F3 during OOBE, make...