• Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:


      Despite using the recommended practices, as well as work-arounds, there is sometimes a problem restarting explorer.

      The latest report:

      The following error sometimes occurs (but it wasn't found in Gregg's logs)

      15:53:07.541: FATAL ERROR: Uncaught exception: win32 error: RmRestart return:352 win32:1314


      Explorer is restarted via  RmShutdown + RmRestart. Sometimes it doesn't work.

      The explorer process either remains or terminates, but in both cases the taskbar is gone.

      Current knowns

      Two events are known to expose this bug:

      • When GPII is started from the installer (but works after restarting GPII).
      • After installing Office.
        (it occurs at other times, but these are the only known ones)

      That these are after an installation, and that the restart API is intended for installers, may not be a coincidence.

      It's possible that the restarting needs to be performed as Administrator - most likely a bug with the API, as there is no clue in the documentation and explorer is ran as the current user. It is speculated that this API is realistically only called as Administrator, considering it's usually used by installers.

      However, on some occasions the win32 error {{ ERROR_PRIVILEGE_NOT_HELD 1314 (0x522)}} is raised form RmRestart (when starting explorer).

      Another method: Close explorer and restart it 'manually'

      Undocumented method of closing explorer: (send 0x5B4 message to the Shell_TrayWnd window)

      Whether or not this method is affected by this issue is to be determined.


          Issue Links



              • Assignee:
                stegru Steve Grundell
                stegru Steve Grundell
              • Votes:
                0 Vote for this issue
                1 Start watching this issue


                • Created: