BITS Client Error 0x80070005 when Chrome in Sandboxie [SOLVED]

[iceberg]

Hello all!

(1) Windows 10
(2) Sandboxie 5.20
(3) Chrome Versions 50 and later in Sandboxie, some chrome extensions

(1) + (2) + (3) -> after some minutes the BITS Client Error 0x80070005 is rising up in the event log.

(2) + (3) but with Windows 7 instaed of 10 -> no error

Someone out there with the same experience? Any ideas?

**********************

[Barb@Invincea]

Hello iceberg,

What are the extensions installed?
Are you using windows x64 or x86? Is there any security software installed?
What actions are you performing when the error occurs?
Which log are you looking at, exactly?
Does the issue happen in a new Sandbox with default settings?

Regards,
Barb.-

[iceberg]

Hi Barb!

Thank you for the quick reply.

Yes, I use some 3rd party extensions (AdBlock, Ghostery) but I got this error also without these extensions.
I get this only under Windows 10 64bit. Currently it's Creators Update, but it happened also versions before. I share the same Chrome installation with Windows 7 Pro 64bit without any errors. Security software only the Defender, which comes with Windows 10, nothing more.

The error (BITS Client Error 0x80070005) is logged in the standard windows event log, nothing special.

The error comes several minutes after starting chrome the first time with empty sandbox, independent from what I am currently browsing. And the error comes 6 times within 2 minutes.

From my perspective Chrome is trying to setup Windows BITS service for some kind of background download and this fails due to rights problems.

Regards,
ICB

[Barb@Invincea]

Hello iceberg,

Are you using drop rights? Please have a look at this thread:
viewtopic.php?f=17&t=24734

Is this error preventing you from doing anything with Chrome ? Sometimes, there are errors showing up in the event log, but they do not mean much. Is functionality affected in any way?

Regards,
Barb.-

[iceberg]

Sorry for the late reply.

No, I am not using drop rights. And I don't think this error prevents me from doing anything with Chrome. It seems that Chrome works well with Sandboxie. But, as written previously, it seems that Chrome tries and has not the permission to setup one or more background transfer jobs to Windows BITS service. And I see this error only under Windows 10, always after several running Chrome in Sandboxie, even if I do nothing in Chrome.

Same configuration, same settings for Chrome and Sandboxie under Windows 7 -> no error.

Same configuration, same settings for Chrome, but starting Chrome outside the sandbox -> no error.

Regards,
ICB

[Barb@Invincea]

Hello iceberg,

If functionality is not affected, then you should be able to ignore the message.
I will reach out to the devs to see if they can provide more info and update this thread if/when anything new comes up.

Here's more info regarding BITS and Google apps:
https://www.sandboxie.com/ServicePrograms

Regards,
Barb.-

------------------------------X ----------------------------
UPDATE, I triggered a manual update of Chrome inside Sandboxie (which is supposed to fail by default), and got this in Google Chrome:

The BITS service failed to start. Error 0x80070005.
An error occurred while checking for updates: Update check failed to start (error code 4: 0x80077005 - system level)

Right after that, I saw the logs in the Event Viewer, so the errors are expected to be there since Sandboxie will not allow Chrome to update.

[iceberg]

Yes, this makes sense and I expected something like that.

So it's all ok for me. Thank you for your support.

It would be nice, but not necessary, to understand why I don't have this error logged in Windows 7 (same chrome and sandboxie settings).

Regards,
ICE

[Barb@Invincea]

Hi iceberg ,

I think under Windows 7, you can find more info under:
Event Viewer ---> Applications and Services Logs ---> Microsoft---> Windows ---> Bits-Client ---> Operational

Regards,
Barb.-

[iceberg]

Now I found the difference between my Windows 10 and my Windows 7 installation and the reason why BITS Error 0x80070005 was only logged in Windows 7.

You are right, calling BITS client inside Sandboxie is supposed to fail by default. I can see this in my Windows 10 installation.

I testet this by opening CMD in sandboxie and calling "bitsadmin /list". Windows 7: no errors !!! Windows 10: BITS Error 0x80070005 logged in the event log.

So under Windows 7 I have access to BITS client even when running in sandboxie. And there I see that the chrome component updater is using BITS, which causes this BITS Error 0x80070005 in my Windows 10 installation when opening chrome in sandboxie.

The remaining question is: Why can I access the BITS client from inside sandboxie? I am not aware to have changed something from defaults in the sandboxie configuration on Windows 7. I always aim to synchronize seetings between Windows 7 and Windows 10 installation. But I guess there is something which can be configured to allow/disallow access to BITS client from inside sandboxie. Right?

[Barb@Invincea]

Hello iceberg,

I get the same error in Chrome if I try to update it inside Sandboxie in Windows 7.
I am not sure why it is not logged the same in Windows 7. If you want to see the BITS logs, check my previous post and you'll be able to find them as "Information" under the Operational Logs.
The code I see is 0x0 instead (Windows 7)

Regards,
Barb.-

[iceberg]

Thanks again for the fast response.

It's not a Chrome issue. It's a question of BITS and sandboxie and I can reproduce it very simple:

As described, open a command prompt in sandboxie and type "bitsadmin /list". This lists the status of current bits jobs. For that the bits service gets triggered by bitsadmin.

Under Windows 7 I see with a process monitor that sandboxiebits get launched after calling "bitsadmin /list". Under Windows 10 nothing.

I don't have any idea why sandboxie does not block BITS under Windows 7 installation. But it does under Windows 10 installation.

Even a complete deinstallation (with deleting seetings) followed by a fresh installation of sandboxie 5.20 did not change the behaviour.

Regards,
ICE

[iceberg]

PS:

Under Windows 7 "bitsadmin /list" in sandboxie runs without error, ending in "Listed 0 job(s)." The same output like without sandboxie.
Under Windows 10 "bitsadmin /list" in sandboxie runs in "Unable to connect to BITS - 0x8007042d".
The settings for drop rights are disabled as they are for default. If I configure drop right in sandboxie settings, then I get 0x80070005 instead of 0x8007042d.

Under Windows 7 I see with a process monitor that SandboxieBITS.exe gets launched after calling "bitsadmin /list". Under Windows 10 it seems that SandboxieBITS.exe gets launched and directly terminates.

So I wonder what the intended behaviour is. Is it this what I get under Windows 10 or this what I get under Windows 7 ? And if BITS is blocked by design, then I don't understand the purpose of SandboxieBITS.

I don't care about the chrome component updater which gets blocked under Windows 10. But if I wonder if I have some kind of misconfiguration in the Windows 7 installation, which opens the door for file access via background download.

Regards,
ICE

[iceberg]

Hello again,

still waiting for an answer. I reduce my question to the following:

Open a command prompt window (simply Windows cmd) in sandboxie and call "bitsadmin /list". Is it expected to run without error or not? Is there a difference between Windows 10 and Windows 7?

Regards,
ICB

[Barb@Invincea]

Hello iceberg,

As far as I can tell, Chrome update was blocked as expected, and BITS is working correctly, per this:
https://www.sandboxie.com/ServicePrograms#bits
The inconsistency is that Windows 7 is not reporting the blocked Chrome update as an error, but as an "Information" entry under the logs mentioned before, but Windows 10 is. It might be the way those OSs handle the events, however I am not 100% sure.

I reached out to the devs but haven't received an answer yet. Once they reply, I will update this thread.

Regards,
Barb.-

[iceberg]

Please don't see it as chrome issue. It's an issue with BITS service and it can be reproduced simple without chrome.

In the meantime I went some steps further reproducing this. I did a total clean install of windows 7 professional SP1, with clean install of sandboxie 5.20, all settings at default, wrote a litte .BAT file (see below), which does steps by step a download of a file from a mircosoft server via BITS service to the temp or download directory of the users profile. Please forward this to the developers. You can see that the download via BITS service works inside a sandboxie window without erros and it really does the download! No blocking. But from my perspective it's ok that it works. The downloaded file gets stored only under the sandbox directory.

Under clean install of Windows 10 Professional (1703) all the commands of this .BAT file get blocked.

Regards,
ICB

Here is the .BAT file:

Code: Select all

@ECHO OFF
SETLOCAL
SET AskForNextStep=Next Step:
SET Source=http://go.microsoft.com/fwlink/?LinkID=18922
rem SET DownloadPath=%USERPROFILE%\Downloads\MSSecure.cab
SET DownloadPath=%TEMP%\MSSecure.cab
ECHO.
ECHO %AskForNextStep% sc query bits
PAUSE
sc query bits
ECHO.
ECHO %AskForNextStep% Bitsadmin /list
PAUSE
Bitsadmin /list
ECHO.
ECHO %AskForNextStep% Bitsadmin /create /download bitstest
PAUSE
Bitsadmin /create /download bitstest
ECHO.
ECHO %AskForNextStep% Bitsadmin /list
PAUSE
Bitsadmin /list
ECHO.
ECHO %AskForNextStep% Bitsadmin /addfile bitstest %Source% %DownloadPath%
PAUSE
Bitsadmin /addfile bitstest %Source% %DownloadPath%
ECHO.
ECHO %AskForNextStep% Bitsadmin /setproxysettings bitstest preconfig
PAUSE
Bitsadmin /setproxysettings bitstest preconfig
ECHO.
ECHO %AskForNextStep% Bitsadmin /info bitstest /verbose
PAUSE
Bitsadmin /info bitstest /verbose
ECHO.
ECHO %AskForNextStep% Bitsadmin /resume bitstest
PAUSE
Bitsadmin /resume bitstest
ECHO.
ECHO %AskForNextStep% Bitsadmin /info bitstest /verbose
PAUSE
Bitsadmin /info bitstest /verbose
ECHO.
ECHO %AskForNextStep% Bitsadmin /complete bitstest
PAUSE
Bitsadmin /complete bitstest
ECHO.
ECHO That's all!
PAUSE
ENDLOCAL