Hello Ryan,

Welcome to the PhD forum

Are you referring to the folders containing the project material? .phd file, cach & faces folders?

Could you please post the folder location and screenshot of what you're seeing?

PIX PIX YouTube channel

This is the folder containing my photos. See attached:

Oh, now I understand.

I took your initial post to mean folders in the OS, rather than folders within PhD.

You're right to be alarmed at that! I've not seen it reported previously.

If this is only happening in one particular project, I'd export the edited photos then delete the project files from your computer. Next. I'd open a new project and re-import the original files/folders.

If this is occurring in many PhD projects, I'd suggest a complte uninstall/re-install using Revo Uninstaller or similar dedicated software to remove the registry items. Re-install after a beboot.

PIX PIX YouTube channel

I'm running into the same thing on a fresh install of PhotoDirector 7.0.7504.0 on a fresh install of Windows 10. I had downloaded it for evaluation prior to purchase and installed it on a clean VM for the trial, so I don't think uninstall/reinstall will necessarily fix it - there's been no upgrade, no other software installs, nothing on this machine.

I have noticed that the names of the folders in the folder list aren't always correct. I've also noticed that they may change to become corrupt (or become correct if they're already corrupt) based on whether I start a new virtual copy of a photo or try some edit operation.

I've attached a screen shot.

In my case, the folder name always becomes "Pictures" - like the name of the parent folder. My folders are all, in reality, named after the year of the photos they contain (1976, 1977, etc.).

Note my pictures are stored on a network machine, not on the local hard drive. I don't know if that has anything to do with the issue.

I contacted support about this, and for me the problem was that I was running the software on a virtual machine rather than a physical machine. I'm not sure why or how that affects things, but after installing the software on a real, physical machine I was unable to reproduce the issue.

I take it back. Being on a virtual machine did not fix the issue and I've re-submitted my ticket to support.

I was able to reproduce this very quickly on my virtual machine setup, but it took several days before it appeared on my physical machine. I'm now looking at a stack of four incorrectly named folders sitting in my folder list, just like in my previous screen shot.

Hello tillig,

Welcome to the PhD forum

I'd be interested to know what options you have checked in your import dialogue. Have you selected "Keep in current location" or "Make extra copy in..."?

Does anything in this post give you any clues? https://forum.cyberlink.com/forum/posts/list/49354.page#259318

Be aware that I'm not working with network drives or virtual machine, as you are, so there would be inconsistencies I'm unable to replicate here.

PIX PIX YouTube channel

I selected "Keep in current location" and nothing else - no "exclude duplicates," no processing options, nothing. Just get the photos in.

The import process worked fine when I ran it initially. I got the photos in, everything looked OK. It was after closing PhotoDirector, logging out, and (the next day) logging back in and opening PhotoDirector again that I saw the corruption.

To be honest, I only noticed it after running Tag Faces on the folder tree. It may have been there prior to that, but it was after that process when I saw the wrong folder names.

The post you noted doesn't seem to help me in this case. I only have one project I'm working with. PhotoDirector has correctly been re-opening that project on launch. It's just displaying names wrong in this project, is all.

I luckily haven't done much in this project beyond the initial import and attempt at face tagging. I may try a brand new project and be slower/more deliberate about the steps I go through to see if I can come up with a known way to replicate the behavior.

I wish there was some sort of database consistency check tool available. I feel like this could pretty easily be rectified with something like that.

Another follow-up: I found that if I mount the network location as a network drive then this doesn't happen, or at least it hasn't happened in the week since I've tried it. I've run face tagging on ~14,000 photos and the folder names haven't gotten corrupted yet. I'm still doing some work on the library (testing different functions like creating virtual photos and such) to see if it happens again, but so far I'm having more luck with the network drive approach.