Now, I will say that we have definitely found a reproducible issue and we do now have a fix for this in testing however, due to the ubiquitous and vague nature of this warning, the issue you are seeing may be unrelated to the issue we've found and fixed. Unfortunately, there was a configuration issue that caused this to fail under some circumstances. Without wanting to get into too much technical detail, the issue can occur when Windows Maintenance speculatively runs the Browser's self-repair feature, during routine maintenance, to give it a chance to perform any necessary self-healing.
I want to reassure everyone that the issue we've found isn't serious and has no direct impact on the Browser nor the integrity/security of your system.
We have now identified an issue with the Browser's self-repair mode, which we believe to be the cause of this warning.
AVAST ERROR FOR MACMINER HOW TO
Unfortunately, this particular warning, in the Windows Reliability report, is a bit vague and so it's been a bit tricky for us to figure out how to reliably reproduce it in our testing/engineering environment. I just wanted to provide an update on this issue.įirstly, please let me start by offering my sincere apologies that it's taken us a bit of time to be able to investigate this issue. I'm one of the lead development engineers on the Secure Browser team.
0 kommentar(er)
