Chocolately GUI cannot be opened/not visible anymore after Windows 11 upgrade

[rklec]

Checklist

• I confirm there are no unresolved issues reported on the Chocolatey Status page.
• I have verified this is the correct repository for opening this issue.
• I have verified no other issues exist related to my problem.
• I have verified this is not an issue for a specific package.
• I have verified this issue is not security related.
• I confirm I am using official, and not unofficial, or modified, Chocolatey products.

What You Are Seeing?

When I start the GUI, it shows the splash screen as wanted and directly afterwards nothing anymore.
It looks like it tried to render an empty/transparent window or maybe at the wrong window position?

I already tried reinstalling the chocolatelygui via choco.

edit: as I've changed my display settings and executed the GUI from the commandline with --debug --verbose as it was requested below, this error was shown:

System.lO,FileLoadException: Die Datei oder Assembly • System,Reactive.Core, Culture=neutral, PublicKeyToken=94bc3704cddfc26Y oder eine Abhängigkeit davon wurde nicht gefunden. Die gefundene Manifestdefinition der Assembly stimmt nicht mit dem Assemblyverweis
überein. (Ausnahme von HRESULT: Ox80131040)
Dateiname: "System,Reactive.Core, Culture=neutral, PublicKeyToken=94bc3704cddfc26Y
bei source)
bei Onlnitialize> d_78.MoveNextO in cs:Zeile 412.
Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde
bei System.Runtime.ExceptionServices,ExceptionDispatchlnfo.ThrowO
bei System.Windows.Threading.ExceptionWrapper.lnternalRealCall(Delegate callback, Object args, Int32 numArgs)
bei System.Windows.Threading,ExceptionWrapper,TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
bei System.Windows.Threading.DispatcherOperation.lnvokelmp10
bei MS,lnternal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)
bei System.Threading.ExecutionContext.Runlnternal(ExecutionContext executionContext, ContextCallback callback, Object State, Boolean preserveSyncCtx)
bei System.Threading,ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object State, Boolean preserveSyncCtx)
bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object State)
bei MS,lnternal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object State)
bei System.Windows.Threading. DispatcherOperation.lnvoke0
bei System.Windows.Threading,Dispatcher,ProcessQueueO
bei System.Windows.Threading.Dispatcher.WndProcHook(lntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr IParam, Boolean& handled)
bei MS,Win32HwndWrapper.WndProc(lntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr IParam, Boolean& handled)
bei MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
bei System.Windows.Threading,ExceptionWrapper,lnternalRealCall(Delegate callback, Object args, Int32 numArgs)
bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object sourcet Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
bei System.Windows.ThreadingDispatcher,Legacylnvokelmpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
bei MS.Win32.HwndSubclass.SubclassWndProc(lntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr IParam)
bei MS,Win32,UnsafeNativeMethods.DispatchMessage(MSG& msg)
bei System.Windows.Threading.Dispatcher.PushFramelmpl(DispatcherFrame frame)
bei System.Windows.Application.RunDispatcher(Object ignore)
bei System.Windows.Application.Runlnternal(Window window)
bei ChocolateyGui.App.Main(StringO args) in 122.
WRN: Protokollierung der Assemblybindung ist AUS.
Sie können die Protokollierung der Assemblybindungsfehler aktivieren, indem Sie den Registrierungswert (DWORD) auf 1 festlegen.
Hinweis: Die Protokollierung der Assemblybindungsfehler führt zu einer gewissen Leistungseinbuße,
Sie können dieses Feature deaktivieren, indem Sie den Registrierungswert entfernen,

The window then freezes and the GUI crashes.

What is Expected?

Show the window or, if needed, reset the window settings or whatever.

How Did You Get This To Happen?

I had Windows 10 installed and upgraded to Windows 11.

System Details

• Operating System: 10.0.26100.0
• Windows PowerShell version: 7.5.1
• Chocolatey CLI Version: 2.4.3
• Chocolatey Licensed Extension version: N/A
• Chocolatey License type: N/A
• Terminal/Emulator: PowerShell Core now, Windows Terminal also works now and I can start all of it. (I also enabled Windows terminal as the default terminal)

Installed Packages

choco list
Chocolatey v2.4.3
***
choco-cleaner 1.1.1
chocolatey 2.4.3
chocolatey-compatibility.extension 1.0.0
chocolatey-core.extension 1.4.0
chocolatey-dotnetfx.extension 1.0.1
chocolateygui 2.1.1
chocolatey-os-dependency.extension 0.0.1
chocolatey-visualstudio.extension 1.11.1
chocolatey-windowsupdate.extension 1.0.5
***
KB2919355 1.0.20160915
KB2919442 1.0.20160915
KB2999226 1.0.20181019
KB3033929 1.0.5
KB3035131 1.0.3
KB3063858 1.0.0
KB3118401 1.0.5
***
winfsp 2.1.25156
wsl-ubuntu-2004 20.4.0.20220127
***

Output Log

N/A as it is no CLI error and I also cannot seem to get log output from the GUI when running it like this

Additional Context

Here I tried running the GUI with these parameters:

[github-actions]

To vote for this issue, please add a 👍 emoji to the issue description. Votes in comments are not recorded.

[rklec]

Okay the exception above could be solved when running choco install --force chocolateygui aka reinstalling it, but the window is still non-existant as you can see in the screenshot above.

[WahoYate]

Exactly same issue ! But I've been using Windows 11 for a long time: the problem appeared today.