locked
Windows 7 - Registry leaks causing slow logoff RRS feed

  • Question

  • We have several Windows 7 32-Bit machines that use a mandatory network profile.  When the user logs off the profile is to be deleted every time as is set in group policy.  Currently it takes the user about 15 minutes to log off.  When they click log off, it sits at the "logging off" screen.  It will not respond to ctrl+alt+del.

    This happens with or without virus-scanning software installed (we use Forefront).  It also happens with all startup programs and services disabled in msconfig.  We also tried manually ending all unnecessary programs and services prior to log-off, which did not resolve the issue.

    The model PC is a Dell Vostro 320.  We also have Dell Optiplexs with identical image and software, imaged from the same server (we used WDS), using the same profile and GPO, and the Optiplex's work fine.  So the problem may somehow be hardware-related.  We did try updating all drivers to current versions.

    Related event errors:

    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 -

    5 user registry handles leaked from \Registry\User\S-1-5-21-1390067357-1202660629-1417001333-42809:

    Process 500 (\Device\HarddiskVolume1\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-1390067357-1202660629-1417001333-42809

    ---------------------------END-----------------------------

    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-1390067357-1202660629-1417001333-41095:

    Process 3640 (\Device\HarddiskVolume1\Windows\System32\winlogon.exe) has opened key \REGISTRY\USER\S-1-5-21-1390067357-1202660629-1417001333-41095

    ---------------------------END-----------------------------

    The winlogon notification subscriber <Profiles> is taking long time to handle the notification event (Logoff).

    ---------------------------END-----------------------------

    The winlogon notification subscriber <Profiles> took xxx second(s) to handle the notification event (Logoff).

     

    Any thoughts?

     

     

    Friday, December 3, 2010 8:39 PM

Answers


  • One thing I would question is the validity of using the same image for Vostro and Optiplex models. The slightest bit of difference between the two systems is going to cause problems.


    SC Tom
    -There's no such thing as TMI when asking for tech support.

    • Marked as answer by Leo Huang Monday, December 13, 2010 12:57 AM
    Saturday, December 4, 2010 7:22 PM