Chrome - nacl64.exe, cmd.exe, and bits

[Tridens]

Hi, I'm running the latest version of Chrome sandboxed with SBIE 5.13.5 64-bit on Windows 10 64-bit.

I have Chrome sandboxed and start/run restricted chrome.exe and dllhost.exe. When I start Chrome sandboxed, I'm receiving the following SBIE1308 Start/Run access restrictions:

nacl64.exe
cmd.exe

and also, due to "Drop Rights" setting, SBIE2214 for service "bits".

I've done some scanning of the forums here and don't understand why these programs are attempting to run. Can anyone help me with that, or at least tell me how to go about determining why these programs are being called?

Also curious what is calling dllhost.exe, and if it's safe to add? My guess is that it's related to Windows File/Save dialog box that opens when attempting to download a file.

Thanks for any help.

Craig

[bo.elam]

I am not a Chrome user so I am not familiar with all that is normal to run when constantly using the browser. According to Google search, nacl64.exe is from Chrome and I reckon cmd.exe attempts to run because of something Chrome is doing. So, if I was using Chrome, I would either run Chrome in a non Start Run restricted sandbox or allow those processes to run.

Regarding dllhost. It is safe allowing it to run. You can either allow it in restrictions or ignore the message. Either way its likely you ll be able to continue doing what you doing in the sandbox. To me it sounds like you seeing the dllhost message often, that is because of the way you handle downloads. Because of that, if I was you I would allow dllhost to run.

In some computers its more convenient to not enable Drop rights in sandboxes where you run Chrome. Sounds like yours is one of them. If mine was one of them and I was a Chrome user, I would run Chrome without Drop Rights.

Bo

[Tridens]

Bo,

Thanks so much for taking the time to help me out. I've gone ahead and approved those programs and un-checked Drop Rights. I just hate letting stuff run when I don't know what it is or why a program is calling it. It's the same problem with svchost ... makes it really hard to track down what's running.

Thanks again!

Craig

[bo.elam]

Thanks so much for taking the time to help me out. I've gone ahead and approved those programs and un-checked Drop Rights. I just hate letting stuff run when I don't know what it is or why a program is calling it.

You are welcome, Tridens, I wrote this yesterday at another forum about running Chrome sandboxed:

"About Chrome. If sandboxed Chrome wants to check for updates, let the browser do it. Thats what I would do if I was a Chrome user. If Chrome wants to run nacl64.exe or something else, let it run. People using Sandboxie and Chrome experience issues and get messages when they want a highly restricted sandbox for Chrome. And in some computers you cant do that. If you are going to run Chrome in a sandbox don't try using Sandboxie to block Chrome (IMO, looking from the side, as a non user of Chrome thats really the key) cause its not going to work. And then the user thinks SBIE is the problem when actually he is setting the sandbox wrong ."

Bo