Starlight mini gets greyed out after Topaz Video 1.0 update

[If you are posting a new bug, please include the following]

  1. Starlight mini gets greyed out after Topaz Video 1.0 update. The application makes me download the files, and thereafter it doesn’t allow me to use them, and tells me they’re not available, only available in the cloud.
  2. Windows 11, 4090, 96GB RAM

After your account page stops saying “Pending Studio Transition”, try logging out in Topaz Video and logging back in. That fixed it for me.

If your account has Founder access or is a Pro account you should have access to run it locally. If you are seeing it still greyed out, log out and then back in to refresh the connection.

If that does not resolve the issue and you should have access to run it locally, please email the support team so we can investigate. help@topazlabs.com

Hi, there. A few days ago, I updated to the new Topaz Video. I am trying to use Starlight Sharp for the first time, and I’m running it on my local machine (not the cloud). I ran the verification test, and my computer meets the requirements to run the Starlight Sharp model locally. I am a Founding member, so I have access to running Starlight Sharp locally. I am running Starlight Sharp on a very short, 4-second 1080p video clip.

I have already allowed Topaz Video to download and install the Starlight Sharp model, and it said the model was downloaded and installed successfully. I am running Windows 11 on a MSI Titan GT77HX 13VI-028US laptop with an Intel i9-13980HX CPU, an NVIDIA GeForce RTX 4090 Laptop GPU, and 192GB of RAM. In case it is helpful, I have uploaded the “DxDiag.txt” file that Topaz uses to determine suitability of my computer to run the Starlight Sharp model locally.

DxDiag.txt (152.7 KB)

I tried this same test with Starlight Sharp a couple of times, then rebooted my computer, and tried it a couple of more times. In each case, it starts to do the export, and then the export fails with an error. I have attached the “logsForSupport.zip” file, and I have also attached a screenshot of what I’m seeing when it displays the error. Any help appreciated!

logsForSupport.zip (145.0 KB)

Hi, what I’ve found in the log

21556 Critical Wonder local processing blocked: Pro license required

Same problem here.
“As a founder” i should update to topaz video, and now i cant render with Starlight sharp. Runs for hours and then the export fails!
Same error message like in screenshot from rforgaard
and same error line in logfiles
27496 Critical Wonder local processing blocked: Pro license required
Is the topaz team looking in this forum? I am new here.
Thanks!

Update: Hmmm. No error after changing output to mp4!?

That is a good find - thanks for pointing out that specific message in the log. I didn’t notice that. I think the “Pro license required” is a bug. Now that Topaz Studio is out, all models can run locally (if you have compatible high-end hardware), if you are Founding member, even models that are normally only available to Pro users. I have emailed help@topazlabs.com to try and find why this “Pro license required” error is getting triggered when running Starlight Sharp locally. (This error does not get triggered for me when running normal Starlight locally, only Starlight Sharp.)

On Tue, Sep 23, 2025 at 2:58 AM Mayday via Topaz Community <noreply@topazlabs.com> wrote:

45x45 Mayday Topaz Video AI Owner
September 23

Hi, what I’ve found in the log

21556 Critical Wonder local processing blocked: Pro license required

Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

For me, even if I change the output to H264/MP4, I’m still getting that error, and a “Pro license required” message in the log, even though I’m a Founding member, when I run Starlight Sharp locally. (This happens regardless of whether I choose Original resolution or 4K resolution. My input video is 1080p.)

Can you try logging out and logging back in to reset the permissions?

Account > logout

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