I can confirm that using the Shift key does allow me to start working without the long delay. As I mentioned earlier in this thread, the delay only happens the first time I open PS after rebooting my pc. If I wait for the catalog health check to complete and then close the program and then reopen it a few minutes later, there is no delay. I guess it keeps track of the fact it already ran the check? If I restart my system and open it again, I get the delay. This makes it a little bit of a hassle to troubleshoot since I need to restart my system every time I want to test it.
I'm guessing that there is some issue with my catalog that I'm not able to discover. I've tried the steps you outlined above. Is there anything else I can look for?
Issues with V2024 on startup
Re: Issues with V2024 on startup
After running through the steps:
Are there still items in the Timeline with a 0 year or an 1899 year?
If you run Tools -> Check for missing thumb and previews...do you get thumbs/previews being built?
Are there still items in the Timeline with a 0 year or an 1899 year?
If you run Tools -> Check for missing thumb and previews...do you get thumbs/previews being built?
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message
Re: Issues with V2024 on startup
I'm not seeing any items with a 0 year or 1899 year. There are some with 1980 year that were not taken in 1980 but at least they do have a date. When I run the check for missing thumbs and previews, it runs very quickly and the progress bar updates so fast that I can't even read the message that flashes below it before it closes. I had 9 out of sync items that would not sync no matter what I tried so I removed them from the catalog. That still didn't prevent the delay after I rebooted and restarted Photo Supreme. I'm learning just to live with it. I open the program, click on something, and then just wait until it responds. It usually takes about 1 minute and then I can work normally. I would just like to know what is causing the delay.
Tom Stoddard
Re: Issues with V2024 on startup
Hmmm, maybe it’s a network share that is not connected?
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message
Re: Issues with V2024 on startup
I don't have any network shares.I'm using the standalone version on a PC at home that is not networked to any other devices.
Tom Stoddard
Re: Issues with V2024 on startup
You report that this happens every time after rebooting the computer and not every time after starting Psu.
That leads me to think that it is a Windows thing. Windows checks for the existence of something (probably a share or external drive, or scanner, or other MTP device, or virtual drive, could even be a software shell extension in Explorer, or a virus scanner) and once checked, Windows caches that info and won’t check again.
You then notice this on starting Psu because Psu monitor local drive changes and as Psu registers in Windows, that is when Windows is triggered to check the drive/medium.
That leads me to think that it is a Windows thing. Windows checks for the existence of something (probably a share or external drive, or scanner, or other MTP device, or virtual drive, could even be a software shell extension in Explorer, or a virus scanner) and once checked, Windows caches that info and won’t check again.
You then notice this on starting Psu because Psu monitor local drive changes and as Psu registers in Windows, that is when Windows is triggered to check the drive/medium.
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message
Re: Issues with V2024 on startup
Is Psu V2024 doing something differently than the previous version? I didn't have this problem until I upgraded to Psu 2024. Didn't the previous version of Psu register in Windows also?
Tom Stoddard
Re: Issues with V2024 on startup
It seems that build 6443 has finally resolved this issue. The first time I rebooted and started PSU after upgrading to 6443 the program frooze permanently and I had to use Task Manager to close it down. Since then, I've rebooted and opened it several times and it opens quickly and starts working normally right away. I hope that continues. Thanks!
Tom Stoddard