When Group Policy is what stops a USB drive from working, it is usually one of the Removable Storage Access policies, and only an administrator can set them back to Not Configured in the Local Group Policy Editor. If an employer, school or IT department manages your computer, the block comes from them: ask IT to allow the drive rather than changing anything yourself; the steps below are for a Windows 10 PC you own or administer.
First, check whether this PC is yours to change
A USB block set by an organization is a rule, not a fault. Microsoft’s troubleshooting checklist for blocked removable devices tells administrators to “Determine where the restriction is being applied (domain, local, cloud-managed, Intune, and so on).” Only one of those, a local policy, is something you can change on the PC itself.
- Work, school or other managed PC: stop here and contact IT. Policies sent from a domain or a device management service are applied again by the organization, and on PCs where Microsoft’s MDM precedence setting is turned on, “The MDM policy is used and the GP policy is blocked,” so a local change cannot win. Working around the rule may also break your organization’s policies.
- Your own PC, or one you administer at home or for a small office: continue, signed in with an administrator account. If you are not sure which account has administrator rights, see how to log in as an administrator on Windows 10.
To see which policies are actually applied, Microsoft’s guidance names two tools: run gpresult /h gpresult.html to save a report you can open in a browser, or open rsop.msc (Resultant Set of Policy). If the report lists policy objects that come from a domain rather than the local computer, the setting is not yours to change.
What a policy block looks like
These policies target storage, so the symptoms are about the drive rather than the port. You might see one of these:
- The drive appears in File Explorer, but opening it or copying files to it fails with an access error.
- You can open files but cannot save anything to the drive (a write block).
- The drive never shows up at all, even though the same port still powers a keyboard, mouse or phone charger.
- The same drive works normally on another computer.
If the drive also fails on other computers, the drive itself is the more likely problem. Opening a USB drive on Windows 10 covers the normal routes to reach its files.
Open the Local Group Policy Editor
- Press Windows + R to open the Run box.
- Type
gpedit.mscand press Enter. Click Yes if User Account Control asks for permission. - In the left pane, expand Computer Configuration > Administrative Templates > System.
If gpedit.msc does not open, the Local Group Policy Editor is not available on that PC. Microsoft’s policy reference lists the removable storage policies for the Pro, Enterprise, Education and IoT Enterprise editions and does not list Home, so this route is for those editions.
Set the Removable Storage Access policies to Not Configured
Microsoft’s Removable Storage policy reference lists each of these under the path System > Removable Storage Access, in both Computer Configuration and User Configuration. The State column in the editor shows which ones are switched on.
- Click Removable Storage Access under System.
- Sort or scan the State column for any policy marked Enabled.
- Double-click All Removable Storage classes: Deny all access. Choose Not Configured and click OK. This is the big one: when it is enabled, Microsoft says “no access is allowed to any removable storage class,” and it takes precedence over the individual policies below it.
- Do the same for any of these that show Enabled: Removable Disks: Deny read access, Removable Disks: Deny write access, Removable Disks: Deny execute access and WPD Devices: Deny read access.
- Now open User Configuration > Administrative Templates > System > Removable Storage Access and repeat the check. Microsoft lists User Configuration versions of these policies too, and one set there can block the drive for your account only.

Not Configured or Disabled? For these deny policies the result is the same. Microsoft’s description of the all-classes policy reads: “If you disable or don’t configure this policy setting, write and read accesses are allowed to all removable storage classes.” Not Configured is the tidier choice because it returns the policy to its default state.
Check Device Installation Restrictions
If the drive does not appear at all, a different policy may be stopping Windows from installing it. Microsoft documents it in the Device Installation policy reference under System > Device Installation > Device Installation Restrictions.
- In the editor, go to Computer Configuration > Administrative Templates > System > Device Installation > Device Installation Restrictions.
- Double-click Prevent installation of removable devices. When this is enabled, Microsoft says “Windows is prevented from installing removable devices and existing removable devices can’t have their drivers updated.”
- Choose Not Configured and click OK. With the policy disabled or not configured, Windows installs removable devices “as allowed or prevented by other policy settings,” so look down the list for any other restriction set to Enabled that mentions the kind of device you are using.
Microsoft notes that if no reboot is forced, a device installation restriction change won’t take effect until the system is restarted, so plan on a restart after changing anything in this folder.
Apply the change and test the drive
- Open Command Prompt as an administrator: search for cmd, right-click Command Prompt and choose Run as administrator.
- Type
gpupdate /forceand press Enter. According to Microsoft’s gpupdate command reference, the /force option “Reapplies all policy settings,” instead of only the ones that changed. There is a longer walkthrough in running gpupdate /force on Windows 10. - Unplug the USB drive, wait a few seconds and plug it back in.
- If the drive is still refused, restart the PC and test again. Microsoft’s removable devices troubleshooting guidance also pairs
gpupdate /forcewith a restart before retesting.
To confirm the change stuck, run gpresult /h gpresult.html again and check that the Removable Storage Access policies no longer appear as applied settings.
If the drive is still blocked
- The policy comes back: a domain or device management service is applying it again. That is the managed-PC case from the first section: ask IT.
- Device Manager: the drive or its controller may be turned off there. Open Device Manager, look under Disk drives and Universal Serial Bus controllers, and enable any device that shows as disabled.
- Security software: some antivirus and endpoint protection products have their own device control that blocks USB storage separately from Group Policy. Check that product’s own settings or ask whoever manages it.
- The port: try another USB port, or work through resetting USB ports on Windows 10.
- A physical lock: some SD cards and drives have a small write-protect switch. If you can read files but not save them, move the switch to the other position and reconnect.
- Firmware settings: some PCs can switch USB ports off in BIOS or UEFI setup. Check your PC maker’s own documentation for that model.
Turn the block back on
If you only needed the drive for a moment, or the PC is shared, restore the block when you are done.
- Open
gpedit.mscand go back to Computer Configuration > Administrative Templates > System > Removable Storage Access. - Double-click All Removable Storage classes: Deny all access, choose Enabled and click OK.
- Run
gpupdate /forcefrom an administrator Command Prompt, then reconnect the drive to confirm it is refused.
A narrower option is Removable Disks: Deny write access, which Microsoft’s reference lists under User Configuration: enabled there, it stops saving to removable disks while still allowing files to be read.
A note on Windows 10 support
Microsoft’s own wording: “Windows 10 has reached the end of support on October 14, 2025.” It adds that technical assistance, feature updates and security updates are no longer provided. Microsoft’s Windows 10 end of support page explains the options.
USB policy questions
Why does my USB drive work on one PC but not this one?
Removable storage policies are set per computer (or per user on that computer), not on the drive. A drive that works elsewhere but is refused here points to a policy, security software or a disabled device on this PC, not to a fault in the drive.
Why does the policy come back after I change it?
Something outside the PC is applying it. A domain’s Group Policy or a device management service such as Intune keeps applying its own settings. On a managed PC, the only lasting fix is a change by the administrator who set the rule.
Do I need to restart after changing the policy?
For the Removable Storage Access policies, gpupdate /force and reconnecting the drive is usually enough to test. For Device Installation Restrictions, Microsoft says the change waits for a restart unless one is forced, so restart before you decide it did not work.
Will Not Configured remove a rule my IT department set?
No. The local editor only changes the local policy. A rule from your organization keeps being applied by its own systems, which is why managed PCs need IT to make the change.
Once the drive opens, copy what you need and decide whether the block should go back on. For a shared PC, leaving All Removable Storage classes: Deny all access enabled between uses keeps the setting where you want it.

Kermit Matthews runs Live2Tech from just outside Philadelphia. He is an IT specialist with over 20 years of experience, from a university help desk to small-business IT, IT management and his own consulting practice, and has written tech guides full time since 2020. Steps are checked against the current software on a real device or the maker’s official documentation. More about Kermit.