Hi guys, I've been searching on how to handle LiveUpdate hanging and NIS going ballistic and throwing up a note every few seconds saying that I'm missing updates. If you people have any idea of how frustrating it is to reboot over and over because Fix or Run LiveUpdate just hangs with an inifinitlely looping bar, then won't cancel, going into a loop of asking me if I'm sure I want to cancel, until I have to kill the process, then will not run again unil I reboot, meantimne the jack in the box keeps popping up and telling me I'm in danger.
Holy cow, who designed this mess.
So I finally got to this thread. I have two computers with NIS 2009 (each with own serial number and 3 PC protection, but for whatever reason I ended up buying new for each of them), one updated to 16.5.0.134 but the other quit autodownloading sometime in last few days when this was rolling out, or I used Remote Desktop probably for first time since I've had NIS 2009, don't now what happened but it now sends one packet every minute or two if click on Fix or otherwise initiate manual LiveUpdate and don't get anything back (no error message, just forever on Checking for updates.)
My question is, is there a way that I can download 16.5 0.134 to fix this, or do I have to reinstall 16.2.0.7 and hope it will start downloads again (I have read the threads when I say hope) and upgrade itself to 16.5.0.134.
I hope this isn't too close to a tech support question, it seems in the spirit of the thread.
I would really like to look for what is blocking LiveUpdate from receiving responses from the server, I checked the firewall app info, seems like the last version of Norton was a lot more robust, I guess cartoons and everyone being kept ignorant is in fashion these days, in any event I especially loved that to stop the jack in the box Danger Will Robinson Danger thingy I have to stop all background checks (it requires that to be silent???) and for only up to 6 hours, so controllingly generous of you. Which is also about the amount of time I let it sit this morning and try to reach a server and get downloads, meanwhile updating last update received even though it is receiving no updates.
I know you guys have your hands full, but is everything really that braindead that you have no idea if you received an update and applied it or not to update that time, and shouldn't there be an x out of y downloaded instead of last time updated seeming to imply everything was completed at that time?
I think you guys (and the rest of the PC programming world now for that matter, I used to be 8086 back in the day) spend too much time on your little bubble gram screens and not enough time with hard data in them.
But hey, I'll take just getting downloads again and NIS working again.
regards,
rd
<<Edited post subject, as it was moved from another thread.>>