We've got several reports that Chrome crashes appear immediately after upgrade to Client Security Premium 12.30.
The workaround for this issue is not to launch Chrome browser immediately after restart of upgraded machine, and wait until Network Interception Framework update will be installed.
Meanwhile, we are currently preparing CS 12.31 maintenance release, which will have the fix in the package, and will be free of such issue.
> Meanwhile, we are currently preparing CS 12.31 maintenance release, which will have the fix in the package
Thanks for the info! However, we wish to inquire about ETA for such a maintenance release?
Thanks in advance, Yours Sincerely:
Tamas Feher, 2F 2000 Kft., Budapest, Hungary.
Unfortunately, the initial idea with including fixed NIF binaries in CS 12.31 installation package doesn't help to avoid the Browser Plugin crash after upgrade. 40% of our Beta group were affected, and the workaround is one more restart of the machine. Because of that CS 12.31 release was postponed. Now we are investigating what else could be done to improve the situation.
Many of our users keep the Chrome installer on their Desktop so that they can simply reinstall Chrome every time this happens. Fortunately this doesn't cause them to lose their bookmarks etc.
However, it's been an annoyance now for 6+ months.
Above you reference contacting support for manual steps to fix this. Why not post the steps here to save myself and others the 2-day wait for a reply (as is my experience with uncleaned virus submissions).
When your software is breaking the world's most popular browser on your users' PCs, and has been doing so for 6+ months, that is a serious issue that should be getting a lot of your attention. This thread is about the only resource available regarding this.
Thanks for your time.
Short status update. Latest version 5 of PSB Workstation Security 12.01 contains fixed Chrome Browsing Protection extension installation procedure, which should eliminate the crashes after PSB product clean install.
Unfortunately, until now, we failed to find out how our product could affect random Chrome crashes happening after Windows 10 update/restart. Our tests show random crashes of F-Secure Browsing Protection extension, as well as crashes of other 3-rd party extensions, or just grayed browser window without mentioning any extension crash.
Google search shows, that Chrome crashes on Windows 10 start-up happen without F-Secure product onboard as well. For example: https://productforums.google.com/forum/#!topic/chrome/9BVg6Wa6DEU
We will continue investigation, and comment here as soon as we'll have any update.
Installed F-Secure 12.31 on two machines last night, both had the Chrome crashes today. We have been running Windows 10 all year with no issues until the F-Secure installs. I have been having this issue intermittently on my machine and another in my office for last two months or so. It will go two weeks with no issues then do this two days in a row.
Windows 10 1703 on two machines and 1511 on the other two.
I have few clarification questions, if i may.
1. Do you have Client Security 12.31 Standard or Premium?
2. If you have Premium version, did you have any other 3-rd party Chrome extensions on your machines (those, which didn't crash for a year), before you install our product?
Thanks in advance,
1. Client Security 12.31 Premium
2. I have several on my machine. One account that we tested with had none. One was a fresh profiles on that machines. Not even sure he had ever logged in. It was an administrative account, so he travels to different machines, but doesn't log into Chrome or install extensions. The other was a teacher, but not sure how many extensions she had.
This topic has been closed due to inactivity. If you would like to discuss this topic further, please start a new post.
You can reference this topic in your post by adding this link:
Visit the Community
Check our Forums or How-to & FAQs for advice or answers
View User Guides
Refer to our getting started guides and product manuals
Talk to our Support and get answers to your questions