First off, a big thanks to the ClamWin (and Clam AV) teams for their excellent software. It's great to have a go-to antivirus application I can recommend to anyone without reservation.

I'm not sure when exactly ClamWin started relying on the ComSpec environment variable, but this does not work for a number of users. Particularly, many people who enjoy the benefits of open source software may also be using Cygwin to emulate a POSIX environment. Of those people, I think a good deal of them may be employing a custom ComSpec environment variable so their system always uses their preferred shell when opening terminal windows (I have mine set to use the tcsh shell from my Cygwin installation [because it is the most similar shell to those I use on my BSD and Linux systems], but there are many others out there).

However, if your shell isn't the stock Windows shell, ClamWin refuses to update or scan (probably due to the path re-routing that the Cygwin shells do).

I think it would be a fantastic addition to ClamWin to be able to specify a custom path to the shell application using the ClamWin.conf file. This way, it would be unobtrusive to everyone who benefits from its current behavior, and those who need Windows to use a different shell for everything else can still have that option.

Thank you for your time.