Notifications
Clear all

Unify standalone won't start up  

  RSS

rrichard63
(@rrichard63)
Active Member
Joined: 6 months ago
Posts: 8
August 13, 2020 2:59 am  

After replacing my system drive and upgrading from Windows 7 to Windows 10 Professional, I reinstalled and reauthorized Unify. It worked fine for a few days, and now suddenly the standalone version won't start up at all. It appears for a couple of seconds in Task Manager, under "Background Processes" but then disappears entirely. Choosing "run as administrator" doesn't make any difference. Also, uninstalling and reinstalling Unify doesn't make any difference.

Windows Problem Reports (Control Panel -> System and Security 0> Security and Maintenance -> Problem Reports) has an entry for every time Unify failed to start up. Each entry says "Stopped working" and "Report sent". I assume that means "sent to Microsoft" rather than "sent to PluginGuru", so it's essentially useless. Back in Windows 7 I knew how to find a more detailed error log, but I have not yet found that in Windows 10.

The VST3 plugin works fine in Reaper.

I've tried both the 1.1.7 and 1.1.10 versions of Unify. My Windows 10 version is 1909.

What should I try next? Thanks!

 

This topic was modified 4 months ago 2 times by rrichard63

Quote
getdunne
(@getdunne)
Member Admin
Joined: 1 year ago
Posts: 1606
August 13, 2020 4:33 pm  

@rrichard63

Locate the Unify.settings file (see https://pluginguru.net/unify/manual/doku.php?id=files-folders#finding_unify_s_files_on_a_windows_pc ), move it to another folder (e.g. your Windows desktop), and try re-starting Unify.

If Unify starts up OK, you'll need to re-activate using your license key, but this won't affect your activation count. At that point you can simply delete the old Unify.settings file.

If Unify does not start up OK, please zip up the Unify.settings file and send to UnifySupport@PlugInGuru.com, and ask that it be forwarded to me.


ReplyQuote
rrichard63
(@rrichard63)
Active Member
Joined: 6 months ago
Posts: 8
August 13, 2020 6:25 pm  

@getdunne

That worked ... thank you! Just out of curiosity, what might I have done to mess up the old settings file?

 


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 1 year ago
Posts: 1606
August 13, 2020 8:49 pm  

@rrichard63

I'm not sure, but this has happened in a few other cases, including recently with John Lehmkuhl where I had him send me the offending Unify.settings file, but I couldn't see anything wrong with it.

It might perhaps be related to Unify trying to connect to audio/MIDI hardware that has since been disconnected? I'd appreciate any thoughts or experience you have, which may help us track down the cause of this rare issue.


ReplyQuote
rrichard63
(@rrichard63)
Active Member
Joined: 6 months ago
Posts: 8
August 13, 2020 9:03 pm  
Posted by: @getdunne

It might perhaps be related to Unify trying to connect to audio/MIDI hardware that has since been disconnected? I'd appreciate any thoughts or experience you have, which may help us track down the cause of this rare issue.

Is it possible that this can happen when a MIDI device is check marked in Unify's MIDI settings and is still physically present but in use by another program when Unify starts up? I know that Unify behaves appropriately when you try to check mark a MIDI device that is already in use by another program. Asking because I've been constantly reconfiguring MIDI devices in the course of recreating my studio in Windows 10.

This post was modified 4 months ago by rrichard63

ReplyQuote
rrichard63
(@rrichard63)
Active Member
Joined: 6 months ago
Posts: 8
August 13, 2020 9:16 pm  
Posted by: @rrichard63
Posted by: @getdunne

It might perhaps be related to Unify trying to connect to audio/MIDI hardware that has since been disconnected? I'd appreciate any thoughts or experience you have, which may help us track down the cause of this rare issue.

Is it possible that this can happen when a MIDI device is check marked in Unify's MIDI settings and is still physically present but in use by another program when Unify starts up? I know that Unify behaves appropriately when you try to check mark a MIDI device that is already in use by another program. Asking because I've been constantly reconfiguring MIDI devices in the course of recreating my studio in Windows 10.

I just tried this: check marked a MIDI device (one that can't be shared) in Unify, closed Unify, opened a second program using the same device and left it open, then reopened Unify. The device was unchecked again in Unify. This is not a definitive test, because the problem might only happen in the presence of some other circumstance, but Unify passed the test this time.

The only other thing I have done that I can think of is muck around with several Windows services related to file sharing on my local network. I can't see how Unify would care about that. This did not involve anything affecting internet connectivity, which Unify might well care about.

This post was modified 4 months ago 2 times by rrichard63

ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 1 year ago
Posts: 1606
August 13, 2020 11:26 pm  

The only other thing I have done that I can think of is muck around with several Windows services related to file sharing on my local network. I can't see how Unify would care about that. This did not involve anything affecting internet connectivity, which Unify might well care about.

 Unify does not presently attempt to use the internet unless you click the button for online license activation.


ReplyQuote
Share: