Cannot rename files

Using LR5.3 on a Mac running OSX 10.8.5, I have selected a series of photos to be renamed. Using F2, I set up the new name and sequence numbers beginning with 001. I receive the following error message, "These files were not renamed because they either were missing, were not writable, or had naming conflicts." I know they aren't missing because there is no question mark indicating LR cannot find them. Any ideas why they might not be writable or how to resolve naming conflicts?

OK, this is a radical suggestion, but it's something that seems to work when all else fails... Saving corruption of an actual System file (which isn't likely since they're all write-locked by default), usually this kind of thing is a corrupted cache file or a corrupted .plist preference file...
If you can't pin-point which finder preference file is causing eratic behavior, and have NO THIRD PARTY software like Haxies or contextual menu item plug-ins etc that could be causing it, then trash them all and redo all your system preferences again..
You can try various utilities like Cache Out X, Tinkertool, OnyX (recommended), or others to delete all the system caches, and the swap file, but if that does not work, your last step before getting out the Mac OS X DVD and doing an archive and install system restoration is to delete all the files in these folders that contain "com.apple." and end in ".plist":
\Library\Preferences
\Users\(account name concerned)\Library\Preferences
The only other thing I can recommend is to create a new user account in System Preferences, and if that account doesn't have the corruption, transfer all your personal files from the old account and then wipe the old account.

Similar Messages

Cannot rename files, folders and drives

tried to GRAB the error message, and it's hanged when I tried to save the image.....
There are problems on rename files, folders and drives, also have problem to delete things....
what can I do.....!!!!

Ok, finally i just reboot the machine and it is fine now.
I guess there are some bugs related to the user permissions...
Indeed, I encountered a few bugs and they were fixed by rebooting the machine.
More details: I am using a early 2008 version mac pro with mountain lion and upgrade os to mavericks last nite.
At first, it cannot connect to my wifi network, it kept asking me to enter password for my network but kept saying it s failed. After trial to fix it by a few methods which were failed, i gave up and reboot, and vala~ It worked again..
Then i tried to rename my system drive as it was named "mountain lion", and i just want to rename it to "mavericks", error popped out, and i found that i cant rename folders or files, or put them in trash.... Again, it worked again after reboot!!!!
Guys, for those who wannna upgrade to mavericks now, better wait for a few more weeks till some update come up n fix those issues....

Cannot Rename files & folders

Starting a few minutes ago, I cannot edit file or folder names with key strokes. I repaired permissions and restarted. No joy. Verify HD test results are OK.
Keyboard works fine in text and graphic aps (eg I am keying this message). Strangely, I can copy text from other sources (with cmd C or with menu/mouse) and paste it into file name using Mouse drag>Edit>Paste command. Paste with key command (Cmd V) does not edit highlighted filename text. Delete key does not delete highlighted filename text.
Related issue, Cmd I no longer opens a Get Info window. Mouse drag File>Get Info does open an Info window. Files and folders have read/write permission.
I tried the usual file name edit options:
1. Desktop icons: click/hold file name to enter text edit mode. text box activates. Key in new text. Keystrokes do not affect the text in the file name. Key cmd C,X,V do not affect highlighted text. Menu command for paste does
2. Column view in finder window (applies to files in any column): click/hold file name to enter text edit mode. Drag to highlight exist text. keystrokes do not affect file name text.
3. Select file and Get Info. Highlight file name. Keystrokes do not edit the text.
Any ideas?
-B
Message was edited by: Benson Shaw

try resetting your finder preferences. delete the file homedirectory/library/preferences/com.apple.finder.plist. then control-option-click on Finder in the dock and choose "relaunch".

I cannot rename files in my Adobe reader app. The files are a mess. Can anyone please help?

The files in my Adobe reader app are saved automatically with random file names and I cannot change the file name. There is no option of rename. I have iPad2 and iOS 4.

Update iOS and install the new version of Adobe Reader.

I cannot rename files located on a server volume in Mac OS 10.7.4

Hello,
I have a user who is unable to rename any file types in bridge while using Mac OS 10.7.4. The same is true for metadata. When clicking on the name, the field should allow name changing but it does nothing when clicked on. Same goes for the metadata fields.
It isn't a permission issue as the user is able to rename the files using the Finder application.
I reproduced the error in CS4 Bridge, also on Mac OS 10.7.4.
However, this is not an issue when using Mac OS 10.6.8. There seems to be a fundamental issue with the way Bridge and Mac OS 10.7.4 are interacting.
What would cause this? Since metadata is very important, we are essentially handcuffed by upgrading to Lion. This may be a question for Apple, but I would like to get some input from the experts at Adobe as to why this would be occurring.
Any and all advice is welcome
P.S. this problem was reproduced on various machines- so it's not hardware specific nor is it a network permissions issue.
Thanks in advance!

Thanks for your input. It certainly is odd and made more difficult by a lack of error prompts! What rings out to me is that all signs point to Lion and Bridge, since I can get multiple Bridge versions to work just fine using an earlier OS.
I'm trying to figure out how to get some logs generated, but since no error comes up its proving diffucult to pinpoint where the application is failing to communicate with the server volume.

Cannot rename file with non-ASCII characters when using the

My application moves files from one directory to another by calling File[] srcFiles = srcDir.listFiles() to get a list of files in the source directory, and then calling srcFiles.renameTo(destFile) to rename each file.
This does not work (renameTo returns false and the file is not moved) under the following circumstances:
- the file's leaf name contains non-ASCII characters, for example "�"
- the OS is Solaris 9
- the LANG and LC_* environment variables are unset, i.e. the C locale is being used
If I set the LANG environment variable to, for example, en_GB.UTF-8 then the rename succeeds.
I have tried calling srcFiles[index].getName().getBytes("UTF-8") and the non-ASCII characters are being replaced with ? (0x3f) characters when LANG is unset.
Is this a bug in the JRE? I would argue that since my code does not actually manipulate the filename (I just use the File object that File.listFiles() gives me) then the rename should succeed. Of course I would not expect the file name to be displayed correctly if I printed it out.
I have reproduced this behaviour with JDK 1.4.2_05 and 1.5.0_04 on Solaris 9.
Francis

Thanks for the info Alan.
I considered setting the locale in the environment (this sounds like the "correct" fix to me and we might implement it later), but this application shares a WebLogic server with many other applications so we would have to do a huge amount of testing to make sure that the locale change wouldn't break the other apps. In the end I worked around the problem by making the code that generates the filenames in the first place strip out any non-ASCII characters (the names of the files are not critically important).
Looking forward to JSR-203, in the meantime perhaps a note about this behaviour in the java.io.File javadoc would be useful.

Cannot rename Files in certain folders.

I am having an odd problem with some random folders/files on an internal drive (not boot drive) of my Mac Pro.
When I try to rename them it tells me I do not have permission to do so.
If I try to add a file to the folder, it asks for a admin password first, even though I'm logged in as an admin.
Not all the folders/files on the drive have this issue.
The drive is shared and in the "Get Info" pane it shows that I have Read and Write access.
Any ideas on how to fix?
Thanks

Did you create those files.
An Admin user on Mac OS X isn't omniscient or omnipotent. An Admin user still can't just delete or rename other users files and folders. It will let you do so after authenticating. An admin user's only special power is to request privilege elevation. That's one reason why unix and thus Mac OS X is way more secure than Windows. The admin doesn't get to do anything it wants.
The volume can show that you have read and write, but that doesn't affect subfolders. What you saw in Get Info was for the root folder of the volume. Do you need permissions on that drive? You can set it to ignore permissions in the Get Info pane.
Message was edited by: Barney-15E

Custom batch rename files with Aperture 3 in the following format: IMG_0023.cr2 to Smith_YYMMDD_0023.cr2? I cannot find a way to structure the date in Aperture as such, as well as extract only the camera file

Please advise how to custom batch rename files with Aperture 3 in the following format: IMG_0023.cr2 to Smith_120816_0023.cr2? I cannot find a way to structure the date in Aperture as such (YYMMDD), as well as extract only the camera file (0023, for example). Adobe Bridge CS5 can do this, but NONE of the Adobe software is retina optimized, and is terrible to look at.

In Aperture you are limited to renaming files by the entries in the File Naming preset window.
At what point are you looking to rename, import or export? It might be possible to do what you are looking to do external to Aperture either via a script or other software.
regards

I close PDF file, but cannot rename in Windows Explorer -- file in use error

After viewing a file in Acropbat X Standard, I save and close the file (but leave Acrobat open).
If i try to rename the file in Windows Explorer, it fails and reports this error:
Cannot rename <filename>.pdf: The file is in use by the following program: Adobe Acrobat.
The only way to release the lock is to close Acrobat.
Any solutions? I frequently have several PDF files open at the same time and do not want to close the tool just to release one file lock.
Jim

Been having the same issue here with Acrobat X. Plus, often can't even delete the file after closing Acrobat entirely. It is Acrobat that will not release the file back to Windows.
Only thing that resolves this here, in order to be able to delete the file, is to log user off/on or reboot Windows. Crazy making.
Would be great if Adobe could patch this up. Acrobat X is an expensive program and would be a nice gesture to customers if they fix this.

Need Help - Problem: Cannot rename the file

I hv three type of file, which is original file, processed file and edited file. Then, my goal is change all the three type of filename after i edit and save the document...
My problem is sometime it can be changed, but sometime it just change either one or two type of filename only.....
Can somebody to help me........10s first....
Below is my coding.....
String nfilename = tokenString[0] + "_edited";
File original = new File(directoryname + "\\" + "original" + "\\" + tokenString[0] + ".txt");
File noriginal = new File (directoryname + "\\" + "original" + "\\" + nfilename + ".txt");
boolean success1 = original.renameTo(noriginal);
File process = new File(directoryname + "\\" + "process" + "\\" + tokenString[0] + ".xml");
File nprocess = new File (directoryname + "\\" + "process" + "\\" + nfilename + ".xml");
boolean success2 = process.renameTo(nprocess);
File edit = new File(directoryname + "\\" + "edit" + "\\" + tokenString[0] + ".xml");
File nedit = new File(directoryname + "\\" + "edit" + "\\" + nfilename + ".xml");
boolean success3 = edit.renameTo(nedit);

I have some problem when I rename file that have filename in thai language.
I think may be it's depend on locale, I changed locale to TH but it's not work yet.
some body help me

Adobe Bridge CC cannot obtain files from this device.

I am getting this error message when I attempt to upload videos to my Mac from my Canon 7D:
Adobe Bridge CC cannot obtain files from this device. Please be sure the device is properly plugged in and the battery is full charged.
Battery is full charged and camera is connected properly. I have restarted the camera, Bridge, and the computer as well. I tried reinstalling Bridge and it allowed me to upload 3 of the video files. Then the error message came back. There were a few RAW images on the camera that I was able to upload, but when I tried the video again I got the error message. I read a post about renaming the folder that you are saving to as a fix. I tried that as well, but it did not work.
Any help would be greatly appreciated! Thanks!
-J

This excerpt is from a long-gone post by author Bruce Fraser:
Bruce Fraser - 4:17pm Jun 14, 04 PST (#5 of 21) Opening files directly from the camera is a bad idea for a variety of reasons*, and it most certainly isn't faster than using a FireWire or USB2 card reader.
        • Drains the camera battery
        • Runs the risk of the software you're using to open the images writing to the card and destroying the format
        • Runs a small but significant risk of USB power frying the camera
• runs the risk of wearing out the camera's connector,
• Slowest method known to mankind of getting images off a CF or SD card

Cannot delete file - tried everything - file in use by Windows Explorer error

Hi - I have tried now for 2-3 hours trying to delete an .mkv file from my "Downloads" folder
It says the file is in use by Windows Explorer and cannot be deleted
I have tried deleting it using Del command prompt as me and as Administrator (I am the Admnistrator, there are no other users) - no luck
I have tried Safe Boot and then deleting - no luck
I have tried rebooting many times and then deleting - no luck
Any ideas? It's driving me nuts

hi to all who have this bug- "file in use by Windows Explorer error"
this is the only way that it works:
1.type cmd in search box
2.go to the drive and the directory the file is in ,for example:
after you type cmd you have a black screen with c:\user\
type in the drive the file is in and hit enter example - d: than hit enter
than you should see d:\>
now click the directory the problem file is in ,for example i will call the directory "movies" type in this- cd movies
now you will see this d:\movies>
to delete the file type this: del filename.mkv (dont forget the .mkv or any other file extension) don't hit enter yet, first open task manager (cntrl+shift+esc) go to process tab than right click on explorer.exe choose and click on end process
now your desktop should disappear. get back to the "cmd" window and hit enter.
now the file is deleted. now go back to the task manager and click on "file" on the upper left corner then on new task then type in "explorer.exe"
and you are done
please note that the file name you choose to delete cant be with spaces between the letters .if so you will need to change it in the same way in the cmd window only the comand will be instead of "del filename.mkv"(for example) after you are in the
right drive and directory:
rename "test space.mkv" testspace.mkv
hope i helped
this is the only way it workes
Instead of running a CMD prompt and typing everything, just start up Winrar or Winzip, kill Explorer, then delete problem MKV files to your hearts content within Winrar or Winzip.
Winrar and Winzip will navigate your folders as well.
After you are done, create a new Explorer task.
or..... if you need to rename MKV files, just rename them within Winrar/Winzip with Explorer not running.
I change the MKV extension to AVI (in Winrar with Explorer killed) in order to avoid Explorer issues, if I ever want to move the files in the future without needing to kill Explorer all the time to do so .
Using WinRAR works for me. Using the cmd function becomes complicated when I cannot rename my file with the rename command".

Cannot delete file: filename too long

Sometime ago, I made a copy of a hierarchy of folders under my "Users" folder to another drive as a quick backup. I no longer need this copy of folders and files. So when I tried to delete these files I got a message that some filenames are too long. When
I look at these files they mostly seem to be part of Internet Explorer temp directory, and also some files used by Mozilla Thunderbird, so they were likely created by these utilities on purpose. I cannot rename them to shorter names, or even move them to lower
folders. I can't even copy their filenames to show you what these filenames are! When I use the DOS prompt's "dir /x" command these files do not even have any 8.3 short filenames either, which I could've used to delete them with. There are over 400 of these
files!
I know what the problem is, the Windows OS has a limit of somewhere around 250 characters for filenames and complete pathnames. I've seen some utilities advertised saying that they can delete these files, but they all require money. Anything that's free?
Yousuf Khan

Hi,
It is just for testing. It is good since the files can be deleted in Linux.
However, if you don't have Linux, it needs to find the way to delete the files under Windows.
Since the files are located in Internet Explorer temp directory, you could use Disk Cleanup to clear the Temporary Internet Files.
Also, check if the following KB is helpful. It has several methods. Go to check if 8.3 name creation is disabled.
http://support.microsoft.com/default.aspx?scid=kb;en-us;320081
Best Regards,
L.S
Regarding it being in the Internet Explorer temp directory, it actually wasn't. Remember I said in the original posting that this was in a backup directory of these directories, so Disk Cleanup has no way of knowing that this belongs to Internet Explorer
or anything else. Also there was a Thunderbird directory having the same issues as well, which Disk Cleanup wouldn't have touched no matter what.
Okay, I checked out the state of the filesystem registry. The "NtfsDisable8dot3NameCreation" entry in the "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem" is set to non-zero, meaning the feature is in effect. Interestingly it was set to 2
rather than 1, but I doubt that makes a difference.
Even if I disable this feature right now, all previously created files still won't be assigned the 8.3 filenames, just only those files that are newly created will have the 8.3 filenames available.
Yousuf Khan

Renaming files in OS X Snow Leopard with illegal chars..

I'm still using Leopard but want to know if the behavior of renaming files is on par of that in, gasp, Windows Vista. I was jsut doing a lot of renaming and it reminded me of the days I used to use Vista when renaming a file and using an 'illegal' character it would pop-up a yellow dialog (not an error window) to remind me of the characters I can use only.
In OS X Leopard 10.5x if I try to use e.g. ":" I get an error box and this then reverts the file back to its original name which erases all of what I had done, all for one char probably. On top of this the error box then gives me a cryptic message as to what the error was about:
"The name "xxxxx" cannot be used.
Try using another name, with fewer characters or no punctuation marks."
I heard that the guys working on OS X 10.6 Snow Leopard tidied everything up, doing all those things they always wanted to do, I bet they didn't get many opportunities like that! And was hoping that they did something toward file rename?
I'd expect that the erroneous char would be highlighted and some kind of error shown, but not to delete everything typed in. Can anybody tell me?
Thanks.

It's a unix thing, and not quite something I'd classify as needing to be cleaned up...
• The only illegal character for file and folder names in Mac OS X is the colon “:”
• File and folder names are not permitted to begin with a dot “.”
• File and folder names may be up to 255 characters in length

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.

Cannot rename files

Similar Messages

Maybe you are looking for