none
Drawbacks of enabling 'Do not forcefully unload the user registry at user logoff' in Group policy RRS feed

  • Question

  • I am receiving errors 1530 which is breaking the application associated. 

    Description:
    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.  

    Below is the solution i found:

    The policy setting 'Do not forcefully unload the user registry at user logoff' counters the default behavior of Vista and newer operating systems. When enabled, the User Profile Service will not forcefully unload the registry, Instead it waits until no other processes are using the user registry before it unloads it. The policy can be found in the group policy editor (gpedit.msc). The policy is located under: Computer Configuration->Policies ->Administrative Templates->System-> User Profiles   'Do not forcefully unload the user registry at user logoff' Change the setting from "Not Configured" to "Enabled" which disables the new User Profile Service feature.

    If you enable this policy setting, Windows will not forcefully unload the users registry at logoff, but waits until no other processes are using the user registry before it unloads it.

    But, i would like to know whether this will cause performance issues ? Since, the registry handles wont be unloaded and the numbers might keep increasing entil not being used by any process.

    Please help me to know the drawbacks of enabling this policy. If everything is good, this will be enabled throughout a domain.

    Tuesday, April 9, 2013 1:47 PM

Answers

  • Hello,

    But, i would like to know whether this will cause performance issues ? Since, the registry handles wont be unloaded and the numbers might keep increasing entil not being used by any process.

    You should try to figure out what process is causing this.
    Please connect with another user and run process monitor.
    Set a filter for the ntuser.dat of the user that has this issue.

    Please also check the events for the User Profile Service in Applications- and Services Logs.


    MVP Group Policy - Mythen, Insiderinfos und Troubleshooting zum Thema GPOs: Let's go, use GPO!

    Tuesday, April 9, 2013 3:12 PM