Recent content by garlin

Is your FAT32 a GPT? We have this crazy Venn diagram... USB Drives is looking at USBSTOR service (which is mostly removable drives). Previously I was using BusType USB, but people said that was missing devices... MBR + FAT32 covers some devices like Rufus or Ventoy. But if your SSD is GPT +...

I may have found a clue, but no idea why the values are different for you. $USB_DeviceIDs = @(Get-PnpDevice -PresentOnly | where { $_.Service -eq 'USBSTOR' } | foreach { ($_.PNPDeviceID -split '\\')[2] }) (Get-CimInstance -ClassName Win32_DiskDrive | where { (($_.PNPDeviceID -split '\\')[-1]...

Try this test script. It incorporates your differences, and also runs the other "more relaxed" filter criteria. Let me know if there's a difference or not.

That confirms my suspicion about another bug. Try this version, it works when there's no USB drives.

You don't need abbodi's list, that's for expert Windows modders. If you accidentally lose a Winre.wim file (disappears for some reason), you can extract it from an existing ISO using 7-Zip or whatever. You open "\sources\install.wim" (or .esd) and browse one of the indexes (it doesn't matter...

I don't see how this fixes the problem. boot.wim itself is missing files, because MS forgot to add them in recent builds. There used to be an older version of the "Repair My PC" app and they switched to look like the WinRE version. Except WinRE already has the required files, which boot.wim...

@hader's current Execution Policy for PS scripts is configured for RemoteSigned (in the absence of other policy settings). 1. If you download any file from the web, most browsers will add the "Mark of The Web" to its NTFS file attributes. The only way to avoid that is to change your browser's...

The only two cases where MS appears to have messed up MCT's schedule is .8653 and .8873. They never released .8655 on MCT. Those are probably errors on their end. Patch Tuesday is a hard deadline inside MS, because security fixes are normally only released on Patch Tuesday (because of...

Self-introspection is worth +10 points. (y)

Unless MS mistakenly deployed an App Control policy file. In a policy file, then can restrict instances of command scripts from running. Or unsigned .ps1 scripts like mine. Normally these files are created by enterprises to lock down what their users are allowed to do. Did you update to .9168...

That's weird. SVN 9.0 is correct, but it's the wrong certificate. CA 2011 is \Windows\Boot\EFI CA 2023 is \Windows\Boot\EFI_EX Try the copy command again.

The batch script should work when clicked from Explorer. The first window asks to run as Admin, and opens a second window. The second window should stay open after running. When I run as Admin, the first windows stays open and doesn't need to open another window.

There are two major events in the Secure Boot process: 1. Installing the right CA 2023 certs. This is an one-time event, and any W11 ISO going back to 24H2 (October 2024) will install. 2. Revoking the CA 2011 cert. When revocation happens, another Windows security feature is added. The SVN...

It's an Easter egg for fans of @fg2001gf11F's postings. Since April 2026 (?) the "Repair My PC" option in WinPE has been broken because MS added a new Cloud Rebuild feature. 1. Assuming your normal Windows volume is generally borked, but WinRE can still be booted, you can run "Repair My PC"...

Relax. Just reload, you were clicking when I had to update the script after reading @Capricornus' report on 7z.exe.