Rufus error 0x80070032, “The request is not supported,” usually appears when you try to create a bootable USB drive and the tool cannot perform a required operation on your USB device or system. This guide walks you through the most common causes and fixes, from simple USB port changes to adjusting Windows settings, so you can get back to creating your bootable drive.
What You’ll Need
- A USB flash drive (at least 8 GB, but 16 GB or more is recommended for most ISOs)
- The ISO file you want to write (Windows, Linux, etc.)
- Rufus (latest version) downloaded from the official website
- Administrator access to your Windows PC
- Possibly a second USB drive for testing if the first one is faulty
Step-by-Step
- Run Rufus as Administrator. Right-click the Rufus executable and select “Run as administrator.” This ensures Rufus has the necessary permissions to access low-level disk functions. Many 0x80070032 errors are simply due to missing admin rights.
- Check the USB drive connection. Unplug the USB drive and plug it into a different USB port, preferably a USB 2.0 port (often black) on the back of your PC. Avoid USB hubs and front-panel ports that may not provide stable power. If the error persists, try a different USB drive entirely.
- Format the USB drive using Windows built-in tool. Open File Explorer, right-click the USB drive, select “Format,” choose FAT32 (or NTFS if the ISO is larger than 4 GB), and click “Start.” After formatting, try Rufus again. This clears any partition table issues that might trigger the error.
- Use Rufus’s “List USB Hard Drives” option. In Rufus, click the arrow next to the “Show advanced drive properties” button (usually a small triangle icon) and check “List USB Hard Drives.” This makes Rufus detect USB drives that are not showing up normally.
- Disable Windows Write Protection. If your USB drive is write-protected, you may see this error. Open Command Prompt as administrator and type
diskpartthenlist disk. Identify your USB drive number (e.g., Disk 1), then typeselect disk 1(replace 1 with your number), thenattributes disk clear readonly. Exit diskpart and try Rufus again. - Change the Rufus partition scheme. In Rufus, under “Partition scheme,” try switching between MBR and GPT. Some UEFI systems require GPT, while older BIOS systems need MBR. If you’re unsure, try both. Also, under “Target system,” select “BIOS or UEFI” for maximum compatibility.
- Disable Windows Defender or third-party antivirus temporarily. Antivirus software can interfere with Rufus’s operations. Temporarily disable real-time protection (Windows Defender: Settings > Privacy & Security > Windows Security > Virus & threat protection > Manage settings > Real-time protection off) and try again. Re-enable after.
- Update Rufus to the latest version. Go to the official Rufus website and download the newest version. Older versions may have bugs that cause this error. Also, check if your Windows version has pending updates and install them.
- Try a different ISO file. The ISO itself might be corrupted. Download the ISO again from the official source, or verify its checksum (e.g., SHA-256) against the official value. A corrupted ISO can cause unexpected errors during writing.
- Use Rufus’s “Check device for bad blocks” option. In Rufus, under “Format Options,” check “Check device for bad blocks.” Set the pass count to 1 or 2. This will scan the USB drive for errors. If bad blocks are found, the drive may be faulty and you should replace it.
Common Mistakes
- Using a USB 3.0 port on an old system. Some older systems have compatibility issues with USB 3.0 ports. Use a USB 2.0 port if available.
- Not running Rufus as administrator. This is the most frequent oversight. Without admin rights, Rufus cannot access the disk and throws this error.
- Selecting the wrong USB drive. Double-check that you have selected the correct USB drive in Rufus. Accidentally selecting a hard drive can cause errors and data loss.
- Using a USB drive with a hidden write-protection switch. Some USB drives have a physical switch on the side. If it’s set to “Lock,” the drive is read-only.
- Ignoring the “Target system” setting. For UEFI systems, you need “UEFI (non CSM)” or “UEFI (CSM)” depending on your BIOS settings. Mismatched settings can cause errors.
Tips
- Use a high-quality USB drive. Cheap or counterfeit drives are more prone to errors. Stick to reputable brands.
- Keep Rufus updated. The developer regularly fixes bugs and adds support for new ISOs. Always use the latest version.
- Write the ISO in DD mode if needed. For Linux ISOs, Rufus offers a “DD image” mode. If the default ISO mode fails, try switching to DD mode by clicking the arrow next to “Write in ISO Image mode” and selecting “Write in DD Image mode.”
- Check your BIOS settings. If you’re creating a bootable USB for UEFI, ensure Secure Boot is disabled temporarily, as some ISOs are not signed.
- Use a different USB drive for testing. If you have another USB drive, try it. This helps isolate whether the issue is with the drive or the system.
Troubleshooting
If the error persists after trying all the steps above, here are additional things to try:
- Check the USB drive’s health. Use a tool like ChipGenius or H2testw to check if the drive is genuine and has the advertised capacity. Counterfeit drives often fail during writing.
- Try a different computer. The issue might be with your PC’s USB controller or BIOS. Test the USB drive on another computer. If it works there, the problem is your system.
- Update your USB drivers. Go to Device Manager, expand “Universal Serial Bus controllers,” right-click each USB Root Hub, and select “Update driver.” Restart your PC after updating.
- Disable fast startup. Windows Fast Startup can sometimes interfere with USB device initialization. Go to Control Panel > Power Options > Choose what the power buttons do > Change settings that are currently unavailable > Uncheck “Turn on fast startup.” Restart.
- Use Rufus’s “Log” feature. In Rufus, click the “Log” tab (or press Ctrl+L) to see detailed logs. The error message may give more specific clues. You can also save the log and search online for the exact error.
- Try a different USB writing tool. If Rufus still fails, try using the Windows Media Creation Tool (for Windows ISOs) or balenaEtcher (for Linux ISOs). This helps determine if the issue is Rufus-specific.
- Check if your USB drive is in a “raw” state. Open Disk Management (right-click Start > Disk Management). If your USB drive shows as “RAW” or “Unallocated,” right-click it and format it to NTFS or FAT32. Then try Rufus again.
Frequently Asked Questions
Q: What does error 0x80070032 mean exactly?
A: It means Windows returned an “ERROR_NOT_SUPPORTED” status, indicating that the requested operation is not supported by the device or system. In Rufus, it usually relates to USB device incompatibility or permission issues.
Q: Will this error damage my USB drive?
A: No, the error itself is harmless. It just stops the writing process. However, repeatedly trying to write to a faulty drive may cause further wear, so it’s best to test the drive’s health.
Q: Can I fix this error by using a different USB port?
A: Yes, often the issue is with the USB port or controller. Try a different port, especially a USB 2.0 port, and avoid hubs.
Q: Does the size of the USB drive matter?
A: Not directly, but the drive must be large enough to hold the ISO. For Windows 10/11 ISOs, you need at least 8 GB, but 16 GB is recommended. Also, some very large USB drives (e.g., 256 GB) may have compatibility issues with older systems.
Q: Why does Rufus work on another computer but not mine?
A: This points to a system-specific issue, such as USB drivers, BIOS settings, or Windows configuration. Follow the troubleshooting steps above, especially updating drivers and disabling fast startup.
Q: Is it safe to disable antivirus to use Rufus?
A: Yes, temporarily disabling real-time protection is safe if you do it only for a few minutes and re-enable it immediately after. Just make sure you trust the ISO file you’re writing.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Fix 0x80070422 on Windows Server (Step-by-Step)
- Google Chrome Helper: What It Is & How to Disable
- How to Troubleshoot a Malfunctioning Driver on Windows
- How to Create Folders in Microsoft Outlook
- Fix Status Range List Conflict 0xc0000282 in Windows
- Fix Software Not Uninstalling on Windows 10