Event ID 1530 is a Warning event and is logged because Windows automatically closes registry handles that an application left open while the user profile is being closed. The event is by design, but the application named in the event details should be investigated.
To pinpoint what is blocking profile unload:
- Open Event Viewer.
- Go to Windows Logs > Application.
- Select Filter Current Log.
- In Event sources, select User Profiles Service.
- Review the Warning and Error events, especially around the affected sign-out time.
- Open the
1530event details and identify the application listed there. That application is leaving the registry handle open.
For deeper correlation:
- In Event Viewer, go to Applications and Services Logs > Microsoft > Windows > User Profile Service > Operational.
- Review events that occurred at the same time as the Application log warnings or errors.
- Use the timestamps to determine where in the profile unload process the delay is occurring.
If more detail is needed, enable diagnostic logging on the affected computer.
- In Event Viewer, select View > Show Analytic and Debug Logs.
- Go to Applications and Services Logs > Microsoft > Windows > User Profile Service > Diagnostic.
- Select Enable Log and confirm with Yes.
- Reproduce the long sign-out.
- Review the Diagnostic log for more detailed User Profile Service activity.
- When finished, disable the Diagnostic log and clear Show Analytic and Debug Logs.
Important notes:
-
Event ID 1530itself can be safely ignored as a system condition, but the application named in the event should be investigated. - On Windows Vista and Windows Server 2008, the User Profile Service already includes the functionality that prevents many profile unload problems and logs event
1530when it takes action. - If a COM+ application stops working after user logoff because the profile is unloaded, the policy Do not forcefully unload the user registry at user logoff can be enabled in Computer Configuration > Administrative Templates > System > User Profiles. This changes the default behavior so Windows waits until processes release the user registry. This workaround can affect sign-out behavior and should be used carefully.
References:
- Troubleshoot user profiles with events
- Event ID 1530 may be logged in the application log in Windows
- You experience log-off problems on a Windows XP-based, Windows Server 2003-based, Windows 2000-based, or Windows NT 4.0-based computer
- A COM+ application may stop working in Windows when a user logs off