I've noticed after the Chrome browser updates that WSA shows "new_chrome.exe", rather than "chrome.exe", under the Application Protection tab. As new_chrome.exe does not exist is the Chrome browser still protected? I think it is OK as I seem to remember reading somewhere that WSA protects based on hash values not filenames (and the padlock does show). Anybody confirm this please?
Yes, and you are correct in your speculation. It protects based on file hash. It only records the first filename it sees for that hash locally, not the current location of the (or all) files that have that hash. So you were 100% correct and you're good to go. ^.^
Thanks for confirming. It is confusing though on first glance, especially when you try to specifically add the application "chrome.exe" and it adds "new_chrome.exe" instead!
