Installation and Upgrade Download Official Windows 11 ISO file from Microsoft

garlin said:

Here's an improved version of my script:
1. If your drive is a Removable device, \sources\boot.wim is updated in place. You don't have to copy files around.

2. If your drive is a Read-Only device (like a mounted ISO file), an updated boot.wim is created in the same folder as the script. When the script is done, copy this boot.wim to your USB device.

Click to expand...

Thanks again,
this worked, I tried with Microsoft Build 29617.1000 on a USB installation media.
Boot.wim was updated in place. "Repair my PC" worked fine after the update.
According to Copilot there are more than just those 2 .dll files missing. If I compare the size of boot.wim of the Microsoft official ISO and the one built from UUP dump there are many more files missing.



People who diffed the two boot.wims found missing folders and packages such as:

• Windows\System32\drivers\* (several networking and storage drivers)
• Windows\System32\en-US\* (localization resources)
• Windows\System32\WinPE-StorageWMI.dll
• Windows\System32\WinPE-Scripting.dll
• Windows\System32\WinPE-WMI.dll
• Windows\System32\WinPE-SecureStartup.dll
• Windows\System32\WinPE-Fonts\*
• Windows\System32\WinPE-Rejuv\* (the modern recovery UI)
• Windows\System32\Recovery\* (extra UI assets)
• Windows\System32\drivers\USB\* (some USB class drivers)
• Windows\System32\drivers\NetAdapterCx.sys
• Windows\System32\drivers\WDI\*

abbodi mentioned you only need the two files to make "Repair My PC" work.

1. WinRE is actually an extended version of the base WinPE image. Most of the missing features can be integrated as Optional Components (OC's) using the Windows ADK PE Add-on's, with the exception of WinPE-Rejuv.

WinPE-Rejuv feature is only provided in the base WinRE image.

2. A properly installed WinRE will inherit all of the live system's 3rd-party drivers for networking and storage.

garlin said:

abbodi mentioned you only need the two files to make "Repair My PC" work.

1. WinRE is actually an extended version of the base WinPE image. Most of the missing features can be integrated as Optional Components (OC's) using the Windows ADK PE Add-on's, with the exception of WinPE-Rejuv.

Windows RE optional components​

WinPE-Rejuv feature is only provided in the base WinRE image.

2. A properly installed WinRE will inherit all of the live system's 3rd-party drivers for networking and storage.

Click to expand...

Yes, it opens the recovery menus, but who knows what other recovery functions are missing?
I hope Microsoft puts out an official fix.

Windows 11 version 25H2 build 26200.8875 now available to download as ISO or USB with MCT.

Brink said:

Windows 11 version 25H2 build 26200.8875 now available to download as ISO or USB with MCT.

Download Official Windows 11 ISO file from Microsoft

This tutorial will show you how to download an official Windows Server or Windows 11 64-bit or ARM64 ISO file from Microsoft. Microsoft provides ISO files for Windows Server and Windows 11 to download. You can use these ISO files to clean install or in-place upgrade Windows 11. The Flight Hub...

www.elevenforum.com

Find Build and Version of Windows 11 Installation ISO or USB

This tutorial will show you how to see full details such as language, edition, build, version, architecture, and more for a Windows 11 installation ISO or USB. A Windows 11 ISO file is a disc image file that can be used to create a Windows 11 installation USB or DVD to install Windows 11 with...

www.elevenforum.com

View attachment 177884

Click to expand...

Like the previous MCT this one still fails to show the recovery menus, when you hit "Repair my PC" it reboots to the main OS and never shows any recovery menus.

I still have to use the one created from UUP dump to get "Repair my PC" to work.

What worked for us...

Ran MCT and created a bootable USB.

Ran garlin's script .\Update_UEFI-CA2023.ps1 -BootMedia

Ran copy C:\Windows\System32\mobilenetworking.dll C:\Users\<User Name>\AppData\Local\Temp

Ran copy C:\Windows\System32\wlanapi.dll C:\Users\<User Name\AppData\Local\Temp

Ran powershell -ep bypass -f C:\Users\<User Name>\Downloads\Repair_My_BootWIM.ps1 E: (my USB drive letter)

Booted from the USB, and selected Repair. Loaded correctly with no reboot.

I ran a few of the Repair functions with no issues.

Banjoman301 said:

What worked for us...

Ran MCT and created a bootable USB.

Ran garlin's script .\Update_UEFI-CA2023.ps1 -BootMedia

Ran copy C:\Windows\System32\mobilenetworking.dll C:\Users\<User Name>\AppData\Local\Temp

Ran copy C:\Windows\System32\wlanapi.dll C:\Users\<User Name\AppData\Local\Temp

Ran powershell -ep bypass -f C:\Users\<User Name>\Downloads\Repair_My_BootWIM.ps1 E: (my USB drive letter)

Booted from the USB, and selected Repair. Loaded correctly with no reboot.

I ran a few of the Repair functions with no issues.

Click to expand...

Some extra steps to work around the bug.

Banjoman301 said:

Ran MCT and created a bootable USB.

Ran garlin's script .\Update_UEFI-CA2023.ps1 -BootMedia

Click to expand...

This step only replaces the boot file on the USB. But nothing else from the boot.wim or install WIM/ESD contents. So your USB is bootable from UEFI.

Banjoman301 said:

Ran copy C:\Windows\System32\mobilenetworking.dll C:\Users\<User Name>\AppData\Local\Temp

Ran copy C:\Windows\System32\wlanapi.dll C:\Users\<User Name\AppData\Local\Temp

Click to expand...

Don't have to perform these extra steps.

Banjoman301 said:

Ran powershell -ep bypass -f C:\Users\<User Name>\Downloads\Repair_My_BootWIM.ps1 E: (my USB drive letter)

Click to expand...

This script repairs the "Repair My PC" feature by grabbing the two previous files from the install WIM/ESD and transplanting them to your boot.wim. It will always extract the two DLL's as needed, so you don't have to worry about finding the files yourself.

Banjoman301 said:

Booted from the USB, and selected Repair. Loaded correctly with no reboot.

I ran a few of the Repair functions with no issues.

Click to expand...

Scripts worked as they were designed.

garlin said:

This script repairs the "Repair My PC" feature by grabbing the two previous files from the install WIM/ESD and transplanting them to your boot.wim. It will always extract the two DLL's as needed, so you don't have to worry about finding the files yourself.

Click to expand...

Actually, they didn't extract, and threw errors in the script.

garlin said:

This step only replaces the boot file on the USB.

Click to expand...

Correct.

And boot itself failed until I ran the update script.

garlin said:

Scripts worked as they were designed.

Click to expand...

Indeed they did.

Big thanks.

garlin said:

This step only replaces the boot file on the USB. But nothing else from the boot.wim or install WIM/ESD contents. So your USB is bootable from UEFI.


Don't have to perform these extra steps.


This script repairs the "Repair My PC" feature by grabbing the two previous files from the install WIM/ESD and transplanting them to your boot.wim. It will always extract the two DLL's as needed, so you don't have to worry about finding the files yourself.


Scripts worked as they were designed.

Click to expand...

I want to see how long it will take Microsoft before they fix this mess.
I just use the ones I created from UUP dump, they still work correctly.

Banjoman301 said:

Actually, they didn't extract, and threw errors in the script.

Click to expand...

If you see the errors again, post them for me.

OK. I think there's a race condition where one imagex doesn't finish before another one is called. Try this version (it adds a short delay).

garlin said:

Try this version (it adds a short delay).

Click to expand...

Unfortunately, it did not work.


Microsoft Windows [Version 10.0.26200.8875]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Jim>cd downloads

C:\Users\Jim\Downloads>powershell -ep bypass -f C:\Users\Jim\Downloads\Repair_My_BootWIM.ps1 E:
Updating boot WIM on E:

[ERROR] blob could not be assigned to a solid resource
ERROR: Exiting with error code 20:
An entry in the WIM's lookup table is invalid.
Scanning "C:\Users\Jim\AppData\Local\Temp\wlanapi.dll" (loading as WIM path: "\Windows\System32\wlanapi.dll")...
[ERROR] Can't open "C:\Users\Jim\AppData\Local\Temp\wlanapi.dll" (status=c0000034): Object Name notfound
ERROR: Exiting with error code 47:
Failed to open a file.

Performing clean-up on boot WIM.

"E:\sources\boot.wim" original size: 592488 KiB
Using LZX compression with 4 threads
Archiving file data: 1349 MiB of 1349 MiB (100%) done
"E:\sources\boot.wim" optimized size: 590390 KiB
Space saved: 2098 KiB
Remove-Item : Cannot find path 'C:\Users\Jim\AppData\Local\Temp\wlanapi.dll' because it does not
exist.
At C:\Users\Jim\Downloads\Repair_My_BootWIM.ps1:106 char:5
+ Remove-Item "$TEMP_DIR\wlanapi.dll","$TEMP_DIR\mobilenetworking.d ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (C:\Users\Jim\Ap...emp\wlanapi.dll:String) [Remove-I
tem], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.RemoveItemCommand

Remove-Item : Cannot find path 'C:\Users\Jim\AppData\Local\Temp\mobilenetworking.dll' because it
does not exist.
At C:\Users\Jim\Downloads\Repair_My_BootWIM.ps1:106 char:5
+ Remove-Item "$TEMP_DIR\wlanapi.dll","$TEMP_DIR\mobilenetworking.d ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (C:\Users\Jim\Ap...enetworking.dll:String) [Remove-I
tem], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.RemoveItemCommand

C:\Users\Jim\Downloads>


The only way it did was after I manually copied those two DLLs from System32 to AppData\Local\Temp...

Microsoft Windows [Version 10.0.26200.8875]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Jim>cd downloads

C:\Users\Jim\Downloads>powershell -ep bypass -f C:\Users\Jim\Downloads\Repair_My_BootWIM.ps1 E:
Updating boot WIM on E:

[ERROR] blob could not be assigned to a solid resource
ERROR: Exiting with error code 20:
An entry in the WIM's lookup table is invalid.
Scanning "C:\Users\Jim\AppData\Local\Temp\wlanapi.dll" (loading as WIM path: "\Windows\System32\wlanapi.dll")...
578 KiB scanned (1 files, 0 directories)
Scanning "C:\Users\Jim\AppData\Local\Temp\mobilenetworking.dll" (loading as WIM path: "\Windows\System32\mobilenetworking.dll")...
136 KiB scanned (1 files, 0 directories)
Using LZX compression with 1 thread
Archiving file data: 714 KiB of 714 KiB (100%) done

Performing clean-up on boot WIM.

"E:\sources\boot.wim" original size: 594543 KiB
Using LZX compression with 4 threads
Archiving file data: 1350 MiB of 1350 MiB (100%) done
"E:\sources\boot.wim" optimized size: 590658 KiB
Space saved: 3884 KiB

C:\Users\Jim\Downloads>

Additionally, Windows can't open wimlib-bin.zip.

I was able to extract the contents with 7-Zip.

Looks like it just contains some licensing and readme files, but if you're trying to extract anything critical anywhere else, it could be a problem.

Its sounds like either there's a security problem, where wimlib-imagex is being blocked.

Here's the script's flow in a nutshell:
1. Check if your AppData\Local\Temp has an existing copy of wimlib-imagex.exe. If not, download it from the website and extract the EXE and one DLL to AppLocal\Temp.
2. Run wimlib-imagex to extract the two DLL's from your install WIM/ESD to AppData\Local\Temp.
3. Run wimlib-imagex to append those two files to the boot.wim.
4. Run wimlin-imagex to clean up (garbage collect) boot.wim.

What I would do is delete these files (as Administrator) from your AppData\Local\Temp:

wimlib-1.14.5-windows-x86_64-bin.zip
wimlib-imagex.exe
libwim-15.dll
wlanapi.dll
mobilenetworking.dll

garlin said:

Check if your AppData\Local\Temp has an existing copy of wimlib-imagex.exe

Click to expand...

It does, after the script errors out....along with libwim-15.dll

That's it.

The permissions seem correct. (SYSTEM, myself, Administrators have full permissions...owner is Administrators)

I'll need to read up on wimlib-imagex.exe...have not used it.

wimlib is kinda like a 7-ZIP for WIM files. It avoids having to mount and unmount WIM's just to do anything, which is a huge improvement in speed and not taking up so much disk space.

This sort of indicates (to me, anyway) a problem with the original boot.wim that MCT wrote to the USB flash drive...

[ERROR] blob could not be assigned to a solid resource
ERROR: Exiting with error code 20:
An entry in the WIM's lookup table is invalid.

I built a new bootable USB with MCT again this morning...I copied boot.wim to my hard drive, and use that to copy it back to \sources before each test run.

I dunno...may not be permissions at all. Everything else works correctly when it has those two DLLs in AppData\Local\Temp