For file paths over 260 characters W7 gives a nice warning "the file name is too long". Windows 10 DOES NOTHING !! - UGH

Our small business has a mix of windows 10 and windows 7 clients running under Server 2016.

When copying a folder into a subfolder, we sometimes get "problem" files where the full path is over 260 characters.  

Under both windows 10 and windows 7  Microsoft Explorer displays the folders & files properly .

But when a windows 10 user double clicks on one of the problem files, nothing happens.  Sometimes the users waste quite a bit of time  then come to me for help.

When a windows 7 user double clicks on a problem file, explorer.exe gives a nice error message "the file name is too long". This is much better, and sometimes they don't even need to come to me to solve the problem.

Is there a way to get windows 10 build 1709 to generate the same error message?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Seth SimmonsSr. Systems AdministratorCommented:
Is there a way to get windows 10 build 1709 to generate the same error message?

just enable the registry value so that it can use the long path name
i have tested this and it does work; we have a few long path names on an old netapp and was able to access on windows 10 without issue

How to Make Windows 10 Accept File Paths Over 260 Characters

it unfortunately doesn't help with windows 7 clients since it is new with windows 10
yo_beeDirector of Information TechnologyCommented:
I just looked at my reg on Windows 10 and this is enabled, but I do get the error message.
rberkeConsultantAuthor Commented:
Yo_bee: i am interested in more details about your comment.  You say you are getting the message.  But, I and my coworkers do NOT get the message.  I wonder what is different ?  I have w10 1709 and MS office pro 2010.  What version of office do you have?   Also, does your message come in an explorer.exe dialog?  Does it come when you double clicke the file?  

Seth: That registry entry does not help on my computer.  I turned it from 0 to 1 then signed off and on. Double clicking the problem file still does nothing. Perhaps this is because I (and most of our office) have  MS Office 2010 32 bit?

That W10 article says "any modern applications should be fine" so maybe that means only office 2016? I will eventually try it on our one and only Office 2016 computer.  

But, even if it works on that one computer, it does not help on the other windows 10 computers.  The "most ideal" solution would allow files to be opened when possible, and a warning message to appear otherwise.    I already get that warning message on W7 just never on W10.

Another perfectly acceptable solution would be to have w10 always give a warning message whenever there is any attempt to open the file.
OWASP Proactive Controls

Learn the most important control and control categories that every architect and developer should include in their projects.

rberkeConsultantAuthor Commented:
The article says to change  [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]LongPathsEnabled
from 0 to 1.

I have tried that on 3 of our computers,  W7 office 2010;   w10 office 2010;  w10 office 2016.
That registry entry had no affect on any of those environments.

My original problems with a 280 by path remain unfixed:

None of the environments allow the file to be opened.
Only w7 gives informative error messages when attempting to open the file.

I am still not giving up.  In particular, I hope to hear back from Yo_bee who says he DOES get an error message.  But, my guess is that he is just wrong.
yo_beeDirector of Information TechnologyCommented:
I get the error, But I do not know why since my reg setting is enabled.
I really do not have any insight In why.
rberkeConsultantAuthor Commented:
I would appreciate it if you could answer a few questions.

Please close all instances of MS Word, then try to double click on a  long filename file in MS Explorer.

Do you still get the message?  Does it come from Explorer and look like this windows 7 message? msg: "The file name is too long"

What version of  Windows do you use and is it 64 bit?  (I have 64 bit Windows 10 pro creator version (build 1709).
What version of office do you have and is it 32 bit?  (I have 32 bit Office 2010 pro, but i have also tested it on office 2016 home and business).
yo_beeDirector of Information TechnologyCommented:
I never have the issue of opening a file with too long of a filename in W7.  I just lose the ability to rename or copy from within Explorer.  When this happens I use Robocopy to move the file to a location locally and that gives me enough of a buffer so I can rename the file.

I was posting because I was curious about the reg setting.  

I have a 64 Bit Win 10 1703, office 365 most current(Pre Creators Editions)
rberkeConsultantAuthor Commented:
Is your office 365 a 32 bit version or a 64 bit version?

Just to make sure I understand.

Let's say your file name is like this, and that ..50.. means a 50 character string.
s:\Root folder ..50..\levelA..50...\levelB..50..\levelC..50..\levelD..50..\levelE..50.\my file name.doc
So, the full path is about 350 characters.

You are saying you could double click on that on a windows 7 machine and it would just open without any complaint?

But, your first post said "I do get the error message."  So you are saying the older windows 7 system opened the file, but the newer windows 10 does not?

I am most confused.  

yo_beeDirector of Information TechnologyCommented:
Sorry for all the confusion.  

On my Windows 10 machine it is a home computer and I was just trying to save a file to my local drive with 260 characters and I got the error.

The windows 7 machine is my Work one and I am accessing files from my NetApp filer. This one I open files with longpathname, but I cannot save rename, copy, cut or delete.

I will try my w10 machine tomorrow and see what happens
rberkeConsultantAuthor Commented:
that makes more sense.  NetApp filer is for huge network attached storage, so it is much more flexible than normal Windows software.  It is probably very well integrated into w7, w10 an Windows Server environments, and may completely eliminate 260 character problems.

But, that does not apply to my situation at all.

Also, I am not surprised that you get an error message when you try to SAVE a file on your home machine.   All of my environments do exactly that.

My main issue is that my w10 users do not get an error message when they OPEN a file.

I suspect you will find that your W10 machine works exactly like mine, which means that opening a 280 character file path will fail and will NOT say "file name is too long".

So, after a long discussion, I am back at square one.  I will probably PAQ this question,
The "best answer" is
Microsoft Office 32 bit versions cannot open a 261 byte file path.  Error messages sometimes occur when this is attempted, but sometimes don't, and it is difficult to predict.  64 bits versions might work better.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rberkeConsultantAuthor Commented:
Several experts attempted to help but none of there solutions made any difference.

I do not believe there is a solution, and I cannot devote any more time to searching for something I do not think exists.
Ross GramCommented:
you can try to Long Path Tool program to resolve this issue. This tool is very helpful to resolve the issue.
rberkeConsultantAuthor Commented:
I do not believe Long Path Tool helps my situation.  It looks like the tool will let me change all my long paths so that they will be shorter but that is not what I want.   I would have to run it periodically to keep up with any new files that were created.  And each time I would have to grapple with the typical tricks like changing "Stock" to "Stk" etc.  And, of course users like the names they have chosen and would often ask "what happened to the name that I liked?".  

I simply want to warn the users when they try to open one of these files.  W7 gives such a warning, too bad w10 doesn't.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.