Why Block USB Drives?
USB storage devices are the easiest way to steal data from a computer. An employee copies client files to a thumb drive and walks out. An attacker drops an infected USB in the parking lot and someone plugs it in. Every major compliance framework (NIST 800-171, ISO 27001, HIPAA) requires controls on removable storage devices.
Method 1: Make USB Drives Read-Only with Sherlock Forensics USB Write Blocker
Sherlock Forensics USB Write Blocker makes USB disks read-only. Windows can read them, but nothing can be written to them, which stops files from being copied to a USB drive. It does not deny access to the drive and does not block phones that connect over MTP. It covers USB mass storage (BOT) disks. USB Attached SCSI (UAS) enclosures, which include many fast USB-C NVMe enclosures, are not covered yet. For a full block, use Method 2 or Method 3.
The Pro edition uses sherlockwb.sys, a Microsoft-signed kernel filter driver that refuses every command able to change a disk, starting with the first command the disk receives.
Step-by-step
- Download USB Write Blocker. Get it from our product page. One .exe covers both editions.
- Activate Pro. Activate your Pro licence. The Microsoft-signed kernel driver installs itself.
- Turn write blocking ON. The control panel turns solid red. Disks that are already connected are left alone, so connect USB drives after this step.
- Verify. Try to copy a file to the USB drive. Windows reports the disk as write-protected and the copy fails.
The free version blocks with Windows' read-only disk attribute. The Pro Edition ($129 one-time) adds a Microsoft-signed kernel write blocker, per-disk block and allow, a signed audit log and blocking that stays on across restarts.
Method 2: Windows Group Policy
Windows Pro and Enterprise editions include Group Policy controls for removable storage:
- Press Win+R, type gpedit.msc, press Enter.
- Navigate to Computer Configuration > Administrative Templates > System > Removable Storage Access.
- To stop files being copied to USB drives, enable Removable Disks: Deny write access. To block the drives outright, also enable Removable Disks: Deny read access.
- To cover phones, CD and DVD drives and every other removable class as well, enable All Removable Storage classes: Deny all access instead.
- Run gpupdate /force from an administrator prompt, then reconnect the drive.
The policy path is the same on Windows 10 and on Windows 11 24H2 and 25H2. Windows 11 25H2 is an enablement package on the 24H2 code base, so nothing moved between the two.
Limitations: This is all-or-nothing. You cannot block one USB drive and allow another. It does not work on Windows Home edition. Any user with local admin privileges can reverse it. There is no audit trail of who changed the policy or when.
Method 3: Registry Edit
You can disable the USB storage driver directly in the Windows Registry:
- Press Win+R, type regedit, press Enter.
- Navigate to HKLM\SYSTEM\CurrentControlSet\Services\USBSTOR.
- Change the Start value from 3 (enabled) to 4 (disabled).
- Restart the computer.
From an administrator PowerShell prompt the same change is one line: Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Services\USBSTOR' -Name Start -Value 4
Fast USB 3 and USB-C drives often connect over USB Attached SCSI (UAS). Windows loads the UASPStor driver for those instead of USBSTOR, so the USBSTOR value does not stop them. Microsoft does not document a registry value for those drives. Test the block with the drives you need to stop. Defender device control can allow or deny those drives by vendor ID, product ID or serial number.
Limitations: This blocks ALL USB storage devices with no exceptions. There is no per-device control. Any admin can reverse it. One wrong registry edit can break other system services. There is no logging of when the change was made or who made it.
Comparison
| Feature | USB Write Blocker | Group Policy | Registry |
|---|---|---|---|
| Per-device control | Yes (Pro) | No | No |
| Audit logging | Signed audit log ($129 Pro) | No | No |
| What it does | Makes USB disks read-only | Denies writes or all access | Disables USB storage |
| Windows editions | Windows 10 (2004 or later) and 11, x64 | Pro and Enterprise | All editions |
| A local admin can undo it | Yes | Yes | Yes |
| Pushed to a fleet | No, one machine at a time | Yes, through Active Directory | With Intune or a script |
Also handling email evidence? See how to open PST files without Outlook. Opening PDFs from unknown sources? Read how to safely open unknown PDFs.
Blocking USB Devices Across a Fleet
The three methods above block USB devices on a single machine. To block USB devices across a domain or a fleet of endpoints, the trade-offs change. Group Policy scales through Active Directory but only where every machine is domain-joined and running a Pro or Enterprise edition; a local administrator can still reverse it. The registry method reaches the Home editions that Group Policy cannot, but pushing and auditing a registry value across hundreds of endpoints needs a configuration-management layer of its own. Sherlock Forensics USB Write Blocker is a per-workstation forensic write blocker, not a centrally managed device-control or data-loss-prevention platform. For policy-driven USB control across many endpoints, use Group Policy, Intune or Defender device control.
Block USB storage with Intune
Intune reaches machines that Group Policy cannot, such as laptops that never join the domain. In the Intune admin center, go to Devices > Manage devices > Configuration > Create > New policy. Pick Windows 10 and later with the Settings catalog profile type. Add the Device Installation Restrictions settings from Administrative templates > System > Device installation, then enable Prevent installation of devices not described by other policy settings. List the device IDs or device setup classes you still allow, such as keyboards and mice, in the two Allow settings. This is an allowlist: any new device that is not listed is refused, so test it on a pilot group first. Microsoft walks through it in Restrict USB devices using the settings catalog in Microsoft Intune.
Defender for Endpoint device control
Microsoft Defender for Endpoint device control goes further on onboarded Windows 10 and Windows 11 devices. Its removable storage policies control read, write and execute access by device, device type or user group. One approved drive can be allowed by vendor ID, product ID or serial number while every other USB disk is denied or made read-only. Audited access shows up in advanced hunting. Device control does not run on Windows Server.
Why not Device Manager?
Disabling a USB host controller in Device Manager stops USB drives, but it also stops every keyboard, mouse and other device on that controller. Any local administrator can turn it back on in the same window and nothing records the change, so it is not a control.
GPO vs registry vs per-device blocking
Group Policy and the registry both block USB devices coarsely: mass storage is on or off for the whole machine. Neither can allow one sanctioned encrypted drive while blocking the rest. Per-disk write blocking is narrower: Sherlock Forensics USB Write Blocker Pro can keep one known drive writable with an "always allow" entry in Device Memory while every other USB disk connects read-only.
Read-only USB vs a full block and the audit trail
Some investigations need read-only USB rather than a full block, so existing files can be copied off the drive but nothing can be written back. A full block refuses the device outright. Where you have to prove the control held, an audit log of every blocked USB device insertion, with timestamp and hardware ID, is the compliance artifact HIPAA, PCI-DSS and SOC 2 reviewers ask for. Group Policy and registry edits leave no such record. Sherlock Forensics USB Write Blocker Pro keeps a signed audit log.
When each method to block USB devices fails
Group Policy fails on Home editions and on any machine that leaves the domain. The registry method fails the moment a user with local admin flips the value back. Both fail silently, with no alert that USB devices are no longer blocked. A local administrator can switch off a software write blocker too, so pair any method with removing local admin rights.
Frequently Asked Questions
Can I block USB drives but allow keyboards and mice?
Yes. Group Policy's Removable Storage Access settings and the USBSTOR registry method act on USB mass storage only, so keyboards and mice keep working. Sherlock Forensics USB Write Blocker also acts only on USB mass storage disks, which it makes read-only rather than blocking.
Does blocking USB work on Windows Home?
Group Policy (gpedit.msc) is not available on Windows Home edition. The registry method works on every edition, including Home. Sherlock Forensics USB Write Blocker runs on Windows 10 (2004 or later) and Windows 11, x64.
Can users bypass USB blocking?
Registry edits and Group Policy settings can be reversed by any user with local admin privileges. The same is true of software controls, including Sherlock Forensics USB Write Blocker, which a local administrator can switch off. If users must not undo the block, remove their local admin rights.
How do I block USB devices across an entire domain or fleet?
Group Policy pushes a USB block through Active Directory to every domain-joined Pro or Enterprise machine, but not to Home editions and not against a local admin who reverses it. For devices managed in Intune, use a Settings catalog profile with the Device Installation Restrictions settings. To allow approved drives by serial number, use Defender for Endpoint device control. Sherlock Forensics USB Write Blocker is a per-machine forensic tool, not a fleet device-control platform.
What is the difference between blocking USB devices and read-only USB?
A full block refuses USB storage devices outright. Read-only USB lets existing files be copied off the drive but blocks any write, which suits evidence handling. Group Policy can deny write access only or deny read access too. The registry method is a full block. Sherlock Forensics USB Write Blocker does read-only.
Do these methods work on Windows 11 24H2 and 25H2?
Yes. The Removable Storage Access policies, the USBSTOR registry value and the Intune settings are the same on Windows 10 and on Windows 11 24H2 and 25H2. Windows 11 25H2 is an enablement package on the 24H2 code base. Sherlock Forensics USB Write Blocker runs on Windows 10 (2004 or later) and Windows 11, x64.
Why does the registry block miss some USB drives?
Fast USB 3 and USB-C drives often connect over USB Attached SCSI (UAS), which loads the UASPStor driver rather than USBSTOR. Setting USBSTOR to 4 leaves those drives working. Microsoft does not document a registry value for those drives. Test the block with the drives you need to stop. Defender device control can allow or deny those drives by vendor ID, product ID or serial number.
