KB# | 1728 |
Title | What files need to be added to an anti-virus exception/white-list? |
URL Name | What-files-need-to-be-added-to-an-anti-virus-exception-white-list |
Summary | Issues such as incomplete installations, installed components failing to start/preform normal functionality and/or Blue-screens (BSOD) can occur if SecureDoc components are scanned/blocked/moved by Anti-virus software. This article contains a complete list of files/directories to be excluded from scans if this occurs. |
Issue:
This article contains a complete list of files/directories to be excluded from anti-virus software scans if issues such as:
- An incomplete installation
Examples: Installer does not start, bootlogon will not install - Installed components failing to start or not preforming normal functionality
Examples: Devices do not communicate with SES and/or password synchronization is denied - Blue-screens (BSODs)
The system will halt with blue-screen accompanied by an explanatory message indicating a memory leak or a page-fault had occurred
Possible Cause:
SecureDoc is designed to not allow reading or modification of it's components such as executables, libraries (DLLs), running services, the boot sector and the internal SDSpace/Metadata. These denials can be interpreted as hostile by security software and can have negative side-effects for the system.
Proposed Solution:
File exceptions
C:\Windows\System32\drivers\sddisk2k.sys
C:\Windows\System32\drivers\sddtoki.sys
C:\Windows\System32\drivers\sddvd.sys
C:\Windows\System32\drivers\sdupc.sys
C:\Windows\System32\drivers\sdvce.sys
C:\Windows\System32\drivers\WMSDFVE.sys
C:\Windows\System32\drivers\PinFile.sys
C:\Program Files\WinMagic\*
C:\Program Files\WinMagic\SecureDoc-NT
MPNotify.exe
SecureDoc_32.exe
SecureDoc_64.exe
SecureDoc_32.msi
SecureDoc_64.msi
SDbat.exe
SDForm.exe
SDPin.exe
SDService.exe
SecurDoc.exe
SecurDocOld.exe
SecurDoc.Wmg
(Note: This list was designed to copied and is based on best-practices from an average installation, paths and directories may be different on target systems)
Additional Exceptions
- The master-boot-record (MBR) of drives that are encrypted with SecureDoc should be exempted from scans if possible
- The disk-partition labeled WMSD should also be excluded from scans. It will not have a drive-letter assigned under a complete SecureDoc installation.
Conclusion:
In the event that the following does not resolve the conflict such as memory leaks and/or Blue-screens occur; please contact WinMagic technical support and be sure to include information such as the SecureDoc and Windows version including Third-party software information.