072707
May 1st, 2008, 09:29 AM
When I try to fast user switch my XP SP2 machine hangs/crashes.
When I turn off nod32 it fast user switches normally.
Does anyone know how to resolve this issue?
Incidentally, the problem does occur on new user accounts as well.
Searching has revealed other nod32 users with the identical problem.
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Windows/XP/Q_23275836.html
note: This issue must certainly have arisen recently after a nod32 update because I never have had this problem before during almost a year of using nod32 on the machine. I now use a Mac mostly so I have not been active enough on the XP machine to encounter the issue before now.
Update: I contacted Eset via telephone and they said to uncheck "System startup file check" under "Scheduler/Planner". I did so and "Fast User Switching" works again. However, turning off "System startup file check" now, after 7 months with no issues, is not something that I am comfortable with. As I mentioned, it is obvious that this issue arose after a recent nod32 update, but the Eset "Engineer" did not, in my opinion, seem to know much at all.
In fact, he needed to ask someone else for the "fix" information he did give me. Furthermore, the first thing he said in response to me describing the problem was "Upgrade or reinstall nod32"; in my experience, every incompetent tech support person I have encountered ALWAYS wants to fix everything by reinstalling. In this case, I am fairly certain the only thing that a reinstall would have accomplished is significant wasted time.
It is, both, deeply troubling and frustrating to me that the "trend" in customer service is for companies to make so called "technical support representatives" or, as Eset calls them, "Engineers" available that OBVIOUSLY don't know a thing; not even their own product.
When I turn off nod32 it fast user switches normally.
Does anyone know how to resolve this issue?
Incidentally, the problem does occur on new user accounts as well.
Searching has revealed other nod32 users with the identical problem.
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Windows/XP/Q_23275836.html
note: This issue must certainly have arisen recently after a nod32 update because I never have had this problem before during almost a year of using nod32 on the machine. I now use a Mac mostly so I have not been active enough on the XP machine to encounter the issue before now.
Update: I contacted Eset via telephone and they said to uncheck "System startup file check" under "Scheduler/Planner". I did so and "Fast User Switching" works again. However, turning off "System startup file check" now, after 7 months with no issues, is not something that I am comfortable with. As I mentioned, it is obvious that this issue arose after a recent nod32 update, but the Eset "Engineer" did not, in my opinion, seem to know much at all.
In fact, he needed to ask someone else for the "fix" information he did give me. Furthermore, the first thing he said in response to me describing the problem was "Upgrade or reinstall nod32"; in my experience, every incompetent tech support person I have encountered ALWAYS wants to fix everything by reinstalling. In this case, I am fairly certain the only thing that a reinstall would have accomplished is significant wasted time.
It is, both, deeply troubling and frustrating to me that the "trend" in customer service is for companies to make so called "technical support representatives" or, as Eset calls them, "Engineers" available that OBVIOUSLY don't know a thing; not even their own product.