12-05-2014, 11:46 AM
OK, speculative update...by adding the SIW.EXE to the Microsoft Security Essentials exception list eliminates the app from false detection.
The app is then, of course, not detected therefore and stays open.
After this rename the SIW.exe to something else and the problem returns.
Both siw-x64.exe and siw-Technicians.exe remains unaffected at this time (until MS adds to their db). So the detection trigger is not based soley on naming.
Closing of the app automatically therefore is a MSE action and not releated directly to SIW.exe.
Does not explain why siw.exe is detected as a severe PWS:Win32/Cimuz.gen! intrusion unless the password feature of SIW is the culprit?
Item seems resolved so far.

