Checklist
- I looked at https://github.com/pbatard/rufus/wiki/FAQ to see if my question has already been answered.
- I performed a search in the issue tracker for similar issues using keywords relevant to my problem, such as the error message I got from the log.
- I clicked the ‘Log’ button or pressed Ctrl—L in Rufus, and copy/pasted the log into the line that says
<FULL LOG>below. - The log I am copying is the FULL log, starting with the line
Rufus version: x.y.z— I have NOT removed any part of it.
Additionally (if applicable):
- I ran a bad blocks check, by clicking Show advanced format options then Check device for bad blocks, and confirmed that my USB is not defective.
- I also tried one or more of the following:
- Using a different USB drive.
- Plugging the USB into a different port.
- Running Rufus on a different computer.
- If using an image, I clicked on the
(✓)button to compute the MD5, SHA1 and SHA256 checksums, which are therefore present in the log I copied. I confirmed, by performing an internet search, that these values match the ones from the official image.
Issue description
Error[0xC003045D]
Log
Rufus x86 v3.11.1678 (Portable)
Windows version: Windows 10 64-bit (Build 19041.508)
Syslinux versions: 4.07/2013-07-25, 6.04/pre1
Grub versions: 0.4.6a, 2.04
System locale ID: 0x0809 (en-GB)
Will use default UI locale 0x0809
SetLGP: Successfully set NoDriveTypeAutorun policy to 0x0000009E
Localization set to 'en-US'
Notice: The ISO download feature has been deactivated because 'Check for updates' is disabled in your settings.
Found USB 2.0 device 'SanDisk Ultra USB Device' (0781:558A)
NOTE: This device is a USB 3.0 device operating at lower speed...
1 device found
Disk type: Removable, Disk size: 32 GB, Sector size: 512 bytes
Cylinders: 3738, Tracks per cylinder: 255, Sectors per track: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0xAEC37384
Drive has a Zeroed Master Boot Record
Partition 1:
Type: FAT32 LBA (0x0c)
Size: 28.6 GB (30752620544 bytes)
Start Sector: 32, Boot: No
Format operation started
Requesting disk access...
Will use 'F:' as volume mountpoint
Deleting partitions (This may take a while)...
Deleting ALL partition(s) from disk '\?PhysicalDrive2':
● Partition 1 (offset: 16384, size: 28.6 GB)
Could not delete partitions: [0x8007045D] The request could not be performed because of an I/O device error.
Opened \.PhysicalDrive2 for exclusive write access
I/O boundary checks disabled
Could not lock access to \?Volume{f894b532-6b2b-11e9-847e-d8cb8ada668c}: [0x00000005] Access is denied.
Could not lock volume
Re-mounted volume as F: after error
Found USB 2.0 device 'SanDisk Ultra USB Device' (0781:558A)
NOTE: This device is a USB 3.0 device operating at lower speed...
1 device found
Disk type: Removable, Disk size: 32 GB, Sector size: 512 bytes
Cylinders: 3738, Tracks per cylinder: 255, Sectors per track: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0xAEC37384
Drive has a Zeroed Master Boot Record
Partition 1:
Type: FAT32 LBA (0x0c)
Size: 28.6 GB (30752620544 bytes)
Start Sector: 32, Boot: No
Found USB 2.0 device 'SanDisk Ultra USB Device' (0781:558A)
NOTE: This device is a USB 3.0 device operating at lower speed...
1 device found
Disk type: Removable, Disk size: 32 GB, Sector size: 512 bytes
Cylinders: 3738, Tracks per cylinder: 255, Sectors per track: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0xAEC37384
Drive has a Zeroed Master Boot Record
Partition 1:
Type: FAT32 LBA (0x0c)
Size: 28.6 GB (30752620544 bytes)
Start Sector: 32, Boot: No
Format operation started
Requesting disk access...
Will use 'F:' as volume mountpoint
Deleting partitions (This may take a while)...
Deleting ALL partition(s) from disk '\?PhysicalDrive2':
● Partition 1 (offset: 16384, size: 28.6 GB)
Could not delete partitions: [0x8007045D] The request could not be performed because of an I/O device error.
Opened \.PhysicalDrive2 for exclusive write access
I/O boundary checks disabled
Analyzing existing boot records...
Drive has a Zeroed Master Boot Record
Clearing MBR/PBR/GPT structures...
Erasing 32 sectors
write_sectors: Write error [0x0000045D] The request could not be performed because of an I/O device error.
StartSector: 0x00000000, nSectors: 0x1, SectorSize: 0x200
Retrying in 5 seconds...
write_sectors: Write error [0x0000045D] The request could not be performed because of an I/O device error.
StartSector: 0x00000000, nSectors: 0x1, SectorSize: 0x200
Retrying in 5 seconds...
write_sectors: Write error [0x0000045D] The request could not be performed because of an I/O device error.
StartSector: 0x00000000, nSectors: 0x1, SectorSize: 0x200
Retrying in 5 seconds...
write_sectors: Write error [0x0000045D] The request could not be performed because of an I/O device error.
StartSector: 0x00000000, nSectors: 0x1, SectorSize: 0x200
Could not reset partitions
Re-mounted volume as F: after error
Found USB 2.0 device 'SanDisk Ultra USB Device' (0781:558A)
NOTE: This device is a USB 3.0 device operating at lower speed...
1 device found
Disk type: Removable, Disk size: 32 GB, Sector size: 512 bytes
Cylinders: 3738, Tracks per cylinder: 255, Sectors per track: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0xAEC37384
Drive has a Zeroed Master Boot Record
Partition 1:
Type: FAT32 LBA (0x0c)
Size: 28.6 GB (30752620544 bytes)
Start Sector: 32, Boot: No
Found USB 2.0 device 'SanDisk Ultra USB Device' (0781:558A)
NOTE: This device is a USB 3.0 device operating at lower speed...
1 device found
Disk type: Removable, Disk size: 32 GB, Sector size: 512 bytes
Cylinders: 3738, Tracks per cylinder: 255, Sectors per track: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0xAEC37384
Drive has a Zeroed Master Boot Record
Partition 1:
Type: FAT32 LBA (0x0c)
Size: 28.6 GB (30752620544 bytes)
Start Sector: 32, Boot: No
A lot of users have been getting the “The Request could not be performed because of an I/O Device Error” message either while using Diskpart or on Virtual Disk Manager and this prevents them from accessing the disk or sometimes from being able to view its properties and format it.
In this article, we have listed some common reasons due to which the error message is seen such as conflicting partition letters, faulty Storage Device connection, etc. In addition to that, we have listed some comprehensive solutions that should get rid of this error completely and help you access the storage device normally.
After sifting through user recommendations and troubleshooting guides regarding this error message, we came to the conclusion that the following are the primary reasons due to which it is triggered.
- Ports: Some ports on your computer might not be able to work properly due to which the Storage device connected to them isn’t being properly recognized by Windows. Therefore, it is recommended to switch SATA ports if you are getting the “The Request could not be performed because of an I/O Device Error” error with a storage device and switch the USB ports if you are getting this with a USB.
- Outdated Drivers: Sometimes, outdated drivers can cause the “Diskpart has encountered an error The Request could not be performed because of an I/O Device Error” message and prevent the command from being carried out. Therefore, we recommend that you check for any outdated storage device drivers and update them ASAP.
- Bad Sectors: In your storage device, due to prolonged usage, several bad sectors might be created due to storage failures and wearing out of the device. Therefore, it is recommended to perform a scan and amend any bad sectors that might be present on your storage device.
- Incorrect Configuration: It is possible that your computer isn’t using the proper storage configuration mode to be able to run the Storage device due to which you are running into this error message. Basically, some Windows versions have the ability to determine the transfer modes for the device and if the incorrect one is selected, you will run into the “The Request could not be performed because of an I/O Device Error” message.
- Partition Letter: The Partition letter assigned to the storage device if already occupied by another partition or unpartitioned sector, will create complications and incompatibility. Therefore, assigning the partition a new letter can sometimes get rid of the error message.
- General Misconfiguration: Sometimes, Windows might run into conflicts or internal misconfiguration due to which it is unable to launch into the local disk drive and throws this error. Therefore, we recommend that you check to see if troubleshooting the issue using the default troubleshooter fixes the error message.
- USB Controllers: Some USB Controller drivers on your computer might be malfunctioning or they might be simply outdated. Therefore, checking for any misconfiguration, fixing them, and checking if there are any updates available for the drivers might be the way to go.
Now that you have been familiarized with most of the reasons behind this error, we can finally begin the fixing process.
Before You Start:
The simplest troubleshooting technique in the case of this error message is to look for any loose connections and fix them back properly. Initially make sure that the cable is fully plugged into the hard drive or the USB port and also look that there does not exist any breaks in the cable. Moreover, also try to check the device on another computer to see if it’s not your computer causing the issue. These are some of the simple and potential fixes in getting you through the error successfully but if you still aren’t able to resolve the issue then proceed with some of the advanced solutions listed below.
Fixing the request could not be performed because of an i/o device error USB:
Solution 1: Switch Ports
It so happens that quite a lot of times the fault may exist in the USB port so try plugging in your hard drive or USB into an alternate port. Also, plug in your hard drive into the USB ports on the motherboard instead of the ports on the case front. Moreover, try to switch from USB 2.0 to 3.0 or vice versa to see which connection your drive supports better. You may also plug your SD card into another card reader or try to connect the device directly via a cable. Check to see if switching the port gets rid of the The Request could not be Performed because of an I/O Device Error message.
Solution 2: Update USB Driver
Sometimes the old or defective device drivers can also take a toll on your device and can give rise to such errors. In order to fix this update your device drivers instantly by following the below-mentioned steps:
- Open your PC and type in “Device Manager” in the search bar located near the Start menu. Then click to open it.
Open Device Manager - In here look for the option of “Universal Serial Bus controllers” and afterward click to expand it.
- From the pop-up list search for the specific device causing the issue and right-click on it to select the option of “Update Driver”.
Update Device Drivers - Windows will start looking up for the latest driver available for your device and will take you through downloading and installing the updated driver automatically.
- Finally, check to see if the error got resolved now.
Solution 3: Repair Bad sectors
Chkdsk is used to check and repair a device for any sort of error so in order to check your disk for any sort of errors and repairing it proceed with these steps:
- Open your PC and search for “Command Prompt” from the search bar located near the Start menu, right-click on it and select “Run as Administrator”.
Run Command Prompt Note: You specifically need to check for your drive name e.g. if your drive is shown as “Local Disk E” your drive letter entered with the chkdsk command would be E.
- Now type the following command in the command prompt window and press Enter:
chkdsk E:/f/r/x
- Windows will start checking for your device errors and will repair them automatically.
- Lastly, check to see if you have been able to resolve the Request could not be performed because of an I/O Device Error now.
Solution 4: Change the Transfer Mode
Your windows cannot transfer files if the transfer mode is different and not compatible with the OS. To change the transfer mode proceed with these steps:
- Open your PC and type in “Device Manager” in the search bar located near the Start menu. Then click to open it.
Open Device Manager - In here look for “IDE ATA/ATAPI Controllers” and click to expand this option.
- Now right-click on the “Primary IDE Channel” and then click to select the “Advanced” settings tab at the top of the window.
- In the “Transfer Mode” box select “PIO only” for the device causing errors and then click “OK”.
Select PIO Only Option - Exit from all the windows and now observe if the issue got resolved.
Solution 5: Disconnect All External Devices
Sometimes the other devices connected to your computer can also be troublesome so disconnect all sorts of extra devices and restart your computer again. Now only connect those devices which are necessary and see if the problem is removed.
Solution 6: Changing the Drive Letter
Some users were also able to resolve their I/O device error by simply changing their drive letter. So in order to change the drive letter follow these steps:
- On the search bar near the Start menu type in “Disk Management” and click to open it up.
Disk Management - When the disk management window opens up it will show you all of the connected storage devices. From here right-click on the particular device causing errors.
- Then click to select “Change Drive Letter and Paths” and a new window will open up and from here click to select the “Change” option.
Change Drive letter and paths - Now assign a new drive letter to the drive from the drop-down menu and click to select “OK”.
- Close all windows and now check whether the problem still persists or not.
Solution 7: Use Windows Troubleshooter
Windows has a built-in troubleshooting feature that searches for all possible errors and provides possible solutions. To run the troubleshooter on your computer implement the following steps:
- Open your PC and search for “Troubleshoot” in the search bar located near the Start menu.
- When in the troubleshoot settings window here look for “Hardware and Devices” in the right pane and click on “Run the Troubleshooter” to select it.
Run the troubleshooter - The Windows will start troubleshooting for any errors and will provide you with the best possible solutions sidewise.
- Carry out those fixes in order to get through the error instantly.
Solution 8: Scan with Windows Drive Check Facility
In order to check a drive for error with windows default drive check you need to carry out these steps:
- Open your PC and go to “This PC” on the main window and right-click on the drive causing issues.
Click on This PC - Then click to select “Properties” from the pop-up list and in the Properties tab navigate to select the “Tools” tab located at the top of the window.
- Proceed to the “Error Checking” section and click on the “Check” option.
Check Drive - A new window will open up asking you if you want to proceed to scan the drive. Press the option of “Scan Drive”.
Scan Drive
Solution 9: Clean Boot Your PC
Sometimes the other third-party apps installed on your computer can be in a clash with your device causing it not to work properly. To check if any other program is at a clash with your drive proceed with these steps:
- Search for “msconfig” in the search bar located near the Start menu to open up the “System Configuration” window.
Typing in “Msconfig” - When the window opens click on the “Services” tab placed at the top.
- Scroll down to the bottom of the window to checkmark the option of ‘’Hide all Microsoft Services’’. Then click on “Disable All” at the bottom of the window.
Hide all Microsoft services - Now proceed to open up the “Startup” tab and click to open “Task Manager”.
- When the task manager window opens up in the Startup tab click to select “Disable” at the bottom of the screen.
- Close the task manager window and go back to the “Services” tab and click OK.
- Close all windows and restart your computer now to check if the error still persists or not.
Solution 10: Boot Your PC into Safe-Mode
To check if any third-party install isn’t causing you issues you can boot into Safe-Mode. Safe-Mode enables you to use your computer with very minimal tasks and apps running in your background. To get into Safe-Mode follow these steps:
- Press the “Windows + R” keys on your keyboard to open up the RUN dialog box.
- When the RUN window appears up type in “msconfig” in the dialog box and press Enter.
Typing in “Msconfig” - In the System configuration window navigate to select the “Boot” tab beside the General tab.
- Below the “Advanced” options tick mark the “Safe-Mode” check box and make sure “Minimal” is selected.
Enter Safe Mode - Press OK and select “Restart”.
- Once you are booted into Safe-Mode, try transferring files now and check to see if The Request could not be Performed because of an I/O Device Error has been fixed.
Solution 11: Reinstall USB Controllers
Sometimes errors are caused by defective USB controllers so try to reinstall them by carrying on the below-listed steps:
- Search for “Device Manager” in the search bar located near the Start menu.
Open Device Manager - In here look for “Universal Serial Bus Controllers” on the new window and click to expand this option.
- Now right-click on the “USB Controller” of your drive and click to select “Uninstall”.
Uninstall Device Driver - Close the window and restart your computer. Your computer will automatically reinstall the missing USB controller.
- Finally, proceed to check if the virtual disk manager the request could not be performed because of an i/o device error got fixed now.
Solution 12: Fixing I/O Device Error in CMD
- On the search bar near the Start menu search for “Command Prompt”, right-click on it to select “Run as Administrator”.
Run Command Prompt - When the command prompt window opens up type in the below-listed commands respectively:
list disk (press Enter)
The command prompt window will show you a list of drives connected so here you need to look for the drive causing the issue. If in case its Disk 1, type:
select disk 1 (Press Enter) attributes disk clear readonly (Press Enter) clean (Press Enter) create partition primary (Press Enter) format fs=fat32 (Press Enter)
Note: This will format the drive, thus, erasing all data on it.
Check to see if implementing this has fixed the “The Request could not be Performed because of an I/O Device Error” message.
Solution 13: Contact Manufacturer
If none of the above-listed fixes worked for you then there must be certain hardware issues and in such a scenario you would need to backup all of your data from the affected drive. To backup your data, you will be needing an expert’s help so contact the drive’s manufacturer for assistance in this case.
Hopefully, the aforementioned fixes will lead you towards eradicating the problem completely but if the issue still exists you may Contact Us here.
You may receive the error message “the request could not be performed because of an i/o device error USB” due to the connection issue between the storage device and PC. Sometimes, this error is also triggered due to corrupted or outdated hardware drivers. Regardless the causes, this error can be easily fixed by checking the hardware connection, running chkdsk utility, updating the device drivers and many others solutions mentioned in this blog.
When the USB i/o device error occurs, you won’t be allowed to read/write a disk. Additionally, you will not be able to edit or transfer the any file of USB. In other words, you can say that, the data or files stored in your USB drive are at great risk of being lost permanently.
But since you have visited this webpage then I must say that you don’t have to worry at all. Because this post contains 9 working fixes to troubleshoot device i/o error USB drive and recover data from USB drive easily.
Rated Excellent on Trustpilot
Free USB Drive Recovery Tool.
Recover data from USB drives, Pendrives, SSDs, HDDs, and other devices on Windows. Try now!
Quick Navigation:
- What Is I/O Device Error?
- How To Fix USB Flash Drive I/O Device Error
- Recover Deleted Data From USB Flash Drive
- How Do I Initialize A Disk With An I/O Error?
- What Causes USB Flash Drive I/O Device?
Before fixing this issue, let us know more about the pendrive i/o device error.
What Is I/O Device Error On USB Flash Drive Error?
I/O stands for Input/Output and I/O device error is actually an issue with the device that stops Windows from reading or writing the data on it.
This error appears not only on USB flash drives but also on SSD or HDD, SD card, external hard drive, CD/DVD, etc. When you get this error, you will be unable to read or write any new data to that device on your Windows PC.
Generally, when you get I/O device error, you may get these below two error messages:
- The request could not be performed because of an I/O device error USB
- Only part of a read process memory or write process memory request was completed
Also, you may get error code errors such as error 6, error 21, error 103, error 105, and error 131.
Quick Solutions |
Step-By-Step Solutions Guide |
|
Fix 1: Check The Hardware Connection |
If there is a loose connection or faulty cable or USB port, it can cause this error to take place…Complete Steps |
|
Fix 2: Fix I/O Error USB Flash Drive In Command Prompt |
Using a command prompt will help you run chkdsk function that will check…Complete Steps |
|
Fix 3: Start Computer In Clean Boot State |
Starting the computer in a clean boot state can make you clean…Complete Steps |
|
Fix 4: Change The Drive Letter |
You can change the drive letter and fix this issue…Complete Steps |
|
Fix 5: Update The Device Driver |
Due to the outdated device drivers, it is possible that you may get this issue…Complete Steps |
|
Fix 6: Reinstall USB Controllers |
Try to solve this error by reinstalling the USB controllers…Complete Steps |
|
Fix 7: Change The Transfer Mode In IDE Channel Properties |
If Windows is trying to use a transfer mode that your device does not support…Complete Steps |
|
Fix 8: Repair USB IO Device Error With ‘Error Checking |
Error Checking scans internal & external hard drives for several file system errors…Complete Steps |
|
Fix 9: Seek Help From Hardware Manufacturer |
It is suggested to contact the technical support of the hardware manufacturer for help…Complete Steps |
Fix #1: Check The Hardware Connection
The very first fix you can try to fix USB flash drive I/O device error is to check the connection. If there is a loose connection or faulty cable or USB port, then it can cause this error to take place. You can try these fixes below to overcome this issue:
- Try to connect USB flash drive to another computer
- Connect the USB flash drive to another USB port
- Replace the USB cable
However, after trying these, even if you get I/O device error then you can try other solutions mentioned below.
You May Also Read: Fix Please Insert A Disk Into USB Drive Without Losing Data
Fix #2: Fix I/O Device Error USB Flash Drive In Command Prompt
Using a command prompt will help you run chkdsk function that will check and fix usb flash drive i/o device error in command prompt. So, to do so, follow the below steps:
- First of all, press Windows keys and then type there cmd to open the menu. Next, right-click on the option ‘Command Prompt’ and then choose ‘Run as administrator’.
- Now, you have to click ‘Yes’ to simply launch the Command Prompt as Administrator.
- Next, in the new Command Prompt window, you have to type there chkdsk E: /f /r /x where you can replace E with the drive letter you are using.
This fix will also help you fix USB flash drive using cmd command and further recover data from it using the data recovery tool mentioned below.
Fix #3: Start Computer In Clean Boot State
Starting the computer in a clean boot state can make you clean whether i/o device error USB external hard drive is caused due to a driver or application conflict. If it is, then it will help you know which application or software is causing this error.
So, in this case, it is easy to start the computer in a clean boot. To start the computer in the clean boot state, follow the below steps:
- First of all, you have to log in Windows as Administrator account and then press Windows + R keys together and it will open Run dialog box.
- You can then type msconfig in Run box and then press Enter key and it will open System Configuration window.
- Next, you have to click ‘General’ tab on System Configuration window and then select Selective startup and then simply uncheck the ‘Load startup items’ box.
- Now, click the ‘Services’ tab on the pop-up window and then check the box ‘Hide all Microsoft services’ and then tap ‘Disable all’.
- Next, you have to go to the Startup option and then click there ‘Open Task Manager’ and this will open Task Manager
- After this, you have to select all startup items and then click ‘Disable’ and then again click ‘x’ to close the Task Manager.
- Next, you have to go back to ‘System Configuration’ and then Startup and then click ‘OK’ and then reboot the Windows PC.
You Might Also Read: Complete Steps To Fix ‘USB Drive Detected But Not Accessible’ Issue
Fix #4: Change The Drive Letter
Sometimes you may also get USB flash drive I/O device error because the system doesn’t show its drive letter when connected to the PC.
In this case, you can change the drive letter and fix this issue and get the request could not be performed because of an i/o device error disk management. So, follow the below steps to do so:
- First of all, you have to go to ‘This PC’ and then right-click and then choose the option ‘Manage’ and then go to ‘Disk Management’.
- Next, you have to right-click the USB flash drive and then go to USB flash drive and then select ‘Change Drive Letter and Paths’.
- Now, click ‘Change’ in the new window and then assign a new drive letter to the USB flash drive and then click ‘OK’.
Fix #5: Update The Device Driver To Fix ‘The Request Could Not Be Performed Because Of An I/O Device Error USB’
Due to the outdated device drivers, it is possible that you may get a USB flash drive I/O device error. As for example, ‘there is no media in USB flash drive’ or USB not showing up in Windows and the ‘the request could not be performed because of an IO device error USB’.
So, to update the driver drive, you have to follow the below steps:
- Firstly, you have to connect the USB flash drive to the PC and then right-click on the option ‘This PC’ and then choose ‘Manage’.
- Next, you have to click ‘Device Manager’ and then go to ‘Disk drives’. Next, search and right-click the problematic USB flash drive and then simply select the option there ‘Update driver’.
- Now, you have to click the option ‘Search automatically search for driver software online’.
- After doing so, wait for the driver to be updated and then reboot the computer. You can further open the device to check whether the USB flash drive I/O error still persists.
Fix #6: Reinstall USB Controllers
When you get any I/O device error, you also try to solve this error by reinstalling USB controllers. Yes, doing so can somehow fix the i/o device error flashdisk. Follow the below steps to do so:
- At first, click the Windows + X keys together to open the power users’ menu.
- Next, you have to click on Computer Management and then go to Device Manager.
- Now, you have to expand Universal Serial Bus controllers and then make a right-click on a device and click Uninstall.
- Next, you have to repeat for each device and then after you complete this task, restart your PC. After your PC gets restarted, the USB controllers will install automatically.
Fix #7: Change The Transfer Mode In IDE Channel Properties
If Windows is trying to use a transfer mode that your device does not support then you will encounter this error message. So, to remove or fix USB flash drive I/O device error, you have to switch the transfer mode:
- Firstly, press the Windows + X keys to open the menu and then select the option ‘Device Manager’.
- Next, you have to expand ‘IDE ATA/ATAPI controllers’. A subset will then get opened and listing the different IDE ATA/ATAPI channels for the PC.
- Now, you have to make a right-click the channel where the appropriate disk drive is connected. Next, you have to click there ‘Properties’ and this channel will then become ‘Secondary IDE Channel’.
- After this, select ‘PIO Only’ in the ‘Transfer Mode’ in the ‘Advanced Settings’ tab for the device that represents the appropriate drive. Generally, this is Device 0, and then click OK option and exit all the windows.
You can then test the USB flash drive and then check if the message ‘USB flash drive I/O device error’ has been removed.
Also Read: Fix Error Checking USB Drive Scanning and Repairing Stuck
Fix #8: Repair USB IO Device Error With ‘Error Checking’ Utility
Windows has the feature which is known as ‘Error Checking’. It helps to scan internal & external hard drives for several file system errors and resolves them.
In order to repair bad sectors for SD card/USB drive, try the below instructions:
1: First of all, connect the USB drive to a PC.
2: In the second step, you have to press on Win + E keys together in order to launch Windows Explorer.
3: Make right-click on a drive that has the bad sectors >> open the Properties.
4: At this time, tap on Tools >> Check.
Now, the scanning process starts. Once the scan process completes, if the usb i/o error is found then, try the next way.
Fix #9: Seek Help From Hardware Manufacturer
If you have already tried all the above ways to fix the request could not be performed because of an i/o device error when initializing disk and you still fail then you can seek expert help. It is suggested to contact the technical support of the hardware manufacturer for further help.
To do so, you have to follow the below steps:
- You have to first visit the hardware manufacturer’s website and then download the latest driver or firmware for the device which reposts I/O device error.
- Next, you have to double-click the drive or firmware installer and get it installed on the PC. You can then restart the PC and check if the error persists.
- After this, email the technical support team of the hardware in question and then ask for fixes. However, if the solution still persists, then replace the USB flash drive with the new one.
Recover Deleted Data From USB Flash Drive Using USB Flash Drive Data Recovery Tool
If you ever notice that the data from USB flash drive has been deleted due to any reason then you can easily perform USB flash drive data recovery.
Yes, I am saying so because, with the help of the USB Flash Drive Data Recovery Tool, you can easily recover deleted media files from USB flash drives.
This data recovery tool is very easy to use and is 100% safe and secure to use. This tool recover data of all types like photos, video and audio files from external hard drives. Also, it recovers all file formats of photos, videos and audio files which include the following:
- Image file formats: PNG, JPEG/JPG, TIFF, GIF, BMP, RAW image file formats
- Video file formats: MP4, MPEG, FLV, VOB, WMV, M4V, MOV, F4V, AVI, MKV, etc
- Audio file formats: MP3, FLAC, WMA, M4A, AIFF, RPS, OGG, MIDI, AMR, etc
Well, to use this tool, you have to just download and install USB Flash Drive Data Recovery Tool and follow the further steps as directed in the tool
* Free version of the program only scans and previews recoverable objects.
Here is the step-by-step guide to recover deleted data from a USB flash drive in no time using this fully-featured data recovery tool.
How Do I Initialize A Disk With An I/O Error?
Well to initialize a disk with I/O device error, you have to follow the below steps:
- First of all, connect the uninitialized USB flash drive, external hard drive, or other storage devices to your computer.
- Next, you have to press Windows + R keys to open Run command and then type there diskmgmt.MSC and then hit Enter key.
- You have to then find the uninitialized or unknown USB flash drive with I/O device error and then right-click on it and then select the option ‘Initialize Disk’.
- After this, you have to set the disk to initialize and then set the drive as MBR or GPT.
What Causes USB Flash Drive I/O Device Error To Take Place?
There are several reasons why the request could not be performed because of an i/o device error in USB takes place. Some of them are mentioned below:
- Hardware drivers are incompatible or corrupt
- The hardware device is damaged
- USB controllers have become corrupt or unstable
- Connection issues like faulty cable
Also Read: Fix Unknown USB Device (Device Descriptor Request Failed)
FAQs [Frequently Asked Questions]
How Do You Fix The Request Could Not Be Performed Because Of An I/O Device Error Using CMD?
If you want to fix the request could not be performed because of an i/o device error using CMD then you need to follow the below process:
All you need to do is, go to the Start menu & type CMD. Then, right-click on ‘Command Prompt’ > ‘Run as administrator’ > ‘Yes’ to open a Command Prompt as Administrator. Once the new Command Prompt window opens, simply type: chkdsk E: /f /r /x command to replace E with a drive letter.
Is USB an IO device?
Yes, USB is an IO device.
Since an USB receives data from your computer as input & also sends data to your PC or another device as output, thus you can say it an IO device. Here’s the examples of some I/O storage devices: USB flash drives, hard disk drives & CD/DVD-ROM drive. Examples of some communication I/O devices: dongles and modems, network adapters & Bluetooth adapters.
What are the 3 types of IO?
Generally, the IO is categorized into three groups — Control Output, Sensory Input & Data Transfer.
Time To Conclude
If you ever get USB flash drive I/O device error then you can try these above-mentioned ways to fix this error. All these fixes are very effective and one can easily try the fixes even without having any technical knowledge.
Also, if the data saved in the USB flash drive gets deleted due to any reason then you can easily recover it using USB Flash Drive Data Recovery Tool. This tool will help you restore lost media files from USB flash drives or other external hard drives in no time.
Taposhi is an expert technical writer with 5+ years of experience. Her in-depth knowledge about data recovery and fascination to explore new DIY tools & technologies have helped many. She has a great interest in photography and loves to share photography tips and tricks with others.
Владельцы компьютеров не обойдутся без загрузочной (bootable) флешки. Rufus – бесплатная утилита для записи загрузочных носителей с содержимым разнообразных образов ОС. Приложение работает практически без сбоев ввиду мизерного размера и отточенных за годы алгоритмов. Однако бывают проблемы при работе программы. Рассмотрим, почему Rufus не запускается, какие ошибки выдаёт, как их решить с помощью наших инструкций.
Возможности программы Rufus
Руфус отформатирует флешку, портативный HDD (hard disk drive) или винчестер и запишет на накопитель содержимое образа с загрузочной областью. Так превратит устройство в загрузочный носитель. Если скачали рабочий ISO (оригинальный с сайта разработчика или сборку), без ошибок, используете неповреждённую флешку, проблемы исключены. В иных случаях и по вине пользователя начинаются «танцы с бубном»: Rufus то не запускается на Windows, то не может отформатировать накопитель.
Почему возникают ошибки в работе утилиты
Источники проблем: состояние флешки, образа, операционная система. Иногда они зависят от «ровности рук» пользователя.
Преимущественно ошибки при записи образов и форматировании флешки в Rufus вызывают:
- Использование накопителя иными приложениями (открыт находящийся на устройстве файл);
- Повреждённые ячейки памяти, иные проблемы с устройством;
- Незагрузочный или повреждённый образ;
- Использование дешевых китайских USB-хабов и удлинителей;
- Антивирусное программное обеспечение, которое блокирует работу программы.
Неисправности Flash-накопителя
На повреждённую флешку Rufus вряд ли запишет содержимое образа. Если файлы и скопирует, в дальнейшем они могут не читаться. Для исправления ошибок с неработающими секторами:
- Откройте свойства устройства через Проводник (Win + E).
Свойства flash-накопителя. - Во вкладке «Сервис» кликните «Проверить».
Проверка диска на ошибки. - Запускайте сканирование накопителя.
Проверка диска.
Форматирование, как метод решения проблемы
При большом количестве логических проблем или физических повреждений на USB-диске отформатируйте его:
- Кликните правой клавишей мыши, выберите соответствующую команду.
Форматирование дисков при ошибках. - Снимите флажок «Быстрое…», жмите «Начать».
- Подтвердите стирание файлов на устройстве, предварительно скопировав информацию.
Иногда приходится прибегать к продвинутым утилитам для низкоуровневого форматирования и восстановления, например, HDD Regenerator.
Ошибки файловой системы
Rufus работает с семью файловыми системами:
- FAT – устаревшая, вышла с обихода.
- FAT32 – последовательница FAT. Используется для разделов GPT и UEFI. Не поддерживает запись файлов объёмом более 4 ГБ.
- NTFS – избавлена от ряда недостатков FAT32, формируется по умолчанию для разделов MBR и BIOS. Не поддерживается DOS (FreeDOS).
- UDF – спецификация оптических накопителей, на флешках – редкость.
- exFAT (иногда называется FAT64) – файловая система с увеличенными количеством перезаписей сектора, размером кластера и поддержкой прав доступа. Ресурсоёмкая.
- Ext2, ext3 – файловые системы для разных дистрибутивов Linux, причём ext2 обгоняет ext Ext2 почти не используется, для записи загрузочных флешек Линукс выбирайте вторую.
Кстати, о том какую выбрать файловую систему написано здесь.
Ошибки ISO-образа
При появлении уведомления, что образ повреждён:
- его придётся загрузить заново;
- перехэшировать, если качали через торрент, и докачать несколько мегабайт, содержащих ошибку;
- найти альтернативный неповреждённый образ;
- проверить раздел с образом на битые секторы, возможно, файл ISO хранится в повреждённых областях жесткого диска.
Конфликт с антивирусными ПО
Добавьте утилиту в исключения антивируса либо завершите работу программы безопасности на время запуска Rufus.
Запустите утилиту с привилегиями администратора – кликните правой клавишей, укажите соответствующий вариант.
Нужны соответствующие привилегии в Windows. Вы должны быть залогинены в ОС как админ.
Далее замените флешку, скачайте иной образ.
Ошибка «BOOTMGR is missing»
На накопителе не обнаружен загрузчик. Воспользуйтесь предварительно функцией Rufus для формирования загрузочного накопителя на базе соответствующего образа.
Ошибка [0x00000015] The device is not ready
Ошибка перед форматированием флешки в Rufus возникает при отключённом автоматическом монтировании.
Инструкция по исправлению:
- Запустите командную строку с правами администратора через Win + X.
Запуск командной строки. - Выполните команду «mountvol /e».
- Закройте окно и попробуйте выполнить действия снова.
Ошибка «Device eliminated because it appears to contain no media»
Срок службы флешки подходит либо подошёл к концу. Купите или используйте другую.
Rufus не дает выбрать FAT32
Зачем вам FAT32? Приложение автоматически выбирает файловую систему, исходя из содержимого образа. Если для диска с разделами MBR установлена NTFS, не меняйте.
Невозможно смонтировать Guid-том
Попробуйте иной накопитель. Просканируйте текущий на предмет повреждений.
Ошибка [0x00000005] Access is denied
Какая-то программа мешает Rufus получить доступ к карте памяти. Часто это антивирусы.
Ошибка «Невозможно считать носитель информации. Возможно, он используется другим процессом»
Аналог предыдущего варианта: закройте антивирус, завершите сторонние приложения, использующие флешку. Просканируйте диски на наличие вирусов. Попробуйте загрузиться в безопасном режиме.
Ошибка «Error: Legacy boot of UEFI media. This drive can only boot in UEFI mode»
Правильно создайте накопитель. Проверьте режим BIOS командой «msinfo32», выполненной в окне Win+R.
Ошибка при создании разделов в Rufus
Убедитесь, что флешка не используется другими программами, образ – не повреждённый, занимает менее, чем объём носителя. Откажитесь от разбиения на разделы или попробуйте найти ответ по ссылке.
Ошибка 0x80070032 «такой запрос не поддерживается»
Завершите работу антивируса.
Ошибка «This drive was created by Rufus»
Накопитель создан в Rufus для UEFI, вы пытаетесь запустить его в режиме BIOS или (CSM). Посетите настройки UEFI, отключите Legacy Mode (CSM). Заново запишите загрузочную флешку для BIOS и MBR.
Ошибка «Another Rufus application»
Приложение уже запущено: переключитесь на его окно либо закройте. Возможно стоит завершить задачу через «Диспетчер задач».
Ошибка извлечения ISO образа
Ошибка извлечения ISO-образа в программе Rufus лечится быстро. Если качали файл через торрент, откройте клиент для работы в пиринговых сетях (uTorren, BitTorrent, qBitTorrent), кликните правой клавишей и выберите «Проверить принудительно» или аналогичный вариант. В ином случае загрузите ISO заново, найдите иной образ на другом трекере.
«Ошибка отложенной записи»
Отформатируйте флешку. Если не поможет, сбросьте её через Rufus – зажмите Alt+Z и подтвердите операцию.
Затем форматируйте накопитель в утилите Управление дисками (вызывается через Win+X).
Невозможно назначить букву диска в Rufus
Решение разделом выше.
Недоступна кнопка «СТАРТ»
Проверьте настройки. Что-то сделано неправильно, возможно:
- Не обнаружена флешка (см. первый выпадающий список).
- Не указан ISO – нажимайте «Выбрать» и укажите файл.
- Выбран повреждённый или незагрузочный образ (с неподдерживаемым загрузчиком). Попробуйте иной.
Ошибка записи образа Linux
Согласитесь докачать недостающие (обновлённые) файлы с интернета. Это больше не ошибка, Руфус предлагает скачать обновленные библиотеки для создания загрузочного образа.
Другие вопросы и ответы по ошибкам
Что делать, если возникает ошибка при создании флешки с Win 7, 8-ка при этом монтируется без ошибок?
Слишком мало информации для анализа, опишите проблему подробнее. Попробуйте иной образ, проверьте, не повреждён ли используемый.
Почему Rufus не запускается на Windows XP?
Почитайте требования к программе здесь. Последняя версия Rufus для Windows XP выпущена под редакцией 2.18.
Что делать, если после Руфуса не работает флешка?
Виноваты сами. То ли флешка была повреждённой, старой, то ли прервали процесс записи, форматирования. Отформатируйте устройство через «Управление дисками» или Rufus. Сбросьте карту памяти через утилиту Rufus – нажмите Alt+Z и подтвердите. Затем отформатируйте накопитель.
Почему Руфус зависает при записи образа?
Возможно повреждён USB-диск, образ записан в битые секторы, диск, где хранится ISO, слишком фрагментирован, компьютер или ноутбук загружен иной работой.
Проверяет ли Руфус на плохие блоки флешку?
Нет, но может запустить системную утилиту Windows, которая проверит.
Что делать, если образ слишком большой для выбранного устройства?
Возьмите флешку с объёмом, превышающим размер файла.
Что делать, если Rufus пишет «Недопустимая метка устройства»?
Измените её в поле «Новая метка тома».
Как из загрузочной флешки сделать обычную?
Отформатируйте накопитель.
Остались еще вопросы? Пишите комменты – ответим.
Summary: This article will tell you about the I/O Device error on an external or internal hard disk/USB drives/SD cards on Windows system. Furthermore, you are going to get the details for fixing the request could not be performed because of an I/O device error on Windows 10/8/7.
You will receive this issue normally on external media devices which have been attached to your system lately. Meanwhile, the error shows up generally with external hard disks. The error message arises when attempting to locate the drive in either way, such as seeking to open any of its subfolders.
Moreover, the I/O device error doesn’t allow to read or write from a hard disk, drive or movable device and so forth, reflecting with “Error 0x8007045d: the request could not be performed because of an i/o error initialize” message. So generally, the error happens on external & internal hard drives, CD drives or DVD or USB drives when you try to read or copy data in Windows 10/8/7. In order to solve this I/O error, you must rightly know the feasible causes of it.
Causes related to Input/Output device error
- Maybe the plugged storage device is wrongly attached that’s why your PC cannot find your associated device frequently.
- Damaged or destroyed computer USB port or USB card reader.
- Computer storage device driver is old, damaged or inconsistent with your connected device.
- External hard disk, SD card or USB drive is diagnosed with an incorrect drive letter.
- Using damaged external hard drive, memory card or USB driver.
- Windows using a transferal method that your hardware device doesn’t support.
General symptoms of “the request could not be performed because of an I/O device error”
You will get the following messages visible to you on your computer screen if your system detects an I/O device error on Windows 10/8/7:
- The request could not be completed because of an I/O device error.
- I/O error 32, I/O error 21 or I/O error 0x8007045d.
- Only part of a read or write process memory request was completed.
There exist numerous reasons which can be associated with this particular dilemma. Like sometimes the media storage of your device may be damaged and that is the first thing which you should normally check. If you encountered any physical damage, then there are no techniques you can opt to make it work again. In any other situation, you can try the below-mentioned brisk methods we have come up with.
Approach 1: Check for Hardware Connections
Most of the times, a loose or free attachment among hardware and computer can create an I/O device error.
- If the external hard drive is causing the error then, reconnect the USB or file wire to unite the machine.
- If the issue is still out there, insert the drive into another USB port of the computer. It is advised to directly use the computer’s USB port.
- Then use a substitute wire for the drive to reconnecting to the system.
- Now again try to access the drive.
Remember: If the internal hard drive is causing the error then it is not recommended to reconnect the drive for irregular users if the situation causing the damage to the drive.
Approach 2: Check for I/O error using Windows default tool
Running the Windows default tool for checking error checking can be one of the most practical methods to fix input/output device error. Follow below to do the same.
- Choose Properties option by right-clicking on the inaccessible hard drive.
- From the Tool tab, choose the Check button to check for error.
- Hit the Scan drive button on the pop-up window.
Through this, the windows will automatically try to fix the error.
Approach 3: Changing the IDE Transfer Properties
Sometimes input and output error may occur as the Windows tries to transfer data from the computer using a wrong transfer mode. So for situation follow the below-mentioned tricks to fix such an issue.
- Drag mouse pointer on My Computer and right click it.
- Choose ‘Manage -> Device Manager -> IDE ATA/ATAPI controllers’.
- Select option properties by right-clicking from the secondary IDE channel where the external device is connected.
- From ‘Advance settings’ choose POI only option in ‘Transfer Mode’ box. Click OK to close the window.
- Now Restart your system.
Approach 4: Using Command Prompt
Another method to resolve this error is by running the CHKDSK command in cmd.
- Open cmd panel in your computer.
- Type chkdsk /f /r /x
- And press Enter.
Thenceforth, the Windows will check for the error and try to resolve it.
Recover Data from Windows hard drives/external USB/SD card with I/O device error
Whenever there is a ‘the request could not be performed because of an I/O device error’ first thing you have to do is recover all your important data with the help of Windows Data Recovery software from all of the inaccessible devices. The tool is technically designed to recover windows data without any data alteration. After recovering the data you can fix the I/O device error on Windows 10 without worrying any data loss. You can easily restore and recover data from corrupt or accidentally formatted devices.
Free Download
Time to Conclude
So now it’s your call to that how you resolve this I/O error. But remember one thing before opting for any technique to fix IO error you must recover your windows data. So that if the system fails due to any reason the data is totally safe with you. The recovery tool discussed in the handset is recommended by Windows experts and professionals.