Synapse install code error 142 | Razer Insider
Skip to main content
Hi,

Synapse 3 crashed so I needed to reinstall it. I perform a clean uninstall, download the RazerSynapseInstaller_V1.0.131.167 but it always gives me the 142 error even with the firewall disabled.

What did I do wrong?

Thanks



Edit:

Been having the same exact issue for the last week. Please update if you find a solution!
Please indicate your OS version and if you're on a moderated network. If you're on a Windows platform, please check if you have these installed:



- Microsoft Visual C++ 2012 Redistributable (x64) - 11.0.61030

- Microsoft Visual C++ 2012 Redistributable (x86) - 11.0.61030

- Microsoft Visual C++ 2013 Redistributable (x64) - 12.0.30501

- Microsoft Visual C++ 2013 Redistributable (x86) - 12.0.30501

- Microsoft Visual C++ 2017 Redistributable (x64) - 14.13.26020

- Microsoft Visual C++ 2017 Redistributable (x86) - 14.13.26020
I have the same problem, all of the above components were installed, but I reinstalled them. As with a friend above, Synaps was already installed, but hung with the message Failed to start. Error 142 occurred after uninstalling and attempting to reinstall.
I'm running Win10 pro 64 on the Razer Blade 15 advanced from 2019. All those C++ packages are already installed. I'm wired to my internet router with 190Mbps speed.



Razer.Caziel
Please indicate your OS version and if you're on a moderated network. If you're on a Windows platform, please check if you have these installed:



- Microsoft Visual C++ 2012 Redistributable (x64) - 11.0.61030

- Microsoft Visual C++ 2012 Redistributable (x86) - 11.0.61030

- Microsoft Visual C++ 2013 Redistributable (x64) - 12.0.30501

- Microsoft Visual C++ 2013 Redistributable (x86) - 12.0.30501

- Microsoft Visual C++ 2017 Redistributable (x64) - 14.13.26020

- Microsoft Visual C++ 2017 Redistributable (x86) - 14.13.26020
@SHELLeasyOchre516 @xnhn00 Please send me your System and Application logs from the Windows Event Viewer via PM. It would be best that we have our Software Team further isolate the issue. *Locking the thread to curb the conversations to PMs.
CookiesCookie settings