G
Guest
I have searched the archive and this error was apparently a problem a year
ago until Microsoft patched Defender. It appears to be back, I look after 200
machines and I am getting it on a number of them (including one of my own
when it usually occurs when scanning the same file C:\Windows\iun6002.exe
which is the uninstaller for the IndigoRose's Setup Factory). Any ideas why
it has returned.
ago until Microsoft patched Defender. It appears to be back, I look after 200
machines and I am getting it on a number of them (including one of my own
when it usually occurs when scanning the same file C:\Windows\iun6002.exe
which is the uninstaller for the IndigoRose's Setup Factory). Any ideas why
it has returned.