Secunia recently released version 3.0 of the PSI (Personal Software Inspector). It turns out that this application has an SSL conflict similar to that with Windows Update. The difference is that the PSI will start running and then halt and there will be no indication as to why it has stopped or any log entries that reveal the reason. The cause of the halt is that NOD32 with SSL scanning enabled will block the SSL certificate for ps3.secunia.com. If that certificate is excluded in the SSL setup, then the PSI will work fine. There seems to be no other way to get it to work if SSL scanning is enabled in NOD32. I know this to be the case with 220.127.116.11 beta and assume that the same issue will show up with 5.x so long as SSL scanning is enabled. Of course, if SSL scanning is disabled, there will be no problem. That may be what many users will choose to do, at least for now. I wonder how many other new applications will have similar problems with SSL scanning in NOD32? I wonder why there is no notification of blocked certificates when these conflicts happen? I know, one can set the program to ask every time a new site is visited, but that is very inconvenient and should not be necessary for most sites and applications.