Unable to Empty Trash - Files with invalid characters

I have tried everything I can find on the internet to empty my Trash of these two files:
"Empty Trash" does nothing. Terminal commands (rm -rf and the like) result in "Directory not empty" or "No such file or directory".
Any help most appreciated.

Here are suggested solutions from other threads:
https://discussions.apple.com/message/19055838#19055838
https://discussions.apple.com/message/19508937#19508937
https://discussions.apple.com/message/15860098#15860098

Similar Messages

Renaming files with invalid characters in their names on NTFS partitions, introduced by operating systems other than Windows

Essentially, Linux created some files with colons (:) in the name on a NTFS partition where I have Windows installed. I have since uninstalled Linux, but now I can only view these files in Windows Explorer. I can't open them, I can't even rename them to
correct the problem. It's as if they don't exist, because of the invalid search paths.
If I try to rename them in Windows Explorer I get following message.
The file name you specified is no valid or too long.
Specify a different file name.
Well isnt' that something?... isn't that nice? Windows is able to display these files, but it doesn't allow me to open them and it certainly doesn't like me to rename them. So why is it whining about it then, when I'm trying to help? It says "try a different
file name". Yeah, right! Like I haven't tried that one already! It doesn't matter what file name I input it will never accept it.
So what am I supposed to do now? Ditch Windows and go back to Linux? Surely, Microsoft doesn't like the sound of that. Sure, I could reinstall Linux or run a Linux live system to correct the problem. But what good is Windows then? I might as well switch to
Linux altogether.
After doing some research I now know by fact that it's (kind of) possible to rename files from UNIX and UNIX-like operating systems to those compliant with Windows by using something called file name character translation. To some level this is essential and
necessary for Windows interoperability with other operating systems (Windows is not the only operating system in the world). But this seems to be very complicated and I can't get my head around it. My brain is in overload. I don't know where to start.
Once there was a...
There's the Windows Services for UNIX (SFU) 1.0, 2.0, 3.0, 3.5. The first two versions were based on MKS Toolkit, a package licensed by Microsoft from MKS Inc. The later versions were based on the similar Interix product, after Microsoft purchased the company
that made it.
Then there's the new Subsystem for UNIX-based Applications (SUA). These are services for UNIX components. They are supposed to have Client for NFS v3 included as well. But the server components from the SFU line is missing (e.g. Server for NFS). These are included
in Server editions of Windows.
Then there's the Microsoft Knowledge Base article
289627: "How to Enable File Name Character Translation". This article seems to describe exactly my situation.
Windows and UNIX operating systems have restrictions on valid characters that can be used in a file name. The list of illegal characters for each operating system, however, is different. For example, a UNIX file name can use a colon (:), but a Windows
file name cannot use a colon (:). If a UNIX user attempts to create a file with a Windows illegal character on a Windows Services for UNIX network file system (NFS) share, the attempt is unsuccessful and the UNIX client computer receives an input or output
error.
It goes further than that. At first glance, this KB article also seems to offer a solution to this exact problem, with examples as shown below.
For example, the following maps the UNIX colon (:) to a Windows dash (-):
0x3a : 0x2d ; replace client : with - on server
I checked these values in charmap.exe and they are correct. Except for 2D not being a "dash", it's rather a hyphen ("hyphen minus" to be exact), but these two have pretty much the same appearance and they get interchanged a lot, I'm sure
they are used to it by now. (Yes, the characters! They don't mind.)
Then there's this registry key.
HKEY_LOCAL_MACHINE\Software\Microsoft\Server For NFS\CurrentVersion\Mapping
Well, of course, I don't have Server for NFS. So this is a dead end. Well, actually, it was a dead end from the beginning...
1. First of all, I'm not working with a network share on a NAS or SAN storage. The files are on the local disk drive where Windows is installed, so that's a DAS for you.
2. I don't have SFU! Well obviously, I'm on Windows Vista! So that means SUA!
3. SUA are service components only. No server components. Can you guess what that means? Yeah... no "Server for NFS" since it's a server component.
4. Windows Vista is a client side operating system! Server for NFS is only offered for use with Windows Server systems.
5. Back to square one!
So there you have it. They all lived happy for the rest of their lives...
I'm stuck here. Can someone tell me what to do? I mean beyond the obvious option to use Linux to fixa a Windows problem? The NTFS file system itself supports colons in file names. It's Windows that doesn't, and so by default it proclaims it invalid character.
Surely, even a Windows client operating system like Windows Vista should be able to allow the user to at least rename files with invalid characters to something more sensible (from the system point of view) and valid, if not being able to open them as they
are. Just add some crazy voodoo code to it and it will work. If you can make it possible on Windows Server with UNIX user-mode subsystem on NT kernel, then what's stopping you from giving the Windows client system the same benefit?
So what now? Purchase a Windows Server 2012 R2 license, copy my invalid files to a NAS share with NFS on a UNIX or Linux system, and have a go at the Windows registry and Server for NFS? Yeah... you're right, it's probably a bit over the top...
On a second thought... I might as well install Linux again. There are countless situations where Linux has helped me solve problems related to, and more often than not caused by Windows.

Essentially, Linux created some files with colons (:) in the name on a NTFS partition where I have Windows installed. I have since uninstalled Linux, but now I can only view these files in Windows Explorer. I can't open them, I can't even rename them to
correct the problem. It's as if they don't exist, because of the invalid search paths.
If I try to rename them in Windows Explorer I get following message.
The file name you specified is no valid or too long.
Specify a different file name.
Well isnt' that something?... isn't that nice? Windows is able to display these files, but it doesn't allow me to open them and it certainly doesn't like me to rename them. So why is it whining about it then, when I'm trying to help? It says "try a different
file name". Yeah, right! Like I haven't tried that one already! It doesn't matter what file name I input it will never accept it.
So what am I supposed to do now? Ditch Windows and go back to Linux? Surely, Microsoft doesn't like the sound of that. Sure, I could reinstall Linux or run a Linux live system to correct the problem. But what good is Windows then? I might as well switch to
Linux altogether.
After doing some research I now know by fact that it's (kind of) possible to rename files from UNIX and UNIX-like operating systems to those compliant with Windows by using something called file name character translation. To some level this is essential and
necessary for Windows interoperability with other operating systems (Windows is not the only operating system in the world). But this seems to be very complicated and I can't get my head around it. My brain is in overload. I don't know where to start.
Once there was a...
There's the Windows Services for UNIX (SFU) 1.0, 2.0, 3.0, 3.5. The first two versions were based on MKS Toolkit, a package licensed by Microsoft from MKS Inc. The later versions were based on the similar Interix product, after Microsoft purchased the company
that made it.
Then there's the new Subsystem for UNIX-based Applications (SUA). These are services for UNIX components. They are supposed to have Client for NFS v3 included as well. But the server components from the SFU line is missing (e.g. Server for NFS). These are included
in Server editions of Windows.
Then there's the Microsoft Knowledge Base article
289627: "How to Enable File Name Character Translation". This article seems to describe exactly my situation.
Windows and UNIX operating systems have restrictions on valid characters that can be used in a file name. The list of illegal characters for each operating system, however, is different. For example, a UNIX file name can use a colon (:), but a Windows
file name cannot use a colon (:). If a UNIX user attempts to create a file with a Windows illegal character on a Windows Services for UNIX network file system (NFS) share, the attempt is unsuccessful and the UNIX client computer receives an input or output
error.
It goes further than that. At first glance, this KB article also seems to offer a solution to this exact problem, with examples as shown below.
For example, the following maps the UNIX colon (:) to a Windows dash (-):
0x3a : 0x2d ; replace client : with - on server
I checked these values in charmap.exe and they are correct. Except for 2D not being a "dash", it's rather a hyphen ("hyphen minus" to be exact), but these two have pretty much the same appearance and they get interchanged a lot, I'm sure
they are used to it by now. (Yes, the characters! They don't mind.)
Then there's this registry key.
HKEY_LOCAL_MACHINE\Software\Microsoft\Server For NFS\CurrentVersion\Mapping
Well, of course, I don't have Server for NFS. So this is a dead end. Well, actually, it was a dead end from the beginning...
1. First of all, I'm not working with a network share on a NAS or SAN storage. The files are on the local disk drive where Windows is installed, so that's a DAS for you.
2. I don't have SFU! Well obviously, I'm on Windows Vista! So that means SUA!
3. SUA are service components only. No server components. Can you guess what that means? Yeah... no "Server for NFS" since it's a server component.
4. Windows Vista is a client side operating system! Server for NFS is only offered for use with Windows Server systems.
5. Back to square one!
So there you have it. They all lived happy for the rest of their lives...
I'm stuck here. Can someone tell me what to do? I mean beyond the obvious option to use Linux to fixa a Windows problem? The NTFS file system itself supports colons in file names. It's Windows that doesn't, and so by default it proclaims it invalid character.
Surely, even a Windows client operating system like Windows Vista should be able to allow the user to at least rename files with invalid characters to something more sensible (from the system point of view) and valid, if not being able to open them as they
are. Just add some crazy voodoo code to it and it will work. If you can make it possible on Windows Server with UNIX user-mode subsystem on NT kernel, then what's stopping you from giving the Windows client system the same benefit?
So what now? Purchase a Windows Server 2012 R2 license, copy my invalid files to a NAS share with NFS on a UNIX or Linux system, and have a go at the Windows registry and Server for NFS? Yeah... you're right, it's probably a bit over the top...
On a second thought... I might as well install Linux again. There are countless situations where Linux has helped me solve problems related to, and more often than not caused by Windows.

Yosemite is awful- unable to empty trash, volume options are haywire, error codes on file management, and files won't replace when moved. What are my options at this point?

Like the topic - "Yosemite is awful- unable to empty trash, volume options are haywire, error codes on file management, and files won't replace when moved. What are my options at this point?"
I installed this OS, and it looks nice, but it's terrible to use. I randomly have the volume controls get disabled, and sometimes the volume menu in the system tray does nothing when adjusted which I've never seen in an OS before. The trash won't empty. When I try to drag and drop newer files over existing ones, nothing happens. The old ones just stay there. I have to delete the old ones and then move the new ones. And when I go into the protected files to manage audio plugins (I make music), the first thing I hit are error codes galore, and password prompts that either don't popup when they should, or don't execute the command after I provide my password.
What can I do now that I installed the flames of **** onto my computer?

Back up all data before proceeding.
This procedure will unlock all your user files (not system files) and reset their ownership, permissions, and access controls to the default. If you've intentionally set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it, but you do need to follow the instructions below.
Step 1
If you have more than one user, and the one in question is not an administrator, then go to Step 2.
Triple-click anywhere in the following line on this page to select it:
sudo find ~ $TMPDIR.. -exec chflags -h nouchg,nouappnd,noschg,nosappnd {} + -exec chown -h $UID {} + -exec chmod +rw {} + -exec chmod -h -N {} + -type d -exec chmod -h +x {} + 2>&-
Copy the selected text to the Clipboard by pressing the key combination command-C.
Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window by pressing command-V. I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting.
You'll be prompted for your login password, which won't be displayed when you type it. Type carefully and then press return. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command may take several minutes to run, depending on how many files you have. Wait for a new line ending in a dollar sign ($) to appear, then quit Terminal.
Step 2 (optional)
Take this step only if you have trouble with Step 1, if you prefer not to take it, or if it doesn't solve the problem.
Start up in Recovery mode. When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open. In that window, type this:
resetp
Press the tab key. The partial command you typed will automatically be completed to this:
resetpassword
Press return. A Reset Password window will open. You’re not going to reset a password.
Select your startup volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.

MacBook Pro: Unable to Empty Trash (secure or otherwise). Have tried all remedies suggested on Apple's site. I think "Secure Empty Trash" bogs at the first file "iPhone4, 1_8.02_12A495_Restore.ipsw" at 1.78 GB size and goes no further.

MacBook Pro: Unable to Empty Trash (secure or otherwise). Have tried all remedies suggested on Apple's site. I think "Secure Empty Trash" bogs at the first file "iPhone4, 1_8.02_12A495_Restore.ipsw" at 1.78 GB size and goes no further. When I try to move it out of Trash to a temporary location so I can empty remainder of Trash, I get the message "Some of the items you are moving are in use by another application. Moving the items can cause problems with the application using them. Are you sure you want to move these items?" at which point I select "Stop" to avoid possible disaster. Can you help? Thanks.

01/05/15 6:01:27.000 pm kernel[0]: Previous shutdown cause: -62
That usually indicates an abnormal shutdown due to a hardware fault. The exact cause can only be determined by Apple, so schedule a Genius Bar Reservation.

I am getting disc full messages on my Mac, unable to empty trash because not enough space, how do I proceed or do I need to increase my 4gig of memory

I am getting disc full messages on my Mac, unable to empty trash because not enough space, how do I proceed or do I need to increase my 4gig of memory in which case how do I go about this process.

You are confusing RAM (Random Access Memory) with hard drive data storage space.
Your hard drive storage is getting too full if you can't empty your Mac's main trash.
Here are some general tips to keep your Mac's hard drive trim and slim as possible
You should never, EVER let a conputer hard drive get completely full, EVER
With Macs and OS X, you shouldn't let the hard drive get below 15 GBs or less of free data space.
If it does, it's time for some hard drive housecleaning.
Follow some of my tips for cleaning out, deleting and archiving data from your Mac's internal hard drive.
Have you emptied your Mac's Trash icon in the Dock?
( as you mentioned, you can't empty this as your hard drive is too full.)
If you use iPhoto, iPhoto has its own trash that needs to be emptied, also.
If you store images in other locations other than iPhoto, then you will have to weed through these to determine what to archive and what to delete.
If you use Apple Mail app, Apple Mail also has its own trash area that needs to be emptied, too!
Delete any old or no longer needed emails and/or archive to disc, flash drives or external hard drive, older emails you want to save.
Look through your other Mailboxes and other Mail categories to see If there is other mail you can archive and/or delete.
STAY AWAY FROM DELETING ANY FILES FROM OS X SYSTEM FOLDER!
Look through your Documents folder and delete any type of old useless type files like "Read Me" type files.
Again, archive to disc, flash drives, ext. hard drives or delete any old documents you no longer use or immediately need.
Look in your Applications folder, if you have applications you haven't used in a long time, if the app doesn't have a dedicated uninstaller, then you can simply drag it into the OS X Trash icon. IF the application has an uninstaller app, then use it to completely delete the app from your Mac.
To find other large files, download an app called Omni Disk Sweeper.
Download an app called OnyX for your version of OS X.
When you install and launch it, let it do its initial automatic tests, then go to the cleaning and maintenance tabs and run the maintenance tabs that let OnyX clean out all web browser cache files, web browser histories, system cache files, delete old error log files.
Typically, iTunes and iPhoto libraries are the biggest users of HD space.
move these files/data off of your internal drive to the external hard drive and deleted off of the internal hard drive.
If you have any other large folders of personal data or projects, these should be archived or moved, also, to the optical discs, flash drives or external hard drive and then either archived to disc and/or deleted off your internal hard drive.
Good Luck!

Upload files with swedish characters NS 4.7

Hi,
I can upload files with swedish characters in the file name with IE 5, but not with Netscape 4.7. iFS presents an error message that the file doesn't exist or is empty.
Is there a solution for this problem?
/Elin
null

check out if you are using javascripts and whether IE supports it
Roberto Nanamura <[email protected]> wrote:
>
Hi,
I am having a problem uploading files with Internet Explorer, it works with
Netscape Communicator. Has someone had the same problem?
I am using WebLogic 5.1 service pack 5 with Netscape iPlanet 4.1 service pack 2
in a Solaris 7.
Best regards,
Roberto N Nanamura
Technical Consultant
Summa Technologies

Have been unable to empty trash for the last 24hours, says it is being used by another task, how do I clear it. Thanks for any help.

Have been unable to empty trash for the last 24hours, says it is being used by another task, how do I clear it. Thanks for any help.

Generally when you get the resource in use error logging out or rebooting will take care of it. When a file just absolutely refuses to delete try restarting in Safe Mode (hold the left shift key after the computer restarts) and then empty the trash.

Unable to empty trash getting constant faultcode -8003

After dragging some Backup Files from my My Book External Harddisk to the trash I tried many times to empty the trash but I am constantly unable to do so in order of faultcode -8003.
Who can help me to fix this problem?

unable to empty trash error code 8003: Apple Support Communities

Create a flat file with multiple characters for enclosures

Hello,
we use OWB 11g2 (11.2.02).
Now we try to create a flat file with multiple characters for enclosures. The manual wrote:
"Enclosures (Left and Right): Some delimited files contain enclosures that denote text strings within a field. If the file contains enclosures, enter an enclosure character in the text box or select one from the list. The list displays commonenclosures. However, you may enter any character. The default for both the left and right enclosure is the double quotation mark ("). You can specify multiple characters and hexadecimal characters as field enclosures."
But it will not work. The OWB use the first character from the left enclosure definition as left enclosure and the second one as right enclosure !?!
Did anyone know this behavior? Is there a solution for this problem?
Thanks and regards
Norbert

HI Raghu,
Use the function module 'GUI_UPLOAD'.
In that you have to specify the field_separator value = 'X' in export section.
Regards,
S.C.K

Unable to open PDF files with Adobe Reader, Mac trying to open files with Quicktime instead, but not succeeding. HELP!

Unable to open PDF files with Adobe Reader, Mac trying to open files with QuickTime instead, but not succeeding. HELP!

Hi BDAqua,
Thanks for the info, I dragged a PDF to desktop ctrl-, get info. change all to open with adobe.
Problem solved, many thanks for a quick response.
Barry69

Getting empty log files with log4j and WebLogic 10.0

Hi!
I get empty log files with log4j 1.2.13 and WebLogic 10.0. If I don't run the application in the application server, then the logging works fine.
The properties file is located in a jar in the LIB folder of the deployed project. If I change the name of the log file name in the properties file, it just creates a new empty file.
What could be wrong?
Thanks!

I assume that when you change the name of the expected log file in the properties file, the new empty file is that name, correct?
That means you're at least getting that properties file loaded by log4j, which is a good sign.
As the file ends up empty, it appears that no logger statements are being executed at a debug level high enough for the current debug level. Can you throw in a logger.error() call at a point you're certain is executed?

Unable to open d800 files with cs6 and camera raw 8.3

unable to open d800 files with cs6 and camera raw 8.3

Have you used Nikon Transfer on those files? Early versions are known to corrupt files so that ACR can't read them. Nikon has since fixed the bug so new versions are safe.
Here's a thread (with a fix) in the Lightroom forum: https://forums.adobe.com/message/6253962

Unable to empty trash error code 8003 appears ?

Unable to empty trash error code 8003 appears ?

I had the same problem - tried all sorts but nothing worked. Eventually I used a tool called Trash It! which did the job (though apparently it is only to be used as a last resort).
http://www.macupdate.com/app/mac/8214/trash-it! Emptied the Trash and no problems since.
Cheers
J

Unable to empty trash error code 8003

Unable to empty trash error code 8003
MacBook Pro
OSX 10.6.7
4GB RAM

I had the same problem - tried all sorts but nothing worked. Eventually I used a tool called Trash It! which did the job (though apparently it is only to be used as a last resort).
http://www.macupdate.com/app/mac/8214/trash-it! Emptied the Trash and no problems since.
Cheers
J

I am unable to empty trash error 8003

I am unable to empty trash. I get an error 8003 message. What do I do?

HI, this thread offers a solution:
https://discussions.apple.com/message/15031360#15031360 (paid for app)
or
this thread: https://discussions.apple.com/message/11620698#11620698
http://www.titanium.free.fr/download.php?sid=3092b5fa238323a3658fab8a16db71ee
(free app - be sure to download the correct version for your OS)

Unable to Empty Trash - Files with invalid characters

Similar Messages

Maybe you are looking for