Well, here's one that will leave you scratching your heads. Last night I booted up my computer and got this error message: "Sgtray.exe unable to locate component. This application has failed to start because SUS.DLL was not found. Re-installating the application may fix the problem." Never saw it before and being a non-techie, I have no clue. Then, I noticed my Eset Nod32 icon was not in the notification tray and that the splashscreen never appeared during startup. So I clicked Start > Programs and saw Eset was there. But when I tried to open the program, the cursor would quickly flash an hour glass and revert back to a cursor. No Eset program would open. Was it still installed? Was it corrupted? Was I having a bad dream? Next, I tried rebooting. I got a similar error message as the above, except this time it referred to something called "tfswcres.dll was not found". And the Eset Nod32 icon and splashscreen were still missing. I think I checked Taskmanager at this point, but I don't recall with certainty if I saw an Eset-related entry or not. After 2 hours of me googling and what-not trying to stumble across some other poor soul with a similar experience, I decided to go for broke. I uninstalled Nod32 (I was on v 3.0 5 something) using the Eset uninstaller and reinstalled the newest version. I didn't get any error messages during the uninstall, so my best guess is that the Eset program must have been on my system. If so, it remains a mystery why it was not opening up and why the splashscreen and icon went on hiatus. The new install seemed to work...at least for now (who knows what I'll see when I get home tonight). The icon is back, splashscreen is working, etc. But, the weird SUS.dll and tfswcres.dll application error messages continue (only during startup...and they seem to take turns). I'm starting to hate computers. Does anyone have any idea why (a) Eset became inaccessible and (b) why these SUS.dll and tfswcres.dll errors are occurring? I'm guessing the Eset problem and the .dll problems may be related since I never saw them before last night, but who knows? The more I tinker with my system to fix stuff, the more unstable it seems to get. Sorry for being long-winded. Not sure how much detail to go into. BTW - I'm running Windows XP PRO SP2 on an IBM/Lenovo A51 ThinkCentre desktop. I've had Eset on my system for about 2 months. If there's a genius out there , now's the time to show up!