No, I'm not running a scan during setup - I'm not crazy smile

I have SAV install itself during runoncexec... and by the time it gets around to doing the driverpacks finisher, SAV has already updated itself with the latest defs and then catches the driverpack files with it's auto-protect feature.

The working solution is just to unplug the ethernet to these computers during setup.

Is this issue something we could bring to Symantec's attention?  Or more likely the driverpacks files would need to be altered/recompiled?

Thanks.

Scanned the files on another machine, different platform and same results - another screenshot with all the info I can give you:

http://img404.imageshack.us/img404/551/dpacksmf5.jpg

I don't know how Symantec works, but it would seem it's flagging these files as the MSN.FLOODER virus, but their help docs on that virus just say: "MSN.Flooder is a generic name for all malware intended to flood MSN Chat channels."

I understand that it's obviously a false positive and I can set Symantec to ignore it in the future, but as the driverpacks finisher runs unattended-ly as Windows installs itself unattended-ly, there's no chance to setup this ignore rule before Symantec's Auto-Protect flags and deletes them before they ever have a chance to execute....

Thanks for any ideas you may have.

Hi All,

I just stumbled upon DriverPacks a few weeks ago while on my quest for a unified unattended XP install disc and love it!  That said, as of this morning, Symantec Corporate Client (with 5/30 virus defs) has been detecting the various driverpack finisher .exe files as viruses!  I took a screenshot of the info:

http://img442.imageshack.us/img442/5360 … rusqp8.png

I also downloaded a fresh copy of the driverpacks base and extracted these files on a separate machine (with 5/30 defs) and it also finds them infected.  The 5/29 definitions do not catch them.

Any idea what's going on?

Thanks.