Wonderfox video convertor security error code 12175

[Neil_Holstein]

Wonderfox HD Video convertor is now showing a security error code 12175 when

I try to open the programm. This seems to be a handshake issue and may be related to their

certificate but i’m also convinced norton is picking this up as an unrecognised cert.

I’ve loaded it on another PC (without Norton) and there is no issue.

Wonderfox have no knowledge of this problem and cannot help

any Suggestions would be welcome

[bjm]

@Neil_Holstein

Wonderfox HD Video convertor is now showing a security error code 12175 when
I try to open the programm. This seems to be a handshake issue and may be related to their
certificate but i’m also convinced norton is picking this up as an unrecognised cert.
I’ve loaded it on another PC (without Norton) and there is no issue.
Wonderfox have no knowledge of this problem and cannot help
any Suggestions would be welcome

Hello @Neil_Holstein
Are you referring to HD Video Converter Factory Pro 28.9?
https://www.videoconverterfactory.com/hd-video-converter/

• Which Norton product and version are you running?
• Which version/build of Windows is on the affected PC?
• Does the error occur immediately when launching WonderFox, or only when checking for updates, downloading, or activating the software?
• What is the exact wording of the error message (or can you post a screenshot)?
• Have you tested with Norton VPN disabled (if installed)?
• Have you temporarily disabled Norton’s protection and then tried launching WonderFox again? If so, did the error persist?
• Is the affected PC fully updated via Windows Update?

Error 12175 tells us that a secure HTTPS connection failed, but it doesn’t by itself identify which component rejected the certificate. The rejection could come from:

• Windows certificate validation
• The application itself (WonderFox)
• Norton’s HTTPS inspection
• A proxy/VPN
• The remote server

The fact that the software works on another PC without Norton makes Norton a reasonable suspect, but it is not proof. The two PCs may also differ in:

• Windows version/build
• Root certificate store
• TLS settings
• Installed updates
• Network path (VPN, DNS, router, ISP)

Error 12175 is generally a secure connection (SSL/TLS certificate) failure. While Norton could be involved, the error itself does not prove Norton is the source of the certificate rejection. Additional details may help determine whether the issue originates with Norton, Windows certificate validation, or WonderFox’s servers.

Error 12175 is a Windows secure connection (SSL/TLS) failure and often indicates a certificate validation problem. Since the application works on another PC, try determining whether Norton is involved by temporarily disabling Norton features such as Safe Web, Intrusion Prevention, Secure VPN, or any HTTPS/encrypted traffic inspection features and then retesting.

Also verify that Windows date/time is correct and that Windows is fully updated, as outdated root certificates can also trigger 12175 errors.

If disabling Norton features does not change the behavior, the issue may lie with WonderFox’s connection to its update/licensing servers or with certificate validation on the affected Windows installation rather than Norton itself.

• Exact error message text (or screenshot).
• Windows version/build.
• Norton product and version.
• Whether the error occurs:
  • at program launch,
  • during update checks,
  • during activation/license validation,
  • or when accessing a specific feature.
• Whether disabling Norton changes the behavior.
• Whether the affected machine uses a VPN, proxy, or HTTPS-filtering software besides Norton.

Can you identify the server WonderFox is trying to contact (sometimes visible in logs or the error details), that would be especially helpful. A 12175 error against a specific hostname often points directly to the certificate or TLS negotiation problem.

AI sourced content may make mistakes
Caveat: I’m not familiar with HD Video Converter Factory Pro

[bjm]

@bjm

Are you referring to HD Video Converter Factory Pro 28.9?
https://www.videoconverterfactory.com/hd-video-converter/

fwiw ~ as test:

WonderFox HD Video Converter Factory Pro 28.9 installed on W11.
The application installed, launched, and successfully performed a manual update check without triggering Error 12175. However, my copy is unregistered, so I did not test license activation or license verification functions.

Does Error 12175 occur before registration, during registration, or after the product is already activated?

HD Video Converter Factory Pro 28.9 installed on W11 running Norton 360. The program installed, launched normally, and a manual update check completed successfully. My copy is unregistered, so I did not test activation/licensing functions.

Error 12175 generally indicates a secure connection (SSL/TLS) failure, but by itself does not identify Norton as the source of the certificate rejection.

Can you provide:

• WonderFox version
• Norton product/version
• Windows version/build
• Whether the main program window opens before the error appears
• The exact text of the error message (or a screenshot)

The phrase “is now showing” implies it previously worked.
If so, What may have changed?

• Norton update?
• WonderFox update?
• Windows update?
• VPN connected?
• New network?

Those timeline clues are often more revealing than the error code itself. Right now, based on your test, I’d be hesitant to support the claim that Norton is simply rejecting a WonderFox certificate. There’s not enough evidence yet, and your test result points the other way.

AI sourced content may make mistakes
Caveat: I’m not familiar with HD Video Converter Factory Pro

[Neil_Holstein]

Many thanks for the suggestions.

I am using the latest version of windows 11 and Wonderfox Video Convertor. I tried disabling Norton 360 but it made

no difference i’m afraid . The vendor says that all certificates are valid and up to date plus they have not heard of any

other instances of this issue so they are stumped. I have checked that windows date and time are correct.

and up to about six weeks ago the programm worked fine and played nice with Norton.

The error msg says “error sending data:(12175) A security error occured” and appears when i open the program

Thanks again

[SoulAsylum]

@Neil_Holstein Check these settings in Norton.

SA

[bjm]

@Neil_Holstein

I tried disabling Norton 360 but it made no difference

What engines/functions did you disable?
Disable Auto-Protect | Smart Firewall does not disable all functions.
Norton 360 utilizes a modular defense architecture, meaning various defensive engines operate independently of Auto-Protect and will continue blocking files, network traffic, or scripts unless explicitly disabled individually.

Disable Auto-Protect | Smart Firewall does not disable:

1. Behavioral Protection
2. Email Protection
3. Block Malicious Scripts
4. Exploit Prevention
5. Ransomware Protection
6. Sandbox
7. WiFi Security
8. Intrusion Prevention
9. Safe Web
10. Download Intelligence

===================================

Did you install any Windows feature updates or cumulative updates around the time the problem started?
Did the error begin suddenly one day, or did it begin immediately after updating WonderFox?

1. WonderFox version changes.
2. Windows updates.
3. Whether the program continues running after the error.
4. Registered vs unregistered status.
5. VPN connected or not.

Quick Troubleshooting for WonderFox 12175 Error

Hi, thanks for the details. A few things to check that often help isolate this kind of TLS/secure connection error:

1. Program Behavior:

• Does the program keep running after the error, or does it close immediately?

2. Registered Copy:

• Is your WonderFox copy registered/activated or unregistered?

3. VPN / Network:

• If you use Norton Secure VPN or another VPN, disconnect it and try again.

4. Windows & Certificates:

• Make sure Windows is fully updated.
• Confirm that your date/time are correct (you already did).
• Sometimes outdated root certificates can cause handshake failures.

5. WonderFox Version:

• Try reinstalling the latest version over your existing install.

6. Error Details:

• If possible, take a screenshot of the error dialog and note any titles or module names.

Following these steps will help pinpoint whether the issue is local (Windows/TLS) or server-side (licensing/update), and rules out Norton as the culprit.

Suggested Diagnostic Steps for WonderFox 12175 Error

1. Confirm Program Behavior

• Does the program continue running after the 12175 error, or does it exit immediately?

2. Check Registered/Unregistered Status

• Is your WonderFox copy registered/activated or unregistered?
• If registered, the licensing server may be the failing endpoint.

3. Verify Windows TLS/Root Certificates

• Ensure Windows is fully updated via Windows Update.
• Open certmgr.msc → check that Trusted Root Certification Authorities contains up-to-date Microsoft roots.
• Optional: Run this PowerShell to check WinHTTP root store:

certutil -generateSSTFromWU roots.sstcertutil -addstore -f root roots.sst

4. Check Network Path

• Are you using VPN or proxy? If yes, disconnect and retry WonderFox.
• Even if Norton Secure VPN is installed, confirm whether it is connected during testing.

5. Check WinHTTP TLS Settings

• Open PowerShell as Admin and run:

reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp"

* Ensure that **TLS 1.2 or 1.3** is enabled.
* Many servers now require TLS 1.2+; older TLS disabled can cause 12175.

6. Optional: Reinstall Latest WonderFox Version

• Backup any settings.
• Uninstall the program → reinstall the latest version.
• Retry startup without activating yet to see if the error occurs.

7. Collect Exact Error Details

• If possible, take a screenshot of the error dialog.
• Note whether the error window title or module name provides clues (update, license, telemetry).

---

Following this checklist will either isolate the problem to:

• Windows/TLS environment
• Licensing/update server connection
• Or confirm that the issue is not related to Norton.

AI sourced content may make mistakes

Edit: I C @SoulAsylum

[bjm]

How to Block WonderFox in Norton 360

1. Open the main Norton 360 dashboard.
2. Click on Settings (the gear icon), then select Firewall.
3. Navigate to the Program Control tab.
4. Scroll through the list of applications to locate HD Video Converter Factory Pro (or VideoConverterFactoryPro.exe).

• If you do not see it in the list, click the Add button, browse to C:\Program Files (x86)\WonderFox Soft\HD Video Converter Factory Pro\, and select the main application file.

5. Change the drop-down menu in the Access column from Auto or Allow to Block.
6. Click Apply, then click OK.

Once this is set, Norton will immediately tell WonderFox that there is no internet connection available the millisecond it opens. The app will skip the broken background security handshake entirely, and the error popup will disappear forever.

AI sourced content may make mistakes

Edit: I C @SoulAsylum

[Neil_Holstein]

Thanks for your suggestion.

I tried disabling all parts of Norton but still no Joy ,

I blocked wonderfox and the error code was changed to 12029 A connection with the server could not be established.

when i allowed the program again then it reverted to the previous error code 12175.

Ive downloaded an alternative program that does the same job so I’m able to resume

what I was doing and just write off Wonderfox.

thanks again for your help

[bjm]

@Neil_Holstein

I tried disabling all parts of Norton but still no Joy ,

I blocked wonderfox and the error code was changed to 12029 A connection with the server could not be established.

when i allowed the program again then it reverted to the previous error code 12175.

The fact that blocking WonderFox changes the error from 12175 to 12029 is actually consistent with what we’d expect:

• 12029 = cannot establish a connection to the server at all.
• 12175 = connection reached the server, but the secure SSL/TLS handshake failed.

In other words:

When blocked, no connection.

When allowed, connection succeeds but certificate/TLS validation fails.

That tends to support the idea that WonderFox is successfully reaching a server and then failing during the HTTPS negotiation.

What I find interesting is that:

• Norton disabled → still 12175.
• WonderFox blocked → 12029.
• WonderFox allowed → 12175.

That makes Norton look less and less like the direct cause.

If I were following the breadcrumbs, I’d now be thinking:

1. WonderFox is contacting a specific server during startup.
2. The connection is reaching that server.
3. The TLS handshake is failing on that machine.
4. The same software works elsewhere.
5. The problem started ~6 weeks ago.

That starts to smell like:

• a certificate chain issue,
• a TLS protocol/cipher mismatch,
• or a machine-specific trust problem.

One question I’d be tempted to ask the OP now:

Does the error occur on a different network?

For example:

• Home Wi-Fi.
• Mobile hotspot.
• Work network.

Because if WonderFox is hitting a CDN, licensing server, or regional endpoint, a network-path difference could be revealing.

Another useful test:

Temporarily disconnect from the internet entirely and launch WonderFox.

If the program immediately throws 12029 (or a similar connection error), that further confirms the startup process is attempting an online connection before or during initialization.

The change from 12175 to 12029 indicates the application is attempting to contact a server when it starts. When blocked, it cannot connect. When allowed, it reaches the server but encounters a secure connection (SSL/TLS) failure. That behavior suggests the issue lies somewhere in the secure connection process rather than Norton simply blocking the application.

That’s a fairly evidence-based conclusion from the information gathered so far.

AI sourced content may make mistakes

[Neil_Holstein]

I connected via a mobile hotspot which norton asked me to accept

on doing this i reconnect via wifi and it connected without any issues.

a very big thank you for your help you are a star,

[bjm]

@Neil_Holstein

I connected via a mobile hotspot which norton asked me to accept
on doing this i reconnect via wifi and it connected without any issues.
a very big thank you for your help you are a star,

Hi @Neil_Holstein

The issue was resolved after connecting through a mobile hotspot, accepting the network in Norton, and then reconnecting to Wi-Fi. No changes were made to WonderFox itself. This suggests the problem may have been related to the local network or networking state on the affected PC rather than a problem with WonderFox certificates or a general Norton compatibility issue.

Regards w Respect