Windows 10, 22H2, 19045.6466
I haven't used Windows PowerShell for a while.
Today, I tried Get-Volume, and the results were nothing:
PS C:\windows\system32> Get-Volume
PS C:\windows\system32>
So I tried PS on a Windows 11 machine, and it worked fine.
I searched online, and the suggestion was to install PS using this
command within the command prompt:
winget install --id Microsoft.PowerShell --source winget
Same (none)results.
I dis some more searching, and found this:
Microsoft supports PowerShell until PowerShell reaches end-of-support or
the version of Windows reaches end-of-support.
Since my Windows 10 has reached end-on-support, is there any way to
install a version of PS that will work on my Windows 10 machine? I'm
not interested in ESU, and not even sure if that would include the
ability to install a working edition of PS.
There are other ways to find system information.
Thanks.
Sorry for all the mis-spells. I should have proof read before sending.
Windows 10, 22H2, 19045.6466
I haven't used Windows PowerShell for a while.
Today, I tried Get-Volume, and the results were nothing:
PS C:\windows\system32> Get-Volume
PS C:\windows\system32>
So I tried PS on a Windows 11 machine, and it worked fine.
I searched online, and the suggestion was to install PS using this command within the command prompt:
winget install --id Microsoft.PowerShell --source winget
Same (none)results.
I dis some more searching, and found this:
Microsoft supports PowerShell until PowerShell reaches end-of-support or
the version of Windows reaches end-of-support.
Since my Windows 10 has reached end-on-support, is there any way to install a version of PS that will work on my Windows 10 machine? I'm not
interested in ESU, and not even sure if that would include the ability to install a working edition of PS.
There are other ways to find system information.
Thanks.
On 8/14/26 5:59 PM, Boris wrote:
Sorry for all the mis-spells. I should have proof read before sending.
Few do, as much as most software has spell checkers.
Doesn't dew anything four using the wrong words though.
Windows 10, 22H2, 19045.6466
I haven't used Windows PowerShell for a while.
Today, I tried Get-Volume, and the results were nothing:
PS C:\windows\system32> Get-Volume
PS C:\windows\system32>
So I tried PS on a Windows 11 machine, and it worked fine.
I searched online, and the suggestion was to install PS using this command within the command prompt:
winget install --id Microsoft.PowerShell --source winget
Same (none)results.
I dis some more searching, and found this:
Microsoft supports PowerShell until PowerShell reaches end-of-support or
the version of Windows reaches end-of-support.
Since my Windows 10 has reached end-on-support, is there any way to install a version of PS that will work on my Windows 10 machine? I'm not
interested in ESU, and not even sure if that would include the ability to install a working edition of PS.
There are other ways to find system information.
Thanks.
Windows 10, 22H2, 19045.6466
I haven't used Windows PowerShell for a while.
Today, I tried Get-Volume, and the results were nothing:
PS C:\windows\system32> Get-Volume
PS C:\windows\system32>
So I tried PS on a Windows 11 machine, and it worked fine.
Windows 10, 22H2, 19045.6466
I haven't used Windows PowerShell for a while.
Today, I tried Get-Volume, and the results were nothing:
PS C:\windows\system32> Get-Volume
PS C:\windows\system32>
So I tried PS on a Windows 11 machine, and it worked fine.
On Fri, 8/14/2026 5:41 PM, Boris wrote:
Windows 10, 22H2, 19045.6466
I haven't used Windows PowerShell for a while.
Today, I tried Get-Volume, and the results were nothing:
PS C:\windows\system32> Get-Volume
PS C:\windows\system32>
So I tried PS on a Windows 11 machine, and it worked fine.
I searched online, and the suggestion was to install PS using this
command within the command prompt:
winget install --id Microsoft.PowerShell --source winget
Same (none)results.
I dis some more searching, and found this:
Microsoft supports PowerShell until PowerShell reaches end-of-support
or the version of Windows reaches end-of-support.
Since my Windows 10 has reached end-on-support, is there any way to
install a version of PS that will work on my Windows 10 machine? I'm
not interested in ESU, and not even sure if that would include the
ability to install a working edition of PS.
There are other ways to find system information.
Thanks.
PS C:\windows\system32> $PSVersiontable
If that runs, then the shell is running.
I mean, as soon as it put up that PS prompt, it was working.
But having it print the table is fun too.
If "Get-volume" won't run, maybe wmic.exe is malfunctioning.
Using one of your shells, test it out a bit.
wmic partition get name,size,index
wmic logicaldisk
wmic diskdrive
C:\Windows\System32> wmic partition get name,size,index
Index Name Size
0 Disk #0, Partition #0 104857600
1 Disk #0, Partition #1 127088459776
2 Disk #0, Partition #2 1073741824
3 Disk #0, Partition #3 138510690816
4 Disk #0, Partition #4 1074790400
5 Disk #0, Partition #5 732331769856
6 Disk #0, Partition #6 3000582012928
0 Disk #1, Partition #0 91225063424
You can try a "mountvol" for another view.
Or the diskpart.exe utility can list things as well.
Powershell could depend on a version of dotNET.
DotNet assemblies have to be recompiled after a
DotNet update, and you might see a couple "ngen.exe"
running as well as other things. You might have
a number of versions of DotNet, but after an update
of a specific version, ngen will attempt to verify the
other versions and a kind of "null update" is the
result. So you might see "busy, blip, blip, blip"
as the things that don't need maintenance, don't
get any effort.
Maybe this is one of those dism/sfc times :-)
But I don't know whether the shell maintenance
is covered by such things. It would make sense
for the effort to be there, I just don't know off
hand how it is maintained.
dism /Online /Cleanup-image /RestoreHealth
Sfc /ScanNow
If the signing had expired, there might have
been an entirely different visual result. The calmness
of your description, suggests a dependency is taking
a nap.
Paul
"Alan K." <alan@invalid.com> wrote in news:115o5tp$2tp4b$1@dont-email.me:
On 8/14/26 5:59 PM, Boris wrote:
Sorry for all the mis-spells. I should have proof read before sending.
Few do, as much as most software has spell checkers.
Doesn't dew anything four using the wrong words though.
Nice, very nice.
On 2026/8/15 3:25:26, Boris wrote:
"Alan K." <alan@invalid.com> wrote in news:115o5tp$2tp4b$1@dont-email.me:
On 8/14/26 5:59 PM, Boris wrote:
Sorry for all the mis-spells. I should have proof read before sending. >>>Few do, as much as most software has spell checkers.
Doesn't dew anything four using the wrong words though.
Nice, very nice.
Time for the old poem - rest of this post is a document I've created
over time summarising what various sources have said about its origin,
and minor variations in its text: ======================================================================
Copied (and "corrected") from a post by bjprice@cal.berkeley.edu
(Bennett Price) in alt.comp.os.windows-10 2026-2-21 0:33:21, though
much older.
One version at https://arnold.hosted.uark.edu/Other/ZarOde.pdf .
Google-AI says it was created by "Jerrold H. Zar, a professor at
Northern Illinois University." Doesn't give a date, though says "gained popularity in the 1990s".
Ode to a Spell Checker
Eye halve a spelling chequer have
It came with my pea see. I disk covered four my PC.
It plane lee marks four my revue
Miss steaks aye kin knot see. can
Eye ran this poem threw it.
Your sure reel glad two no.
Its very polished in its weigh,
My checker tolled me sew.
A check her is a bless sing.
It freeze yew lodes of thyme.
It helps me right awl stiles two reed,
And aides me when aye rime.
Each frays comes posed up on my screen,
Eye trussed too bee a joule;
The checker pours o'er every word
To cheque sum spelling rule.
Bee fore wee rote with checkers
Hour spelling was inn deck line,
Butt now when wee dew have a laps,
Wee are not maid too wine.
Butt now bee cause my spelling
Is checked with such grate flare,
There are know faults with in my cite, in awl this peace,
Of nun eye am a wear.
Now spelling does knot phase me,
It does knot bring a tier;
My pay purrs awl due glad den
With wrapped words fare as hear.
To rite with care is quite a feet
Of witch won should be proud,
And wee mussed dew the best wee can,
Sew flaws are knot aloud.
That's why eye brake in two averse
Caws Eye dew want too please.
Sow glad eye yam that aye did bye
This soft wear four pea seas. ======================================================================
_My_ spelling checker only didn't know "mussed".
Boris <Boris@invalid.invalid> wrote:
Windows 10, 22H2, 19045.6466
I haven't used Windows PowerShell for a while.
Today, I tried Get-Volume, and the results were nothing:
PS C:\windows\system32> Get-Volume
PS C:\windows\system32>
So I tried PS on a Windows 11 machine, and it worked fine.
I searched online, and the suggestion was to install PS using this
command within the command prompt:
winget install --id Microsoft.PowerShell --source winget
Same (none)results.
I dis some more searching, and found this:
Microsoft supports PowerShell until PowerShell reaches end-of-support
or the version of Windows reaches end-of-support.
Since my Windows 10 has reached end-on-support, is there any way to
install a version of PS that will work on my Windows 10 machine? I'm
not interested in ESU, and not even sure if that would include the
ability to install a working edition of PS.
There are other ways to find system information.
Thanks.
Windows 10 22H2 build 19045.7417
A slightly later build of Win10. I'm on the free ESU schedule ending in
Oct 2027. There's actually some pending updates, but I paused those
while I work on some RAM issues.
Powershell works on my Win10 host even before ESU was offered, so it
worked on an older Win10 22H2 for me. In an admin command shell, I run (there are many ways to load the PS shell):
powershell
then run:
get-host
to see I have 5.1.19041.7417 of PS. I recall looking at a later version
of PS, but can't remember why I stuck with the bundled version instead
of getting a later version. I then ran:
get-volume
After a 1-second pause got a list of drives, even those not mounted (no
drive letter assigned). So, get-volume and loading the PS shell works
on my Win10 setup.
When you load the PowerShell shell, what welcome message do you see? I
see:
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Try the new cross-platform PowerShell https://aka.ms/pscore6
It wants me to upgrade, but, as I said, I tried that, didn't like it for
some reason or it didn't install, so I stuck with v5 that came bundled
with Win10.
If you managed to load the PS shell, entering get-volume should return something even if it didn't compile a list of devices, like a "not
recognized for a cmdlet name" error.
https://learn.microsoft.com/en-us/powershell/scripting/install/install-po wershell-on-windows?view=powershell-7.6
I don't need multiple versions of PS, and maybe why I uninstalled the
latest version since it didn't give me anything. No bang for the buck.
If the winget method installed a later version, you need to make sure
you load that version and not the default old version that still exists.
When I have winget search for the latest available released version of Powershell:
winget search --id Microsoft.PowerShell --exact
it shows the latest version is 7.6.7.0, as below:
Name Id Version Source -----------------------------------------------
PowerShell Microsoft.PowerShell 7.6.5.0 winget
That won't get rid of the PS5 that you have before, and perhaps the
version that is failing for you. You'll need to run PS7 to get the new version. Since the new version is installed in a different folder,
you'll have to use a shortcut that points there.
"PowerShell 7 doesn't replace Windows PowerShell 5.1. It installs to a
new directory and runs side-by-side with Windows PowerShell 5.1."
I ran PS7, still with no luck when issueing get-volume.
Guess I'm at a standstill. Now going to try Paul's dism/sfc.
Boris <Boris@invalid.invalid> wrote:
I ran PS7, still with no luck when issueing get-volume.
Guess I'm at a standstill. Now going to try Paul's dism/sfc.
I'd try booting into Windows' Safe Mode to make sure you aren't loading drivers or software that interferes with querying the devices.
Boris <Boris@invalid.invalid> wrote:
I ran PS7, still with no luck when issueing get-volume.
Guess I'm at a standstill. Now going to try Paul's dism/sfc.
I'd try booting into Windows' Safe Mode to make sure you aren't loading drivers or software that interferes with querying the devices.
VanguardLH <V@nguard.LH> wrote in news:1u7ivq4a2xxv5.dlg@v.nguard.lh:
Boris <Boris@invalid.invalid> wrote:
I ran PS7, still with no luck when issueing get-volume.
Guess I'm at a standstill. Now going to try Paul's dism/sfc.
I'd try booting into Windows' Safe Mode to make sure you aren't loading
drivers or software that interferes with querying the devices.
Neither PS5 nor PS7 had any luck with dism/sfc, or safe mode.
I'm closing this ticket.
On 8/14/26 5:59 PM, Boris wrote:
Sorry for all the mis-spells. I should have proof read before sending.
Few do, as much as most software has spell checkers. Doesn't dew
anything four using the wrong words though.
Paul <nospam@needed.invalid> wrote in news:115ot80$33m5k$1@dont-email.me:
On Fri, 8/14/2026 5:41 PM, Boris wrote:
Windows 10, 22H2, 19045.6466
I haven't used Windows PowerShell for a while.
Today, I tried Get-Volume, and the results were nothing:
PS C:\windows\system32> Get-Volume
PS C:\windows\system32>
So I tried PS on a Windows 11 machine, and it worked fine.
I searched online, and the suggestion was to install PS using this
command within the command prompt:
winget install --id Microsoft.PowerShell --source winget
Same (none)results.
I dis some more searching, and found this:
Microsoft supports PowerShell until PowerShell reaches end-of-support
or the version of Windows reaches end-of-support.
Since my Windows 10 has reached end-on-support, is there any way to
install a version of PS that will work on my Windows 10 machine? I'm
not interested in ESU, and not even sure if that would include the
ability to install a working edition of PS.
There are other ways to find system information.
Thanks.
PS C:\windows\system32> $PSVersiontable
If that runs, then the shell is running.
I mean, as soon as it put up that PS prompt, it was working.
But having it print the table is fun too.
If "Get-volume" won't run, maybe wmic.exe is malfunctioning.
Using one of your shells, test it out a bit.
wmic partition get name,size,index
wmic logicaldisk
wmic diskdrive
C:\Windows\System32> wmic partition get name,size,index
Index Name Size
0 Disk #0, Partition #0 104857600
1 Disk #0, Partition #1 127088459776
2 Disk #0, Partition #2 1073741824
3 Disk #0, Partition #3 138510690816
4 Disk #0, Partition #4 1074790400
5 Disk #0, Partition #5 732331769856
6 Disk #0, Partition #6 3000582012928
0 Disk #1, Partition #0 91225063424
You can try a "mountvol" for another view.
Or the diskpart.exe utility can list things as well.
Powershell could depend on a version of dotNET.
DotNet assemblies have to be recompiled after a
DotNet update, and you might see a couple "ngen.exe"
running as well as other things. You might have
a number of versions of DotNet, but after an update
of a specific version, ngen will attempt to verify the
other versions and a kind of "null update" is the
result. So you might see "busy, blip, blip, blip"
as the things that don't need maintenance, don't
get any effort.
Maybe this is one of those dism/sfc times :-)
But I don't know whether the shell maintenance
is covered by such things. It would make sense
for the effort to be there, I just don't know off
hand how it is maintained.
dism /Online /Cleanup-image /RestoreHealth
Sfc /ScanNow
If the signing had expired, there might have
been an entirely different visual result. The calmness
of your description, suggests a dependency is taking
a nap.
Paul
$PSVersiontable and the wmic commands gave results, but Get-Volume still
does not.
-----------------------------------------------
PS C:\WINDOWS\system32> Get-Volume
PS C:\WINDOWS\system32> wmic partition get name,size,index
Index Name Size
0 Disk #0, Partition #0 524288000
1 Disk #0, Partition #1 984293048320
2 Disk #0, Partition #2 897581056
3 Disk #0, Partition #3 12823035904
4 Disk #0, Partition #4 1518338048
PS C:\WINDOWS\system32> wmic logicaldisk
Access Availability BlockSize Caption Compressed
ConfigManagerErrorCode ConfigManagerUserConfig CreationClassName Description DeviceID DriveType ErrorCleared ErrorDescription ErrorMethodology FileSystem FreeSpace InstallDate LastErrorCode MaximumComponentLength MediaType Name NumberOfBlocks PNPDeviceID PowerManagementCapabilities PowerManagementSupported ProviderName
Purpose QuotasDisabled QuotasIncomplete QuotasRebuilding Size Status StatusInfo SupportsDiskQuotas SupportsFileBasedCompression SystemCreationClassName SystemName VolumeDirty VolumeName VolumeSerialNumber 0 C: FALSE
Win32_LogicalDisk Local
Fixed Disk C: 3
NTFS 781053693952 255
12 C:
TRUE
TRUE FALSE 984293044224
TRUE TRUE Win32_ComputerSystem DADSDELLLAPTOP FALSE OS 181B2739
D:
Win32_LogicalDisk CD-ROM Disc D:
5
11 D:
Win32_ComputerSystem
DADSDELLLAPTOP
PS C:\WINDOWS\system32> wmic diskdrive
Availability BytesPerSector Capabilities CapabilityDescriptions
Caption CompressionMethod ConfigManagerErrorCode ConfigManagerUserConfig CreationClassName DefaultBlockSize Description DeviceID ErrorCleared ErrorDescription ErrorMethodology FirmwareRevision Index InstallDate InterfaceType LastErrorCode Manufacturer MaxBlockSize MaxMediaSize MediaLoaded MediaType MinBlockSize Model
Name NeedsCleaning NumberOfMediaSupported Partitions PNPDeviceID PowerManagementCapabilities PowerManagementSupported SCSIBus SCSILogicalUnit SCSIPort SCSITargetId SectorsPerTrack SerialNumber Signature Size Status StatusInfo SystemCreationClassName SystemName TotalCylinders TotalHeads TotalSectors TotalTracks TracksPerCylinder
512 {3, 4, 10} {"Random Access", "Supports
Writing", "SMART Notification"} ST1000LM024 HN-M101MBB
0 FALSE
Win32_DiskDrive Disk drive
\\.\PHYSICALDRIVE0
2BA30004 0 IDE
(Standard disk drives)
TRUE Fixed hard disk media
ST1000LM024 HN-M101MBB \\.\PHYSICALDRIVE0
5
SCSI\DISK&VEN_ST1000LM&PROD_024\4&D14604B&0&000000
0 0
0 0 63
S314J90H259607 1000202273280 OK
Win32_ComputerSystem DADSDELLLAPTOP 121601
255 1953520065 31008255 255
PS C:\WINDOWS\system32>
--------------------------------------------------
I'm going to move on to VanguardLH's reply before I do the dism/sfc thing.
Thanks.
On Sat, 8/15/2026 12:40 PM, Boris wrote:
Paul <nospam@needed.invalid> wrote in
news:115ot80$33m5k$1@dont-email.me:
On Fri, 8/14/2026 5:41 PM, Boris wrote:
Windows 10, 22H2, 19045.6466
I haven't used Windows PowerShell for a while.
Today, I tried Get-Volume, and the results were nothing:
PS C:\windows\system32> Get-Volume
PS C:\windows\system32>
So I tried PS on a Windows 11 machine, and it worked fine.
I searched online, and the suggestion was to install PS using this
command within the command prompt:
winget install --id Microsoft.PowerShell --source winget
Same (none)results.
I dis some more searching, and found this:
Microsoft supports PowerShell until PowerShell reaches end-of-support
or the version of Windows reaches end-of-support.
Since my Windows 10 has reached end-on-support, is there any way to
install a version of PS that will work on my Windows 10 machine? I'm
not interested in ESU, and not even sure if that would include the
ability to install a working edition of PS.
There are other ways to find system information.
Thanks.
PS C:\windows\system32> $PSVersiontable
If that runs, then the shell is running.
I mean, as soon as it put up that PS prompt, it was working.
But having it print the table is fun too.
If "Get-volume" won't run, maybe wmic.exe is malfunctioning.
Using one of your shells, test it out a bit.
wmic partition get name,size,index
wmic logicaldisk
wmic diskdrive
C:\Windows\System32> wmic partition get name,size,index
Index Name Size
0 Disk #0, Partition #0 104857600
1 Disk #0, Partition #1 127088459776
2 Disk #0, Partition #2 1073741824
3 Disk #0, Partition #3 138510690816
4 Disk #0, Partition #4 1074790400
5 Disk #0, Partition #5 732331769856
6 Disk #0, Partition #6 3000582012928
0 Disk #1, Partition #0 91225063424
You can try a "mountvol" for another view.
Or the diskpart.exe utility can list things as well.
Powershell could depend on a version of dotNET.
DotNet assemblies have to be recompiled after a
DotNet update, and you might see a couple "ngen.exe"
running as well as other things. You might have
a number of versions of DotNet, but after an update
of a specific version, ngen will attempt to verify the
other versions and a kind of "null update" is the
result. So you might see "busy, blip, blip, blip"
as the things that don't need maintenance, don't
get any effort.
Maybe this is one of those dism/sfc times :-)
But I don't know whether the shell maintenance
is covered by such things. It would make sense
for the effort to be there, I just don't know off
hand how it is maintained.
dism /Online /Cleanup-image /RestoreHealth
Sfc /ScanNow
If the signing had expired, there might have
been an entirely different visual result. The calmness
of your description, suggests a dependency is taking
a nap.
Paul
$PSVersiontable and the wmic commands gave results, but Get-Volume
still does not.
-----------------------------------------------
PS C:\WINDOWS\system32> Get-Volume
PS C:\WINDOWS\system32> wmic partition get name,size,index
Index Name Size
0 Disk #0, Partition #0 524288000
1 Disk #0, Partition #1 984293048320
2 Disk #0, Partition #2 897581056
3 Disk #0, Partition #3 12823035904
4 Disk #0, Partition #4 1518338048
PS C:\WINDOWS\system32> wmic logicaldisk
Access Availability BlockSize Caption Compressed
ConfigManagerErrorCode ConfigManagerUserConfig CreationClassName
Description DeviceID DriveType ErrorCleared ErrorDescription
ErrorMethodology FileSystem FreeSpace InstallDate LastErrorCode
MaximumComponentLength MediaType Name NumberOfBlocks PNPDeviceID
PowerManagementCapabilities PowerManagementSupported ProviderName
Purpose QuotasDisabled QuotasIncomplete QuotasRebuilding Size
Status StatusInfo SupportsDiskQuotas SupportsFileBasedCompression
SystemCreationClassName SystemName VolumeDirty VolumeName
VolumeSerialNumber 0 C: FALSE
Win32_LogicalDisk Local
Fixed Disk C: 3
NTFS 781053693952 255
12 C:
TRUE
TRUE FALSE 984293044224
TRUE TRUE Win32_ComputerSystem
DADSDELLLAPTOP FALSE OS 181B2739
D:
Win32_LogicalDisk CD-ROM Disc D:
5
11 D:
Win32_ComputerSystem
DADSDELLLAPTOP
PS C:\WINDOWS\system32> wmic diskdrive
Availability BytesPerSector Capabilities CapabilityDescriptions
Caption CompressionMethod
ConfigManagerErrorCode ConfigManagerUserConfig CreationClassName
DefaultBlockSize Description DeviceID ErrorCleared
ErrorDescription ErrorMethodology FirmwareRevision Index
InstallDate InterfaceType LastErrorCode Manufacturer
MaxBlockSize MaxMediaSize MediaLoaded MediaType
MinBlockSize Model
Name NeedsCleaning NumberOfMediaSupported
Partitions PNPDeviceID
PowerManagementCapabilities PowerManagementSupported SCSIBus
SCSILogicalUnit SCSIPort SCSITargetId SectorsPerTrack SerialNumber
Signature Size Status StatusInfo SystemCreationClassName
SystemName TotalCylinders TotalHeads TotalSectors TotalTracks
TracksPerCylinder
512 {3, 4, 10} {"Random Access", "Supports
Writing", "SMART Notification"} ST1000LM024 HN-M101MBB
0 FALSE
Win32_DiskDrive Disk drive
\\.\PHYSICALDRIVE0
2BA30004 0 IDE
(Standard disk drives)
TRUE Fixed hard disk media
ST1000LM024 HN-M101MBB \\.\PHYSICALDRIVE0
5
SCSI\DISK&VEN_ST1000LM&PROD_024\4&D14604B&0&000000
0 0
0 0 63
S314J90H259607 1000202273280 OK
Win32_ComputerSystem DADSDELLLAPTOP 121601
255 1953520065 31008255 255
PS C:\WINDOWS\system32>
--------------------------------------------------
I'm going to move on to VanguardLH's reply before I do the dism/sfc
thing.
Thanks.
OK, ran this "ticket" through CoPilot :-)
************* CoPilot Question ***************
On Windows 10 19045.6466 , the Powershell there, execution of
"Get-Volume" returns no output. Other commands used to collect
information about storage, seem to return outputs. For example, the wmic logicaldisk command produces output OK. What would be an explanation for
such behavior ? Why would Get-Volume return with no output ? Does it
need elevation as Administrator, or could that be a factor ? If that
were the case, then you would think other commands would have an Administrator group dependency. So far, no other sample command has a
problem producing output.
PS C:\WINDOWS\system32> Get-Volume
PS C:\WINDOWS\system32> wmic partition get name,size,index
Index Name Size
0 Disk #0, Partition #0 524288000
1 Disk #0, Partition #1 984293048320
2 Disk #0, Partition #2 897581056
3 Disk #0, Partition #3 12823035904
4 Disk #0, Partition #4 1518338048
The disk is ST1000LM024 HN-M101MBB and the laptop is Dell branded.
The laptop has an optical drive D: as well.
************** CoPilot Answer *******************
The behavior you?re seeing ? ** Get-Volume returning absolutely
nothing**, while WMIC and other storage-related commands work - is
unusual but *not mysterious*. On Windows 10, especially on OEM-modified builds and older PowerShell versions, there are several well-known
failure modes that cause **Get-Volume** to return an empty result set.
Below is the complete, technically grounded explanation.
---
## **Concise answer**
Get-Volume returns nothing when **the Storage Management API (SMAPI)**
cannot enumerate volumes.
This happens when:
- The **Storage Service ( StorSvc ) is disabled or broken**
- The **Virtual Disk Service (VDS)** is disabled
- The **CIM/WMI provider for storage is missing or corrupted**
- The **PowerShell Storage module is mismatched with OS version**
- The **Dell OEM image has removed or altered storage providers**
- The **optical drive or disk controller reports unexpected data**
- The **system is missing required privileges** (rare, but possible)
Elevation *usually* is **not** required, but a broken service or
provider *is*.
---
# **Why Get-Volume can return no output**
### 1. **Storage Service ( StorSvc ) is disabled**
Get-Volume depends on the Windows Storage Service.
Check:
sc query StorSvc
If it is **Stopped** or **Disabled**, you will get *no output* from:
Get-Volume
Get-Partition
Get-Disk
But WMIC will still work, because WMIC uses **Win32_LogicalDisk**
(classic WMI), not SMAPI.
This is the **#1 cause** on OEM laptops.
---
### 2. **Virtual Disk Service (VDS) is disabled**
Older storage cmdlets still fall back to VDS.
Check:
sc query vds
If VDS is disabled, Get-Volume may return nothing.
---
### 3. **PowerShell Storage module mismatch**
Windows 10 19045 uses:
Microsoft.PowerShell.Management
Microsoft.PowerShell.Storage
If the Storage module is corrupted or mismatched (common after OEM
recovery or DISM cleanup), the cmdlet loads but returns no objects.
Test:
Get-Module -ListAvailable Storage
If missing --> Get-Volume returns nothing.
---
### 4. **CIM provider for storage is broken**
Get-Volume uses:
root/Microsoft/Windows/Storage
Check:
Get-CimClass -Namespace root/Microsoft/Windows/Storage
If this returns **nothing**, the provider is missing --> Get-Volume
returns nothing.
This is surprisingly common on Dell/HP OEM images after upgrades.
---
### 5. **Dell OEM storage driver quirks**
Your disk (ST1000LM024) is a **Samsung/Seagate hybrid laptop drive**.
Dell often ships:
- Intel RST drivers
- OEM AHCI drivers
- OEM ATAPI drivers for optical drives
If the optical drive reports invalid volume metadata, the Storage API
can fail enumeration and return **zero volumes**.
WMIC still works because it uses the older Win32 provider.
---
### 6. **Optical drive D: causing enumeration failure**
This is a known issue:
If the optical drive reports:
- No media
- Invalid geometry
- Zero-byte size
- Unexpected partition style
Then Get-Volume may return **nothing at all**, not even the HDD
volumes.
You can test this by temporarily disabling the optical drive in Device Manager.
---
### 7. **Elevation is NOT normally required**
Running PowerShell as Administrator is not required for:
Get-Volume
Get-Disk
Get-Partition
But if a service is disabled, elevation won?t fix it.
---
# **Diagnostic commands (run these)**
These will pinpoint the cause.
### 1. Does Get-Disk return anything?
Get-Disk
If **Get-Disk also returns nothing**, the Storage API is broken.
---
### 2. Check Storage Service
sc query StorSvc
Expected:
STATE: RUNNING
If not running --> this is the cause.
---
### 3. Check CIM provider
Get-CimClass -Namespace root/Microsoft/Windows/Storage
If empty --> provider missing --> Get-Volume cannot work.
---
### 4. Check Storage module
Get-Module -ListAvailable Storage
If missing --> module corruption.
---
### 5. Check optical drive behavior
Get-Volume -DriveLetter D
If this hangs or returns nothing --> the optical drive is blocking enumeration.
---
# **Why WMIC works while Get-Volume fails**
WMIC uses **legacy WMI classes**:
Win32_LogicalDisk
Win32_DiskDrive
Win32_DiskPartition
These do **not** depend on:
- Storage Service
- VDS
- Storage CIM provider
- PowerShell Storage module
So WMIC continues to work even when the modern storage stack is broken.
---
# **Most likely explanation for your system**
Given:
- Windows 10 19045.6466
- Dell laptop
- Optical drive present
- WMIC works
- Get-Volume returns nothing
The most probable causes are:
### **1. Storage Service (StorSvc) not running**
or
### **2. Optical drive D: reporting invalid geometry**
or
### **3. Storage CIM provider missing/corrupted**
These three account for 95% of cases.
---
If you want, I can walk you through **repairing the Storage CIM
provider**,
**checking the Dell storage drivers**, or **testing the optical drive
hypothesis**.
************** End: CoPilot Answer *******************
Some of those are borderline absurd, others are possibilities.
Paul
VanguardLH wrote:
Boris <Boris@invalid.invalid> wrote:
I ran PS7, still with no luck when issueing get-volume.
Guess I'm at a standstill. Now going to try Paul's dism/sfc.
I'd try booting into Windows' Safe Mode to make sure you aren't loading
drivers or software that interferes with querying the devices.
You would think at least a C: drive would answer to a call like this.
Paul <nospam@needed.invalid> wrote in news:115tako$gt0g$1@dont-email.me:
If it is **Stopped** or **Disabled**, you will get *no output* from:
Get-Volume
Get-Partition
Get-Disk
Ok. Looks like StorService is enable, yet the three commands result in no output. I am running as admininstor. I'll investigate other options in a while. ------------------------
PowerShell 7.6.5
PS C:\Windows\System32> get-volume
PS C:\Windows\System32> wmic partition get name,size,index
Index Name Size
0 Disk #0, Partition #0 524288000
1 Disk #0, Partition #1 984293048320
2 Disk #0, Partition #2 897581056
3 Disk #0, Partition #3 12823035904
4 Disk #0, Partition #4 1518338048
PS C:\Windows\System32> sc query StorSvc
SERVICE_NAME: StorSvc
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE,
IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
PS C:\Windows\System32> get-partition
PS C:\Windows\System32> Get-Disk
PS C:\Windows\System32>
-----------------------------------
I searched online, and the suggestion was to install PS using this command within the command prompt:
winget install --id Microsoft.PowerShell --source winget
Same (none)results.
On 14/08/2026 22:41, Boris wrote:
I searched online, and the suggestion was to install PS using this
command
within the command prompt:
winget install --id Microsoft.PowerShell --source winget
Same (none)results.
I think that should install Powershell 7.x
Then try using the command "pwsh" instead of "powershell".
OK, ran this "ticket" through CoPilot :-)
************* CoPilot Question ***************
On Windows 10 19045.6466 , the Powershell there, execution of
"Get-Volume" returns no output. Other commands used to collect
information about storage, seem to return outputs. For example, the wmic logicaldisk command produces output OK. What would be an explanation for
such behavior ? Why would Get-Volume return with no output ? Does it
need elevation as Administrator, or could that be a factor ? If that
were the case, then you would think other commands would have an Administrator group dependency. So far, no other sample command has a
problem producing output.
PS C:\WINDOWS\system32> Get-Volume
PS C:\WINDOWS\system32> wmic partition get name,size,index
Index Name Size
0 Disk #0, Partition #0 524288000
1 Disk #0, Partition #1 984293048320
2 Disk #0, Partition #2 897581056
3 Disk #0, Partition #3 12823035904
4 Disk #0, Partition #4 1518338048
The disk is ST1000LM024 HN-M101MBB and the laptop is Dell branded.
The laptop has an optical drive D: as well.
************** CoPilot Answer *******************
The behavior you?re seeing ? ** Get-Volume returning absolutely
nothing**, while WMIC and other storage-related commands work - is
unusual but *not mysterious*. On Windows 10, especially on OEM-modified builds and older PowerShell versions, there are several well-known
failure modes that cause **Get-Volume** to return an empty result set.
Below is the complete, technically grounded explanation.
---
## **Concise answer**
Get-Volume returns nothing when **the Storage Management API (SMAPI)**
cannot enumerate volumes.
This happens when:
- The **Storage Service ( StorSvc ) is disabled or broken**
- The **Virtual Disk Service (VDS)** is disabled
- The **CIM/WMI provider for storage is missing or corrupted**
- The **PowerShell Storage module is mismatched with OS version**
- The **Dell OEM image has removed or altered storage providers**
- The **optical drive or disk controller reports unexpected data**
- The **system is missing required privileges** (rare, but possible)
Elevation *usually* is **not** required, but a broken service or
provider *is*.
---
# **Why Get-Volume can return no output**
### 1. **Storage Service ( StorSvc ) is disabled**
Get-Volume depends on the Windows Storage Service.
Check:
sc query StorSvc
If it is **Stopped** or **Disabled**, you will get *no output* from:PS C:\Windows\System32> sc query StorSvc
Get-Volume
Get-Partition
Get-Disk
But WMIC will still work, because WMIC uses **Win32_LogicalDisk**
(classic WMI), not SMAPI.
This is the **#1 cause** on OEM laptops.
---
### 2. **Virtual Disk Service (VDS) is disabled**
Older storage cmdlets still fall back to VDS.
Check:
sc query vds
If VDS is disabled, Get-Volume may return nothing.
---
### 3. **PowerShell Storage module mismatch**
Windows 10 19045 uses:
Microsoft.PowerShell.Management
Microsoft.PowerShell.Storage
If the Storage module is corrupted or mismatched (common after OEMPS C:\Windows\System32> Get-Module -ListAvailable Storage
recovery or DISM cleanup), the cmdlet loads but returns no objects.
Test:
Get-Module -ListAvailable Storage
If missing --> Get-Volume returns nothing.
---PS C:\Windows\System32> Get-CimClass -Namespace
### 4. **CIM provider for storage is broken**
Get-Volume uses:
root/Microsoft/Windows/Storage
Check:
Get-CimClass -Namespace root/Microsoft/Windows/Storage
If this returns **nothing**, the provider is missing --> Get-Volume
returns nothing.
This is surprisingly common on Dell/HP OEM images after upgrades.
---
### 5. **Dell OEM storage driver quirks**
Your disk (ST1000LM024) is a **Samsung/Seagate hybrid laptop drive**.
Dell often ships:
- Intel RST drivers
- OEM AHCI drivers
- OEM ATAPI drivers for optical drives
If the optical drive reports invalid volume metadata, the Storage API
can fail enumeration and return **zero volumes**.
WMIC still works because it uses the older Win32 provider.
---
### 6. **Optical drive D: causing enumeration failure**
This is a known issue:
If the optical drive reports:
- No media
- Invalid geometry
- Zero-byte size
- Unexpected partition style
Then Get-Volume may return **nothing at all**, not even the HDD
volumes.
You can test this by temporarily disabling the optical drive in Device Manager.
---
### 7. **Elevation is NOT normally required**
Running PowerShell as Administrator is not required for:
Get-Volume
Get-Disk
Get-Partition
But if a service is disabled, elevation won?t fix it.
---
# **Diagnostic commands (run these)**
These will pinpoint the cause.
### 1. Does Get-Disk return anything?
Get-Disk
If **Get-Disk also returns nothing**, the Storage API is broken.
---
### 2. Check Storage Service
sc query StorSvc
Expected:
STATE: RUNNING
If not running --> this is the cause.
---
### 3. Check CIM provider
Get-CimClass -Namespace root/Microsoft/Windows/Storage
If empty --> provider missing --> Get-Volume cannot work.
---
### 4. Check Storage module
Get-Module -ListAvailable Storage
If missing --> module corruption.
---
### 5. Check optical drive behavior
Get-Volume -DriveLetter D
If this hangs or returns nothing --> the optical drive is blocking enumeration.
---
# **Why WMIC works while Get-Volume fails**
WMIC uses **legacy WMI classes**:
Win32_LogicalDisk
Win32_DiskDrive
Win32_DiskPartition
These do **not** depend on:
- Storage Service
- VDS
- Storage CIM provider
- PowerShell Storage module
So WMIC continues to work even when the modern storage stack is broken.
---
# **Most likely explanation for your system**
Given:
- Windows 10 19045.6466
- Dell laptop
- Optical drive present
- WMIC works
- Get-Volume returns nothing
The most probable causes are:
### **1. Storage Service (StorSvc) not running**
or
### **2. Optical drive D: reporting invalid geometry**
or
### **3. Storage CIM provider missing/corrupted**
These three account for 95% of cases.
---
If you want, I can walk you through **repairing the Storage CIM
provider**,
**checking the Dell storage drivers**, or **testing the optical drive
hypothesis**.
************** End: CoPilot Answer *******************
Some of those are borderline absurd, others are possibilities.
Paul
Paul <nospam@needed.invalid> wrote in news:115tako$gt0g$1@dont-email.me:
If VDS is disabled, Get-Volume may return nothing.
PS C:\Windows\System32> sc query vds
SERVICE_NAME: vds
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
Many of the possibilities given by CoPilot are beyond my understanding,
but at this point, it seems that #2, VIrtual Disk Services, 'may' be the issue, as it was reported as STOPPED.
On Mon, 8/17/2026 1:13 PM, Boris wrote:
Paul <nospam@needed.invalid> wrote in
news:115tako$gt0g$1@dont-email.me:
If VDS is disabled, Get-Volume may return nothing.
PS C:\Windows\System32> sc query vds
SERVICE_NAME: vds
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
Many of the possibilities given by CoPilot are beyond my understanding,
but at this point, it seems that #2, VIrtual Disk Services, 'may' be
the issue, as it was reported as STOPPED.
You should be able to look at that in "services.msc" .
Look for "Virtual Disk" in the list.
Mine is stopped too. It is labeled as "Manual".
When I run Disk Management (right-click Start, menu),
the vds starts on its own. Part of the reason for that, is
Disk Management (and diskpart.exe), have to know about
multiple classnames, more than Get-Volume might be using.
Like, the status of DynamicDisks has to be checked, to color
the Disk Management rectangles appropriately.
And my Get-Volume runs without causing "vds" to start.
If Disk Management is running, Get-Volume run in
a Powershell window, seems to run and return the results faster.
In a thread here, they claim Get-Volume relies on this command
internally. So this should be returning nothing as well.
https://github.com/PowerShell/PowerShell/issues/16688
Get-CimInstance -ClassName MSFT_Volume -Namespace
ROOT/Microsoft/Windows/Storage <=== "Get-Volume"
[ And this returns potential ClassName values that could be
used...
The list is larger if you don't specify a NameSpace. ]
Get-CimClass -Namespace ROOT/Microsoft/Windows/Storage
# These are some examples from the list.
MSFT_Volume \
MSFT_Partition \___ Likely associated with the other
Powershell commands that also failed MSFT_Disk /
MSFT_PhysicalDisk
MSFT_VirtualDisk
Get-CimInstance -ClassName MSFT_PhysicalDisk -Namespace
ROOT/Microsoft/Windows/Storage # Returns two drives OK
Get-CimInstance -ClassName MSFT_VirtualDisk -Namespace
ROOT/Microsoft/Windows/Storage # Returns nothing
I don't know, I'm not getting a strong feeling here, that VDS is
important to Powershell. It looks more like a "buddy for Disk
Management" in its behavior, it starts when Disk Management is running.
You can have a play with that, and see how yours responds.
Start Disk Management, go to Powershell and do the "Get-Volume" again.
*******
Plug in a USB key, or any storage device that does not
rely on whatever storage driver your Southbridge is using right now.
Then run the "Get-Volume" and see if the volume on the USB stick is
visible.
You can have a look in Device Manager too, and see what kind of
driver is being used for the storage. My storage is set to AHCI
at BIOS level, so I expect this to match. Your Dell, it will be
whatever Dell wanted it to be for your design (they like RAID-ready
setups, but a laptop would be a poor choice for such a thing when
there is only one storage bay). I'm expecting your driver will be
more fancy than this more or less standard one.
IDE ATA/ATAPI controllers
Standard SATA AHCI Controller Driver="storahci.sys"
For other classes of Southbridge SATA driver, the name of what
is there could be different, and it could be an Intel one
installed by Dell.
Paul
Paul <nospam@needed.invalid> wrote:
VanguardLH wrote:
Boris <Boris@invalid.invalid> wrote:
I ran PS7, still with no luck when issueing get-volume.
Guess I'm at a standstill. Now going to try Paul's dism/sfc.
I'd try booting into Windows' Safe Mode to make sure you aren't loading
drivers or software that interferes with querying the devices.
You would think at least a C: drive would answer to a call like this.
I don't know how Bitlocker, if enabled, might interfere. There are
other programs that use stacked I/O drivers, and those could interfere
with casual accessing of drives. Safe Boot won't get rid of Bitlocker.
You'd have to remove that to retest. Often the other stacked I/O
drivers don't load during safe boot, but some may. You could use SysInternals' loadorder to see what drivers loaded. For example, could
be some anti-malware or security software blocks casual interrogation of devices, like drives, to prevent malware (ransomware) from finding them.
Boris replied that safe mode didn't help. Next I'd try booting with a Windows distro from a removable drive (CD/DVD, USB flash drive), like
WinPE, to see if it his current Windows setup that has the trouble. But
it looks like Boris doesn't want to pursue the issue.
Paul <nospam@needed.invalid> wrote in news:115vj7r$17e53$1@dont-email.me:
On Mon, 8/17/2026 1:13 PM, Boris wrote:
Paul <nospam@needed.invalid> wrote in
news:115tako$gt0g$1@dont-email.me:
If VDS is disabled, Get-Volume may return nothing.
PS C:\Windows\System32> sc query vds
SERVICE_NAME: vds
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
Many of the possibilities given by CoPilot are beyond my understanding,
but at this point, it seems that #2, VIrtual Disk Services, 'may' be
the issue, as it was reported as STOPPED.
You should be able to look at that in "services.msc" .
Look for "Virtual Disk" in the list.
Mine is stopped too. It is labeled as "Manual".
In "services.msc", mine shows status "Running", start up type "Manual".
When I run Disk Management (right-click Start, menu),
the vds starts on its own. Part of the reason for that, is
Disk Management (and diskpart.exe), have to know about
multiple classnames, more than Get-Volume might be using.
Like, the status of DynamicDisks has to be checked, to color
the Disk Management rectangles appropriately.
And my Get-Volume runs without causing "vds" to start.
If Disk Management is running, Get-Volume run in
a Powershell window, seems to run and return the results faster.
In a thread here, they claim Get-Volume relies on this command
internally. So this should be returning nothing as well.
https://github.com/PowerShell/PowerShell/issues/16688
Get-CimInstance -ClassName MSFT_Volume -Namespace
ROOT/Microsoft/Windows/Storage <=== "Get-Volume"
[ And this returns potential ClassName values that could be
used...
The list is larger if you don't specify a NameSpace. ]
Get-CimClass -Namespace ROOT/Microsoft/Windows/Storage
# These are some examples from the list.
MSFT_Volume \
MSFT_Partition \___ Likely associated with the other
Powershell commands that also failed MSFT_Disk /
MSFT_PhysicalDisk
MSFT_VirtualDisk
Get-CimInstance -ClassName MSFT_PhysicalDisk -Namespace
ROOT/Microsoft/Windows/Storage # Returns two drives OK
Get-CimInstance -ClassName MSFT_VirtualDisk -Namespace
ROOT/Microsoft/Windows/Storage # Returns nothing
I don't know, I'm not getting a strong feeling here, that VDS is
important to Powershell. It looks more like a "buddy for Disk
Management" in its behavior, it starts when Disk Management is running.
You can have a play with that, and see how yours responds.
Start Disk Management, go to Powershell and do the "Get-Volume" again.
With Disk Management either running, or not running, I get the same
results:
PS C:\Windows\System32> Get-Disk
PS C:\Windows\System32> Get-PhysicalDisk
PS C:\Windows\System32> Get-Partition
PS C:\Windows\System32> Get-Volume
PS C:\Windows\System32> Get-PSDrive
Name Used (GB) Free (GB) Provider Root
CurrentLocation ----
--------- --------- -------- ----
--------------- Alias Alias C 185.84 730.85 FileSystem C:\
Windows\System32 Cert
Certificate \ D
FileSystem D:\ E 0.63 114.80 FileSystem
E:\ Env Environment
Function Function
HKCU Registry HKEY_CURRENT_USER
HKLM Registry HKEY_LOCAL_MACHINE
Temp 185.84 730.85 FileSystem C:\Users\Bruce\AppData\Local\Temp\ Variable Variable WSMan WSMan
*******
Plug in a USB key, or any storage device that does not
rely on whatever storage driver your Southbridge is using right now.
Then run the "Get-Volume" and see if the volume on the USB stick is
visible.
With a USB drive plugged in, I get the same as above.
You can have a look in Device Manager too, and see what kind of
driver is being used for the storage. My storage is set to AHCI
at BIOS level, so I expect this to match. Your Dell, it will be
whatever Dell wanted it to be for your design (they like RAID-ready
setups, but a laptop would be a poor choice for such a thing when
there is only one storage bay). I'm expecting your driver will be
more fancy than this more or less standard one.
IDE ATA/ATAPI controllers
Standard SATA AHCI Controller Driver="storahci.sys"
For other classes of Southbridge SATA driver, the name of what
is there could be different, and it could be an Intel one
installed by Dell.
Device Manager shows storage driver as:
IDE ATA/ATAPI controllers
Inter(R) 6th Generation Core Processor Family Platform I/O SATA AHCI
Controller
On Mon, 8/17/2026 4:09 PM, Boris wrote:
Paul <nospam@needed.invalid> wrote in
news:115vj7r$17e53$1@dont-email.me:
On Mon, 8/17/2026 1:13 PM, Boris wrote:
Paul <nospam@needed.invalid> wrote in
news:115tako$gt0g$1@dont-email.me:
If VDS is disabled, Get-Volume may return nothing.
PS C:\Windows\System32> sc query vds
SERVICE_NAME: vds
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
Many of the possibilities given by CoPilot are beyond my
understanding, but at this point, it seems that #2, VIrtual Disk
Services, 'may' be the issue, as it was reported as STOPPED.
You should be able to look at that in "services.msc" .
Look for "Virtual Disk" in the list.
Mine is stopped too. It is labeled as "Manual".
In "services.msc", mine shows status "Running", start up type "Manual".
When I run Disk Management (right-click Start, menu),
the vds starts on its own. Part of the reason for that, is
Disk Management (and diskpart.exe), have to know about
multiple classnames, more than Get-Volume might be using.
Like, the status of DynamicDisks has to be checked, to color
the Disk Management rectangles appropriately.
And my Get-Volume runs without causing "vds" to start.
If Disk Management is running, Get-Volume run in
a Powershell window, seems to run and return the results faster.
In a thread here, they claim Get-Volume relies on this command
internally. So this should be returning nothing as well.
https://github.com/PowerShell/PowerShell/issues/16688
Get-CimInstance -ClassName MSFT_Volume -Namespace
ROOT/Microsoft/Windows/Storage <=== "Get-Volume"
[ And this returns potential ClassName values that could be
used...
The list is larger if you don't specify a NameSpace. ]
Get-CimClass -Namespace ROOT/Microsoft/Windows/Storage
# These are some examples from the list.
MSFT_Volume \
MSFT_Partition \___ Likely associated with the other
Powershell commands that also failed MSFT_Disk /
MSFT_PhysicalDisk
MSFT_VirtualDisk
Get-CimInstance -ClassName MSFT_PhysicalDisk -Namespace
ROOT/Microsoft/Windows/Storage # Returns two drives OK
Get-CimInstance -ClassName MSFT_VirtualDisk -Namespace
ROOT/Microsoft/Windows/Storage # Returns nothing
I don't know, I'm not getting a strong feeling here, that VDS is
important to Powershell. It looks more like a "buddy for Disk
Management" in its behavior, it starts when Disk Management is
running.
You can have a play with that, and see how yours responds.
Start Disk Management, go to Powershell and do the "Get-Volume" again.
With Disk Management either running, or not running, I get the same
results:
PS C:\Windows\System32> Get-Disk
PS C:\Windows\System32> Get-PhysicalDisk
PS C:\Windows\System32> Get-Partition
PS C:\Windows\System32> Get-Volume
PS C:\Windows\System32> Get-PSDrive
Name Used (GB) Free (GB) Provider Root
CurrentLocation ----
--------- --------- -------- ----
--------------- Alias
Alias C 185.84 730.85 FileSystem C:\
Windows\System32 Cert
Certificate \ D
FileSystem D:\ E 0.63 114.80 FileSystem
E:\ Env Environment
Function Function
HKCU Registry HKEY_CURRENT_USER
HKLM Registry HKEY_LOCAL_MACHINE
Temp 185.84 730.85 FileSystem
C:\Users\Bruce\AppData\Local\Temp\ Variable
Variable WSMan WSMan
*******
Plug in a USB key, or any storage device that does not
rely on whatever storage driver your Southbridge is using right now.
Then run the "Get-Volume" and see if the volume on the USB stick is
visible.
With a USB drive plugged in, I get the same as above.
You can have a look in Device Manager too, and see what kind of
driver is being used for the storage. My storage is set to AHCI
at BIOS level, so I expect this to match. Your Dell, it will be
whatever Dell wanted it to be for your design (they like RAID-ready
setups, but a laptop would be a poor choice for such a thing when
there is only one storage bay). I'm expecting your driver will be
more fancy than this more or less standard one.
IDE ATA/ATAPI controllers
Standard SATA AHCI Controller Driver="storahci.sys"
For other classes of Southbridge SATA driver, the name of what
is there could be different, and it could be an Intel one
installed by Dell.
Device Manager shows storage driver as:
IDE ATA/ATAPI controllers
Inter(R) 6th Generation Core Processor Family Platform I/O
SATA AHCI
Controller
Most mysterious.
Did you try this, while Disk Management was running ?
PS C:\Windows\System32> Get-Disk
PS C:\Windows\System32> Get-PhysicalDisk
PS C:\Windows\System32> Get-Partition
PS C:\Windows\System32> Get-Volume
PS C:\Windows\System32> Get-PSDrive
Name Used (GB) Free (GB) Provider Root
CurrentLocation ----
--------- --------- -------- ----
--------------- Alias
Alias C 185.84 730.85 FileSystem C:\
Windows\System32 Cert
Certificate \ D
FileSystem D:\ E 0.63 114.80 FileSystem
E:\ Env Environment
Function Function
HKCU Registry HKEY_CURRENT_USER
HKLM Registry HKEY_LOCAL_MACHINE
Temp 185.84 730.85 FileSystem C:\Users\Bruce\AppData\Local\Temp\ Variable Variable WSMan WSMan
As that would start "vds" service for you.
In Device Manager, you might want to look at the Driver tab
and see if it is "storahci.sys" or "IAahci.sys" (an Intel driver).
In your control panels, Programs and Features, it might tell you
whether the Intel RST driver was installed or not.
driver might drop something which is RAID-ready, and the name
could then be different. Some RST drivers are only "licensed"
to work with certain chipsets. So a C600 might be the only chipset
that supports a certain version of RST paired with it.
But the thing is, you're failing at the USB stick test, and
the Intel driver would not affect the response of the USB stick.
The LLM-AI output, says that an inability to parse the optical
drive output, could stop all output entirely, but that seems
far-fetched as a root cause. There's no evidence that the
slop that pours out of this stuff, can be stopped :-)
So something about this, a dependency is missing, but what is it ?
It doesn't smell of VDS here, in testing.
Get-CimInstance -ClassName MSFT_Volume -Namespace
ROOT/Microsoft/Windows/Storage
Paul
On Mon, 8/17/2026 4:09 PM, Boris wrote:
Paul <nospam@needed.invalid> wrote in
news:115vj7r$17e53$1@dont-email.me:
On Mon, 8/17/2026 1:13 PM, Boris wrote:
Paul <nospam@needed.invalid> wrote in
news:115tako$gt0g$1@dont-email.me:
If VDS is disabled, Get-Volume may return nothing.
PS C:\Windows\System32> sc query vds
SERVICE_NAME: vds
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
Many of the possibilities given by CoPilot are beyond my
understanding, but at this point, it seems that #2, VIrtual Disk
Services, 'may' be the issue, as it was reported as STOPPED.
You should be able to look at that in "services.msc" .
Look for "Virtual Disk" in the list.
Mine is stopped too. It is labeled as "Manual".
In "services.msc", mine shows status "Running", start up type "Manual".
When I run Disk Management (right-click Start, menu),
the vds starts on its own. Part of the reason for that, is
Disk Management (and diskpart.exe), have to know about
multiple classnames, more than Get-Volume might be using.
Like, the status of DynamicDisks has to be checked, to color
the Disk Management rectangles appropriately.
And my Get-Volume runs without causing "vds" to start.
If Disk Management is running, Get-Volume run in
a Powershell window, seems to run and return the results faster.
In a thread here, they claim Get-Volume relies on this command
internally. So this should be returning nothing as well.
https://github.com/PowerShell/PowerShell/issues/16688
Get-CimInstance -ClassName MSFT_Volume -Namespace
ROOT/Microsoft/Windows/Storage <=== "Get-Volume"
[ And this returns potential ClassName values that could be
used...
The list is larger if you don't specify a NameSpace. ]
Get-CimClass -Namespace ROOT/Microsoft/Windows/Storage
# These are some examples from the list.
MSFT_Volume \
MSFT_Partition \___ Likely associated with the other
Powershell commands that also failed MSFT_Disk /
MSFT_PhysicalDisk
MSFT_VirtualDisk
Get-CimInstance -ClassName MSFT_PhysicalDisk -Namespace
ROOT/Microsoft/Windows/Storage # Returns two drives OK
Get-CimInstance -ClassName MSFT_VirtualDisk -Namespace
ROOT/Microsoft/Windows/Storage # Returns nothing
I don't know, I'm not getting a strong feeling here, that VDS is
important to Powershell. It looks more like a "buddy for Disk
Management" in its behavior, it starts when Disk Management is
running.
You can have a play with that, and see how yours responds.
Start Disk Management, go to Powershell and do the "Get-Volume" again.
With Disk Management either running, or not running, I get the same
results:
PS C:\Windows\System32> Get-Disk
PS C:\Windows\System32> Get-PhysicalDisk
PS C:\Windows\System32> Get-Partition
PS C:\Windows\System32> Get-Volume
PS C:\Windows\System32> Get-PSDrive
Name Used (GB) Free (GB) Provider Root
CurrentLocation ----
--------- --------- -------- ----
--------------- Alias
Alias C 185.84 730.85 FileSystem C:\
Windows\System32 Cert
Certificate \ D
FileSystem D:\ E 0.63 114.80 FileSystem
E:\ Env Environment
Function Function
HKCU Registry HKEY_CURRENT_USER
HKLM Registry HKEY_LOCAL_MACHINE
Temp 185.84 730.85 FileSystem
C:\Users\Bruce\AppData\Local\Temp\ Variable
Variable WSMan WSMan
*******
Plug in a USB key, or any storage device that does not
rely on whatever storage driver your Southbridge is using right now.
Then run the "Get-Volume" and see if the volume on the USB stick is
visible.
With a USB drive plugged in, I get the same as above.
You can have a look in Device Manager too, and see what kind of
driver is being used for the storage. My storage is set to AHCI
at BIOS level, so I expect this to match. Your Dell, it will be
whatever Dell wanted it to be for your design (they like RAID-ready
setups, but a laptop would be a poor choice for such a thing when
there is only one storage bay). I'm expecting your driver will be
more fancy than this more or less standard one.
IDE ATA/ATAPI controllers
Standard SATA AHCI Controller Driver="storahci.sys"
For other classes of Southbridge SATA driver, the name of what
is there could be different, and it could be an Intel one
installed by Dell.
Device Manager shows storage driver as:
IDE ATA/ATAPI controllers
Inter(R) 6th Generation Core Processor Family Platform I/O
SATA AHCI
Controller
Most mysterious.
Did you try this, while Disk Management was running ?
PS C:\Windows\System32> Get-Disk
PS C:\Windows\System32> Get-PhysicalDisk
PS C:\Windows\System32> Get-Partition
PS C:\Windows\System32> Get-Volume
PS C:\Windows\System32> Get-PSDrive
Name Used (GB) Free (GB) Provider Root
CurrentLocation ----
--------- --------- -------- ----
--------------- Alias
Alias C 185.84 730.85 FileSystem C:\
Windows\System32 Cert
Certificate \ D
FileSystem D:\ E 0.63 114.80 FileSystem
E:\ Env Environment
Function Function
HKCU Registry HKEY_CURRENT_USER
HKLM Registry HKEY_LOCAL_MACHINE
Temp 185.84 730.85 FileSystem C:\Users\Bruce\AppData\Local\Temp\ Variable Variable WSMan WSMan
As that would start "vds" service for you.
In Device Manager, you might want to look at the Driver tab
and see if it is "storahci.sys" or "IAahci.sys" (an Intel driver).
In your control panels, Programs and Features, it might tell you
whether the Intel RST driver was installed or not.
driver might drop something which is RAID-ready, and the name
could then be different. Some RST drivers are only "licensed"
to work with certain chipsets. So a C600 might be the only chipset
that supports a certain version of RST paired with it.
But the thing is, you're failing at the USB stick test, and
the Intel driver would not affect the response of the USB stick.
The LLM-AI output, says that an inability to parse the optical
drive output, could stop all output entirely, but that seems
far-fetched as a root cause. There's no evidence that the
slop that pours out of this stuff, can be stopped :-)
So something about this, a dependency is missing, but what is it ?
It doesn't smell of VDS here, in testing.
Get-CimInstance -ClassName MSFT_Volume -Namespace
ROOT/Microsoft/Windows/Storage
Paul
Paul <nospam@needed.invalid> wrote:
VanguardLH wrote:
Boris <Boris@invalid.invalid> wrote:
I ran PS7, still with no luck when issueing get-volume.
Guess I'm at a standstill. Now going to try Paul's dism/sfc.
I'd try booting into Windows' Safe Mode to make sure you aren't loading
drivers or software that interferes with querying the devices.
You would think at least a C: drive would answer to a call like this.
I don't know how Bitlocker, if enabled, might interfere. There are
other programs that use stacked I/O drivers, and those could interfere
with casual accessing of drives. Safe Boot won't get rid of Bitlocker.
You'd have to remove that to retest. Often the other stacked I/O
drivers don't load during safe boot, but some may. You could use SysInternals' loadorder to see what drivers loaded. For example, could
be some anti-malware or security software blocks casual interrogation of devices, like drives, to prevent malware (ransomware) from finding them.
Boris replied that safe mode didn't help. Next I'd try booting with a Windows distro from a removable drive (CD/DVD, USB flash drive), like
WinPE, to see if it his current Windows setup that has the trouble. But
it looks like Boris doesn't want to pursue the issue.
On 08/17/2026 12:46 AM, VanguardLH wrote:
Paul <nospam@needed.invalid> wrote:
VanguardLH wrote:
Boris <Boris@invalid.invalid> wrote:
I ran PS7, still with no luck when issueing get-volume.
Guess I'm at a standstill. Now going to try Paul's dism/sfc.
I'd try booting into Windows' Safe Mode to make sure you aren't
loading drivers or software that interferes with querying the
devices.
You would think at least a C: drive would answer to a call like this.
I don't know how Bitlocker, if enabled, might interfere. There are
other programs that use stacked I/O drivers, and those could interfere
with casual accessing of drives. Safe Boot won't get rid of Bitlocker.
You'd have to remove that to retest. Often the other stacked I/O
drivers don't load during safe boot, but some may. You could use
SysInternals' loadorder to see what drivers loaded. For example, could
be some anti-malware or security software blocks casual interrogation
of devices, like drives, to prevent malware (ransomware) from finding
them.
Boris replied that safe mode didn't help. Next I'd try booting with a
Windows distro from a removable drive (CD/DVD, USB flash drive), like
WinPE, to see if it his current Windows setup that has the trouble.
But it looks like Boris doesn't want to pursue the issue.
The general rule for symptoms like this.
=> Try another(or create a new) logon profile on the device.
dism
"....winston" <winstonmvp@gmail.com> wrote in news:1161rot$1tak0$2@dont-email.me:
On 08/17/2026 12:46 AM, VanguardLH wrote:
Paul <nospam@needed.invalid> wrote:
VanguardLH wrote:
Boris <Boris@invalid.invalid> wrote:
I ran PS7, still with no luck when issueing get-volume.
Guess I'm at a standstill. Now going to try Paul's dism/sfc.
I'd try booting into Windows' Safe Mode to make sure you aren't
loading drivers or software that interferes with querying the
devices.
You would think at least a C: drive would answer to a call like this.
I don't know how Bitlocker, if enabled, might interfere. There are
other programs that use stacked I/O drivers, and those could interfere
with casual accessing of drives. Safe Boot won't get rid of Bitlocker.
You'd have to remove that to retest. Often the other stacked I/O
drivers don't load during safe boot, but some may. You could use
SysInternals' loadorder to see what drivers loaded. For example, could
be some anti-malware or security software blocks casual interrogation
of devices, like drives, to prevent malware (ransomware) from finding
them.
Boris replied that safe mode didn't help. Next I'd try booting with a
Windows distro from a removable drive (CD/DVD, USB flash drive), like
WinPE, to see if it his current Windows setup that has the trouble.
But it looks like Boris doesn't want to pursue the issue.
The general rule for symptoms like this.
=> Try another(or create a new) logon profile on the device.
I have a "Testing" profile. I get the same (non) results, there.
You sure that your Windows 10 was touched by some
evil persons?
Paul <nospam@needed.invalid> wrote in news:115vt0u$1avif$1@dont-email.me:
So something about this, a dependency is missing, but what is it ?
It doesn't smell of VDS here, in testing.
Get-Volume calls:
Get-CimInstance -ClassName MSFT_Volume -Namespace ROOT/Microsoft/Windows/Storage
The above command returns nothing.
| Sysop: | Tetrazocine |
|---|---|
| Location: | Melbourne, VIC, Australia |
| Users: | 10 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 153:53:22 |
| Calls: | 220 |
| Files: | 21,513 |
| Messages: | 85,728 |