Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

SEP11 Updates with i32 instead of v5i32?

Created: 20 May 2011 • Updated: 20 May 2011 | 5 comments
This issue has been solved. See solution.

Although the SEP11 product is listed under the v5i32 updater, I can only get it to work using the i32 file on my older Dell PC.  When I update SEP 11.0.6005.562 on an XP Dell Optiplex 755 I have to use the i32, however on an XP Dell Optiplex 780 with SEP 11.0.5002.333 the v5i32 updater is required.  I suspect it is the difference in processor but am not sure.

My concern/question is this:  Is using the i32 updater for Sep11 giving me full coverage? 

Secondarily: Is there someplace where this is explained and I missed it?


Comments 5 CommentsJump to latest comment

Thomas K's picture

Not sure why that is, i32.exe (Rapid Release Definition) is for the older SAV and Norton products. Was this system ever upgraded from SAV?

You should understand that rapid release-quality virus definitions do pose some risks such as the higher potential for false positives.

Moving this thread to the Endpoint Protection forum.

Dann's picture

I just ran a full scan after updating SEP 11 with the 20110520-002-i32 updater with no false positives.  Hmmm...  

I received this system last September from the corporate office (many miles away) and will need to check whether an upgrade was performed.  There is no evidence of that in the logs.  The latest AV updates on it, before I ran the unsuccessful May 18 v5i32 updater were dated sometime last September.

The log.intelligent updater indicates a successful load of the updater, but when reading DLL SAVIUAuth from the registry, there is a Reg Failure: Failed while opening the key from registry.  Return code: 2   SAVIUDeploy also fails returning code: 2.



sandra.g's picture

Both Intelligent Updaters (i32 vs v5i32) apply the same virus definitions. They are not dependent, to the best of my knowledge, on the processor, only the version installed (SAV vs. SEP).

To clarify, the i32 installer is not necessarily delivering Rapid Release definitions: = Certified definitions = Rapid Release definitions

There was an issue similar to what you're experiencing in an earlier build but that was resolved with MR4 MP1a. I'm not aware of any issues subsequent to that.

Intelligent Updater fails to update definitions when using the Version 5 updater.

I suppose it is possible that in the case of an older machine, the operating system has been up and running so long there is file system degradation or incorrect file/registry permission somewhere along the line. Just a thought.


Symantec, Senior Information Developer
Enterprise Security, Mobility, and Management - Endpoint Protection

Don't forget to mark your thread as 'solved' with the answer that best helps you!

Mithun Sanghavi's picture


"Thumbs UP!!!" & I agree to Sandra. 

Just trying to understand, were these older machines updated from SAV to SEP?

Use the v5i32 executable file for 32-bit client installations only if you are using one of the supported products that are listed below. For Symantec Antivirus Corporate Edition 10.x and older clients please use the i32 or x86 packages.

  • Norton AntiVirus 2011 for Windows XP/Vista/7
  • Norton Internet Security 2011 for Windows XP/Vista/7
  • Norton AntiVirus 2010 for Windows XP/Vista/7
  • Norton Internet Security 2010 for Windows XP/Vista/7
  • Norton AntiVirus 2009 for Windows XP Home/XP Pro/Vista
  • Norton Internet Security 2009 for Windows XP Home/XP Pro/Vista
  • Norton AntiVirus 2008 for Windows XP Home/XP Pro/Vista
  • Norton Internet Security 2008 for Windows XP Home/XP Pro/Vista
  • Norton 360 version 5.0 for Windows XP/Vista/7
  • Norton 360 version 4.0 for Windows XP/Vista/7
  • Norton 360 version 3.0 for Windows XP/Vista
  • Norton 360 version 2.0 for Windows XP/Vista
  • Symantec Endpoint Protection 11.0
  • Symantec Endpoint Protection Small Business Edition 12.0

Mithun Sanghavi
Senior Consultant

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

Dann's picture

I am not sure about the history of the XP build or if it had SAV on it before, but I now suspect it did.  That would explain the registry barfing on the 5i32 updater but working with the i32 even though the current product is SEP 11.  If I knew how to flush the registry I would do that and run the correct product, but since the i32 seems to work I will do that for now until I can figure out a permanent solution.  Thanks.