Share via

Server 2022 Error when connecting external drive enclosures

Jay Updegrove 0 Reputation points
2025-09-12T20:06:56.5933333+00:00

I have a Server 2022 instance (less than a month old) that is struggling with External USB Hard Drive enclosures. It works fine with thumb drives, and it sees the drive enclosures just fine, too, but when you put a disk in the enclosure (tried with multiple different brands, not just the one) the machine starts generating error logs

Filter Manager failed to attach to volume ‘\Device\HarddiskVolume5’. This volume will be unavailable for filtering until a reboot. The final status was 0xC0000022.

and

Failed to open device ?\USBSTOR#Disk&Ven_SABRENT&Prod_&Rev_4102#DD5641988396B&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}. Error code: 5@020D0002

Doing some light Googling, it appears this is potentially a permissions issue but I don't see where or how to update permissions on a drive that I can't see in Disk Management or Explorer.

I've tried driver updates but everything I'm finding online says the default MS driver should be just fine and that's what these things pull anyway. I'm pretty short on luck figuring this out.

Windows for business | Windows Server | Devices and deployment | Other
0 comments No comments

1 answer

Sort by: Most helpful
  1. Quinnie Quoc 11,055 Reputation points Independent Advisor
    2025-09-13T02:47:15.69+00:00

    Hi,

    The error codes you’ve encountered—0xC0000022 and 5@020D0002—typically indicate permission or access-related issues, often tied to system-level filtering or driver initialization. Since the drives are recognized but inaccessible, we recommend checking the Group Policy settings under Computer Configuration > Administrative Templates > System > Removable Storage Access, ensuring that access is not restricted for external devices.

    Additionally, verify that the drives are formatted with a supported file system (e.g., NTFS or exFAT) and that no third-party security software is interfering with device initialization. Running sfc /scannow and chkdsk may also help identify system-level corruption.

    If the issue persists, we suggest reviewing Microsoft’s guidance on USB drive accessibility in Server 2022 or opening a support case for deeper diagnostics.

    If my message is useful for you,please vote for it.

    Best regards,

    Quinnie Quoc.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.