Hey 
Thanks for the fast reply, and i really appreciate your text formatting!
The problem is the missing key file. Luckily we can „pinpoint“ what causes this.
1. Clean Reinstall
- Uninstall Topaz Video AI
- Delete: (i cant verify it, since im not at PC but they SHOULD be here)
C:\Program Files\Topaz Labs LLC\Topaz Video AI\
C:\ProgramData\Topaz Labs LLC\Topaz Video AI\
2. Reinstall with Admin Rights
- Right-click the installer → Run as administrator
3. Launch App with Admin Rights
- Right-click the app icon → Run as administrator
4. Log In and Check
- After logging in, go to:
C:\ProgramData\Topaz Labs LLC\Topaz Video AI\models\
- See if
auth.tpz appears
If it does NOT we can assess with near 100% certainty that its a network related “issue” (aka some process/rule that blocks/breaks the authentication process.)
Since we’ve ruled out all local permission and installation issues, the problem is now definitely network-related—the app can’t reach Topaz’s licensing servers in a way that allows it to complete activation and generate the auth.tpz file.
Here’s the tricky part:
I work with enterprise networks (firewall management, domain architecture, security testing, etc.), and honestly, there are dozens of different configurations that could silently break this kind of authentication. Without visibility into how your corporate environment handles outbound traffic, it’s nearly impossible to say exactly what’s blocking it—but I can point you in the right direction.
What to ask your IT team to verify:
Can you confirm there’s no firewall or proxy blocking HTTPS (port 443) to these endpoints?
These are the critical (according to avilable documentation) services Topaz uses for license activation:
api.topazlabs.com
licensing.topazlabs.com
cdn.topazlabs.com
Are these domains subject to SSL inspection, packet rewriting, or certificate substitution (MITM TLS proxies)?
If yes, ask IT to whitelist (exempt) them from inspection—Topaz’s licensing relies on strict TLS trust.
Is the network using a proxy that requires authentication (NTLM, Kerberos, or login portal)?
Topaz’s license client LIKELY does not support proxy-authenticated flows, which can cause silent handshake failures.
Can they check the DNS resolution path for the domains above?
Make sure the returned IPs are correct and not being filtered or sinkholed by security software or DNS policies.
Is outbound traffic on port 443 limited to browser traffic or approved user agents only?
Some enterprise networks block non-browser HTTPS connections, which breaks background authentication flows.
Additional domains the app may contact (but less likely to block login):
These are used for downloading models, telemetry, and update checks. While not critical to license activation, they may still affect functionality or background processes:
AGAIN: Warning! i can NOT verify that those are all. I spent quite abit of time with their documentation and here is what i found:
downloads.topazlabs.com
veai-models.topazlabs.com
models.topazlabs.com
et.topazlabs.com
hope this helps,
Cheers