|
Post by anixx on Jun 30, 2024 5:12:27 GMT -8
Reportedly, replacing explorer.exe with a version from older build (or Win10) works fine and restores the cassic taskbar.
So, one needs to replace ExplorerFrame.dll (with one from build 22000 or earlier) and Explorer.exe (with one from build 22631 or earlier) for smooth experience.
|
|
|
Post by enderboy on Jun 30, 2024 23:17:04 GMT -8
Reportedly, replacing explorer.exe with a version from older build (or Win10) works fine and restores the cassic taskbar.
So, one needs to replace ExplorerFrame.dll (with one from build 22000 or earlier) and Explorer.exe (with one from build 22631 or earlier) for smooth experience.
The classic taskbar, I tried using explorer from 22h2 19045 and 21390 but 22h2 kept crashing and 21390 said certificate past expiration
|
|
|
Post by Brawllux on Jul 1, 2024 3:55:12 GMT -8
Reportedly, replacing explorer.exe with a version from older build (or Win10) works fine and restores the cassic taskbar.
So, one needs to replace ExplorerFrame.dll (with one from build 22000 or earlier) and Explorer.exe (with one from build 22631 or earlier) for smooth experience.
The info that this thread gives really depends on what you call "working". If you use Windows 10's explorer it will crash at least 3 times in a minute. With server 2022 explorer app notifications will crash explorer and you will not be able to pin any UWP app into the taskbar. With Windows 10 21390 explorer only way to get it working is removing it's expired certificate/signature and use it with "signature enforcement" disabled. Using Windows 11 21H2-22H2 explorers should be fine since they are not much different.
|
|
|
Post by Windows User on Jul 1, 2024 5:29:24 GMT -8
Reportedly, replacing explorer.exe with a version from older build (or Win10) works fine and restores the cassic taskbar.
So, one needs to replace ExplorerFrame.dll (with one from build 22000 or earlier) and Explorer.exe (with one from build 22631 or earlier) for smooth experience.
The classic taskbar, I tried using explorer from 22h2 19045 and 21390 but 22h2 kept crashing and 21390 said certificate past expiration You nned to do this on Windows 11 21h2 youtu.be/SU-jtQqjj-A?t=354
|
|
|
Post by enderboy on Jul 1, 2024 5:43:06 GMT -8
The classic taskbar, I tried using explorer from 22h2 19045 and 21390 but 22h2 kept crashing and 21390 said certificate past expiration You nned to do this on Windows 11 21h2 youtu.be/SU-jtQqjj-A?t=354Opps, I forgot, thanks
|
|
|
Post by anixx on Jul 1, 2024 7:59:34 GMT -8
Reportedly, replacing explorer.exe with a version from older build (or Win10) works fine and restores the cassic taskbar.
So, one needs to replace ExplorerFrame.dll (with one from build 22000 or earlier) and Explorer.exe (with one from build 22631 or earlier) for smooth experience.
The info that this thread gives really depends on what you call "working". If you use Windows 10's explorer it will crash at least 3 times in a minute. With server 2022 explorer app notifications will crash explorer and you will not be able to pin any UWP app into the taskbar. With Windows 10 21390 explorer only way to get it working is removing it's expired certificate/signature and use it with "signature enforcement" disabled. Using Windows 11 21H2-22H2 explorers should be fine since they are not much different. Thanks for the invaluable details!
|
|
malcolm
Freshman Member
Posts: 81
OS: Windows 8.1 Pro
Theme: XP Luna 8.1 (My Own)
CPU: AMD Ryzen 9 5900X
RAM: 32GB
GPU: Nvidia GTX 1080Ti
Computer Make/Model: My Own
|
Post by malcolm on Jul 7, 2024 16:36:06 GMT -8
Is this the classic taskbar that allows you to change the size? Because at the moment my Openshell start menu is hovering a good bit above Retrobar and it's because I cannot change the size of the taskbar icons.
|
|
Erizur
Freshman Member
5iVE STAR
Posts: 53
OS: Windows 10 LTSC 2021
Theme: Windows 8 - Release Preview
CPU: Intel(R) Core(TM) i5-4570 @ 3.20GHz
RAM: 16GB DDR3
GPU: NVIDIA GeForce GTX 1050
Computer Make/Model: Lenovo
|
Post by Erizur on Jul 8, 2024 20:18:47 GMT -8
|
|
|
Post by anixx on Jul 8, 2024 22:43:08 GMT -8
It is not compatible with Classic theme.
|
|
|
Post by OrthodoxWin32 on Jul 9, 2024 1:05:14 GMT -8
It is not compatible with Classic theme. It absolutely must be reported, i think.
|
|
|
Post by OrthodoxWin32 on Jul 9, 2024 1:11:14 GMT -8
It's strange, it is indicated that the code cannot be disclosed for legal reasons.
|
|
|
Post by anixx on Sept 10, 2024 7:21:45 GMT -8
Reportedly, replacing explorer.exe with a version from older build (or Win10) works fine and restores the cassic taskbar.
So, one needs to replace ExplorerFrame.dll (with one from build 22000 or earlier) and Explorer.exe (with one from build 22631 or earlier) for smooth experience.
The info that this thread gives really depends on what you call "working". If you use Windows 10's explorer it will crash at least 3 times in a minute. With server 2022 explorer app notifications will crash explorer and you will not be able to pin any UWP app into the taskbar. With Windows 10 21390 explorer only way to get it working is removing it's expired certificate/signature and use it with "signature enforcement" disabled. Using Windows 11 21H2-22H2 explorers should be fine since they are not much different. So, you are right, the Win10 Explorer under Win11 while works, is unstable and crashes. The 21H2-23H2 Explorer does not work under 24H2.
Even build 26080 does not start (but build 26090 works). Since the older version of EP enables Win10 taskbar on 26100.1 and some later builds, and it works reliably, the main problem remains is the absence of system tray. I wonder if it was completely removed or simply disabled...
Since we already have a mod that allos to run Explorer in taskbar mod from any location without affecting the system files, finding a way to restore system tray may be a good solution for Server 2025, IoT Enterprise LTSC, etc... This means usability till 2030s...
|
|
|
Post by anixx on Sept 10, 2024 7:26:46 GMT -8
It's strange, it is indicated that the code cannot be disclosed for legal reasons. I am not really sure but it looks like Microsoft has shared the Explorer code with a closed circle. Or some kind of leak happened. Possibly, it is a conscious move by MS so to keep people capable of using the old taskbar but removing it from the system.
|
|
|
Post by Brawllux on Sept 10, 2024 8:32:52 GMT -8
The info that this thread gives really depends on what you call "working". If you use Windows 10's explorer it will crash at least 3 times in a minute. With server 2022 explorer app notifications will crash explorer and you will not be able to pin any UWP app into the taskbar. With Windows 10 21390 explorer only way to get it working is removing it's expired certificate/signature and use it with "signature enforcement" disabled. Using Windows 11 21H2-22H2 explorers should be fine since they are not much different. So, you are right, the Win10 Explorer under Win11 while works, is unstable and crashes. The 21H2-23H2 Explorer does not work under 24H2.
Even build 26080 does not start (but build 26090 works). Since the older version of EP enables Win10 taskbar on 26100.1 and some later builds, and it works reliably, the main problem remains is the absence of system tray. I wonder if it was completely removed or simply disabled...
Since we already have a mod that allos to run Explorer in taskbar mod from any location without affecting the system files, finding a way to restore system tray may be a good solution for Server 2025, IoT Enterprise LTSC, etc... This means usability till 2030s...
It's gone completely,not just hidden sadly. And when i replace explorer i do not replace explorer.exe/mui only. To get it working correctly you also need to downgrade explorerframe.dll/mui and shell32.dll/mui.
|
|
|
Post by anixx on Sept 10, 2024 11:06:02 GMT -8
So, you are right, the Win10 Explorer under Win11 while works, is unstable and crashes. The 21H2-23H2 Explorer does not work under 24H2.
Even build 26080 does not start (but build 26090 works). Since the older version of EP enables Win10 taskbar on 26100.1 and some later builds, and it works reliably, the main problem remains is the absence of system tray. I wonder if it was completely removed or simply disabled...
Since we already have a mod that allos to run Explorer in taskbar mod from any location without affecting the system files, finding a way to restore system tray may be a good solution for Server 2025, IoT Enterprise LTSC, etc... This means usability till 2030s...
It's gone completely,not just hidden sadly. And when i replace explorer i do not replace explorer.exe/mui only. To get it working correctly you also need to downgrade explorerframe.dll/mui and shell32.dll/mui. You say, you can make it working corrrectly? Is explorerframe.dll needed? I thought it affects only how folders are displayed. Regarding shell32.dll, if you replace it, does the taskbar have tray?
|
|
|
Post by Brawllux on Sept 10, 2024 14:52:06 GMT -8
It's gone completely,not just hidden sadly. And when i replace explorer i do not replace explorer.exe/mui only. To get it working correctly you also need to downgrade explorerframe.dll/mui and shell32.dll/mui. You say, you can make it working corrrectly? Is explorerframe.dll needed? I thought it affects only how folders are displayed. Regarding shell32.dll, if you replace it, does the taskbar have tray? The tray area is in explorer, you will need explorerframe and shell32 downgrade to get older explorer versions working a bit better. They aren't related to the tray itself.
|
|