The information in this article applies to:
SYMPTOMSWhen you enable or disable system policies that affect the Start menu, the Start menu does not reflect the policy change until you log off and log back on or you restart the system. CAUSEThe Start menu information is cached, but the Start menu fails to flush certain items from its cache. RESOLUTIONThe only workaround for this bug is to log off and log back on. STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article.
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.
PostMessage(HWND_BROADCAST, WM_SETTINGCHANGE, 0, 0);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
REFERENCESFor additional information on system policies, please see the following article in the Microsoft Knowledge Base: Q151176 Policy Registry Entries (Default User) Additional query words:
Keywords : kbNTOS400 kbNTOS400bug kbWinOS2000 kbSDKPlatform kbSDKWin32 kbGrpUser kbWinOS95bug kbWinOS98bug |
Last Reviewed: February 1, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |