ExplorerPatcher
ExplorerPatcher copied to clipboard
valinet
The hardblock was added to prevent Explorer from crashing when ExplorerPatcher is installed.
Hi Team,
The hardblock was added to prevent Explorer from crashing when ExplorerPatcher is installed. You only need to adjust the setup exe name to get around the block in your new version. We will continue to block ANY version that crashes Explorer.
Please let me know if you have any question.
Thanks Michelle
Edit: ignore my post. solved after updating to latest version
Is this why my taskbar is transparent now with win10 style?
This issue is not repro with the latest prerelease on latest 26090 build. I have my changes to make the 11 taskbar the default on all Windows 11 versions unpushed.
@Amrsatrio please kindly confirm if you received my comment above. Please let me know if you have any question. Thanks a lot!
Hi @Michellehdr as I'm not one of the developers here, I'll let @Amrsatrio reply to this :)
As for code removal, is @Michellehdr digging in their heels about not allowing moving or resizing the Taskbar?
Hi @Michellehdr, I'm here to let you know that I've received your comment. Sorry for taking a while, I've been having other errands lately. I will make a new release today or tomorrow to make the Windows 10 taskbar no longer an option when run on 26002+.
@Amrsatrio thanks for the update. Looking forward to the new release. And long termly, it will be great if you could update the app to stop using undocumented code to prevent current and future issues.
Since the legacy Explorer Taskbar has been killed off, please consider feedback that re-enables more Windows 10 Taskbar features, especially resizing and moving the Taskbar.
Most people have widescreen displays, and some have ultrawide displays, and thus vertical space is a bit more at a premium, hence why some people like to put their Taskbar on the side of the display.
Hi, sorry for taking so long. I have pushed the code where the 10 taskbar is no longer available on 26002 to comply with your decisions. It would be very great if versions 22621.3527.65.1 and above can be whitelisted.
Feel free to close this issue if the 65.1 no longer causes crashes on unreleased GE builds.
Hi, sorry for taking so long. I have pushed the code where the 10 taskbar is no longer available on 26002 to comply with your decisions. It would be very great if versions 22621.3527.65.1 and above can be whitelisted.
Feel free to close this issue if the 65.1 no longer causes crashes on unreleased GE builds.
@Amrsatrio If you read the opening post carefully, they said that you'll just need to rename the ep_setup.exe to something else to lift the block. As far as I can see the new release is still ep_setup.exe. Also it seems that they have retracted the claim that Win10 taskbar code is removed, at least it doesn't appear anymore on the edited post... So as long as it doesn't crash it can inculde the Windows 10 taskbar code.
Hi, sorry for taking so long. I have pushed the code where the 10 taskbar is no longer available on 26002 to comply with your decisions. It would be very great if versions 22621.3527.65.1 and above can be whitelisted. Feel free to close this issue if the 65.1 no longer causes crashes on unreleased GE builds.
@Amrsatrio If you read the opening post carefully, they said that you'll just need to rename the ep_setup.exe to something else to lift the block. As far as I can see the new release is still ep_setup.exe. Also it seems that they have retracted the claim that Win10 taskbar code is removed, at least it doesn't appear anymore on the edited post... So as long as it doesn't crash it can inculde the Windows 10 taskbar code.
That would explain why the new version blew up when I tried and that I had to rename the uninstaller to get rid of it. But then, I'm on build 26200 Canary, and more legacy code may have been ripped out of Explorer.
@Bec-de-Xorbin I will consider this later.
Also it seems that they have retracted the claim that Win10 taskbar code is removed, at least it doesn't appear anymore on the edited post
I have confirmations that EP and StartAllBack are being blocked due to fighting the DisableWin10Taskbar feature flag. Now in EP the Windows 10 taskbar option is no longer here, so is the code that fights DisableWin10Taskbar.
The system tray-less Windows 10 taskbar code still exists in the latest GE builds, but they still have DisableWin10Taskbar crash bombs sprinkled all over the constructors of various Windows 10 taskbar-related classes, and again, Microsoft isn't happy when someone tries to defuse the bombs for the masses.
@VaiCaDep0893 Stability wise I disagree. Doesn't work if you have more than one input languages.
@VaiCaDep0893 Stability wise I disagree. Doesn't work if you have more than one input languages.
Not to mention that Microsoft would probably frown on this project contining Microsoft-owned files.
Where would this explorer.exe go?
Also, be wary of anyone sending you an executable. Don't just run it or add it to your OS.
If this means there won't be any way to have to get the taskbar on Win11 on the side as well as all the other functionality MSFT has chosen to remove (Quick Launch, etc), then Windows 11 will no longer be usable at our company.
Due to the uncertainty around MSFT's intentions to fulfill their earlier promises about implementing full taskbar functionality in Win11 we've avoided upgrading our computers. Unfortunately, our IT vendor is only offering laptops with Win11 recently. Prior to deployment we'll need to downgrade all new laptops to a Win10 Long Term Maintenance version or the last Win11 version that can be made usable with ExplorerPatcher (and then freeze them on that version).
Does anyone know the final working version of Windows 11?
Where would this explorer.exe go?
Also, be wary of anyone sending you an executable. Don't just run it or add it to your OS.
the explorer.exe goes into the C:\WINDOWS folder. also, the explorer.exe (22H2 Windows 11) was taken from my system and verified with virustotal, so no virus was detected. see here for analysis: https://www.virustotal.com/gui/file/698e8a2eabad13876d0af28e82129e47a9cb24f31d6d287dc00d2c1929ed04b5
If this means there won't be any way to have to get the taskbar on Win11 on the side as well as all the other functionality MSFT has chosen to remove (Quick Launch, etc), then Windows 11 will no longer be usable at our company.
Due to the uncertainty around MSFT's intentions to fulfill their earlier promises about implementing full taskbar functionality in Win11 we've avoided upgrading our computers. Unfortunately, our IT vendor is only offering laptops with Win11 recently. Prior to deployment we'll need to downgrade all new laptops to a Win10 Long Term Maintenance version or the last Win11 version that can be made usable with ExplorerPatcher (and then freeze them on that version).
Does anyone know the final working version of Windows 11?
Probably 23H2, because i haven't had any issues running it.
Still recommend against it.
it's the only way
Still, EP needs to put out a build that is fully 26100 compliant to be exempted from the block, and the option of injecting older builds of copyrighted MS binaries is probably not all that legal.
How about adding a function to backup the system's current explorer.exe. After a new version without Taskbar10 gets shipped, just ask to overwrite it from a backup. License-wise, it's a clean approach, and keeps the functionality.
Also, fsck what MSFT likes, some of their recent decisions (e.g. killing off WSA after getting it almost perfect, but way before it had a real chance to catch on) are just mind-bogglingly stupid.
@vlascik Nuh uh. It's not as modular as you thought.
It seems to be. Saw this video yet? https://www.youtube.com/watch?v=52YV657Rd1Q
Reading over this and seems like the Win 10 taskbar is gone from here on out - is that correct? My main reason for using it all this time was the ability to NOT group windows which is something that is standard with Win 11. Not sure if anyone else deals with this, but for me personally and the work I do, it is a huge pita when taskbar icons are grouped together. Have to hover over, figure out which window from the popups I actually want given the small thumbnail previews, and so on - not productive at all for me at least.
If the Win 10 taskbar is removed is there any possibility of an 'ungrouping' option for the Win 11 taskbar?
Reading over this and seems like the Win 10 taskbar is gone from here on out - is that correct? My main reason for using it all this time was the ability to NOT group windows which is something that is standard with Win 11. Not sure if anyone else deals with this, but for me personally and the work I do, it is a huge pita when taskbar icons are grouped together. Have to hover over, figure out which window from the popups I actually want given the small thumbnail previews, and so on - not productive at all for me at least.
If the Win 10 taskbar is removed is there any possibility of an 'ungrouping' option for the Win 11 taskbar?
The ungrouping options were added back in either 23H2 or 22H2.