I've loaded multiple different versions of WIndows 11 Pro on modern hardware (z590 mainboard, DDR4 RAM, etc.). Each install was clean (wiped the boot SSD each time). I was able to successfully load the OS each time but each time I was unable to execute any .exe, .cmd, .ps1 file/program/script. I get an error stating that there is no available associated program. I've used only clean ISO's downloaded from UUPDump and even one from MS MDT. All have June 2026 updates. I use a small autounattend.xml to create a local user account. Nothing removed/added otherwise. Very generic. I have not tried older ISO's but may as I have time. Does nayone out there have a clue? I'm at the frustration, pulling hair out stage. TIA
I did not notice any problems with the latest (Dutch) ISO's downloaded from Microsoft and June updated one from MAS. But that was on my old scratch/test Toshiba Satellite C50 and I3 3110M with Ventoy to bypass the TPM restriction. Things you could do/try: Verified the ISO hashes? Use a clean ISO without your autounattend.xml? Install offline and check if all is working and then update the system? You can use the oobe\bypassnro, which seems to work (again?) on the latest ISO's or the newer start ms-cxh:localonly to bypass the online account.
These hashes are never the same, the ISO is created locally, same for MDT if he means MCT. This happens when you have used the customapps settings in uup>iso conversion.
I use UUP Dump as well but where is this customapps located in the scheme of things? I have never seen this? Is this something you select when configuring the .iso? Thanks
BTW...I'll be getting back to work on this project this weekend and will report on my finding....thanks to all who replied...
Update - Downloaded a clean ISO from MS via MCT (26200.8653) and let MCT configure my USB stick. Created a generic autounttend.xml file to create a local user profile. Nothing else added or removed. All seems to be functioning a expected now. I have done some additional troubleshooting with the previous ISO's and autounattend.xml's. Noted that "%1" %* was missing from registry key HKEY_CLASSES_ROOT\exefile\shell\runas\command but adding that only partially fixed the issue. Run As Admin didn't function consistantly giving me the same missing file association error for some executables but not others. Doesn't seem to have a rhyme or reason. So, I still don't have a complete fix but do have more clues. Seems I'll be at this for a while longer but can at least get the one project out the door.