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 No 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 No comments

114 additional answers

Sort by: Oldest
  1. 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

  2. Anonymous
    2022-12-28T13:39:48+00:00

    Sorry for the wait, I've been busy at work today. From what I understand I should start by using these two attributes: GPT_BASIC_DATA_ATTRIBUTE_NO_DRIVE_LETTER and GPT_ATTRIBUTE_PLATFORM_REQUIRED in command promopt as administrator? And then proceed with the rest? As well as use gpt attributes=0x4000000000000000 instead of gpt attributes=0x8000000000000001 in step 3?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-12-28T13:46:05+00:00

    I've typed the complete set of commands (Step 1, Step 2, and Step 3). Pls try that. Post screenshots after each step.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-12-28T14:00:38+00:00

    BTW, we can try 0x8000000000000001. If that doesn't do the trick, use 0x4000000000000000.

    Was this answer helpful?

    0 comments No comments