**resolved** Win 11 Pro and PSU: Extremely slow start (Single User Version)

[JensSteyer]

Since I started using PSU, nothing has changed. All my programs (Photoshop, Capture One Pro, MS Office Suite and many more) start lightning fast, only PSU takes between 30 and more than 60 seconds to start......... And that has been the case since the beginning, regardless of the version.

I only use a Dell mobile workstation that is 2 years old (Precision 5770, i9 CPU, 64 GB RAM, NVidia RTX A3000 / 12 GB, 2x 2 TB NVMe SSD Class 40) and Windows Defender (without additional virus scanner) and NordVPN.

How is it for other Windows users? Does PSU start lightning fast for you or does it take longer or even a long time?

This extremely slow start always makes me unsure whether I have already started PSU. It has happened that I clicked on the icon again and then started two PSU instances at the same time... That was also bad, because the database seems to have problems with it...

Once the PSU has started, everything runs very quickly, I am completely satisfied with that. However, starting the PSU is nerve-wracking every time...

An analysis program would be good to see what is delaying the PSU start so much. Is there something like that, dear Hert?

[RobiWan]

Hi Jens,
on my AMD Desktop 6,5 Sec (icl confirm user PWD).
on my Gigabyte Laptop 7,8 Sec

My Server versions
Desktop 8,1 Sec (icl select Database/ User)
laptop 8,2 Sec c (icl select Database/ User)

Show maybe there are old PSu processes running

Start PowerShell and then
Get-Process -ProcessName IDI*

[G8DHE]

On my Laptop it takes 6 seconds from clicking the taskbar Icon to load 63,000 images both program, database and data are on SSD.
OS Name Microsoft Windows 11 Home,Version 10.0.22631 Build 22631
Processor 12th Gen Intel(R) Core(TM) i9-12900HK, 2900 Mhz, 14 Core(s), 20 Logical Processor(s)
Installed Physical Memory (RAM) 32.0 GB

On my Workstation it takes 15 seconds to load 334,000 images program and database on SSD but the images are over the network to a server using HD's.
OS Name Microsoft Windows 10 Pro, Version 10.0.19045 Build 19045
Processor Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz, 3501 Mhz, 6 Core(s), 12 Logical Processor(s)
Installed Physical Memory (RAM) 24.0 GB

[apanella]

I am at about 6s with about 185,000 images.
The local set usually less than 2,000 (Laptop, i9, NVMe, 32G RAM, 802.3ax wireless connection to a mesh)
Remaining 183,000 are on a spinning disk RAID'd NAS connected to the network in another room.

Comparing to the above, it would seem I am middle of the pack... much less than JensSteyer

The difference I see....
I also >exclude< the following from Defender: 1) video/photo file extensions; 2) PSU folders that contain EXE 3) PSU folders that contain the database


Thinking about this further...
I do not often touch the NAS files... so having those in travel mode most of the time would be OK.
Maybe it could be possible to have the best of both worlds by having the option to assign travel mode by imported folder. (Today it seems to be all or nothing). Is it worth entering this into Mantis as a new idea?

[JensSteyer]

Thank you for your feedback, dear friends.

I had already completely excluded the database folders and the Photo Supreme installation folder in Windows Defender, and also specifically IDimagerSU.EXE.) Unfortunately, I still haven't achieved the right result (i.e. "quick start").


@ Hert
Question 1: If I uninstall PSU completely and without leaving any residue in order to get a new, clean installation: How can I save the PSU settings? Is there a file that stores the special settings and that I can save?

Question 2: I haven't assigned a password because I work alone on my computers. If I save my databases, can I reload the databases in PSU without any problems?

Question 3: I observed the PSU start with the Process Explorer (sysinternals.com):
- I start PSU > and I see it immediately in the Process Explorer.
- PSU generates a CPU load of 4-6% for about 6 seconds.
- After that nothing happens for a long time, no PSU action in the Process Explorer.
- At some point (30 to 90 seconds later) PSU starts and a (low) CPU load is also displayed in the Process Explorer.
My question would be: What happens during this long idle time without any CPU load (including no CPU load from any other app)?


Thank you in advance.

[Hert]

Most likely PSU is waiting for the OS to respond to the availability of one or more shares to a network or some other device in Windows.
Are you using shares in Windows? If so, try to disconnect those and see if that impacts the startup time.

Question 1: If I uninstall PSU completely and without leaving any residue in order to get a new, clean installation: How can I save the PSU settings? Is there a file that stores the special settings and that I can save?

While I don't expect a reinstall to make any difference...make a backup to safeguard all existing settings.

[JensSteyer]

Most likely PSU is waiting for the OS to respond to the availability of one or more shares to a network or some other device in Windows.
Are you using shares in Windows? If so, try to disconnect those and see if that impacts the startup time.
...

You really are a real expert, Hert - and once again you are completely right: It was the shares. But it wasn't the (all temporary) shares to my NAS, but the two (also temporary) to my large image editing PC.
So I have now separated the last two network drives and connect them via batch when necessary. That is easily solvable.

The start of Photo Supreme 2024 (PSU) now takes a smooth and quick 4 seconds - and this is reproducible every time it starts.


But please answer this questions for me, dear Hert:
What do the temporary shares X: and Y: to my large PC have to do with starting PSU?
How can I turn off the (in my opinion) unnecessary search for shares?

All of my images are stored locally on
d:\Photos-local-current\
and my PSU database on
d:\Catalog PhotoSupreme\

[johnbarrett]

Ditto for exclusion as I have links to desk pc and nas

[johnbarrett]

I have a new laptop and due to the poor networking of W11 had created links to the desktop drives and to my server. Today has been the first time I used the laptop away band PS2024 was so slow at opening I made the mistake of re clicking it a number of time with a good crop of crashes as there was an update. It took over 4 minutes once I removed the drive links it opened nearly instantly. But it means I will have to recreate the links every time at home and if there is no way of getting PS2014 to ignore preset links I will have to remove them every time I am away.

[G8DHE]

Odd behaviour, I have 4 machines here on the network, but don't seem to suffer this problem despite all having links to this laptop only the server machine has images that PSU knows about other than on its own drives, but never have this problem?

[johnbarrett]

Is this with the laptop away from the network? At home I had no problems and the old latop running 10 didn't need links to folders it worked perfectly over the network. I hadn't expected it to cause such a big hit on opening which what surprised me

[G8DHE]

No its all on the same network with shares between all the machines so that all the drives (or a lot of them) are instantly available as drive letters. Doesn't seem to make any difference when I'm away from the LAN without the shares being available, the start up times remain the same.

[johnbarrett]

Odd I restarted PS number of times every one was at or more than 4 minutes took off the shares to the desk pc and served and it's now starting almost instantly (I only have the current year on the laptop). I hadn't expexted it to be affected which is why I thought it wasn't started/running

[JensSteyer]

Odd I restarted PS number of times every one was at or more than 4 minutes took off the shares to the desk pc and served and it's now starting almost instantly (I only have the current year on the laptop). I hadn't expexted it to be affected which is why I thought it wasn't started/running

That's exactly how it was for me. Without the (often inactive) network connections, it starts almost immediately - no comparison to before.

If I then need these connections, I restore them using a small batch:

Code: Select all

@Echo off
echo I check if the Synology is online...

:Loop
ping -n 1 -w 5000 192.168.178.133 | find /i "TTL" && (goto Online)
goto Loop

:Online
if exist J: net use /d /yes J: > NUL
net use J: "\\Diskstation\music" > NUL
echo Laufwerk J: (Photos) verbunden

rem Here are the further connections to the Syno shares.
exit

[johnbarrett]

Thanks will have a go adapting it when home but zzI must say it's been 20 or 30 years since doing batch files
I must admit I don't understand whey the progrsm checks every drive rather than just the one/s in use. Had a look and bit lost after all this time so just recreating links and will just have remove them each time away