Recent content by wabbit

I did try updating a Rufus made window 11 usb. using the update script, just to see what happens. Rufus already added the latest CA 2023 bootloader to the main ntfs partition of the usb. The 1 MB FAT rufus-boot partition could not be written to because that partition was write protected.

Running the dism /online /Cleanup-Image /RestoreHealth was a bit slower than usual. Otherwise, all seems fine for now on 3 machines.

If I were in this situation, I would seriously consider getting a new PC. The other option would be to just disable secure boot until I get a replacement PC.

It does offer to install the Windows UEFI CA 2023 certificate. My usbs done with version 4.14 worked fine on all my systems, including a new HP laptop. The issue I had was with the new beta version that I was testing.. Here is the partial screenshot of running one of @garlin's Check_UEFI scripts:

A follow-up on my previous post #50. I did make a windows 11 usb from a windows 11 iso, 25H2-8653. The usb was GPT and rufus made a 1 mb FAT partition that's the RUFUS_BOOT partition that load the ntfs driver and the rest of the usb was NTFS. As in post #50, I applied the CA 2023 certs, but...

I just downloaded the latest beta and made a usb. Chose to add t023 boot files. After running one of Garlin's scripts to check boot media, the RUFUS-BOOT partition of the usb had the MS Corp UEFI CA 2011 cert. Checc screen shot that show partial results:

The latest ISO from using the MCT is 26200.8653. The windows version after the update on Patch Tuesday is 26200.8455. Just a few digits off.

@garlin I've updated my Macrium X boot media, sometimes a real PITA. I.m just waiting for Macrium to update its software where we can make bootable winre rescue media without having to constantly manually update it with the new CA 2023 certs.

Got one machine done. Update failed on the second machine. Attempted to download from the microsoft update catalog web site, but that site isn't loading for me. Maybe I'll try later. I Think the servers are very busy.

I got the SBAT key in the registry on the HP laptop. I just ran it from a command prompt and opted out. I'm lot likely to ever use Linux on that laptop.

On an HP laptop I recently bought, it doesn't show \secureBoot\SBAT in the registry either. The system has the May 26 preview update. After I got this laptop, it got the latest bios update from HP. Apparently, the system has the required CA 2023 certs. My other 2 systems have the latest...

The latest download using the MCT is windows 11 25H2.8457. It took me a bit to install the latest preview update. The latest preview update is 25h2.8524

If just putting the windows installation files on the usb only, a 16 GB usb should be fine. Even an 8 GB usb would work fine for now, but with the size of the install.esd ever increasing with each release, a 16 GB usb is a safe choice.

I had similar issues while updating 2 of my systems. Running sfc found errors and repaired them. Running DISM analyze, says the component store is repairable. Ram DISM Restore health, which took a long time, but eventually finished.

I have a Geekom mini-PC and a Dell Inspiron desktop that can boot from NTFS formatted USB drives using the GPT partition scheme. Geekom recommends creating the install media with NTFS. The windows 11 iso's have had the install.wim file in excess of 4 GB, in which that would need to be split to...