While upgrading through the 3.33 betas on my Vista systems, I have seen at least three instances of the install hanging with something like an "unable to stop the SbieSvc service" popup. As a workaround, I now stop the SbieSvc service manually (after shutting down SBIE Control) before upgrading to the next build. However, stopping the service manually sometimes leads to timeout errors as well...

Log Name: System
Source: Service Control Manager
Date: 12/24/2008 9:14:38 PM
Event ID: 7011
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Q9450
Description:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SbieSvc service.

Despite the timeout errors, I am always able to proceed once services.exe eventually terminates sbiesvc.exe.

Just saw another instance while upgrading to 3.33.12 from 3.33.11 on my Vista laptop. I had not shut down SbieSvc manually, hence the installer's KmdUtil popup...

Cannot stop the service at this time.
The service 'SbieSvc' is busy.

Please click OK to retry.

This is the first of three retries.

The next popup asks whether I want to retry or abort...

Cannot create or update Sandboxie program files.

Please make sure that Sandboxie Control is not running,
and that no programs are running sandboxed.

Then click OK to retry the installation.

Otherwise click Cancel to abort the installation.

I click OK to retry. By now the SbieSvc service has shut down and the install completes successfully.

OK, I'll try to reproduce these hangs.

I've had this happen as well. I always just kill SbieSvc with "taskkill /f" before running the update.

I use "taskkill /f" because I've had the hangs using both "sc stop" and "kmdutil stop". This has happened on both XP and Vista for as long as I've been using Sandboxie. It seems to be pretty random and nothing I can reproduce with any certainty. It's no big deal to me, so I just kill it first.

Are you guys using a secure delete that maybe isn't finished?

Nope. Totally empty sandbox.

I know this or similar behavior too, would say in 2 or 3 of 5 updates.

Before an update I close the last running sandboxed application, wait some seconds and close Sandboxie Control too.

Wow! 2-3 out of 5 is like 50%. There has to be security products involved or something. I can honestly say that the only time that has ever happened here was once - and it was my fault. You know when you install Sandboxie there are two times back to back for the button "next", once I went too fast and click-clicked the "next"......

There were cases where I had to uninstall SBIE after an update because the update was broken - new and old filed mixed, some files removed, error messages after an system restart...

Every time I start an update it's a "Hope that it works this time" feeling SBIE is one of the few applications I don't like to update.
Ok, if it went wrong, I just uninstall it and reinstall the new version. One way, but not the best

Hmm. I have always used the upgrade option. I always put my other software (OA and SSM) in learning mode first) Has never failed.

Pete

Pete are you on Vista? The hangs described here typically occur on Vista. I already tried to do something about it earlier in this beta cycle, but I guess it wasn't enough, so I will revisit the issue.

The SbieSvc hang may also be the cause of the random slow shutdowns I have noticed on Vista since installing Sandboxie. My Vista systems normally shut down in 5-6 seconds. Randomly, I see shut down times of about 25 seconds. The lag occurs during Vista's "Shutting down..." status message. The lag is equivalent to the random hang time it sometimes takes for the SbieSvc service to shut down...~20 seconds.

In regards to security software, the only other thing I run is NOD32, and I always disable it before running the Sandboxie upgrade. And I've had this hang on both XP and Vista (same security software setup).

Hi Tzuk

No, I am on old and stody(but it sure works ) XP Pro.

Pete

I've seen that behavior upon Upgrading SBIE on Vista SP1 where I keep getting an error that the service was still active yet there was nothing running SBIE related. I did an uninstall\reinstall and just reloaded my saved sandboxie.ini file.

dja2k