Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[22635.3420] When Windows 10 Start menu style is selected, the Windows 11 Start menu appears instead. #3066

Closed
Amrsatrio opened this issue Mar 29, 2024 · 13 comments

Comments

@Amrsatrio
Copy link
Collaborator

Amrsatrio commented Mar 29, 2024

Windows version: 22635.3420 (Beta channel)
EP version: 64.2

Steps to reproduce

  1. Install all updates up to 22635.3420.
  2. Install ExplorerPatcher version 64.2.
  3. Open ExplorerPatcher's Properties window.
  4. Go to Start menu section.
  5. Set Start menu style to Windows 10.
  6. Restart Explorer.
  7. Open the start menu.
  8. Observe that the 11 menu is shown instead of the 10 one.

Additional information

Upon investigating further, I've seen that 3420's StartMenuExperienceHost.exe no longer has the Windows PPI edition check that uses GetProductInfo which is intercepted by EP to enable the old menu. More intricate patches are needed to restore the Windows 10 start menu on this build onwards.

Video evidence

https://cdn.discordapp.com/attachments/1211286128125153290/1223359447322202274/20240329-1951-50.8268292.mp4?ex=66199145&is=66071c45&hm=a611524b2d039f8bd2dfbf9c9a74dc2758ef23855c7f0c0c750bad6e1da99dbf&

@Amrsatrio Amrsatrio changed the title [22635.3420 [22635.3420] When Windows 10 Start menu style is selected, the Windows 11 Start menu appears instead. Mar 29, 2024
@pyrates999
Copy link

that's an insider preview: https://blogs.windows.com/windows-insider/2024/03/29/announcing-windows-11-insider-preview-build-22635-3420-beta-channel/

@Amrsatrio
Copy link
Collaborator Author

Amrsatrio commented Mar 29, 2024

Yep, I am posting this myself so that everyone including me is aware on this. I've clearly added (Beta channel) to indicate that it's a Beta build.

Critical issues in 22621-based builds like those in Beta and RP cannot be taken lightly as for this case it only takes a week or two for the issue to appear on broader channels like Release Preview or even Release, which would impact our reputation.

@pyrates999
Copy link

Oh I didn't even notice it was you posting it lol

@SherlockChiang
Copy link

Same for me, surprised to find win11 theme startup after updating my OS

@PandaFiredoge
Copy link

我也是,开始菜单无法修改为Win10

Me too, the start menu cannot be modified to Win10

@171h
Copy link

171h commented Mar 31, 2024

+1

@pyrates999
Copy link

Might be related to this: #3053

@Amrsatrio
Copy link
Collaborator Author

Amrsatrio commented Mar 31, 2024

@pyrates999 No, this is unrelated to that.

Amrsatrio added a commit that referenced this issue Mar 31, 2024
@Amrsatrio
Copy link
Collaborator Author

Made a new prerelease that should allow the 10 menu to show up again, but pin to start is now broken yet again:

https://github.com/valinet/ExplorerPatcher/releases/tag/22621.3296.64.2_5e25663

Amrsatrio added a commit that referenced this issue Mar 31, 2024
@pseudo555
Copy link

64.2 seems to solve the issue, but there is also another regression when using win10 taskbar. The button that handle sound is missing. I get the one from network, the locale for keyboad, a cog button then the hour.
This wasn't the case before updating windows.

@Amrsatrio
Copy link
Collaborator Author

Amrsatrio commented Mar 31, 2024

Hi @pseudo555, please file a separate issue complete with the details. I've never encountered this issue even in latest Canary/24H2 builds.

@pseudo555
Copy link

Hi @pseudo555, please file a separate issue complete with the details. I've never encountered this issue even in latest Canary/24H2 builds.

ne need anymore, the 64.3 you published make explorerpatcher working fine on my windows (fr 11 23h2 - 22631.3374)

@Amrsatrio
Copy link
Collaborator Author

Fix is live in the newly built latest release of EP, version 65.2. Further issues like this will be closed immediately without any explanations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants