search

ramensoftware / windhawk-mods

The official collection of Windhawk mods
317 stars 57 forks source link

[Windows 10 taskbar on Windows 11] not working on Win 11 23H2 build 22631.4169 #1051

Open cakepuller opened 1 month ago

cakepuller commented 1 month ago

Hi There Thank you for creating WindHawk. Lifesaver. I had to switch from Win 10 to Win 11 following a new computer purchase. It runs Win 11 23H2 build 22631.4169. I installed WindHawk but the win10-taskbar-on-win11 mod isn't working. Logs below, thanks!

Mod Author: @Anixx 

> DbgViewMini v1.0.1
> Listening for OutputDebugString messages...
> 10:43:28.507 11652 explorer.exe  [WH] [`anonymous-namespace'::ModDebugLoggingScope::ModDebugLoggingScope]: >>> Entering LoadedMod::LoadedMod
> 10:43:28.508 11652 explorer.exe  [WH] [LoadedMod::LoadedMod]: Windows 10.0.22631
> 10:43:28.508 11652 explorer.exe  [WH] [LoadedMod::LoadedMod]: Windhawk v1.5.1
> 10:43:28.508 11652 explorer.exe  [WH] [LoadedMod::LoadedMod]: Mod id: win10-taskbar-on-win11
> 10:43:28.510 11652 explorer.exe  [WH] [LoadedMod::LoadedMod]: Mod version: 1.0.2
> 10:43:28.516 15736 explorer.exe  [WH] [`anonymous-namespace'::ModDebugLoggingScope::ModDebugLoggingScope]: >>> Entering LoadedMod::LoadedMod
> 10:43:28.516 15736 explorer.exe  [WH] [LoadedMod::LoadedMod]: Windows 10.0.22631
> 10:43:28.516 15736 explorer.exe  [WH] [LoadedMod::LoadedMod]: Windhawk v1.5.1
> 10:43:28.517 15736 explorer.exe  [WH] [LoadedMod::LoadedMod]: Mod id: win10-taskbar-on-win11
> 10:43:28.517 15736 explorer.exe  [WH] [LoadedMod::LoadedMod]: Mod version: 1.0.2
> 10:43:28.520 11652 explorer.exe  [WH] [LoadedMod::LoadedMod]: Mod base address: 00007FFA9B040000
> 10:43:28.520 11652 explorer.exe  [WH] [`anonymous-namespace'::ModDebugLoggingScope::~ModDebugLoggingScope]: <<< Exiting LoadedMod::LoadedMod
> 10:43:28.520 15736 explorer.exe  [WH] [LoadedMod::LoadedMod]: Mod base address: 00007FFA9B040000
> 10:43:28.520 11652 explorer.exe  [WH] [`anonymous-namespace'::ModDebugLoggingScope::ModDebugLoggingScope]: >>> Entering LoadedMod::Initialize
> 10:43:28.521 15736 explorer.exe  [WH] [`anonymous-namespace'::ModDebugLoggingScope::~ModDebugLoggingScope]: <<< Exiting LoadedMod::LoadedMod
> 10:43:28.521 15736 explorer.exe  [WH] [`anonymous-namespace'::ModDebugLoggingScope::ModDebugLoggingScope]: >>> Entering LoadedMod::Initialize
> 10:43:28.521 11652 explorer.exe  [WH] [win10-taskbar-on-win11] [49:Wh_ModInit]: Init
> 10:43:28.521 11652 explorer.exe  [WH] [`anonymous-namespace'::ModDebugLoggingScope::ModDebugLoggingScope]: >>> Entering LoadedMod::SetFunctionHook
> 10:43:28.522 11652 explorer.exe  [WH] [LoadedMod::SetFunctionHook]: Target: 00007FFAB393FAB0
> 10:43:28.522 11652 explorer.exe  [WH] [LoadedMod::SetFunctionHook]: Hook: 00007FFA9B041410
> 10:43:28.522 11652 explorer.exe  [WH] [`anonymous-namespace'::ModDebugLoggingScope::~ModDebugLoggingScope]: <<< Exiting LoadedMod::SetFunctionHook
> 10:43:28.522 11652 explorer.exe  [WH] [`anonymous-namespace'::ModDebugLoggingScope::~ModDebugLoggingScope]: <<< Exiting LoadedMod::Initialize
> 10:43:28.522 15736 explorer.exe  [WH] [win10-taskbar-on-win11] [49:Wh_ModInit]: Init
> 10:43:28.523 15736 explorer.exe  [WH] [`anonymous-namespace'::ModDebugLoggingScope::ModDebugLoggingScope]: >>> Entering LoadedMod::SetFunctionHook
> 10:43:28.523 15736 explorer.exe  [WH] [LoadedMod::SetFunctionHook]: Target: 00007FFAB393FAB0
> 10:43:28.523 15736 explorer.exe  [WH] [LoadedMod::SetFunctionHook]: Hook: 00007FFA9B041410
> 10:43:28.523 15736 explorer.exe  [WH] [`anonymous-namespace'::ModDebugLoggingScope::~ModDebugLoggingScope]: <<< Exiting LoadedMod::SetFunctionHook
> 10:43:28.523 15736 explorer.exe  [WH] [`anonymous-namespace'::ModDebugLoggingScope::~ModDebugLoggingScope]: <<< Exiting LoadedMod::Initialize
> 10:43:28.525 15736 explorer.exe  [WH] [`anonymous-namespace'::ModDebugLoggingScope::ModDebugLoggingScope]: >>> Entering LoadedMod::AfterInit
> 10:43:28.525 15736 explorer.exe  [WH] [`anonymous-namespace'::ModDebugLoggingScope::~ModDebugLoggingScope]: <<< Exiting LoadedMod::AfterInit
> 10:43:28.527 11652 explorer.exe  [WH] [`anonymous-namespace'::ModDebugLoggingScope::ModDebugLoggingScope]: >>> Entering LoadedMod::AfterInit
> 10:43:28.527 11652 explorer.exe  [WH] [`anonymous-namespace'::ModDebugLoggingScope::~ModDebugLoggingScope]: <<< Exiting LoadedMod::AfterInit

Edit: Just to add, in case it matters:
I have the following mods enabled:

I also have OPEN SHELL MENU running.

Anixx commented 1 month ago

I don't know what log did you post here. It is not the log information provided by the mod.

cakepuller commented 1 month ago

I don't know what log did you post here. It is not the log information provided by the mod.

Hmmmm, I followed the instructions at this link: https://github.com/ramensoftware/windhawk/wiki/Troubleshooting. Specifically the section that says: Pick a mod that doesn't work and collect debug logs as following:

Disable the mod.
Go to the mod's Advanced tab.
Set Debug logging to Detailed debug logs.
Click on Show log output.
Enable the mod.
Verify that the mod doesn't work, copy the log and save it to a file.
Set Debug logging back to None.

Doesn't the following line from the above log output indicate it's from "win10-taskbar-on-win11"?

10:43:28.508 11652 explorer.exe [WH] [LoadedMod::LoadedMod]: Mod id: win10-taskbar-on-win11

If not, please kindly let me know how to obtain the logs correctly for this mod.

Anixx commented 1 month ago

Oh I confused which mod you are having problems with. If this mod does not work for you, check if you have Explorer Patcher installed and have a conflicting option enabled there.

cakepuller commented 1 month ago

Nope, Explorer Patcher not installed.

Anixx commented 1 month ago

I am also on build 22631.4169, and it works (even has priority over EP). But I heard and once experienced that this option sometimes is ignored by Windows. This needs research, what can cause this.

cakepuller commented 1 month ago

I actually had Explorer Patcher installed but uninstalled it in case it interfered with WindHawk's mods.

cakepuller commented 1 month ago

Just to report another related bug:

The win10-taskbar-on-win11 mod also disables the Windows Start button on my machine. I tested by systematically turning off and on all the WindHawk mods I had installed and seems like win10-taskbar-on-win11 mod is the culprit.

"Disabled" = Clicking on WINDOWS START BUTTON does nothing; neither does hitting the Windows key.

  1. Turned off all mods > Windows start button: OK
  2. Turned on win10-taskbar-on-win11 > Windows start button: no menu, nothing happens.
  3. Turned off win10-taskbar-on-win11 + turned on all other mods > Windows start button: OK