Solved System Restore shows some drives with resource ID (not drive letter)

[svnfrms2r]

Hi,

As my System Restore (see screen shot) shows some drives with resource ID (not drive letter), I wonder if this is a permissions issue or something else is wrong/unrecognized.

If there is a tool for this problem to (also) reset the permissions (ideally for all drives) this would be much appreciated.

Thank you!

 

[Paul Black]

Hi svnfrms2r, are your drives mapped?

 

[svnfrms2r]

Hi svnfrms2r, are your drives mapped?

Not that I am aware of it.

According to disk mgmt, two partitions are not assigned, and a third is not created by Windows.

A quick permissions check with NTFS Perms Tool showed all drives are local and current user has full access rights.

How could I find out for sure if any drive is mapped? (I am not aware of any network drives, but maybe the router or the printer have anything to do with it.)
How can I find out from the resource ID what it really is that is being referenced?

Thank you!

 

[svnfrms2r]

Just found that
mountvol /?
does list
'possible values for VolumeName along with current mount points'
and that contained three resource IDs without drive letter, which corresponds to the above find of three unassigned, one not create by Windows. And hence I will assume it is the latter, to be explored under Linux with e.g. gpart.

Besides the new finds, any input most welcome, since the quest is not over

 

[svnfrms2r]

Found out by using PowerShell command
GWMI -namespace root\cimv2 -class win32_volume | FL -property Label,DriveLetter,DeviceID,SystemVolume,Capacity,Freespace
that the two resource IDs shown in above screen shot are actually the two unassigned volumes.
So Paul's hint was right, and in the end, there is no problem.
Phew

 

[Paul Black]

Hi svnfrms2r,

So Paul's hint was right, and in the end, there is no problem.
Phew

You have got to love computers. I am glad you got it sorted .