1 user registry handles leaked from \Registry\User\S-1-5-21-1664202422-207725521-1799532761-1139
In the test cases, step S12, I executedCreateLogousers.cmd which created a number of user accounts, including the limited user account "Logo User 1".
When trying to log on with this limited user account I get the error message"Windows could not connect to the System Event Notification Service service". Please consult your system administrator.
I am the system administrator
; but, what the heck do I do to fix this? I checked newsgroups & the web, but came up short.
Running Windows Vista Ultimate 64-bit (Release version)
Try rebooting and do it again.
I had a similar problem where I created a user on a machine that had never had another user created, it took a long time to switch then it failed with that error. I rebooted and the error disappeared. Apparently when you first create the user a lot of work happens under the hood (creating directories, etc).
That was it.
Such an odd error too. I tried creating new limited users manually, and the same error occurred.
I ended up calling Microsoft for support and after checking permissions on the System Event Notification Service (SNES), we just tried rebooting.
I hope this helps someone else out there save a few hours of wondering.
Tim
It appears that the Application event log is generating a warning for Event ID 1530 regarding the User Profile Service. The details indicate that:
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.
DETAIL -
1 user registry handles leaked from \Registry\User\S-1-5-21-1664202422-207725521-1799532761-1139_Classes:
Process 1008 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-1664202422-207725521-1799532761-1139_CLASSES
While I can't tell for sure, it may be that the Switch User functionality is challenged in a domain environment and isn't releasing the registry for the next user or that some other application is holding on to something in the registry the other user needs. Does your application event log show anything? Yes, I got that one and also this one:
The COM+ Event System could not remove the EventSystem.EventSubscription object {3C4FB634-3FF8-482C-8692-6737AED11CA6}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}. The HRESULT was 80070005.
I am getting the same error, but reboot does not help.
I have been experiencing the same problem since 3/28/2007. I have traced it to the installation of Windows Update 905866 Update for Windows Mail Junk E-mail Filter March 2007. Every time that update installs, I cannot log in to my standard user account in Vista. Once I use System Restore to a date prior to 905866 (in the admin account), everything works fine again. I am in the process of e-mailing this info back to Microsoft Support for Microsoft Updates.
I set my machine to "Download and notify me" of updates instead of "Download and install" updates for now. However, the update still comes up and still breaks the standard user account.
Rebooting the machine did help me, thanks!
Interesting about WUpdate...
I've had this same problem happen on two Vista computers: a Dell Inspiron 1501 laptop (Vista Enterprise) and custom-built my workstation (Vista Ultimate). I'm able to login using my administrator account, but non-admin accounts cannot log in. Restarting does not help.
"Windows could not connect to the System Event Notification Service service. This problem prevents limited users from logging on to the system. As an administrative user, you can review the System Event Log for details about why the service didn't respond."
In the AppLog, I see: "The winlogon notification subscriber <SessionEnv> was unavailable to handle a notification event" and "The winlogon notification subscriber <UmRdpService> was unavailable to handle a notification event"
I've been seeing this error off and on for months, ever since first installing Vista Enterprise Edition RTM. Since we have many other things to do, it's been ignored because a reboot typically fixed it, but I can see it becoming a big-time problem. Microsoft needs a KB article about this -- it's just unacceptable to run into a problem where a user cannot login to the system. I read one case online where someone bought Vista, installed it, and created a limited user account -- and then couldn't log in. Unacceptable. I'm going to open a ticket and see where it goes.
This is a random bug that hasn't been fixed, my take. Let me know how the ticket goes, I think it's a good idea that you pursue it.
Dave.........
I get the same error message as you -- Event ID 1530 -- registry leak, and I don't believe it has anything to do with user accounts. I'm the Admin and only user on my system and this Event ID 1530 nukes several of my Vista functions. Reboot doesn't help. No other significant errors or warnings are in the Event Viewer. A mystery!
EW
Well, actually, I've stopped seeing this error, and I asked Microsoft about it and they didn't have much information about it, either. So until it is reported by more people and becomes a bigger issue, I don't see a concrete resolution any time soon.
yea, I never notice the error again once I rebooted and it only happened when I created a user account and then directly tried to switch users to it.
