Anyone having problems with sbie, KB5027231, and chrome 114.0.5735.134

I can reproduce it in one test VM but not on an other dev vm or the hist really strange: https://github.com/sandboxie-plus/Sandboxie/issues/3040
may be an other factor then only the KB + chrom

 

oh great: https://www.bleepingcomputer.com/ne...breaks-chrome-for-cisco-watchguard-edr-users/ its a MSFT screw up other security software is also affected LOL

 

Making Chrome the default browser instead of Edge might solve this problem. I don't know if this workaround is effective when using the browser with Sandboxie.

Code:

https://answers.microsoft.com/en-us/windows/forum/all/microsoft-windows-kb5027231-update-is-preventing/759e852a-529b-43cc-85dc-fe9571aeb105

 

Well for us turning off would mean not to sandbox something so that's not an option.
But a user noticed that when chrome is default the issue does not happen and some more testing showed that its enough to blocks chrome access to the reg key below fixes the issue:

Code:

ClosedKeyPath=HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Associations\UrlAssociations\http\UserChoice

 

i dont use chrome, but chromium, portable, no issues in windows nor sandboxie, the KB is installed, similar for win10. as a portable chromium do not own any associations.

 

I guess it's good that I delay my quality updates by 30 days

 

and keep your windows vulnerable for 30 days, yeah, great move.
"sandboxie has no quality update)

the problem is not windows or chrome, its the "security" software.
same problem exists for malwarebytes, cisco, maybe eset.

 

Sandboxie without any other security software has this problem as well.
So the problem is the windows update, full stop and yea unless there is an urgent remote exploit bugfix I also let the updates mature before subjecting my systems to them.

 

conclusion: software has to meet the current situation. you cant deny the situation, its on you to find a fix, not microsoft to withdraw its security patch. this patch is urgent! (for over a year now)

you have found a solution for sandboxie, it has reason(s). i dont know why nor can i help you out whatever.

however it is a riddle for me why only chrome is affected and not edge.

 

When Microsoft pushes out a broken patch its on them to fix it, especially when it affects multiple different security solutions.

Also the issue is apparently not related to the actual security patch but to other changes MSFT included in that patch.

 

no developer of an OS is in the need to verify its code against tons of software. and this patch only hitted chrome because of not well programmed third party security software.