Windows 11 should have a consistent user interface and that’s why it increasingly works without elements of Windows 8. The first is the “Open with” user interface, whose old design language comes from Microsoft’s touch-enhanced operating system from 2012 and will soon be replaced.
Windows 11 separates itself from older issues
like the site Newer Windows First reported, the latest Windows 11 Insider Preview Build 25151, published in the Dev channel, which is mainly aimed at developers and experienced users, hides the hidden function of changing the “Open With” in the context menu to the Windows 11 design language.
The new demo was already briefly represented in Windows 11 Insider Preview Build 22563, which gave a preview of Windows 11 22H2 back in February. Even in the last preview, the unified look has not yet been introduced to all of our testers, which is why Windows 11 23H2 is likely to be an application candidate.
New Design Hidden In Building 25151
Prerequisites to use the new view are the current Windows 11 Insider Preview 25151 and the Vive applet v0.3.1 (ZIP), which is offered directly through the GitHub platform for developers.
- Download Vive → Unzip Archive
- Right click inside the folder → Open in Windows Terminal
Then enter the following commands via Command Prompt:
- vivetool / enable / id: 36302090
The new view becomes visible immediately after selecting “Open With” in the context menu and fits harmoniously into the user interface of Windows 11.
Microsoft still has a lot of work to do
After Microsoft turned the user interface again and thus the UX of the operating system on its head with the change from Windows 10 to 11, countless generations of designs can now be found on and below the user interface of the operating system.
Microsoft still has a lot of work to do to give Windows 11 a coherent and consistent UI and user experience design.
In the field of icons and system icons, in particular, there are legacies still in use today that go back to the times of Windows 9x and even Windows 3.x. Users who want to convince themselves of this should take a look below %SystemRoot%\System32\SHELL32.dll recommended.
