Windows 11 File Explorer ribbon from Windows 10

[francis11]

Don't forget - MS is backporting updates back to 10 from W11 23H2 and 24H2 to change their new design an smack you with more apps.
And try to force you to update.
About the design - you're out of luck.
In about 5 months your 10 will be outdated. Look down to 10 in the url.
Exept you know how to accomplish to stay safe.

 

[garlin]

There doesn't appear to be a single, reg-based solution that works for every W11 release.

- 21H2 only supports the Shell Extensions method​

- 22H2-24H2 support the InProcServer32 method​

To solve two major issues, a Post-Setup script is required:

1. Shell Extensions method is based on HKLM keys, which can be applied from (Before logon) and work immediately. InProcServer32 requires updating HKCU keys, which require waiting for your first desktop logon (After logon).

You can't add the same HCKU keys to the Default User's profile, because Windows new user provisioning will override your changes.

2. Even if you import the InProcServer32 reg file from (After logon), Explorer needs to be restarted to show the update. The script will do that.

---

Add this script to Post-Setup (After logon). Whenever the Classic Ribbon is enabled, the old context menu is configured at the same time.

If you want to restore the default W11 Explorer ribbon, run:

powershell -ep bypass -f RestoreClassicRibbon.ps1 -revert

 

[Pcgamer27]

There doesn't appear to be a single, reg-based solution that works for every W11 release.

- 21H2 only supports the Shell Extensions method​

- 22H2-24H2 support the InProcServer32 method​

To solve two major issues, a Post-Setup script is required:

1. Shell Extensions method is based on HKLM keys, which can be applied from (Before logon) and work immediately. InProcServer32 requires updating HKCU keys, which require waiting for your first desktop logon (After logon).

You can't add the same HCKU keys to the Default User's profile, because Windows new user provisioning will override your changes.

2. Even if you import the InProcServer32 reg file from (After logon), Explorer needs to be restarted to show the update. The script will do that.

---

Add this script to Post-Setup (After logon). Whenever the Classic Ribbon is enabled, the old context menu is configured at the same time.

If you want to restore the default W11 Explorer ribbon, run:

powershell -ep bypass -f RestoreClassicRibbon.ps1 -revert

is powershell -ep bypass -f RestoreClassicRibbon.ps1 -revert for all versions

 

[garlin]

is powershell -ep bypass -f RestoreClassicRibbon.ps1 -revert for all versions

Yes. The script recognizes which W11 release you're on. It's been tested.

 

[Pcgamer27]

Yes. The script recognizes which W11 release you're on. It's been tested.

this script works well can you also have this registry key

 

[garlin]

You're confused about the script. Let's review your previous question:

is that for all versions of W11

No. There is no reg file which works for all versions of W11.

There are two different sets of reg files, depending on your W11 release. Reg files can only contain fixed settings, they have no scripting ability. So you need a separate install script, to pick which reg file to use.

 

[WizKid]

You're confused about the script. Let's review your previous question:


No. There is no reg file which works for all versions of W11.

There are two different sets of reg files, depending on your W11 release. Reg files can only contain fixed settings, they have no scripting ability. So you need a separate install script, to pick which reg file to use.

Just use ExplorerPatcher and select the option "Windows 10 Ribbon":


and then it works:

 

[garlin]

Well, not everyone has an interest in installing ExplorerPatcher, because it has a history of breaking after MS pushes a random UI update.

Normally it will get fixed, but sometimes it takes a while. This solution works regardless of the installed Windows build.

 

[Pcgamer27]

There doesn't appear to be a single, reg-based solution that works for every W11 release.

- 21H2 only supports the Shell Extensions method​

- 22H2-24H2 support the InProcServer32 method​

To solve two major issues, a Post-Setup script is required:

1. Shell Extensions method is based on HKLM keys, which can be applied from (Before logon) and work immediately. InProcServer32 requires updating HKCU keys, which require waiting for your first desktop logon (After logon).

You can't add the same HCKU keys to the Default User's profile, because Windows new user provisioning will override your changes.

2. Even if you import the InProcServer32 reg file from (After logon), Explorer needs to be restarted to show the update. The script will do that.

---

Add this script to Post-Setup (After logon). Whenever the Classic Ribbon is enabled, the old context menu is configured at the same time.

If you want to restore the default W11 Explorer ribbon, run:

powershell -ep bypass -f RestoreClassicRibbon.ps1 -revert

I tried this in 25H2 too and it doesn't work

 

[tistou77]

If it works with 24h2, then it should work with 25h2 (the base is the same build)

 

[Pcgamer27]

If it works with 24h2, then it should work with 25h2 (the base is the same build)

I tried it and it doesn't work

 

[garlin]

Works for me...

 

[Pcgamer27]

Works for me...

This screenshot after logon RestoreClassicRibon.ps1