4

Does anyone know what "\?\Volume...." is or why it would be listed as a disk on the windows defragmenter?

defragmenter

drives

drivemanag

It is not listed on other defragmenters like defraggler.

The E: and F: drives are mirrors.

Listing for HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices\ . There were many other entries with similar naming but they were removed after using the application suggested by Psycogeek.

reg

I removed the keys as Psycogeek suggested but they repopulated as a different alphanumeric string labelled as "Never run"

defrag2

Judith
  • 673
  • 5
  • 18
Riguez
  • 3,764

5 Answers5

4

HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\CPC\Volume\

USB devices that have been attached, appears safe to be removed, see more information link below.

Source

.

I also found this response

thats were the boot loader goes, its so u can encrypt the whole partition but that is unencrypted so the boot loader can that then get to the windows boot in the partition since the loader in the 100MB can pull the key from your TPM chip and you can use the encrypted drive.

Moab
  • 58,769
2

It's the un-named 300MB partition without a drive letter on disk 0. It's displayed as its volume GUID because it doesn't have a name or drive letter to display instead. On most stock installs this would be labelled "System Reserved".

Certain programs (such as R-Studio) will happily list the GUIDs of every volume, partition, and drive graphically should anyone else be confused by hidden boot partitions in future.

qasdfdsaq
  • 6,779
1

http://www.uwe-sieber.de/drivetools_e.html#drivecleanup find the Drivecleanup here. then run it with the -T option, that will show you what it thinks is orphaned. Might be a safer way of removal. (as long as the programmer knew what he was doing :-)

after all the discussion , I was wondering if it was a "virtual" drive that was once mounted, or a USB booting, where the USB was enabled for booting in the bios.

Psycogeek
  • 9,139
0

Try clicking Start, then type cmd then choose Run as Administrator.

Type vssadmin delete shadows /all then click ENTER. It should remove shadow copies.

galacticninja
  • 6,352
TxTrapper
  • 9
0

To extend on qasdfdsaq's answer, the ID you are seeing should be the GUID of one of the system partitions that Windows creates. Any other partition should be displayed as usual with its label and drive letter. Look at the table in the Wikipedia article if your ID matches to one of these and you have an exact answer.

I would expect that these are already filtered out to not show up in Defrag at all and may be that is the problem here that this is a generated GUID which is not blacklisted in Defrag. You can leave this as it is or just label the partition in Powershell or a partition manager that can access it to make it look nicer. Defrag shouldn't be able to accidentally work on this partition anyway. If you don't have a lot of disks and partitions and you don't want to be overly accurate then just pick any name for the label, otherwise open diskmgmt.msc or run get-partition in Powershell and look at the types. I was able to identify mine as Recovery.

If that's not accurate enough for you, because you have a lot of partitions, then you need a program or code snippet that displays the partition UUIDs/GUIDs for each partition to make an exact association which GUID maps to which partition number and how it is used in Windows. Unfortunately I don't know of a free and quick solution to that on Windows. (In Linux I can look these up with ls under /dev/disk-by-partuuid.) Scratch that, Windows calls it DeviceID, just replace the GUID below with yours and your label of choice.

$guid = "12345678-abcd-abcd-abcd-1234567890ef"
$label = "System Recovery"

$drive = Get-WmiObject -Class win32_volume -Filter "DeviceID = '\\\\?\\Volume{$guid}\\'"
Set-WmiInstance -input $drive -Arguments @{Label="$label"}
LiveWireBT
  • 982