07-17-2008 12:46 PM
If I understand this thread, the issue is that the Diagnostic report is showing PC Tuneup as disabled even though the main screen is showing protected.
I have this issue. I have followed the changes to com host and core LC from manual to automatic, started com host, and ensured all other entries were started and set to automatic. It made no difference. As I previously report "Symantec SymSnap VSS Provider " I did not find at all in my services. Should I under XP?
It occured to me that perhaps if you have not checked all options and at least run all options once, that the diagnostic report will remain as disabled. So on one machine I enabled all options and forced all options to run, then re-ran diagnostic and still it says Disabled. Surely then the fault is in the diagnostic report.
07-17-2008 01:01 PM
Sorry I don't quite follow what you are saying, what is "Symantec SymSnap VSS Provider"? Where did you get that information?
The Diagnostic report gets it's status from the main product, if the main product is reporting green then it should be green. If red, then red.
You have my email, go ahead and forward me the bad diagnostic report.
07-17-2008 01:19 PM
Yes, I got caught out this way too! If you set "Thread options" to "sort messages by threading" you see that I was replying to Tony_Weiss (bottom of page two). Tony_Weiss gave the following link
In that article point 8 of step 1, lists five files. The first has a note indicating that it may be ignored if not found, but in XP I also do not have the fourth item in the list, namely "Symantec SymSnap VSS Provider".
Is that cgoldman guy being pedantic or what ! No, just precise.
I will email u the screen shots of all the relevant screens, from which you will see that all is green, but still saying disabled in diagnostics. I have this on 2 m/c and will explain further in the email.
Thanks for coming to the rescue
07-18-2008 02:40 AM - edited 07-18-2008 02:41 AM
07-18-2008 02:48 AM
I've kudued you. Thanks for the confirmation. I suspect that the missing file only relates to the other operating system, to which the post refers and therefore that there should simply be a note that this file does not exist and may be ignored for XP. However, its always best to have Tony or Matt confirm. I raised this yesterday in private msg to Matt, so I know he is already checking same.
09-22-2008 06:11 AM
09-23-2008 04:00 AM
Just to make sure all the details are correct:
1) The diagnostic report showing PC Tuneup is disabled is a known issue that we are working on and I believe we have a solution, just waiting for it to be released. This is just a visual issue and your PC Tuneup is not actually disabled.
2) PC Tuneup scans are run once per month not daily like the Virus & Spyware scans.
3) We have seen on some machines scans that say 0 files were scanned, although difficult to reproduce, it usually happens when the scan trys to start at idle and you happen to take your system out of idle before the scan has a chance to start. Again not a big issue as the next time you go idle, the scan will restart.
4) So finally the problem with WMI. We use WMI for some of our components and if it's corrupted, there are issues we just can't get around. For example, if you run your diagnostic report and it shows every item in your windows/system32 directory as being a startup item you can be assured that this is a problem with your WMI database. The only solution that I have found to fully reset the WMI DB is at the following location http://www.microforge.net/kb/102