The Windows 10 Modern Start Menu has introduced a range of challenges and frustrations for end users and admins alike, particularly within environments that operated for long periods with a typical Windows 7 or Windows Server 2008 R2 redirected Start Menu, a technique which no longer lends itself well to the new modern Start Menu. Learning to accept, manipulate, alter and manage the Windows 10 / Windows Server 2016 Start Menu is one of an EUC admins biggest challenges, not just in the technology side of things, but in user acceptance also.

I have written previously about managing the Start Menu Layouts, cleaning the base Start Menu clutter, and general frustration with Tiles & Modern Applications and have spent enough time with these solutions and configuration options that they are second nature, however many environments coming out of the Windows 7 and Windows Server 2008 R2 era continue to struggle with the enormous shift to Windows 10 and Windows Server 2016 or 2019.

One of the biggest changes that occurred in the Windows Start Menu (left hand side, forget tiles), is the change in how Windows displays icons and folder structures. There is a limit of 1 folder deep under the “Programs” folder, where the Start Menu will only show you a single folder, with all sub folders ignored, and their icons aggregated into the root folder, an example below

The Browsers Folder contains a file structure on the Operating System of: %AppData%\Microsoft\Windows\Start Menu\Programs\Browsers\Google %AppData%\Microsoft\Windows\Start Menu\Programs\Browsers\Microsoft %AppData%\Microsoft\Windows\Start Menu\Programs\Browsers\Mozilla

Explorer View of the Start Menu

Above: Explorer View of the Start Menu

Each with a corresponding application: Chrome, Internet Explorer and Firefox accordingly

However, the Windows 10 Start Menu will display the applications “Chrome, Internet Explorer and Firefox” icon under the root “Browsers” Folder, ignoring the remaining sub folders

Start menu View of the Browser Folder

Above: Start menu View of the Browser Folder

This can pose a large acceptance challenge to the end user base when moving from legacy Operating Systems. Admins have typically fallen back to solutions such as classic shell to reskin the Start Menu and make it legacy again, which whilst acceptable, doesn’t lend well to future upgrades and changes that may be implemented. Furthermore, once you adapt to the modern start menu, and configure it appropriately for roaming and customisation, its actually quite efficient.

I often talk to customers about adoption of modernisation and our discussions will regularly lead to a misconception that all users are thick, and do not want to change from the day to day of what they do. This is not typically accurate these days, Microsoft and the force feeding of new ways of working via the consumer offerings have stamped a mentality of change on people, where Windows 10 is simply accepted and commonplace in the average home, so the requirement to force the EUC environment in a corporate environment to look legacy is far less than many believe.

Saying that, those environments that have operated via a redirected or deeply structured Start Menu in legacy environments will struggle with this change, more from a perspective of users being lost on where to find their applications rather than a technical view, which is why its important to understand the available tools to help. One such method being the use of Toolbars in Windows, a hidden gem when it comes to Start Menu adoption in the modern era.

Deploying the Solution

A custom Toolbar displays the underlying folder structure as the file system views it. Completely different to the way the modern Start Menu reads and displays this information, which given that the Start Menu folder is still logically structured and managed at a file system level, makes it the perfect addition to the arsenal when moving to the new world, providing both administration and user experience ease.

Deploying a custom toolbar however is not as simple as one might hope, however very much achievable once you know where to look.

Create the custom Toolbar in a standard user profile.

Create a new Toolbar

Above: Create a new Toolbar

Point the toolbar to %AppData%\Microsoft\Windows\Start Menu\Programs, this expands to C:\Users\%UserName%\AppData\Roaming\Microsoft\Windows\Start Menu\Programs

Toolbar File System Location

Above: Toolbar File System Location

The Toolbars Menu will now display our new Programs Toolbar, with the Taskbar shortcut to the toolbar auto created

Created Toolbar

Above: Created Toolbar

If we look at the Browsers Folder via the Toolbar, we can now see the full file system path of the application itself, a very familiar experience for the end user

Toolbar Browser Folder View

Above: Toolbar Browser Folder View

If we look at the WEM Tools Folder via the Start Menu, we we see a consoldated view of the icons

Start Menu WEM Tools View

Above: Start Menu WEM Tools View

However, the Toolbar honours the folder structure:

Toolbar WEM Tools View

Above: Toolbar WEM Tools View

Toolbar configurations are stored in the registry as binary entry under the following key:


Lucky for us this key is in the HKCU user hive, which means we can now get selective in handling deployments and alterations on a per user basis.

I recommend creating a custom toolbar on the system you plan to deploy it on, this isn’t a hard and fast rule, but as with most things EUC based, better safe than sorry. From there you can export the registry entry.

Toolbar Registry Location

Above: Toolbar Registry Location

Save the file as toolbar.reg, and copy it to a central location that is accessible to all users, for this example the reg file ended up living in the NETLOGON share


The registry value applies after an explorer process restart, so you can either log off the user after its been imported or you are going to need to kill the explorer process in the user context. I am using PowerShell to achieve this in the example below, however you can utilise whatever language tickles your fancy

Start-Process -filepath "reg.exe" -argumentlist "import \\\Netlogon\Toolbar\ToolBar.reg"

taskkill.exe /F /IM explorer.exe

Start-Process Explorer.exe

Save the script to a central location that is accessible to all users.

No surprises that I am driving this example with Citrix Workspace Environment Management (Which can also build out your Start Menu structures at the file system layer), using an external task. However once again choose your poison, Group Policy etc

WEM Start Menu Layout

Above: WEM Start Menu Layout

Profile Management will roam the toolbar with the user profile once created, so you may choose to make this a run once action, and run only at logon

WEM Conf Detail
Name Create Start Menu Toolbar
Description Create Start Menu Toolbar
Path Powershell.exe
Arguments -ExecutionPolicy Bypass -File \\\Netlogon\Toolbar\CreateToolbar.ps1

WEM External Task

Above: WEM External Task

If you need to rerun this at any time, you can use my WEM Tracking Cache Reset utility to reset external tasks tracking.

All users assigned the action should now have a Programs Tool bar created based on the %AppData%\Microsoft\Windows\Start Menu\Programs File System location


End user Computing is all about user experience and user acceptance. This doesn’t mean throwing the baby out with the bathwater when it comes to adopting new services and experiences just because there is a significant change, and it doesn’t always mean throwing in additional software to hide or alter the out of box capability of a Modern Operating System.

We are challenged as architects, consultants and Engineers in designing a transition to these new modern “views”, and the simple use of toolbars is yet another weapon in the arsenal associated with balancing user expectations, productivity and adoption of new ways of working all at the same time.

Simplicity, as always is a thing of beauty