Solved garlin's PowerShell scripts for updating Secure Boot CA 2023

Quandary · 2026-08-09T18:20:57-0400

No they are very different USB model drives. Some other USB sticks returned drive letters.

This 64GB USB stick and an external SSD plugged in returned 0.

Not going to try the experiment as it took too much effort creating the Rufus drive some time ago.

Ghot · 2026-08-09T18:27:55-0400

@garlin. Back to normal. Thanks. ^^

Got Win 11 installed.
Booted from Macrium media. Picked the backup I wanted, deleted all the newly installed partitions on my Windows drive and restored.
Went directly from Mac5rium bootable and turned Secure Boot and CSM back on.
And I'm back to where I was.

All is well now. Thanks again.

garlin · 2026-08-09T19:43:01-0400

Quandary said:
No they are very different USB model drives. Some other USB sticks returned drive letters.

This 64GB USB stick and an external SSD plugged in returned 0.

Not going to try the experiment as it was took too much effort creating the Rufus drive some time ago.

I think the best compromise is to allow for manual drive letters, in case your removable drive is "FIXED".

Code:

Check_BootMedia.ps1 E:

garlin · 2026-08-09T21:59:20-0400

@Quandary

Here's a wild shot:

Code:

(Get-CimInstance -ClassName Win32_DiskDrive | where { $_.PNPDeviceID -match @(((Get-PnpDevice -PresentOnly | where { $_.Service -eq 'USBSTOR' }).PNPDeviceID -split '\\')[-1]) } | foreach { Get-CimAssociatedInstance -InputObject $_ -ResultClass Win32_DiskPartition | Get-CimAssociatedInstance -ResultClass Win32_LogicalDisk }).DeviceID

PerpetualCycle · 2026-08-10T00:37:26-0400

garlin said:

@Quandary

Here's a wild shot:

Code:

(Get-CimInstance -ClassName Win32_DiskDrive | where { $_.PNPDeviceID -match @(((Get-PnpDevice -PresentOnly | where { $_.Service -eq 'USBSTOR' }).PNPDeviceID -split '\\')[-1]) } | foreach { Get-CimAssociatedInstance -InputObject $_ -ResultClass Win32_DiskPartition | Get-CimAssociatedInstance -ResultClass Win32_LogicalDisk }).DeviceID

I have a UASP USB drive I am using as a Macrium recovery device. The script doesn't work in that instance.

Its Class is "DiskDrive" and its service is "disk". I can see that it is USB connected if I look at "device stack" in Computer Management properties details, which has \Driver\UASPStor the stack (I don't think "device stack" is a pnp device property in pwsh). Must be another simpler way.

garlin · 2026-08-10T01:27:09-0400

I am missing an entire class of Macrium users, who are using HDD's as their recovery media?
In that case, you wouldn't be limited to USB controller devices.

As a fallback I would need to determine what a Macrium or Hasleo recovery device looks like (regardless of physical media).

- Macrium uses "MACRIUM_PE" as the volume label, and it's formatted FAT32. Hopefully nobody renames the volume label.
- Macrium leaves behind a \RMBuilder.xml in the root folder.

- Hasleo uses "HASLEOBS" as the volume label, and it's formatted FAT32. Hopefully nobody renames the volume label.
- Hasleo leaves absolutely no breadcrumbs in the top-level folders. /shrug

Here's a test script which combines the above logic + looking for MACRIUM_PE/HASLEOBS in the volume label.

t2s50 · 2026-08-10T03:11:29-0400

Didn't follow all the last pages, but it seems that 'Interfacetype' doesn't give a usable result for USB- harddisks?

What about using Get-Disk | Where-Object –FilterScript {$_.Bustype -Eq "USB"}?

I got an emergency disk created with PE-bakery on an SSD in an USB enclosure which correctly shows up in the remove media- dialogue but is mounted as harddrive

Scott · 2026-08-10T04:30:44-0400

garlin said:
- Macrium uses "MACRIUM_PE" as the volume label, and it's formatted FAT32. Hopefully nobody renames the volume label.

From what I've observed with MR 8.1, only drives built with the Windows PE base wim get the MACRIUM_PE volume label.
Drives built with WinRE get no volume labels.

Code:

PS D:\Scripts> .\COMBINED.ps1
USB Devices
-----------
L

CDROM Devices
-------------


Macrium/Hasleo
--------------
K

MBR + FAT32
-----------
K
L
PS D:\Scripts>

K is a WinPE drive.
L is a WinRE drive.

Solved garlin's PowerShell scripts for updating Secure Boot CA 2023

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Syzygy

My Computers My Computers

At a glance

At a glance

Well-known member

Attachments

My Computer My Computer

At a glance

Member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Similar threads

My Computer

My Computers

My Computer

My Computer

My Computers

My Computer

My Computer

My Computers