Razer Update Manager hanging

[glempert]

I am using Razer Synapse 2.0 to add a second screen; using Lenovo Thinkpad and the monitor is an old Acer.

Works fine but, on startup, I get a small window titled "Razer Update Manager" with instructions of "Do not disconnect any Razer device or shut down your computer until the update is finished". The odometer does not even start to move. I waited 2-3 hours.

Any ideas?

 

[Dogsnake]

Uninstall synapse and do a clean install of the latest version from the Razer site.

 

[jennbrd]

I was trying to get Synapse 2.0 working on my new build, and I ran into an issue. It was hanging at 71%.

I could install Synapse 3.0, but much to my chagrin, my Deathstalker Chroma keyboard was not recognized.

At this point, I had tried everything; remove/reinstall, and I even tried creating tournament drivers (ultimate offline mode). I don't have an ASUS router, I had all firewalls and antivirus disabled, etc.

The updater would hang, every time.


Well, GOOD NEWS!
If you are having trouble getting Synapse 2 updated, here is how I "fixed" it. I opened Sysinternals Process Explorer and killed the regsvr32 process when it appeared under the synapse installation.

Process Explorer shows the updater, and anything that the updater is running, in semi-real time. When the Installation hangs, locate "regsvr32" beneath the updater, right click it, and select "kill".

I don't think we have to worry about a .dll mismatch, because so far everything on my machine is running fine. Besides, once we determine which .dll file is failing to register, and/or whether it is essential to "Emily's update" <grin>, you can run regsvr32 to register the .dll manually.

During the installation, the updater would hang indefinitely 71%. So I fired up Process Explorer and looked at what the updater was actually doing.

100% of the time, it would get to regsvr32, and hang (I had let it sit for 2 hours at one point).

Process Explorer wouldn't let me see the details about which .dll was being registered (access denied), so I "killed" the regsvr process (don't process kill the updater, it wont work lol).

Once that has been done, BE PATIENT. Don't kill any more processes. The remaining installation took a little longer, but it eventually finished, all of my devices are recognized, and my profile is working.

I hope this helps people, because nobody should have be frustrated while trying to get their profiles working after a fresh windows installation.

For what its worth, if my keyboard was seen by Synapse 3.0, I would be using it instead of 2.0.

Cheers
Lonny Bristle