Best answer by TripleHelixView original
identiy shield question
I fully understand that Internet Explorer, Firefox, Chrome and Opera are the only browsers supported by Firefox. I understand that Edge is not. However if I enter Microsoftedge.exe and Microsoftedgecp.exe into the identity shield Application protection screen in Webroot, even though it makes Edge unusable I see the little gold padlock on the Webroot icon in the task manager, as I do with Firefox, Chrome and Opera. When I put the Vivaldi.exe into the identity protection screen I do not see the little gold padlock. I was under the impression that the gold padlock showed when the executable program was entered into the Webroot identity shield application screen and that program opened. Am I wrong?
Already have an account? Login
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
So, appears I stumbled upon alternate install path.
Starting over with Vivaldi install at default install path.
Edit: adding new pics
Vivaldi is one of those browsers that I have been thinking on and off of trying when I find time (and I have been particularly encouraged by
Thanks for the information.
Unfortunately, from my perspective there is still something amiss...I have tried replicating what you have described...but to no avail. Despite a reinstall of both Vivaldi & WRSA, etc., I am still 'padlockless'...so either what you have described is a fluke or I have an issue somewhere in my system that is preventing something working in the same way as on yours. :(
I will have retry all of this again a few times to see if I can sort it out...but something suggests to me that perhaps there is something hit and miss when it comes to what are termed 'unsupporte' browsers...given what I stated about Iron showing the same 'issue'.
Sorry to hear that what worked for me did not work for you. I fail to see how an “unsupported browser” is an issue. As I stated previously it is my understanding that any .exe file entered in the identity shield screen in WSA should produce a gold padlock when opening that program. This can be demonstrated by entering EDGE, a unsupported browser. Doing so will produce a gold padlock when opening EDGE, however as we know when we do this one cannot type in the address field in Edge. We also know that this is a Microsoft issue. But the gold padlock shows. When I reinstalled WSA I did not keep any previous settings. After the reinstall my identity shield screen in WSA showed NO entries. Before the reinstallation of WSA there were several entries including Firefox, Chrome, Opera, Outlook. Perhaps that is your problem. Let me know.
Appreciate what you are saying but I think that the unsupported browser point may be material in the sense that Webroot will not have tested to the same depth as it does for the 'supported' browsers; be that Filtering Extensions and/or other aspects of WRSA including the Identity Shield.
In most cases the browsers used by many are a 'derivative' of the main supported browsers and therefore are more than likely to 'work', i.e., display the 'padlock'. Even Opera now is a 'derivative' browser as I believe that it used the Chromium engine.
Vivaldi is as far as I know the only serious mainstream contender that is doing its own thing...so to speak...and hence why results may be variable depending on one's system.
Still, I will persevere with Vivaldi and see if I can find out what the issue is in relation to it & the padlock.
Glad to hear that you are going to persevere. I would be very interested in any conclusions that your find. Specifically is this statement true or false: Any .exe program whether browser or otherwise, supported by Webroot or not supported by Webroot when placed in the identity shield screen should produce a gold padlock when opening that file.
As to my specific instance I put the conclusion down to what I have read so many times in this forum, that a clean install of WRSA solves a world of issues. Maybe I’m wrong but please let me know.
Thank you for pointing out the issues with installing Vivaldi in the Appdata folder. I didn’t think of that when I installed it. I am going to back up my Vivaldi profile folder and uninstall/reinstall Vivaldi to my program files folder. Gosh, I love this forum.
You make an excellent point which, having just done a review of exactly where every browser is installed to, would suggest that you are correct as the only one installed in appdata is indeed...Vivaldi.
So I will uninstall & reinstall elsewhere and see what transpires...I suspect that you will be proved correct. Will let you know.;)
Click anywhere in the open browser and the padlock should show and now click somewhere in the taskbar and the padlock will disappear and then click back within the browser and it will reappear which is normal because the protected app must have Focus so when you click in the taskbar it removes the protective Focus until you click within the browser to bring the secure Focus back to the browser or any other program you have added to the ID Shield! 😉
Just want to say thank you for that post. I reinstalled Vivaldi to c:program files. My Vivaldi profile folder is still in AppData exactly where is should be. Thinking about it I feel better this way. When I installed it in c:program files WRSA automatically put it into identity shield with the correct path. When it was installed in AppData I had to put it into identity shield manually. Interesting.
One learns something new every day. Thank you for that info. Just looked and found I did the same thing with Opera when I installed it so I moved it to c:program files also. Again WRSA automatically added it to the identity shield screen. We keep going this thread may never die (lol)
Did a thorough uninstall of Vivaldi using Revo...boy, does it leave a lot of debris behind. :@
Then reinstalled it base don what yo usuggested...and nothing. Left it for a while and still nothinig. Rebooted, tried Vivaldi again...and low & behold...a padlock. So why it needed a reboot I really do not know...but there you go.
So thanks for the tip...that is now sorted.