Hi, brokencrow,

...the reason it was done was because it's billable. THE NUMBERS... the numbers are God in today's world.
Sure, but when I was doing that sort of thing, I never had any difficulty in selling the additional time for a test on a "reference machine" and for a contingency plan. If the task was more complex we would do a "proof of concept" exercise.

Was this "senior security analyst" one of your guys or an outsider?

I must say that this is a very weird situation. I can live with SAV perhaps clashing with some applications, particularly on start up, but corrupting video drivers and the looping reboots does sound bizarre.

It is a security product after all, it shouldn't have anything to do with video drivers, which I would have expected to have loaded before the AV? You may well have done this, but I would look at a sample of boxes that work and a sample of those with problems and see if there are any differences in the startup sequences.

The rebooting might be SAV itself? try doing a manual update on one of those, without it connected to the network? see if that solves it. I am guessing that an update of this magnitude requires a reboot, and perhaps it has "gotten all confused"