3.9.5: Bare installation produces inconsistent settings for start menu pinning
Start menu and Windows enhancement software
Brought to you by:
ibeltchev
Menu
▾
▴
#233 3.9.5: Bare installation produces inconsistent settings for start menu pinning
Expected behavior:
Pinning shortcuts using the "Pin to Start menu (Classic Shell)" context menu option should pin applications to the initial menu as it does in Windows 7 (running on Windows 8, fresh installation).
Actual behavior:
Pinning causes shortcuts to appear in "AppData\Roaming\Microsoft\Windows\Start Menu", which displays under the full "All Programs" menu rather than the initial menu.
Suspected cause:
The advanced settings for Classic Shell ("Main Menu\Pinned Programs Folder") show that pinned shortcuts should be placed in a dedicated "Pinned" folder, but Classic Shell continues to produce shortcuts in "AppData...\Start Menu". Modifying the setting to "Start Menu" explicitly and back to "Pinned" fixes the behavior, suggesting that the default context menu action for "Pin to Start menu (Classic Shell)" is inconsistent with the default configuration for "Pinned Programs Folder" (default "Pinned"; this behavior manifests specifically when no options are changed on installation, and Classic Shell is being installed for the first time or all user configuration data for Classic Shell has been deleted before reinstallation).
Reproducing the behavior:
- Uninstall Classic Shell.
- Delete all related settings ("AppData\Roaming\ClassicShell", registry key "Software\IvoSoft").
- Install Classic Shell (only Classic Start Menu and Update selected in my installation).
- In initial settings prompt, change no settings and press "OK".
- Open the Start menu, "All Programs" and attempt to pin any shortcut there.
- Close and reopen Start menu and observe a duplicate shortcut in "All Programs" rather than the expected pinning in the initial menu.
Ah! You're right! Good catch and thanks for reporting. This bug happens on a clean installation of Windows without any previous Classic Shell settings stored because the Windows 7 style is pre-selected by default in 3.9.5. If instead of just clicking OK, you click once on the Windows 7 style despite it already being selected, then the bug won't happen.
Gotcha! Yeah, thought it might be worth looking at since it resulted in some really unintuitive behavior until I figured out what was causing it. At any rate, everything else working fine at the moment :) Thanks for the quick reply!