Solved Alternative to wmic volume get driveLetter, label ?

pokeefe0001 · Sunday at 12:50 AM

pseymour said:
I ran each 1,000 times. The (Get-CimInstance...).DeviceID method ran an average of 6.1583 ms (range : 4.8111 to 117.9035 ms). The Select-Object method ran an average of 5.7888 ms (range : 4.8333 to 20.7353 ms).

Interesting. Since I've got it coded your way I'll keep it even if it were less efficient. That code is trivial compared with the rest of the stuff the .bat files do.

hdmi · Sunday at 12:57 AM

pseymour said:
while the other needs error handling...

For me, it doesn't. Both ways produce the same result and no PropertyNotFoundException ever occurs.

pseymour · Sunday at 1:04 AM

Well I demonstrated that it does when a drive without the specified label exists. Maybe it doesn't in the batch file, that wasn't what I said.

hdmi · Monday at 4:13 AM

pseymour said:
Well I demonstrated that it does when a drive without the specified label exists. Maybe it doesn't in the batch file, that wasn't what I said.

For me, It doesn't in the batch script, and it also doesn't in a PowerShell window. I used 3 different computers with completely different hardware to verify this. All are running on Windows 11 version 24H2 (OEM so, even if there are hidden issues at play, these issues could not have been carried over from one computer onto the others). But anyway. I like the simplicity of (Get-WmiObject...).DeviceID, and, the important thing IMO is that it works, which, at least for me, it does.

pseymour · Monday at 9:58 AM

I'm not sure what you're getting at, mate. If you specify a volume label that doesn't exist, you get back a null object, which of course does not have a DeviceID property, and you get an error when you try to reference it. "It works on my machine" is no comfort to anyone but the person who said it.

hdmi · Monday at 2:11 PM

pseymour said:
I'm not sure what you're getting at, mate. If you specify a volume label that doesn't exist, you get back a null object, which of course does not have a DeviceID property

Correct.

, and you get an error when you try to reference it.

That's only because you have enabled strict mode in PowerShell. By default, strict mode is disabled. If you are using a PowerShell profile to enable strict mode, powershell -NoProfile will run PowerShell without loading the profile, and strict mode will be disabled in that PowerShell session as a result of this. This is why I specified the -NoProfile parameter in the batch script. The profile (if it exists, which, by default, it doesn't) is not needed for the intended purpose [what the OP described].

"It works on my machine" is no comfort to anyone but the person who said it.

It should work on every default, clean, installation of Windows 11. I did specify the -NoProfile parameter in the batch script so, it should work in the batch script as-is. (Even, if you have enabled strict mode.) If it turns out that it still doesn't, then you've got more serious problems to worry about.

That said, you can disable strict mode directly in PowerShell by running Set-StrictMode -Off if that's what you want. There is no Get-StrictMode Cmdlet, but you can use this function instead:

function Get-StrictMode { try { $null = ($null -eq @(1)[2]) } catch { return '3.0 or Latest' }; try { ''.Year } catch { return '2.0' }; try { $null = ($undefined -gt 1) } catch { return '1.0' }; return 'Off' }

@pokeefe0001
Sorry for TMI (Too Much Info).

pseymour · Monday at 3:46 PM

I guess you can make a bunch of assumptions and half-bake code, or you can do it correctly.

hdmi · Tuesday at 12:52 AM

pseymour said:
I guess you can make a bunch of assumptions and half-bake code, or you can do it correctly.

I was going to just drop this and move on, but then I realized... this calls for a proper squad debrief.

Picture it: the trenches of PowerShell. The objective? Retrieve that elusive volume label without triggering strict mode landmines or getting bogged down in verbosity crossfire. My solution? Elegant. Efficient. Field-tested.

Enter Private ‘ExpandProperty’, declaring the high ground. And so I said—

“Back in ’85, I was entrusted with a divine gift—the power to wrangle memory-mapped editors and outsmart the TI video chip. Put me and this here `For /F` loop anywhere within one execution cycle of a mislabeled volume... war’s over, fellas. Disk mounted. Amen.”

Scripts go up, not down. Mine compiles to the interpreter. The interpreter compiles to the OS. The OS compiles to the legacy of every developer who ever dared to plug a Bitcorder into a Sony HB-75P.

Respect the process. Honor the context. And when in doubt, remember—not all battles are won with `-ExpandProperty`. Some are won with experience measured in kilobytes and ink ribbons.

Solved Alternative to wmic volume get driveLetter, label ?

Well-known member

My Computer

Jack of all trades – master of none

My Computers

who wants pizza?

My Computer

Jack of all trades – master of none

My Computers

who wants pizza?

My Computer

Jack of all trades – master of none

My Computers

who wants pizza?

My Computer

Jack of all trades – master of none

I was going to just drop this and move on, but then I realized... this calls for a proper squad debrief.​

Picture it: the trenches of PowerShell. The objective? Retrieve that elusive volume label without triggering strict mode landmines or getting bogged down in verbosity crossfire. My solution? Elegant. Efficient. Field-tested.​

Enter Private ‘ExpandProperty’, declaring the high ground. And so I said—​

“Back in ’85, I was entrusted with a divine gift—the power to wrangle memory-mapped editors and outsmart the TI video chip. Put me and this here For /F loop anywhere within one execution cycle of a mislabeled volume... war’s over, fellas. Disk mounted. Amen.”​

Scripts go up, not down. Mine compiles to the interpreter. The interpreter compiles to the OS. The OS compiles to the legacy of every developer who ever dared to plug a Bitcorder into a Sony HB-75P.​

Respect the process. Honor the context. And when in doubt, remember—not all battles are won with -ExpandProperty. Some are won with experience measured in kilobytes and ink ribbons.​

My Computers

Similar threads

I was going to just drop this and move on, but then I realized... this calls for a proper squad debrief.

Picture it: the trenches of PowerShell. The objective? Retrieve that elusive volume label without triggering strict mode landmines or getting bogged down in verbosity crossfire. My solution? Elegant. Efficient. Field-tested.

Enter Private ‘ExpandProperty’, declaring the high ground. And so I said—

“Back in ’85, I was entrusted with a divine gift—the power to wrangle memory-mapped editors and outsmart the TI video chip. Put me and this here `For /F` loop anywhere within one execution cycle of a mislabeled volume... war’s over, fellas. Disk mounted. Amen.”

Scripts go up, not down. Mine compiles to the interpreter. The interpreter compiles to the OS. The OS compiles to the legacy of every developer who ever dared to plug a Bitcorder into a Sony HB-75P.

Respect the process. Honor the context. And when in doubt, remember—not all battles are won with `-ExpandProperty`. Some are won with experience measured in kilobytes and ink ribbons.