always getting this error message trying to move files from pCloud

I suspect this is more a pCloud issue than a Windows 10 issue but my
Googling hasn't found an answer.

I am using Windows 10 Home, ver 1909, OS build 18363.900 if that's
helpful.


Whenever I try to copy a file I have in one of my pCloud folders to a
local drive or to Dropbox I receive this message:


The filename you specified is not valid or too long.

Now it's not an issue of length because one of the files that elicited
that message was key.doc and obviously that's not long and has no
offending letters, symbols, or spaces.

I'm wondering if anyone can tell me why I can't move those files from
the cloud.

thanks


Laurence Smith

--


--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

On 02/07/2020 03:00, Laurence Smith wrote:


You are not authorised to read my posts in plain text. Please install HTML enabled newsreader, such as latest Thunderbird https://www.thunderbird.net, to benefit from solutions posted in my posts.


--

With over 1.2 billion devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

Laurence Smith wrote:
I suspect this is more a pCloud issue than a Windows 10 issue but my
Googling hasn't found an answer.

I am using Windows 10 Home, ver 1909, OS build 18363.900 if that's
helpful.


Whenever I try to copy a file I have in one of my pCloud folders to a
local drive or to Dropbox I receive this message:


The filename you specified is not valid or too long.

Now it's not an issue of length because one of the files that elicited
that message was key.doc and obviously that's not long and has no
offending letters, symbols, or spaces.

I'm wondering if anyone can tell me why I can't move those files from
the cloud.

thanks


Laurence Smith


For your amusement, some fun with mklink and infinite loops
in the pathname...

https://github.com/Microsoft/winfile/issues/131

You see, some of the file system "features", lead to infinite
recursion if you drop stuff on them. Your home directory has
some "Junctions" in it.

*******

You could do a trace with Process Monitor, then filter on

Operation is CreateFile (Add to filter)
Operation is WriteFile (Add to filter)

and see if you can see the absolute pathname used for the
(attempted) operation. You can see even failed file operations
there, such as attempts to create things which are too long.

https://docs.microsoft.com/en-us/sys...nloads/procmon

The tool I think, even has a "find" in it, so you could
enter "key.doc" and that will save some scrolling to find the
reference.

After the "event", the "screwup" is captured, go to the
File menu in Process Monitor and "untick the tickmark".
This stops the trace and then you can take your time
looking at filenames and such.

Paul