See this article for the effects of enabling this feature in either a Local Security Policy or Group Policy: http://support.microsoft.com/kb/811833. Another article on the topic: http://technet2.microsoft.com/windowsserve...3.mspx?mfr=true At the second article, here is a quote from that site: 'FIPS 140-1 validated software is required by the U.S. Government and requested by other prominent institutions.' The feature basically enforces FIPS 140-1 compliance for hashing algorithms among other things. FIPS 140-1 Compliant, Transport Layer Security (TLS) 1.0 protocol, is stronger than Secure Socket Layer for encrypting communications. SSL3 uses the MD5 hashing algorithm (an algorithm that is not FIPS compliant), users whose local security policy forces the use of only FIPS compliant algorithms would experience the error. Information about the FIPS 140-1 validation program can be obtained from the National Institute of Standards and Technology, Computer Systems Laboratory, Gaithersburg, MD 20899. I've never encountered an error with any other program I've used since enabling the feature. The standard has been around for over a decade. Being as this is freeware, it may be a bit much to expect FIPS compliancy. Thank you for your consideration.