App won't open files moved to another folder

Running Win10 Pro, Ver 21H2, OS Build 19044.1706.

This is not a life-and-death issue, just frustrating. I have some files with a .pcb extension that are circuit board layouts. I moved some from a default storage folder into another folder specific to a certain project. Now when I double-click on the files, the app starts and looks as if it's opening the file, but all I see on the screen is a blank workspace with the usual gridlines. The app is otherwise open and ready to go, but the circuit board artwork that should be there just isn't.

But, if I first open the app and then open the file through the app's File/Open utility, the file opens fine. So at least all the work isn't lost (gulp!), it just looked as if it were. Also, if I grab the file that won't open and move it to the Desktop, a double-click opens it there as it should. However, if I take the folder that contains that file and move it to the Desktop, the file cannot be opened with a double-click.

I have moved other .pcb files from the default repository into other folders with no problem. So using Windows Explorer, I brought up two folders, one that opens and one that doesn't, and compared all the Properties of those two folders. They are identical. Then I brought up the individual .pcb files, the one that opens, the one that doesn't, and compared the Properties of those. Identical as well. All the General, Security and Detail tabs look exactly the same. So, what else could be going on here? Oh, yeah, the individual files were generated a few years ago under Win Vista, if that makes any difference.

Thanks for the tips, guys. I don't think it's path length, a more recent file that's got an even longer path length in a parallel folder opens fine. Just for fun I copied a file that's in the folder where they double-click open and put it in the file where they don't. Sure enough, it won't open from that folder. I've appended File Explorer images of both folders; it's the shorter-path one where they won't open. Again, Properties of those folders are identical.

Rather a long-shot, but I notice that the troublesome folder has a 'dot' (misc. Files) in the path name. Shouldn't matte, of course.

Oh, my gosh! Good catch, mngerhold. I'm of course sensitive to extra dots in file names, Lord knows how Windows might call up some obscure program to open an inappropriately-dotted file, but I never considered that it made a difference in a folder name. Before blowing off your observation as a 'can't be' I gave it a try first and simply deleted the dot. Funny, a little circular timer popped up and replaced my cursor for just a fraction of a second, as if Windows was doing some useful work, but then I went into the folder and double-clicked on the file and, wonder of wonders, IT OPENED! So many thanks and kudos to you for thinking of this; I will remember it.

Glad to be of service - I wouldn't have bet on it. Martin