This post is about the latest 16.5 update of NIS/NAV.
For me the 16.5 version is working superb without any problem.......but if you are facing any problem ,
please post all of them here , plus you can share your comments on how is the update for you .
Please post any problems here so that intelligent members of the forum (not me) and the Symantec Employees
don't have to wander through various posts to solve problems.
The NIS 16.5 update was downloaded and installed without any issues on my system. However, they need to fix two problems that accompanied this patch:
I wonder -- take that literally -- if the automatic disabling (which I assume can be reversed) of Defender is a precaution against Microsoft extending it into active AV, which I've heard talk about (Morro?) in which case there could be a conflict.
In this case from my POV it is better to disable it so that if people do re-enable it then they see and can associate any problem that may arise.
Just my 2¢ ....
I have the 16.5 updates on two machines without any problems at all. Both XP Home sp3. I have no right click issues and I uninstalled Windows Defender by preference years ago. I personally believe that Microsoft would be better off perfecting their operating systems instead of dabbling in security, which apparently they know nothing about.
I also have Windows XP Home SP3. Before I disabled the shell extension for the context menu (NavShExt.dll), both Windows Explorer and PowerDesk would crash at offset 0000cffd in kernel32.dll whenever I right-clicked a filename. I posted a method for disabling the shell extension in a couple of threads about right-click problems, so I won’t repeat it here.
Hi All,
Here are my experiences with NIS 2009.
I've been using the 2009 version for a few months now on Windows XP Pro SP3. Not sure when I upgraded from NIS 2008 (using a clean install method), but the experience has been great up until recently.
On March 3rd or 4th, 2009, NIS upgraded to 16.5, which I believe was probably the .134 version? It was fine when I turned the PC on March 4th. I opened My Computer to copy a file, and got a STOP (BSOD) error saying "Bad Pool Header":
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 3/4/2009
Time: 11:05:10 AM
User: N/A
Computer: xxxxxxxx
Description:
Error code 00000019, parameter1 00000020, parameter2 86c1c730, parameter3 86c1c748, parameter4 1a030001.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 31 0000001
0020: 39 20 20 50 61 72 61 6d 9 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 32 30 2c 20 000020,
0038: 38 36 63 31 63 37 33 30 86c1c730
0040: 2c 20 38 36 63 31 63 37 , 86c1c7
0048: 34 38 2c 20 31 61 30 33 48, 1a03
0050: 30 30 30 31 0001
Figuring it was just a glitch, I restarted my PC and went to a client's office to do some work. I connected remotely to my home PC. As soon as I tried to open Windows Explorer again, the connection dropped. When I got home later in the day, I noted the same STOP error (parameters 2 and 3 were different). I knew that I hadn't changed any hardware / software, so I suspected it was due to an automatic update. I noted that in IE there was a new Norton toolbar, and there were Norton site ratings next to Google links, so I figured the NIS update must be the cause. I called Norton Tech Support, and they gave me all kinds of possible reasons, none of them being the NIS update. They uninstalled NIS 2009, and the problem stopped. They reinstalled NIS 2009, and it was working fine, but I noted it was not updated to 16.5. They suggested it was because of a corrupted / failed update, which I was willing to accept then.
Everything was fine until Thursday (March 19th). Once again, I started to get the same STOP errors. I noted, once again, the Norton toolbar in IE had updated and the Google site ratings were back, although this time without the "SafeSearch" feature in the toolbar. I called Norton Tech Support again, and they gave me more possible reasons, suggesting it was not NIS that was causing the problem. I clearly explained how this problem only started after the NIS update. After extensive troubleshooting, we determined that it was a conflict between NIS and something else installed on my PC. After offering to downgrade to NIS 2008 (which I declined), they said they would have to have a "senior support tech" call within 24 hours to figure out what the conflict was. I spent the next couple of hours troubleshooting on my own, and determined two issues (which I haven't seen posted here yet):
1. The STOP errors were caused by a conflict between NIS 2009 (16.5.0.134/5) and Sonic DLA. The offending culprit was tfswctrl.exe, which would run on startup from C:\WINDOWS\system32\dla\tfswctrl.exe. It's possible this was an outdated program, since it came with my Dell over 3 years ago. I don't use DLA, so I simply uninstalled it. No more STOP errors.
2. Once the PC was stable again, I noticed that there was excessive HD access approx. once per minute. The HD light would flicker (and the HD would make a louder than normal read / write noise) about 20 times consecutively, then resume normal activity. As this was happening constantly, I knew this must be another issue with the new 16.5 update. I used Process Monitor to isolate what was going on. It seemed that HPBPRO.exe was being called for some reason, and then NIS would make all kinds of disk activity, which was probably what I was seeing. I solved this (temporarily) by disabling the two HP Toolbox startup items (StatusClient and hpbpsttp) using msconfig. I have a HP LaserJet 1320. I don't use it much, and from what I can tell, these Toolbox items are not essential -- they just keep tabs on the printer and allow you to adjust some settings if necessary. I've seen other postings (on other sites) about all kinds of problems with StatusClient, and they recommend removing it and installing a newer HP utility called HP Easy Printer Care. Not sure if this would fix the NIS 2009 issue as well. Can someone please confirm / advise what should be done with this?
Best Wishes,
Kurosh
Over the last couple of days, my XP/Pro Service Pack 3 & NIS 2009 system has been booting to a BSoD similar to Kurosh's.
I uninstalled NIS and everything was OK. Reinstalled NIS, ran Live Update, and got BSoD.
Uninstalled NIS and everything was OK. Reinstalled NIS, ran a system scan, and got BSoD.
I use Sonic BackupMyPC routinely, so uninstalling that product, which has not changed, is not an acceptable option.
Need help.
Thanks,
Paul
In accordance with the post by delphinium above and a post by michael_shavell on the Dogbert thread (i. e., that Windows XP Home SP3 has no problem and the problem is a PowerDesk bug), I now no longer have a problem. I went to avanquest.com, got the fix for the PowerDesk shell extension, applied it and re-enabled the NavShExt.dll shell extension with ShellExView. Voila! No more crashes!
Of course, there's still a problem on Vista, apparently. The interesting thing to me is that the NIS/NAV upgrade uncovered the PowerDesk bug.
I’m glad that worked for you.
Ever since the update, my NIS 2009 liveupdate has been unable to connect to the servers. I don't have any settings for a proxy server, so I don't know what to do other than waiting. Per a symantec employee:
The LiveUpdate engine was updated with the release of NAV/NIS 16.5 and Norton 360 v3. The new version of LiveUpdate engine will check if it receives HTTP 1.1 server responses, and explicitly reject HTTP 1.0 server responses. This was done to ensure that you are receiving updates from a valid LiveUpdate server. If you are using a proxy server, it could be configured to return HTTP 1.0 responses, and thus LiveUpdate will see this as an improperly configured connection.
A workaround for this issue is to disable the proxy server, or to reconfigure it. Most proxy servers can be configured to return HTTP 1.0 or 1.1 responses. We understand that this may not be possible for some users that are experiencing this issue. We are still working on a good solution for this issue. Thanks for your patience.
gkward
How do you connect to the internet? Do you have a router or other hardware device that has an internal firewall? If so please disable firewall and try again and advise.
Week ago I just did a clean reinstall of windows xp pro and I noticed over night after the 16.5 update this weekend. my scans are a bit weird. If I set Performance Profile to full scan. it doesn't fully scan as many files as it did pre 16.5. 400,000 files. now it says 250,000 files. If I do a smart scan it does the same number and if I do a high trusted scan it does 83,508. I like to do the full scan no matter what time it says it saves me. smart scan doesn't seem to skip many files 12 it says.
anyone noticing anything like that, lower or higher scanning numbers of files?
jarrycanada,
Do you get to see anything in the skipped files section in the scan results window? If there is nothing that shows up in it, I think you can confirm that NIS did not skip anything. However, that does not answer as to why the number of files in question were lesser compared to pre 16.5 scaning.
What I'm suggesting may provide one more layer of confirmation that we can have on your claim.
MbR
I have had a number of problems since 16.5 update.
1. Right context menu has been corrupted and doesn't have proper vista appearance anymore.
2. Defender was stopped running despite it not having any conflict with NIS.
3. Constant startup and shutdown errors in Event Viewer dating only from 20/03/2009 the first boot since 16.5 update. No such warnings or errors prior to this and nothing else has changed on system.
4. On first boot after update my laptop couldn't connect to BT Homehub, first time this has happened since I got computer October 2008. Solved by switching hub off and back on.
5. Since update, possibly connected to startup errors, I have an intermittent problem with IDT Audio speaker not appearing on Task Bar after boot up. Again something I haven't seen at all prior to update.
To check that these are indeed all related to NIS update 16.5 I used an image to go back to set up as at 19/03/2009.
This sorted all the problems but they reapppeared following reboot after automatic update ?!
Nope, it's not skipping any files I don't think. it's just counting strange. I did a reinstall of 16.5 and it still does the strange counting. It seems strange that it would go from counting 390,000 files to 250,000 in a update but maybe they did something I am not sure.I am not sure why. but i am lost to say the least. I am not going to worry about it really. nis not crashing so I am happy. everythings running super fast and the reinstall of windows xp was well worth my time as my system was over two years old and I just had too many left overs from past installs of games and Norton products such as 2008 2007. it was time.
but if some of you guys can try a full scan and see if your numbers are lower or higher that would be great to hear.
http://community.norton.com/norton/board/message?board.id=nis_feedback&thread.id=41976&page=2
For good workaround for LU problem in 16.5 patch consisting of HTTP/1.1 and 1.0 problems go to this link
http://community.norton.com/norton/board/message?board.id=nis_feedback&thread.id=41549&page=6
I have one very annoying problem that I can attribute to the latest update to NIS 2009, version 16.5.0.135. When I delete a file from a folder window, Windows Explorer crashes, after getting a Microsoft notification message asking me if I want to report the incident. Window Explorer immediately restarts itself, but without most of the program icons in my task tray. For my computer to be fully functional I have to either restart it or log off/log on. If a remember to do so, I can drag the file I want to delete out of the folder window and on to the desktop. Deleting a file on the desktop does not cause a problem.
I suspected the problem might be due to Norton's recycle function, which I think is associated with SystemWorks. Using the Norton removal tool I removed all of the Symantec products from my computer. This corrected the problem I've describe. I first reinstalled Systemworks Basic which did not result in the problem reappearing. Next I reinstalled NIS 2009. Both NSWB 2009 and NIS 2009 were installed using setup files downloaded just prior to the reinstallation. After reinstalling NIS 2009 the problem described did not reappear, however the version installed was not 16.5.0.135. Once Live Update installed 16.5.0.135, the problem did reappear.
Is there a way to prevent NIS 2009 from being updated to version 16.5.0.135? I was very happy with the previous version. If that's not an option, is there a method to configure it (presumably by turning off a feature) to eliminate the problem until it's solved with a future update.?
One other action I tried was recommended elsewhere on this forum, uninstalling IE8. The action did not help.
Sry buddy there is no way to stop ur norton product from being updated, options were given till 07 version but since 08 came we have no control over updates.
u have solved problem earlier too.
so try those steps and install 16.5 ver instead of 16.2 this time.
u can get new version setup from trialware at symantec trialwares.
qabraxa,
Do you happen to have PowerDesk? If so, see the thread about right clicking causing Windows Explorer to crash.
Check Reese's message about PowerDesk.
Also perhaps worth trying, if PD is not a factor, is uninstalling NIS and NSW using Norton Removal Tool (note it will take out all Norton applications including ones like GHOST or Save & Restore -- no choices) and then installing them in the reverse order: NIS first and then NSW.
Reese can comment on this I'm sure and whether there can be a conflict between the two different methods of LiveUpdate since 2009's are internal to the application but not so for NSW.
What Norton software did you have installed before these present two and how did you remove them? Specifically did you remove Symantec Live Update which appears, prior to 2009 versions, as a seperate application listed in Control Panel and in Remove Programs.
Apologies if I've missed something you have said before.