Wow, can't believe they still haven't made this product work on Windows 8. I've had this and other problems with NIS on Win8.
I've had to switch to Kaspersky ....which works perfectly on Windows 8......now, since NIS was sold to me as being Windows 8 compatible...where do I get my refund??
Yesterday, first time in months on 3 systems with Win8, i had the problem.
I tried the suggestion of a few posts back : turning off and on Smart definitions, with a Liveupdate in between and a reboot afterwards.
I, however had Smart definitions on off, so i turned on and off with a Liveupdate in between and a reboot afterwards and see : Problem vanished (for now).
I am having this problem using Windows XP pro 32 bit. It has occurred several times in the last six weeks. With Ghost, I reload the C drive and it fixes the problem for a week or so. Its an easy fix - thanks for Ghost!
I have been using NIS2012 in windows 8 since almost w8 release and it always worked fine but last week I updated NIS2012 to 2013 and I started having this problem aswell.
I am sure there's still a problem in Win8 with recognising NIS 2013. If it is Norton's or Microsoft's problem, that's to be sorted out by both companies.
To solve it (temporarily maybe) I used this solution, which user SCN wrote down earlier in this thread. In his case it was the other way around; i have smart definitions standard off, he has it on.
And : I did not see the problem again in Win8.
Quote :
1. Turned on smart definitions
2. ran live update
3. turned smart definitions back off
4. ran live update
5. rebooted
After the reboot windows 8 pro recognized Norton's Internet Security 2013 as controlling anti virus, spyware, and firewall.
Yes, in fact, THERE IS a fix!! But the Norton support staff isn't prepared to give it out freely - they just want to take remote control of your computer and fix it themselves. I had this problem with a brand new HP computer that was bundled with a 60-day NIS package. Same errors appeared, Windows Action Center reporting that neither Norton nor Windows Defender were activated, even while NIS was actually running. Before I retired, I was a professional IT Manager/Administrator/Security Officer, responsible for a state government enterprise of more than 1,000 users. There is NO WAY I would allow a technician, who was very likely less capable than I was to repair the problem, to take control of my BRAND NEW PC. So I persisted, telling three different technicians that I spoke with, that the problem they acted ignorant of was in fact very common, very public, and listed on THIS FORUM, sponsored by their employer. By pushing harder and harder, I finally got the last technician I chatted with to release the information that fixes the problem. I had mine fixed in less than one minute of tweaking. My Action Center now reports that NIS is activated and running, and gives me a Windows 8 wealth of details on NIS functionality, now that I ran the fix.
If you are comfortable with running a simple command line Windows utility, you too can do this. If you aren't, let one of the Chat Support folks do it for you. I will list the fix that worked for me. If you try it and it doesn't work, either go to Support (and let them take remote control - at least some of them know how to fix it, once you clear a few hurdles), or report it here. There are more things for you to do before you are GUARANTEED to have it fixed. I will watch this FORUM, and if I see folks who are comfortable with fixing themselves, but the fix that worked for me doesn't for them, I will provide more information. Here is the fix that worked for me:
Navigate to the command prompt by entering "c", OR by searching for "CMD", from the Windows 8 Start Menu. Don't open CMD, right-click on it. In the bar that opens at the bottom of the screen, select "Run as Administrator" and a Windows command line should open. If you are uncomfortable with this, or can't do it, STOP RIGHT HERE, and contact Norton's Tech Support and open a Chat session to let them take remote control of your PC and do it for you (believe me, they know how, if you persist).
On the command line, type: winmgmt /verifyrepository
You should get an immediate response that the Repository is consistent. If it reports that it isn't consistent, stop here, and report it on the Forum, and I will provide the next step. If you prefer, you can go to a Chat session.
If you got a Consistent, Shut down and restart your computer.
When it restarts, check to verify that Action Center is now happy with Norton as its security protection. If not, report to the Forum again, or start a Chat session.
I hope this helps the many folks who have reported the problem!
Until Microsoft and Norton (and others because apparently it is not specific to Norton) discover what triggers it I doubt we will have a complete solution .....
I have the same problem. At first I thought it was a virus and re-installed my OS. Then now I have had it running for two weeks now and the problem has resurfaced. I have just resorted to asking windows to ignore the problem.
The other way around (if you have Smart definitions standard off) : from Smart definition ON to OFF and back again along the same procedure, also solves the problem temporary.
For some reason this problem seems to re-occur everytime Windows releases new updates - worked fine for ten days soon as Windows Update game out Tuesday old problem returns.
I've had this problem ever since I upgraded from Windows 7 to Windows 8 two months ago. I've tried both deleting the Repository folder and changing the Smart Update settings. Each of them works for a while, and then the problem, like zombies, come back from the dead. I realize these things take time, but surely there is a real permanent fix for this issue by now. How many iterations does it take before Symantec and Microsoft work things out and find a solution? It can't be that difficult.
I could solve this problem installing ccleaner then analyzed useless files and remove them, after this i've gone in ccleaner registry feature and search for problem in all of them press correct problem button then reboot, everything was back to normal.