BUG: Changed System Policies Are Not Displayed on the Start Menu

MORE INFORMATION

Adding or removing policies such as NoRun and NoFind should cause an update of the Start Menu the next time it is displayed. For example, if the NoRun policy is in force, the Start menu should not display the Run command. Despite this bug, the specific policy is enforced. For example, if you select Run while the NoRun policy is in force, a message appears telling you that you cannot perform the requested action.

This bug prevents the Start menu from being updated until the system is restarted or until you log off and log back on again.

For future compatibility, you should post the following message whenever a change to the system policies is made: This will cause the shell to re-read any cached settings, including the system policies.

For non-policy change that affect the Start menu, such as adding a shortcut to the Start menu, you should call SHChangeNotify as shown below to cause the Start menu to update its contents:

Sample Code

   IMalloc *pMalloc;

   if (SUCCEEDED(SHGetMalloc(&pMalloc)))
      {
      LPITEMIDLIST pidl;

      /*
      You can also use CSIDL_COMMON_STARTMENU to get the Start menu for all
      users on Windows NT.
      */ 
      if (SUCCEEDED(SHGetSpecialFolderLocation( (HWND)NULL,
                                                CSIDL_STARTMENU,
                                                &pidl)))
         {
         SHChangeNotify(SHCNE_UPDATEDIR, SHCNF_IDLIST, pidl, NULL);

         // Free the PIDL returned by SHGetSpecialFolderLocation.
         pMalloc->Free(pidl);
         }

      // Release the IMalloc interface.
      pMalloc->Release();
      }