12-10-2010 06:46 AM
It brings me no joy to report the first new version bug.
Steps to reproduce (so far) on Win 7
1: Click the gadget (green bar) soon after bootup
2. Click Settings on top of the UI
3. Hgh disk activity can be observed, the Settings window does not appear
4. NIS becomes unresponsive,'locks'
Window 7 error reporting reports this:
Occurng after first post-update boot and a first reboot..
12-10-2010 06:57 AM - edited 12-10-2010 06:57 AM
Something got badly borked during update, will have to reinstall. Settings and history unavailable. I will save the NIS Installer logs.
12-10-2010 08:17 AM
I must admit I had similar problems on my computer and ended up using the Norton removal tool to get NIS cleaned off.
I reinstalled but now NIS remains at 18.1 after live update. Since the 18.5 patch is being released (as is typical) in a phased manner it may take some time before it comes through live update again.
I will probably download the 18.5 update through Norton Update center tomorrow and see how things goes.
I have reported this to Symantec but we need to see how many others are being affected by this.
12-10-2010 09:07 AM
Yes, problematic it was. I had to go to safe mode because even NRT couldn't stop the NIS service.
The standalone installer from the Update center provided a working & normal experience so far. :) Although I must admit I ''customized'' the 'downloader' installation myself, I canceled the downloader's prompts and installed it the old fashioned way (running the installer myself), can't help it, I'm an old fashioned computerista...
This is what it looks like when it works:
12-10-2010 11:30 AM
The problem came back after the first post-installation boot.
DO NOT MOVE to 126.96.36.199. The update needs to be pulled, this is a blocking issue. The bug causes improper computer shutdown, Process Explorer (by Sysinternals) is broken by it, NIS cannot be properly uninstalled, the litany goes on...
12-10-2010 12:15 PM
Interestingly, a 'proper' (i.e. not involving the power button) restart is possible if you don't go beyond the Windows welcome screen. Deducing from this, it looks like the UI is the culprit again.