I have discovered that if I run an NU 15 scan at startup it somehow disables my Epson printer monitoring, which then fails to load on startup as it should. I know that NU 15 is the cause because the problem on startup disappears if I turn off the initial scan on startup.
Is there any way to instruct NU 15 not to behave in this way? I have looked carefully at all the "repairs" made by NU 15, and I cannot for the life of me see any which is relevant to my printer monitoring (which I could tell NU 15 to ignore - I know how to do that).
So my first problem would be to track down what it is that NU 15 is doing. Looking at the log files accessible from NU15 shows nothing relevant (that I can see).
Any help/ideas would be welcome.
Hi,
if you manually run different cleaning items (registry, disk clean up) do the same happens? If yes, with which cleanup tool does this happen? I would guess at first on the registr cleanup...
Yes, it does happen when I run the tool manually, and I have narrowed it down to the privacy scan (definitely not the registry scan).
Can you plase check what files are being removed during the provacy scan? Do you see anything related to the Epson software (maybe a shortcut, or anything located in an epson progam folder).
The log file should be here: C:\Users\yourusername\AppData\Roaming\Norton Utilities\log\ /Win7 and Vista/
On XP the same should be somewhere here: C:\Documents and Settings\yourusername\Local Settings\Application Data\Norton Utilities\log\ (if not here, try it here: C:\Documents and Settings\yourusername\Application Data\Norton Utilities\log\ )
I have looked at the log file (which I had eventually tracked down for myself), and I have had numerous fruitless exchanges with Epson about it. They were unable to identify anything there that was immediately relevant to their software (in fact at one point I was told that the log file did not mean anything to them).
By a process of elimination I am now pretty certain that a file in the temporary files directory sweep is causing the problem. Most of these files are log files and probably not relevant. Two are in the local settings area (which my PC will not allow me to access manually). My guess is that one of these is the culprit, particularly as it contains a name which looks similar to Epson file names.
Is there any way to create an individual exception, file by file, for this scan, as there is in a registry clean? For the moment I am excluding the temporary files directory from being scanned and that works, but it is not ideal.
Unfortunately in the current releases there's no option to exclude individual files and/or folders :(.
If the Epson files are located in the Temp folder, I think it's the best if you don't let them removed. However it is strange that Epson creates a product that can be so easily harmed by removing so simple things like temp files...
I agree. Since, however, Epson do not appreciate that the problem may be at their end, it is most unlikely that a solution will come from them.