Replies

[Sheldon88]

jabeattyauditor wrote:

Add exceptions for Chrome’s application folder(s) in your SEP policies, then push them out. It’s far from elegant, but it works.

[Application folders – both Program Files and Program Files (x86) – have to watch out for those nasty 32-bit installs.]

It is not that simple, sadly. In an enterprise scenario, the policies are set by a central ICT office and probably they will not change them for a series of reasons: passiveness, indifference, fear, lack of information, different priorities, someone who says ‘no’.

For now, I’m using the “–disable-features=RendererCodeIntegrity” command and I suggested our local ICT to do the same. Someone recommends to use “–no-sandbox”, but I fear it is more intrusive and less secure, as it deactivates the whole sandbox.

I’m just fed up with those Symantec inefficiencies.

• This reply was modified 3 years, 11 months ago by Sheldon88.
• This reply was modified 3 years, 11 months ago by Sheldon88.

Thanks to both of you! I’ll try your solutions to catch the differences.

Just one note: WUMT in Offline Mode uses wsusscn2.cab. It “contains metadata from the following classifications: security updates, update rollups, and service packs”. When I check for updates, WUMT only shows me Security Updates, so it seems good for my purpose, doesn’t it?

-Andrea

I can’t get the point.

So, I deployed KB4099950 to my enterprise computers before April 17, through PDQ Deploy (*not* WSUS). The checksum of the patch is the same, it was only missing pciclearstalecache.exe. What am I supposed to do? Uninstall and redeploy? And should I run pciclearstalecache.exe before/after the .msu or just place it in the same folder?

At the moment, I’m using Simple DNSCrypt to prevent DNS leaks.

https://www.ghacks.net/2018/02/19/encrypt-your-dns-traffic-with-simplednscrypt-for-windows/

That’s because it’s March, I suppose 😀

1 user thanked author for this post.

Cascadian

Did KB4077525 supersede KB4074590 for Win 10 1607? I can’t see KB4074590 anymore.