Jump to content

Recommended Posts

Posted

i have tight vnc in our xp pro machines. Everytime i approve defnder updates on the wsus server, it removes tight vnc from the allowed softwware list. This means that i am unable to vnc the machines and have to do a visit the machine to allow vnc in windows defender.

 

I have worked out how to configure defender to ignore the path to the tight vnc folder.

 

The key is

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Defender\Scan]

 

it appears as

"ExcludePaths" REG_MULTI_SZ C:\Program Files\Tight

 

However when you export the key it appears as

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Defender\Scan]

 

"ExcludePaths"=hex(7):43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\

00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,54,00,69,00,67,00,68,00,74,00,\

00,00,00,00

 

The problem is that everytime i try and import the key onto another machine i get the message. I have tried ending the process tree for the windows defender application.

 

Examining the registry after carrying this out does not give the required results!

tight.jpg

error.JPG

Posted (edited)

Could you stop windows defender from starting automatically and script it in some way to copy the registry file over first then start windows defender afterwards.

 

I assume its located in HKLM\Software\Microsoft\Windows\CurrentVerson\Run

Edited by tomscaper
Posted
Could you stop windows defender from starting automatically and script it in some way to copy the registry file over first then start windows defender afterwards.

 

I assume its located in HKLM\Software\Microsoft\Windows\CurrentVerson\Run

 

 

i will give it a go. thanks!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...