Drive appears when in system properties

Anonymous
2022-12-24T13:28:12+00:00

This drive appeared from nowhere when I was checking for restore points. I only have one user and this drive (\?\Volume{a6810e9c-7196-4ad5...) does not appear anywhere else. I haven't been able to remove it, not because it's causing performance issues or anything, but simply because it bugs me. Any idea what that is and how to remove it?

I've tried resetting my laptop several times but all in vain. Is there any solution for this?

Windows for home | Windows 11 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2022-12-31T15:41:51+00:00

The log says winre.wim can't be found even though the file is present there.

Pls try:

  • attrib -s -h -r c:\windows\system32\recovery\reagent.xml
  • del c:\windows\system32\recovery\reagent.xml /a
  • REAGENTC /disable
  • copy c:\winre.wim T:\Recovery\WindowsRE /y
  • REAGENTC /setreimage /path T:\Recovery\WindowsRE /target C:\Windows
  • REAGENTC /enable

Was this answer helpful?

1 person found this answer helpful.
0 comments

114 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2022-12-27T14:44:44+00:00

    Ah! Didn't realize that BitLocker is enabled on the volume!

    Was this answer helpful?

    0 comments
  2. 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

  3. Anonymous
    2022-12-27T15:22:11+00:00

    From Deploy Windows RE | Microsoft Learn

    Use the GPT attributes: 0x8000000000000001 to hide the drive letters and to mark them as required, by using a combination of two attributes: GPT_BASIC_DATA_ATTRIBUTE_NO_DRIVE_LETTER and GPT_ATTRIBUTE_PLATFORM_REQUIRED.

    So, let's create the partition using DiskPart.

    Step 1: Create the partition and assign drive letter.

    • DiskPart
    • sel disk 0
    • create partition primary size=1130
    • format fs=NTFS quick label=WinRE
    • assign letter=T
    • exit

    Step 2: Copy WinRE.wim and enable Windows RE

    • mkdir T:\Recovery\WindowsRE
    • xcopy /h C:\Windows\System32\Recovery\Winre.wim T:\Recovery\WindowsRE
    • Reagentc /setreimage /path T:\Recovery\WindowsRE /target C:\Windows
    • Reagentc /enable

    Step 3: Mark the partition as Recovery partition *and* hide the drive from Explorer

    • diskpart
    • sel disk 0
    • sel par 4 ##Make sure #4 is your 1130 MB WinRE partition.
    • set id=de94bba4-06d1-4d40-a16a-bfd50179d6ac override
    • gpt attributes=0x8000000000000001
    • lis vol
    • exit

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-12-27T15:30:09+00:00

    As per the documentation, the attribute 0x4000000000000000 looks more apt than 0x8000000000000001 for your situation:

    GPT_BASIC_DATA_ATTRIBUTE_HIDDEN 0x4000000000000000 If this attribute is set, the partition is not detected by the Mount Manager.<br><br>As a result, the partition does not receive a drive letter, does not receive a volume GUID path, does not host mounted folders (also called volume mount points), and is not enumerated by calls to FindFirstVolume and FindNextVolume. This ensures that applications such as Disk Defragmenter do not access the partition. The Volume Shadow Copy Service (VSS) uses this attribute.<br><br>Despite its name, this attribute can be set for basic and dynamic disks.

    Was this answer helpful?

    0 comments