Windows diagnostic Adobe connection blinkl.io

If the connection problem continues, blinkl.io support may ask you to run the Windows diagnostic tool. It helps investigate connection failures between blinkl.io and Premiere Pro for any Blink that runs in Premiere Pro.

These steps apply to Windows 10 or Windows 11 and Blinkl-Premiere-Diagnostic-v1.3-EN.bat.

Run the diagnostic

1. Download Blinkl-Premiere-Diagnostic-v1.3-EN.bat and save it to your computer. If the download is unavailable, ask blinkl.io support for the file.
2. Open blinkl.io and Premiere Pro normally, then open the affected project. Keep both applications open throughout the diagnostic.
3. Double-click the .bat file normally, then accept the administrator prompt. Starting with a normal double-click lets the tool compare connection access before and after elevation.
4. When prompted to reproduce the problem, open the affected Blink and repeat the action that causes the connection issue. Version 1.3 displays “Reproduce the Smoothify connection problem now”, but this instruction applies to whichever Premiere Pro Blink you are testing.
5. Leave the diagnostic window and both applications open until “Diagnostic complete” appears. Allow several minutes for collection.

If you are testing a computer where the connection works, use the Blink you are testing normally when prompted and tell support that this is a working-computer comparison.

Send the report to support

At the end, File Explorer opens the folder containing the report and selects Blinkl-Diagnostic-….zip. The console displays:

Send this ZIP file to Blinkl support: <file path>

Send that ZIP file in your existing support conversation, along with the name of the affected Blink, the approximate time you reproduced the issue and whether it occurred during the diagnostic run.

The report is normally saved on the Desktop of the Windows account that started the tool. If the Desktop is unavailable, it is saved in that account's temporary folder.

If a step shows TIMEOUT

TIMEOUT means a check exceeded its time limit. The tool saves the results collected so far and continues with the next check.

Let it continue until “Diagnostic complete”, then send the report even if some checks timed out. A timeout while checking folder permissions does not, by itself, mean access was denied.

If no ZIP was created or File Explorer does not open

If compression fails, the console displays:

Send this report folder to Blinkl support: <folder path>

File Explorer selects the report folder instead. Right-click that folder, compress it to a ZIP using Windows, and send it to support. If that also fails, send support the exact message and the displayed folder path.

If File Explorer does not open automatically, copy the location shown after “Folder containing the report” into its address bar.

If the diagnostic closes unexpectedly or never reaches the completion message, send a screenshot of the last visible step and tell support whether a Blinkl-Diagnostic-… folder was created on your Desktop.

What the diagnostic collects

The report includes available Blinkl and Adobe extension logs, local connection checks, application versions and processes, relevant Windows errors, folder permissions, and Blinkl resource manifests describing installed components.

The tool does not repair the installation, restart your applications or change Windows permissions, firewall settings or Adobe configuration. Nothing is uploaded automatically.

Original logs are copied unchanged. The report may contain local paths, Windows account names and technical session information. Send it privately to blinkl.io support.

Updated on: 09/10/2026