Hi, seems pretty clear to me you have something going on that is causing SB to lock up - probably waiting for control to be returned to it by a Windows API, which may have a similar problem with a device driver, maybe caused by the device temporarily not co-operating. If it's been working OK for 2 weeks, and the software hasn't changed since (which given it is
out of date now, I guess it hasn't), something else seems ot have changed, though it may be just a temporary glitch. Bear in mind that no-one else seems to be reporting such an issue suddenly...
It's also pretty clear that you must have some external process that is repeatedly triggering fresh instances (copies) of SB, although you didn't mention what it is. I'm guessing you have asked SB to set up a (fairly frequent) Schedule(d Task) for you, and IIRC the default* behavior of a
Windows Scheduled Task if an instance of a Task (thus, the process it invokes)
is already running is to
create another (instance/s of the Task). You can edit this setting to other options such as 'Do Nothing', 'Stop current', etc, but this needs to be done directly via the UI of the
Windows Task Scheduler ('WTS') on the Settings tab of the Task.
I'd recommend the following:
- delete or disable the Schedule(d Task) altogether, so that it won't interfere with any following steps
- power-cycle all the equipment involved (you haven't given any details what SB is trying to utilize, but I'd include any external drives, any router/switch involved, obviously the PC, and if in doubt, anything else); this will of course clear your current stalled instances.
- re-start the PC (etc) and immediately update SB to the latest version (use above link in para-1; install 'over the top' of current install to keep profiles & settings). Note that SB must not be running when you do this (if SB starts with Windows, close it). The above suspension of the Schedule(d Task) should prevent WTS trying to open a copy. If you have any other triggers (such as a batch file or script), disable them.
- After upgrade, try running the profile (or group) that was Scheduled manually. If all seems well, re-enable (or re-create) the Schedule(d Task) and see if it still seems to be fixed when run automatically. You may want to take this opportunity to change the 'start another...' behavior of the Scheduled Task if you haven't done so already.
If your problem persists, come back and confirm; it may be 2BS might ask for debug info (which right now, you don't have anyway), but I obviously can't guarantee that, given
the limited support available to freeware users.
* a little bell is ringing that this may differ depending on your version of Windows, but it seems happening to be for you anyway
