Installing shell components can require elevation, while everyday menu customization is a separate activity. On a shared or managed PC, distinguish installing a program for the machine from choosing settings for the signed-in user.
What to do
- Check whether the computer is personally managed or controlled by an organization. Obtain the necessary installation approval before running setup.
- Read the elevation dialog carefully and confirm it corresponds to the installer you deliberately launched. Cancel an unexpected prompt that appears without an installation action.
- After installation, open the menu settings normally rather than routinely running them as another administrator account. Configure the account that will actually use the menu.
- Sign out and back into that user account, then verify that the chosen style and startup behavior apply there. Record any repeated elevation prompt rather than suppressing UAC.
Check the result
A normal daily launch should not be confused with installation maintenance. If a Windows upgrade prompts a repair task, use the project guidance for that specific situation.
Limits & precautions
Do not disable UAC, alter organization policies, or borrow another user profile to bypass installation restrictions. Administrative deployment should be validated on a test machine.
Questions & answers
Do all users share the same preferences?
Do not assume so. The project exposes per-user startup behavior and settings; test the intended account.
Should I turn UAC off?
No. Resolve the cause of a prompt instead of disabling the protection.
Sources & scope
Documentation checked October 30, 2026. These instructions are documentation-led, not a claim of hands-on testing on your Windows build.