ebloch Posted September 30, 2017 Report Share Posted September 30, 2017 Win 7 SP-1 64 bit Immunet 126.96.36.19985 currently but the following applies from earlier versions. I run an unattended overnight batch to do backups and scans for various "bad" actors. On Wednesdays Immunet does the scan but, since there is no command line interface I use a "button pusher" called PTFBpro to do the work. Following is a simplification of my commands: ---- Early in batch --- CALL "C:\Users\...\Documents\Batch Files\_Versions.bat" Y < extracts current version of Immunet (every day) SET "_ICF=C:\Program Files\Immunet\%ImmunetVer%" <_ICF is location of current version --- Wednesday --- SC START ImmunetProtect_%ImmunetVer% > NUL & TIMEOUT 30 > NUL <restart service shut down earlier in batchSTART "" "%_ICF%\iptray.exe" > NUL < opens Immunet GUI so PTFBpro can actSTART "" /WAIT %PTFB% 74F5 < Runs Immunet Full Scan and proceeds after PTFBpro completesImmunet runs the scan. PROBLEM: After the scan Immunet GUI always displays Last Scanned as "Never" and "Not Secure" even though the scan has completed. If I run a Flash Scan that completes in about 32 seconds and reports "Secure"with the proper scan date and time. After a short time (sorry not measured) it again displays Last Scanned as "Never" and "Not Secure". QUESTION: Does Immunet report scan errors to a user or only logs problems in its log without any indication? After scan completion I look at the Clean File History and there are always files there with the correct date and time. Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.