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-28T17:27:49+00:00

    WinRE is still not enabled. I think BitLocker is enabled on T:

    Can you try disabling BitLocker for T:\ drive and enable reagentc /enable

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-12-28T21:07:21+00:00

    That is not an option for me as I am running Windows 11 Home and not pro, so bitlocker is not available, but I'll try and decrypt the device instead see if that helps.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-12-28T21:59:14+00:00

    Now that I've inactivated device encryption, I think it worked.

    Was this answer helpful?

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