![]() For this, file accesses are redirected to the different resources and libraries using IAT hooks in the Start menu process. ![]() pri) from build 22000.51 are used instead, which work just fine, as well as an older version of StartTileData.dll. Fixing the context menus in the Start menu.In ExplorerPatcher, a mechanism was implemented to trick StartMenuExperienceHost.exe into thinking it runs on the Surface Hub, thus enabling the menu. Previous workarounds for enabling the Windows Start menu meant using an older version of StartMenuExperienceHost.exe which looked for Start_ShowClassicMode. For the XAML menu to launch, it expects to run on "Windows PPI Edition", what is commercially known as the Windows edition that ships with the Surface Hub. More recent versions skip that and just call GetProductInfo, a Win32 call which tells the type of Windows installation. In the builds where the legacy menu was available, there was a registry setting at HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\Start_ShowClassicMode that the launcher looked into to determine which menu to launch. A method for having StartMenuExperienceHost.exe launch the old menu instead of the new one.Taking that into consideration, I have decided to look into and attempt to provide a functional implementation for ExplorerPatcher. Unfortunately, officially, the old, XAML-based live tile Windows 10 Start menu is unavailable since build 22000.65 or so, although attempts have been made to resurrect it, the one I know about and follow being (❤️ many thanks to for the pointers showcased in his repository). I have recently grown frustrated with the lack of flexibility regarding the Windows 11 Start menu.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |