Sandboxie causing "An anonymous session connected from [MY COMPUTER NAME] has attempted to open an LSA policy handle ..." on Windows 10

I'm having this exact same error but I'm using Win7 64-bit, Sandboxie v5.30.

All drivers and OS updates are current. I'm using Firefox and Waterfox.

Hi Sam.

Thank you for the update, I'm glad I'm not the only one. Never had such issues on Windows 7 myself, did you have them before installing v5.30?

With all that has been going on with Sandboxie in the last few months I prefer not see such errors which could be interpreted as some sort of Malware infection.

Hi sandboxieuser456 ,

When I inquired about the May windows update, I assumed you just upgraded to Win10 like most people do. I was thinking perhaps some remnants of Win7 might be left over that could be causing the error. However, I just noticed in your original post you mentioned doing a clean install. I was asking because of the KB4499175 update has been problematic with some anti-virus software but this of course wouldn't effect you on a clean install. I use CIS and Comodo is not effected by the update.

The LsaSrv error is caused from running a sever and the only 2 server items I have running is Intel Turbo Booster and Sandboxie. The Intel software is installed on your system and not in the BIOS. The preliminary research is to attempt to find commonalities between our machines.

So far today and yesterday, I have not experienced any errors yet. On Friday, I'm going to update SB to v5.30 and see if the LsaSrv error comes back. Time will tell.

If you have the time, have your thought about doing a fresh install again and run SB at v5.28 to see if the errors happen? The v5.28 was a part of the image and I don't have another copy but maybe Barbara can get a copy for you to test with. Worse case, I do have v5.26 but the other version would offer better results.

Hi Barb,

The thread you mention is an interesting find and it's actually still valid today.

The 2 reply posts are from March 2019 and both are using Sandboxie.

This makes me wonder about May windows update and Sandboxie being a joint issue.

Will know something more in a couple of days. It's difficult to extrapolate anything at this stage of troubleshooting.

Hi Sam.

I don't have Intel Turbo Booster installed.

Unfortunately this is PC #1 of 5 which I have to format so I have no time to clean install to test v5.28 out.

In my case I believe it's a conflict with KIS because with KIS turned off, I get no events.

Hi sandboxieuser456,

I'm glad you found the culprit and hopefully will find its solution.

Hopefully, in a couple of days I'll have a solution too.

Good luck

I just got another LsaSrv error a little over an hour ago. So I know this is not related to v5.30 or the May update.

Now it likely comes down to Intel Turbo Booster Technology or Sandboxie. These are the only "server" software running on my system.

I uninstalled the Intel software and will wait a couple of days to see if the error is generated.

EDIT: I have not updated Sandboxie or windows yet.

Hi Sam.

Do you get them at random or as it's in my case when you load your browser(or another application) in Sandboxie mode?

i have the same issue.

Would you be so kind to provide some details such as Installed Antivirus(if any), OS and version? I see from your other thread that it's Windows 1903, is that correct?

Yes i'm on 1903 version. Installed eset antivirus 12.0 version.

All,

Just to clarify, this is not an "issue". The event is reporting that something was opened as Anonymous Logon - which means Sandboxie is doing its job. (Sandboxie runs applications as anonymous, which means it has the least amounts of privileges, which increases security).

You can reach out the vendor of any of the apps triggering this message to see how they handle anonymous logon runs, and to see if the message can be avoided.
Otherwise, as previously explained (by dev), nothing has changed on the Sandboxie end, the message is not new, and it is not an issue.

Regards,

All,

Just to clarify, this is not an "issue". The event is reporting that something was opened as Anonymous Logon - which means Sandboxie is doing its job. (Sandboxie runs applications as anonymous, which means it has the least amounts of privileges, which increases security).

You can reach out the vendor of any of the apps triggering this message to see how they handle anonymous logon runs, and to see if the message can be avoided.
Otherwise, as previously explained (by dev), nothing has changed on the Sandboxie end, the message is not new, and it is not an issue.

Regards,

Just for your information: It is clearly related to Sandboxie version 5.30 and a sandboxed Firefox. If I install the previous version 5.28, the message never appears. If I reinstall version 5.30, a sandboxed Firefox will trigger this message every day. That's why it's very strange that there were supposedly no changes...

[Windows 10 1803, Sandboxie 5.30, Windows Defender]

I believe Sam encountered the problem with Sandbox v5.28 as well but I stand corrected.

It's also an issue first reported in May 2017(maybe earlier) so it's pre v5.30.

But it's definitely a Sandboxie issue, I find it hard to believe that Kaspersky, Comodo, ESET and Windows Defender all have the same issue.

Hi sandboxieuser456,

You are correct, I did encounter it with v5.28. After uninstalling Intel Turbo Booster I haven't come across it yet but it's still too soon to tell on my machine. If something is going to happen it will tomorrow or the next (going by the pattern on my machine).

This is an odd error because the Turbo and sandboxie has been installed since I first bought the computer and the only one that has been updated is SB.

I haven't had any issues until recently, which would indicate a possibility that a windows update did something to cause sandboxie to trigger the error on Win7 and Win10 machines.

I'm going to go through the windows updates and see if there is anything that could possibly cause this to happen.

Thank you for the update Sam.

On my side I am now taking care of another upgrade + clean install with KIS 2019 installed.

There are two minor differences, the upgrade is to Win 10 32bit v1903 and not v1809. The clean install will be to Win 10 x64 v1809 though (I don't trust v1903 yet).

Here are the results:

Windows 10 v1903, x86, KIS 2019, Firefox default profile: No event logged

Windows 10 v1903, x86, KIS 2019, My backuped up Firefox profile: No event logged

Windows 10 v1809, x64, KIS 2019, My backuped up Firefox profile: Yet to check.

Interesting results sandboxieuser456.

This morning I woke up to the LsaSrv error. There is no doubt that it's sandboxie but I think something else with sandboxie triggers the event.

I reached out to 2 friends and my son a little while ago because they use sandboxie, also. 2 out of the 3 have the event. All 3 use Comodo Internet Security and are on Win10 64-bit (1809 and (2)1903). None run any type of server software. The one that didn't have the event is on the 1809.

I finally upped to v5.30 and will install the May window updates later. This is so mysterious and I have no clue what is causing it.

I hope the Devs figure it out because I really don't know where to go from here. This really needs to be resolved.

Hi Sam.

By any chance, do you have Giorgio Maone's NoScript installed in Firefox?

I noticed a strange behaviour this afternoon on machine #1, the NoScript icon was a gray square box(also outside the Sandbox). I uninstalled and reinstalled the extension and it's now working again with and without Sandboxie.

I'm not entirely sure it's related but as we're in the dark, I preferred to add it to the thread.

I will complete the clean installation of machine #2 tomorrow so I'll have news on that one as well.

Edit: No event logged on machine #1 today, could it be related to NoScript? Will soon have news on machine #2, almost there.

Edit #2: Machine #2 tested, has same issue.

Edit #3: Machine #1 again logging the event this morning, it did not yesterday because it is probably related to "This message will be logged at most once a day."

HI sandboxieuser456 ,

I do use Noscript and have it installed in several sandboxes. I don't see any abnormal behavior with that plugin on my machine. I suspect it's not the problem because it's a "logging-in" issue and NoScript is not run as a server and it doesn't log in. Doesn't hurt to throw things on the table though.

I just rebuilt my drive from the ground up instead of using an image and Win7 and SB are fully patched - (May updates & v5.30, respectively).

Now it's a waiting game... again!

Oh, boy... It's so fun being a techie. 

Hi Sam.

I confirm NoScript was an unlucky coincidence, I will clean install on another machine next week but since I'll install KIS 2019 as it was the case on the other two, I see no reason why it should behave differently.

Hi sandboxieuser456,

I believe I found the issue on my machine - the Intel Turbo Booster. Before the building the new drive, I was using an image that had an older version of the Turbo util. When I rebuilt from scratch I couldn't find the util anywhere and had to download it from ASUS website. I noticed it was a different version.

Currently, I had not had any errors and before the fresh drive build I also had a "side-by-side" event viewer error which means a program is conflicting with C++ runtime libraries. Neither the errors have shown since the Turbo update. Going by previous patterns, if it does happen, it will within the next 24 hours but I suspect the issue has been addressed. The other two people I mentioned who had these errors, also have ASUS with the Turbo installed. It should fix it for them, too.

This however doesn't explain why it was an issue in the first place being SB and the Turbo played well together for years. I think when I uninstalled Turbo and still got the LSASrv error, maybe there was some remnants of the program that didn't get completely uninstalled. Going back to my earlier thinking, I believe ultimately it's related to either a windows update or .net update that changed something that caused these programs to act differently than they normally would.

Did you contact KIS devs about the issue?

Apologies for the late reply, Sam.

Kaspersky asked for a GSI report which I cannot provide as these systems are used by multiple users so I'm basically stuck on square one.

Still everyone fine with your machines after the changes?