Hi all. I’m one of the lead development engineers on the Secure Browser team. I just wanted to provide an update on this issue.
Firstly, 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. 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.
We have now identified an issue with the Browser’s self-repair mode, which we believe to be the cause of this warning. 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.
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. Unfortunately, there was a configuration issue that caused this to fail under some circumstances.
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. Put simply, there are several different reasons why Windows might report this warning and not all of them are within our control. We hope that the issue we’ve found and fixed will resolve this matter for a majority (if not all) of our users.
As I alluded, we are currently testing this fix and it may be a while before we’ve qualified it for general release. All code changes have to go through a thorough QA process and so I am not yet able to say exactly when we will be releasing an update. It is my sincere hope that we’ll be able to get it released soon. Once we’re in a position to provide more information on when this fix will be available, we will provide a further update.
I’d like to thank everyone who contributed information to this thread to try and help us identify and fix the problem. Again, I can only apologise that it’s taken us a while to track this down and I can only hope that the issue we’ve found and fixed serves to resolve this problem for all of our uses.
We will, of course, welcome feedback once the fix has been released and we will do our best to work with our users and the community to try and put this issue to bed once and for all.
Best regards.