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
without this issue, 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.
Edited by 72707, 01 May 2008 - 01:18 PM.