Skip to main content
Solved

Office 2016 and Identity protection

  • February 10, 2016
  • 3 replies
  • 33 views

Sheltieuk
New Voice
Forum|alt.badge.img+19
Has anyone who uses Office 2016 noticed the following problem, I normally add all the Office executable files to Identity protection in Webroot. I've just noticed that when there has been an Office update these are all removed from Identity protection and replaced with the paths to the Office update folders which means they are no longer protected. I've just to had to add them all back again, the image below shows what has happened, with the correct paths(just added back) and the ones added after the update.
 

Best answer by DanP

@ wrote:
Has anyone who uses Office 2016 noticed the following problem, I normally add all the Office executable files to Identity protection in Webroot. I've just noticed that when there has been an Office update these are all removed from Identity protection and replaced with the paths to the Office update folders which means they are no longer protected. I've just to had to add them all back again, the image below shows what has happened, with the correct paths(just added back) and the ones added after the update.
 


The protection is not based on the path, it is based on a file hash, so the file will be protected no matter what path it is in. 
 
-Dan

3 replies

RetiredTripleHelix
Gold VIP
Forum|alt.badge.img+56
Hello,
 
This is normal behaviour from WSA as it follows the Hash but it is still protecting the apps listed only a clean reinstall of WSA without importing old settings and setting it up as you like again will correct it. Also ? can explain better than I.
 
HTH,
 
Daniel 😉

DanP
Forum|alt.badge.img+35
  • OpenText Employee
  • Answer
  • February 10, 2016
@ wrote:
Has anyone who uses Office 2016 noticed the following problem, I normally add all the Office executable files to Identity protection in Webroot. I've just noticed that when there has been an Office update these are all removed from Identity protection and replaced with the paths to the Office update folders which means they are no longer protected. I've just to had to add them all back again, the image below shows what has happened, with the correct paths(just added back) and the ones added after the update.
 


The protection is not based on the path, it is based on a file hash, so the file will be protected no matter what path it is in. 
 
-Dan

Sheltieuk
New Voice
Forum|alt.badge.img+19
  • Author
  • New Voice
  • February 10, 2016
? ? Thanks both for the explanation thats put my mind at rest.