删除文件时发生io设备错误无法删...

删除文件时发生io设备错误无法删除文件夹（A IO device error occurred while deleting the file. The folder cannot be deleted）An error occurred while deleting the file. The folder error code 0x80070091 cannot be deleted
In/Out devices (i.e., basic input / output devices) like keyboards belong to the input devices, monitors, and printers, which belong to the output device.
1, enter my computer
2. Select the hard disk your desktop is located on
3, right-click -- click Properties -- tools"
4, "check the wrong" point, began to check
5, "auto fix file system error", "scan and attempt to recover bad sectors", two full point hooks
6, click Start
I have the same problem as you have! Windows old cannot be deleted! Delete 0x8007045D:, because I/O device error, you solved it?
Deletion of windows.old is actually very simple, I tried a lot of methods, with only the most effective system disk cleanup, after scanning the windows.old partition, the residual candidate a similar old system in the dialog box options, you
can automatically clean out, save a lot of hard disk
Windows7 Disk Cleanup in "start" - "attachments" - "system tools" - "disk cleanup.""
Reinstall the network card driver, and can not find the driver, the next driver wizard, automatic scanning required drivers
Still not, is it the card itself?...
The ways to delete stubborn files and folders are as follows:
1.360 first aid kit - Repair - repair system select restart
2.360 system first aid kit - Emergency restart
3.360 security guard - cleaning plug-ins
4.360 security guard - function Guinness - File Shredder - adding files - crushing
5. install Unlocker unlock remove tool
Right click the file you want to delete, select Unlocker, or drag the file to Unlocker, pop up a window, select in the action drop-down box, you want to perform the action on this file, that is, delete and then make sure
6. boot F8, enter safe mode to remove
7. use the system tool disk to enter the PE system to delete
1. close any program that might use the file and try again
2. can be deleted in safe mode
3. can be started at startup and deleted in pure DOS
0x8007045D error occurred when deleting files from the computer F disk. Can you tell me how to solve it?
Close any program that might use the file and try again
2. can be deleted in safe mode
3. can be started at startup and deleted in pure DOS
I/o device error
Your card's metal shrapnel is wiped and plugged..
The reader cannot pull out the data while reading it! No read!
Data is pulling out, no problem
There is also because the memory card quality does not pass, also can cause this kind of situation
Here are some of the information I am looking for. If you are interested, you can have a look
Now a lot of friends have a mobile hard disk or U disk and other
removable storage devices, but sometimes to mobile hard disk copy data, jump out of a dialog box to display: mobile hard disk copy to appear unable to copy certain files, because I/O device error cannot run this request. Yesterday, when a friend's mobile hard disk was connected to my computer to copy data, there was a "I/O device error" that was unable to run the request."
Collect some information on the Internet
Fault analysis and solution:
First, do not use the front USB port on the chassis or the USB extension line, and try to use the USB interface on the motherboard, that is, the USB interface at the back of the case.
The reason is: the box front USB port and USB extension line are using USB 1.1 structure, and now the mobile hard disk or U disk is USB 2 interface, so in the USB 1.1 hub socket, use will be wrong timing. Even if some of the pre - USB interfaces are the 2 standard, there may be an increase in resistance due to repeated wiring, resulting in insufficient power supply for the USB 2 interface.
Now some computer has several USB interface, the general case in front of two, four in the back, behind one of them four out of two in the vicinity of the mouse and keyboard interface card in two near, when I use the pre two USB interface when the mobile hard disk USB interface with no response, in the vicinity of the mouse keyboard interface can be read out but prompt "I/O device error when copying some files, the request could not be
performed". Finally, there is no problem with the USB interface near the network card.
Two, defragment the mobile hard disk.
Reason: mobile hard disks are often copied, cut and run, leaving a lot of junk file fragments in the tracks. You can also use the /v disk command that windows brings with you; the DOS command chkdsk/f; /p; if you haven't cleaned up the disk for a long time, and sometimes you have a whim to organize it, you'd better take it first.
Syntax: CHKDSK [drive:][/p][/r][/f]
Recommended parameter /f, for example: F:\>chkdsk /f carriage return
Three, if the data line inserted behind the box, the computer still can not read the data properly, there are several possibilities:
Quote
The 1: motherboard is older and the USB driver is not installed. (right click on my computer > = > Device Manager -=> attributes to check whether there is an exclamation point! If yes, there is no drive installed.
2: if the hard disk has fallen, it could be a damage to the mobile hard disk! Do not prevent low-level formatting! (not recommended! There is no way out
3: if you can use it on someone else's machine, but not on your own machine. This disk = > should be no problem, the upgrading of the main version of drivers.
4:, if not, see if there is a problem with the USB interface on the motherboard, and try to plug in another USB device.
5: if it is MP3, please try the following method:
Remove the battery - - hold down the boot button, connect to the computer - open the upgrade tool, select the model - Download firmware - firmware upgrade - "OK" - upgrade ing... Upgrade is complete.
Reinstall the U disk drive
Try it on someone else's machine
If not, go and fix it
You first try the U disk, no, it's the hardware problem. You can fix it
In your case, it's probably a problem of I/O address conflicts
I/O address is the abbreviation of "input / output address", also known as "address address" or "hardware address". It is mainly used for communication between peripheral and CPU. General computer addressing can only be done from 000 to 3FF 64K I/O address space.
The reason for the conflicting I/O addresses
Each of the hardware in the PC machine has the only corresponding I/O address. It is through this one-to-one I/O address that each peripheral can be correctly identified by CPU. However, if there are two or more peripherals are set to the same I/O address, then CPU sends the message to the corresponding I/O address, on the one hand something and can't handle and respond to this information, on the other hand due to a I/0 address corresponding to a plurality of peripherals, resulting from the CPU information divided into many road, transmit the information to the strength of each peripheral are not enough to make the peripheral response, it makes all the wrong I/O address cannot be used outside.
Method for resolving I/O address conflict
If the I/O address is set incorrectly causing the I/O address to conflict, a conflict device is not available. For Windows 2000 users can access the system through the opening of safe mode, and then open the "control panel", "system", see marked with yellow "!" equipment; check the device, click the "properties" window, view Windows is given from the "resources" list of tips, click the "input / output" change it, until the Windows show "conflict free equipment" to determine exit.
It should be noted that for many devices that have been defined by the system, they often allow only a fixed I/O address. As defined in the precise definition of USB, it uses the I/O address of 3F8 - 3FF. If the user changes it, then COM1 can no
longer be used as a COM1. Therefore, the I/O address should not be changed for the system's default native device.
You know, U disk, how much will have a lot of their own important things, ah, the grid on the grid, how can it be possible?
Here's what I think and what I do
Start setting up the control panel management tools, computer management, disk management
Find the mobile drive, right click, change drive letter and path to change the drop-down arrow to select the letter to determine
Wait a moment, try again. How about accessing the U disk?
If still can not, pull down and then inserted, and basically can be solved
At least that's how I solved it
Of course, this also depends on circumstances
I. conventional solutions:
1., delete or restart the computer, and then try to delete.
2. go to safe mode to delete".
3. use the DEL, DELTREE, and RD commands to delete them in the pure DOS command line.
4., if there is a lot of subdirectories or files in the folder, which can not be deleted, you can first delete the subdirectories and files in the folder, and then delete the folder.
5. end the Explorer.exe process in the task manager and then delete the file at the command prompt window.
6., if you have installed ACDSee, FlashFXP, Nero, Total these several software, you can try to delete the folder in these software.
Two, advanced solutions:
1. disk error
Run disk scan, and scan the file where the partition, before scanning to determine the selected repair files and bad sectors, a full scan all options, scan and then delete the file.
2. prefetch mechanism:
Some media will not be deleted when they are interrupted or are being previewed.
The input in the "run" box: REGSVR32 /U SHMEDIA.DLL, written off reading function. Or delete the following key in the registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{87D62D94-71B3-4
b9a-9489-5FE6850DC73E}\InProcServer32].
3. firewall:
Since antivirus software will take possession of the file under review when checking, resulting in the deletion of the prompt when the file is being executed, then try to temporarily shut down its immediate monitor, which may be resolved.
4.OFFice, WPS series software:
Illegal shutdown of OFFice can also cause files to be deleted or renamed. Rerun the program, then shut it down, and then delete the file.
5. by means of WinRAR:
Right click on the folder you want to delete, and select Add to the compressed file". In the pop-up dialog box, select "zip, delete the source file", literally write a compressed package name, point to determine.
6. permissions issues:
If you are 2000 and XP systems, please make sure that you have permission to delete this file or folder.
7. delete executable files:
If not release call image or the executable file of the DLL dynamic link library file is still in memory, delete will prompt the file is in use, the solution is to delete the system page file, Win98 is Win386.SWP, Win2000/XP is pagefile.sys. Be careful to delete under DOS.
8. file shredding:
Using file shredder such as File Pulverizer, you can completely remove some stubborn files.
Three, the production of a "can not delete" file safe"
The folder cannot be deleted, is not necessarily a bad thing, if you put some important files in this directory, you can not avoid the error? A folder whose name contains only spaces is not allowed to create and delete in Windows, but under DOS it is possible to create a folder containing the name of the file.
In the process of using Windows, we encounter a variety of problems. Even the simplest delete file can be in trouble, or the system prompts that the file is being used by another person or program, or that the report is denied access"...... If you have encountered this situation, you might as well look at this article.
The reason: the file is in use
One of the frequently encountered problems when deleting files is that the file is in use and cannot be deleted. If you try to delete for exclusive access rather than to share access to open, and is being used in the file, the system will appear error: "cannot delete XXX: file is being used by another person or program". In the other case, the file can be deleted using the delete command, but the file is not deleted before the process of opening the file releases the file.
To solve the above problem, you need to determine the process that owns the file and open the handle, and then closes the process. In previous Windows, we can use the resource toolkit's Oh.exe. But in XP, the installed Support
Tools without Oh.exe. However, XP provides a new Openfiles.exe command line tool that reports each file opened by the process. With Oh.
Similar to exe, Openfiles.exe also requires open system kernel monitoring, which consumes some memory and reduces performance of system operations. The command to turn on system monitoring is "Openfiles"
/local
"On", which enables the system global flag, maintains the object list, and needs to restart the system to take effect. When you restart the system and execute the "Openfiles" without arguments at the command prompt, you can see the list of files each process opens.
Reason two: file system Corruption
Bad areas on the disk, other hardware faults, or software errors can damage the file system and cause problems with the file and cannot be deleted. Typical operations fail in a very different way. When a file system is detected, a message that runs Chkdsk is usually received.
If this happens, you can run the Chkdsk utility on the disk volume to correct any errors that are present. Depending on the nature of the damage, Chkdsk may be able to recover the file data and may not be able to recover, but Chkdsk can return the file system to an internally consistent state. For commands and arguments about the Chkdsk utility, you can execute Chkdsk at the command prompt
/?" Refer to.
Reason three: the file uses the access control list
If a file uses the access control list (Access Control)
List, referred to as ACL), and the operator does not have the appropriate permissions, then delete the file, there may be "access denied" prompt.
Typically, the administrator has the implicit ability to obtain any file ownership, and the file owner also has the implicit ability to modify file permissions. However, these default permissions can be modified.
To solve the problem that ACL causes files to be deleted, you must login to the user with the appropriate permissions or to grant permission to delete the file before deleting the file. Note that the operator must have ownership of these files to change permissions. If you are unable to use some security tools to display or modify the power limit because the document is using an irregular ACL, you can try using the command line tool, Cacls.exe, to modify it.
Reason four: the file name uses a reserved name
As you all know, names such as AUX and LPT1 are reserved for older DOS devices. For backward compatibility, these file names are not allowed in Windows, nor can a typical Win32 file tune be used to create them. Conversely, if the file name is a reserved name in the Win32 namespace, it is also possible that this file cannot be deleted.
To solve this problem, you can rename or delete this file under Linux or other non Windows operating systems. In addition, if you can specify the path to the file using a specific syntax, you can also use a few built-in commands to bypass typical Win32 retention name checks. For example, in Windows
Using the following command in XP, you can delete the file named LPT1 (Del command followed by "?"" To prevent the Windows from checking the validity of the filename:
Del [URL=/news/w31/file://? C:]? C:[/URL] file path LPT1
Reason five: Invalid file name
If the file name contains an invalid name, such as the file name with a trailing spaces, or a trailing end, or the file name consists of only one space, also may not be able to delete the file. It is worth mentioning that, if you use the typical Win32 grammar to open the trailing spaces or trailing period file name, trailing spaces or periods will be removed before the actual
file open. Therefore, if there are two in the same folder, they are called File.txt and File.txt
"File" (note the space behind the second filenames), and actually open the first file when you open the second file using the standard Win32 call. Similarly, if the file name is only"
(a space character) that actually opens the parent folder of the file when it attempts to open it using the standard Win32 call. In this case, if you try to change the security settings on these files, you might accidentally change the settings on other files.
Similar to the way the solution file name is kept using a reserved name, you can delete this file with an appropriate internal syntax. For example, to delete files that contain trailing spaces, you can use the following command:
"Del [URL=/news/w31/file://??"] [/URL] c: file path (file name of trailing space)
Six reason: the file path is too deep to access
The file is located in a deeper path than the maximum path character number (MAX_PATH), which may cause the file to be inaccessible. Of course, this is rare. If the path is deep because the folder name is too long, the easiest solution is to use the automatically generated 8.3 name to access the file. If the 8.3 path is too long, you can start renaming the folder from the root folder and shortening their names so that the path of the target file is not more than MAX_PATH. If the depth of
the file is more than 128 folders, you can access the file by accessing the share by creating a network share so that it is as deep as possible in the folder tree.
In general, you can manage these files by using software that creates files when you encounter problems that cannot be accessed because the file path is too deep. That is, if there is a program that can create more than MAX_PATH files, we can also use the program to manage these files. In addition, files that have deep structure created by network sharing can also be deleted by using shared access.
The front introduces several reasons why files or folders cannot be deleted in the Windows system and how to solve them. In some cases, you might encounter different combinations of the above reasons, making the process of deleting files more complex. This requires readers to draw inferences and apply Microsoft's various utilities to solve them.
The problem of deleting AVI files in Windows XP
Many friends may encounter problems with AVI files that cannot be deleted in Windows XP, mainly due to Windows
XP video preview feature caused by Bug. You can try deleting it in the following ways.
Method 1. Enter Regs-vr32/u in the run command box
Shmedia.
DLL and press enter, remove Windows
XP video file preview function. When you want to restore the video preview function later, use the "Regsvr32Shmedia.dll" command to register again.
Method two
First open the command prompt window, then end the Explorer process in the task manager, then switch from the command prompt window to the folder that stores the video file, and then delete the file with the Del command.
Method three
If you install a dual system, you can delete it from another system, such as Win98。