I've noticed a recent problem with my machine, running Windows XP Pro (32-bit). On start-up, there appears to be a couple of 'new' dlls being called (lgNotify.dll and WgaLogon.dll) on the start-up spash screen. Suspect that my user account may have somehow become compromised ... as I'm unable to install new applications (.exe files) from the CD/DVD drive. I've performed the free Microsoft Registry scan and do have the Windows Defender and Microsoft Security Essentials applications running. There are two User Accounts groups visible in the Control Panel ('User Accounts', and 'User Accounts 2'). Other than this, the machine performs normally.
Would anyone be willing to share information or insight re. the role of these dlls and the issue of (possibly) deleting errant user accounts; and how to mitigate the restriction re. installing new applications?
I had the exact same problem a few weeks back, but without the additional user account, after an XP upgrade (sorry, not sure which one now). SpyBot found a reg key which didn't seem at all related to these dlls but once it was corrected, I rebooted and it was still there. Ran it again and this time it worked. No more dlls being shown on the start up. Never could find out what it was but I don't think my machine is compromised at the moment so would be interested in knowing if you get any additional info.
Cheers Paul
Marked as answer byDarin Smith MSThursday, February 25, 2010 10:59 PM
I had the exact same problem a few weeks back, but without the additional user account, after an XP upgrade (sorry, not sure which one now). SpyBot found a reg key which didn't seem at all related to these dlls but once it was corrected, I rebooted and it was still there. Ran it again and this time it worked. No more dlls being shown on the start up. Never could find out what it was but I don't think my machine is compromised at the moment so would be interested in knowing if you get any additional info.
Cheers Paul
Marked as answer byDarin Smith MSThursday, February 25, 2010 10:59 PM
Thank you for taking the time to respond to my thread, and the identification of SpyBot as a mechanism to possibly resolve the issue on my computer.
I will post another response when (or if) I'm able to identify which Registry key has caused this situation to emerge; it may help others in the future.
