Constant verification on start up

Why on earth does AI have to verify my account every time I start it up? None of my other Topaz products do this.

My internet has been down for 2 weeks and I thought I’d catch up on some image processing. No such luck. So I have not been able to use a product I paid for. This is not acceptable. Some of us live off grid without reliable services.

I ditched Photoshop many years ago because they pulled this trick, I hope I don’t have to do the same here because I love the Topaz software.


1 Like

We updated Topaz Photo AI to require a login every 6 months. If it’s asking you to login more than that then there is an issue with the authentication.

Please update to the latest version of Topaz Photo AI. If it’s still requesting authentication every time, attach the logs here. Open Topaz Photo AI, go to the menu bar on the top and click the Help > Open Log Folder menu option.

The authentication is stored in the registry. If something is affecting the registry that could cause this issue as well.

The upgrade is a 600+MB download which I did from within the Topaz package only to have the install fail. Not sure why it failed because at 2-3 hours to download I had to do other things, just came back to an error message.

Here is the log from that attempt (I think)

=== Verbose logging started: 4/08/2023 8:10:20 Build type: SHIP UNICODE 5.00.10011.00 Calling process: C:\Windows\SYSTEM32\MSIEXEC.exe ===
MSI (c) (EC:04) [08:10:20:238]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (EC:04) [08:10:20:239]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (EC:04) [08:10:20:258]: Resetting cached policy values
MSI (c) (EC:04) [08:10:20:258]: Machine policy value ‘Debug’ is 0
MSI (c) (EC:04) [08:10:20:258]: ******* RunEngine:
******* Product: TopazPhotoAI-1.4.3.msi
******* Action:
******* CommandLine: **********
MSI (c) (EC:04) [08:10:20:259]: Note: 1: 2203 2: TopazPhotoAI-1.4.3.msi 3: -2147286960
MSI (c) (EC:04) [08:10:20:259]: MainEngineThread is returning 1620
=== Verbose logging stopped: 4/08/2023 8:10:20 ===

Do you know where it stores the install file so I can run it manually to try again?


OK, I finally got to upgrade and it seems to work now, I’ve launched it a few times and except for the first one no verification required.



Please reach out if you need help with anything else!

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.