02-04-2012 03:42 AM
By the way, what's the difference between Office scanning and the auto protect feature? Does Norton skip Office files by default? Also, does it detect Macro viruses?
02-04-2012 12:20 PM - last edited on 02-04-2012 12:53 PM by Tim_Lopez
Thanks for your diligence in reviewing, and responding to, complaints here.
Please keep me in the loop when a fix is found. I have WinXPProSP3 and the nuisance problem and can and will work around it but know that I shouldn't have to with these standard products.
02-05-2012 01:51 PM
my PC with Microsoft 7 32 bit + Office 2007 + NIS 12, italian version.
Today 2/5/2012, for contingency reasons, I had to perform a full system restore (from backup 1/29/2012) + launched Liveupdate + enabled Office plugin + restarted the system. At that time, NO problem with Word.
Next I performed a new full system backup + launched again Liveupdate + restarted the system. At THIS time, I got the reported problems with Word.
Then I checked file officeav.dll currently running on PC (with Word problems) against officeav.dll version stored within today system backup (with no problem); timestamps (1/27/2012 3.11 PM) and size (74 KB) are just the same.
Maybe Word problems do not relatate to officeav.dll contents only.
Hope this could help
02-05-2012 06:06 PM
I too am having the "The command cannot be performed because a dialog box is open..." in MS Word 2007 problem on one of my two computers. The computer with the problem is running Windows Vista Home Premium 64bit and Office Pro 2007; the one without the problem is running Windows 7 64 bit Pro and Office 2007 student and home. Got a fix yet?
02-07-2012 10:09 AM
Since 18.104.22.168, I am also experiencing this problem but only on a PC running Vista Ultimate with Office Professional 2003.
I do not have the problem on a PC running XP with Office Standard Edition 2003. Don't know if this offers any clues regarding the cause.
02-08-2012 01:58 PM
Any timeframe in which we can expect a resolution for this VERY ANNOYING problem? Again, disabling a security feature is NOT a solution for this (suggesting this is a "workaround" just makes me very frustrated and trusting symantec less).
What about a rollback from this BUGGY 22.214.171.124? I had to install an antivirus to some clients and I am delaying it because I wanted to install NIS 2012 but I won't with this BUG around (otherwise i will be getting the enraged complaints).
I really hope you are working in a solution for this very soon. Otherwise I will have to switch from NIS for clients.
THIS MAKES ME TRUST NORTON LESS. SUGGESTING TO DISABLE A SECURITY FEATURE INSTEAD OF FIXING THE PROBLEM IS RIDICULOUS AND MAKES ME VERY FRUSTRATED. PLEASE FIX THIS BUG OR ROLLBACK THE BUGGY VERSION ASAP.