I also found out that the SbieCtrl_Username + SBIE2331 errors were mentioned in the old SBIE forum, so it's the same old story. Maybe it should be considered some mechanism to detect on the installer side if a reboot is needed after the install/upgrade process, especially if there is a possibility that could prevent issues like this one.
Sandboxie windows 10 1809 install#
I keep seeing random comments about errors fixed after install with a simple reboot (like in this case). Usually, when I updated the program and choose to overwrite the existing installation, I can use it immediately after, no reboot required. It already happened even before 5.55.4: #1353 (comment) Even if I kill the service, I can't delete this file. The driver file is not unloaded from memory. Then reboot and try installing the newer version again. KmdUtil is located on the main Sandboxie folder. SBIE2331 Service start failed: Access is denied.įailed to record configuration setting SbieCtrl_UserName in section Unknown: C0000080 I cannot install some applications which use the Nullsoft installer. I'm running SandBoxie 5.33.1 - the application says it's the latest available version - no updates found. When I right-clicked on it I get the following message: I'm running Windows 10 LTSC (which is based on Windows 1809) with all updates installed: Microsoft Windows Version 1809 (OS Build 17763.973). Otherwise click Cancel to abort the installation.Īfter I managed to finish the installation, I noticed the icon of the program with an exclamation mark in System Tray. Linux, Android, ChromeOS and other new and old OSs like W7 are probably laughing now like there was no tomorrow.
Sandboxie windows 10 1809 update#
Please make sure that Sandboxie Control is not running, and that no programs are running sandboxed. The worst enemy of Windows 10 is Windows Update System. When I try to install the program (overwrite the existing installation), the setup is stuck to this step Extract: LICENSE.TXT.Ĭannot create or update Sandboxie program files. I tested the new versions (5.55.4-5.55.6) on another machine (Windows 10 Enterprise LTSC version 1809 64-bit) and they are working as usual. I installed version 1809 the day it came out on last October. Personally, I am avoiding it, and if I can do, I will skip it. Four months after it came out, only about 15 of W10 users are using it. First of all, Windis a broken version of Windows 10. The last working version of Sandboxie Classic is 5.55.3. Mr X, I am going to say a few things regarding the post you are linking. I did not changed the Sandboxie.ini configuration file. I have no security software running in the background, except Windows Defender Engine Version: 0.4. I have Windows 10 Enterprise 2015 LTSB 64-bit. Starting with 5.55.4, the program no longer works on my machine. I updated the program (Sandboxie Classic), version after version, since the new development.