Powershell Command Repair-Volume Gives Invalid Property Error

Question

Powershell Command Repair-Volume Gives Invalid Property Error

Steve M 16

When I run

PS C:\> Repair-Volume -DriveLetter C -Scan

in Powershell:

PSVersion 5.1.19041.1320
PSEdition Desktop

I get this error:

Repair-Volume : Invalid property
At line:1 char:1

Repair-Volume -DriveLetter C -Scan
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CategoryInfo : MetadataError: (MSFT_Volume:ROOT/Microsoft/...age/MSFT_Volume) [Repair-
Volume], CimException
FullyQualifiedErrorId : HRESULT 0x80041031,Repair-Volume

I ran sfc /scannow and found no issues.

BTW, Get-Volume throws a similar error;

Thank you.

4 answers

Your answer

Answer 1

carlos andres bejarano asprilla 11

LOOK AT THE VERSION OF THE MODULES AND CHECK IF YOU CAN EXECUTE THAT CMDLETS WITH THE CURRENT VERSION OF YOUR POWESHELL

Answer 2

MotoX80 36,401

BTW, Get-Volume throws a similar error;

Were you messing with the code page or something? Does this script produce the same results that I get?

cls  
"C" | format-hex  
""  
(Get-Volume -DriveLetter C).FileSystem  
""  
$vols = get-volume    
ForEach ($vol in $vols) {      
    if (($vol.DriveLetter.ToString().Length  -ne 0) -and ($vol.DriveType -eq "Fixed")) {  
        "Checking drive {0}" -f $vol.driveletter  
        $vol.driveletter.ToString() | format-hex  
        Repair-Volume -DriveLetter $vol.driveletter -Scan  
        return    # the first drive we find should be the C drive. Stop after that. Delete this line to scan all.    
    }       
}

Steve M 16 Reputation points

2021-12-21T03:25:29.75+00:00
Hi @MotoX80 ,
I did not do anything with any Powershell code.
I was attempting to scan my C: drive when I got the error.

I can't run the code you posted because I get the same error.

Get-Volume : Invalid property
At line:1 char:3

(Get-Volume -DriveLetter C).FileSystem

~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo : MetadataError: (MSFT_Volume:ROOT/Microsoft/...age/MSFT_
Volume) [Get-Volume], CimException

FullyQualifiedErrorId : HRESULT 0x80041031,Get-Volume

Thanks,
Steve

MotoX80 36,401

What about the rest of the script?

What does Get-Volume return if you do not specify a drive letter?

Run diskpart and see if it shows the C drive.

DISKPART> list volume

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     C   OS           NTFS   Partition    455 GB  Healthy    Boot
  Volume 1         ESP          FAT32  Partition    500 MB  Healthy    System
  Volume 2         WINRETOOLS   NTFS   Partition    750 MB  Healthy    Hidden
  Volume 3                      NTFS   Partition    509 MB  Healthy    Hidden
  Volume 4                      NTFS   Partition    450 MB  Healthy    Hidden
  Volume 5         PBR Image    NTFS   Partition   8093 MB  Healthy    Hidden
  Volume 6     D   SD           NTFS   Removable    116 GB  Healthy

Steve M 16 Reputation points

2021-12-21T14:01:48.973+00:00
Here is what I get when I type get-volume:

PS C:\WINDOWS\system32> get-volume
get-volume : Invalid property
At line:1 char:1

get-volume

~~~~~~~~~~

CategoryInfo : MetadataError: (MSFT_Volume:ROOT/Microsoft/...age/MSFT_
Volume) [Get-Volume], CimException

FullyQualifiedErrorId : HRESULT 0x80041031,Get-Volume

Do you want me to post what I get when I run your script?
Thanks
Steve M 16 Reputation points

2021-12-21T14:04:41.14+00:00
This is the output from your script:

00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00000000 43 C

Get-Volume : Invalid property
At line:4 char:3

(Get-Volume -DriveLetter C).FileSystem

~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo : MetadataError: (MSFT_Volume:ROOT/Microsoft/...age/MSFT_Volume) [Get-Vol
ume], CimException

FullyQualifiedErrorId : HRESULT 0x80041031,Get-Volume

get-volume : Invalid property
At line:6 char:10

$vols = get-volume

~~~~~~~~~~

CategoryInfo : MetadataError: (MSFT_Volume:ROOT/Microsoft/...age/MSFT_Volume) [Get-Vol
ume], CimException

FullyQualifiedErrorId : HRESULT 0x80041031,Get-Volume
MotoX80 36,401 Reputation points

2021-12-21T14:12:55.773+00:00

Looks like you've got something broken in WMI. Is Windows up to date? Maybe I should start by asking is this Win10? Have you installed the latest feature update?
Steve M 16 Reputation points

2021-12-21T14:13:59.597+00:00

Here is the output from Diskpart:

PS C:\WINDOWS\system32> diskpart

Microsoft DiskPart version 10.0.19041.964

Copyright (C) Microsoft Corporation.
On computer: DESKTOP-T3GFTCQ
Steve M 16 Reputation points

2021-12-21T14:16:30.617+00:00

Windows 10 Home is up to date. How to repair WMI?
MotoX80 36,401 Reputation points

2021-12-21T14:18:20.563+00:00

Run "list volume" while in diskpart.
Steve M 16 Reputation points

2021-12-21T14:22:57.757+00:00

Running this as a .bat:
Will reboot and check WMI

@Echo off
sc config winmgmt start= disabled
net stop winmgmt /y
%systemdrive%
cd %windir%\system32\wbem
for /f %%s in ('dir /b *.dll') do regsvr32 /s %%s
wmiprvse /regserver
winmgmt /regserver
sc config winmgmt start= auto
net start winmgmt
for /f %%s in ('dir /s /b *.mof *.mfl') do mofcomp %%s
MotoX80 36,401 Reputation points

2021-12-21T14:28:13.58+00:00

I'm not sure. MS had a WmiDiag tool, but that has gone unsupported for newer versions of Windows. I used to have a .bat file that I used to rebuild WMI, but that was back on Win2003 servers. Haven't had as many WMI problems as I used to have. I'll have to go play around.

Does a plain old "chkdsk C:" work?

Maybe another forum user has more recent experience and can help you.
Steve M 16 Reputation points

2021-12-21T15:09:59.2+00:00

DISKPART> list volume

Volume ### Ltr Label Fs Type Size Status Info

Volume 0 E DVD-ROM 0 B No Media
Volume 1 C OS NTFS Partition 916 GB Healthy Boot
Volume 2 ESP FAT32 Partition 500 MB Healthy System
Volume 3 NTFS Partition 841 MB Healthy Hidden
Volume 4 Image NTFS Partition 12 GB Healthy Hidden
Volume 5 DELLSUPPORT NTFS Partition 1145 MB Healthy Hidden
Volume 6 F Seagate Rep NTFS Partition 1862 GB Healthy
Volume 7 I DBR_BOOT FAT32 Partition 504 MB Healthy
Volume 8 D Seagate Bac NTFS Partition 5588 GB Healthy

DISKPART>
Steve M 16 Reputation points

2021-12-21T15:17:59.927+00:00
Thanks MotoX80!
The WMI was damaged.
Running the above bat file and rebooting the system fixed the issue.
Here is the output:

PS C:\WINDOWS\system32> (Get-Host).Version

Major Minor Build Revision

5 1 19041 1320

PS C:\WINDOWS\system32> get-volume

DriveLetter FriendlyName FileSystemType DriveType HealthStatus OperationalStatus SizeRema
ining

DELLSUPPORT NTFS Fixed Healthy OK ...12 MB ESP FAT32 Fixed Healthy OK ...83 MB

D Seagate Backup Plus Drive NTFS Fixed Healthy OK 4.13 TB
NTFS Fixed Healthy OK ...48 MB
C OS NTFS Fixed Healthy OK ...51 GB
Image NTFS Fixed Healthy OK ...43 MB
I DBR_BOOT FAT32 Fixed Healthy OK ...29 MB
F Seagate Replica NTFS Fixed Healthy OK 1.21 TB
E Unknown CD-ROM Healthy Unknown 0 B
MotoX80 36,401 Reputation points

2021-12-21T16:20:35.663+00:00

Yep, that looks real familiar.

Answer 3

Rich Matheisen 47,901

Does this work? Get-WMIObject Win32_Volume

How about some other WMI class? Something like $x = Get-WMIObject Win32_GroupUser

Steve M 16 Reputation points

2021-12-21T21:56:40.48+00:00

Hi Carlos & Rich,
Yes, both commands worked.
Thanks!
Rich Matheisen 47,901 Reputation points

2021-12-21T22:35:40.793+00:00
Good. Now let's add a filter to get just the drive you want.

Get-WmiObject win32_volume -Filter "driveletter = 'c:'"

Did that work? If it did, try to use the chkdsk method of the returned object. You can find an example of this here: chkdsk-method-in-class-win32-volume

Don't get fancy -- just use the values in the link.
Steve M 16 Reputation points

2021-12-21T23:44:28.763+00:00

Hi Rich,
I did a chkdsk and everything is normal.
I think I'm good to go.
Thanks for the help, and Happy Holiday's everyone!
SteveM

Answer 4

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Share via

Powershell Command Repair-Volume Gives Invalid Property Error

4 answers

Your answer