I have the following problem:
when running CompactGUI 4.0.0 beta 10 on Windows 10 22H2 with .NET 10.0.11 Desktop Runtime installed.
The window is white, but I can:
- move & resize it;
- close, maximize it when I click where the window butttons should be;
- and there is a small spot (visible on-screenshot) where my cursor becomes a hand;
so I guess the GUI is kinda active - just not shown.
I deleted the "%LOCALAPPDATA%\IridiumIO" folder beforehand.
"%LOCALAPPDATA%\IridiumIO\CompactGUI\log-20260906.log" now just shows:
2026-09-06T08:28:00.8388462+02:00 [INF] Watcher started.
2026-09-06T08:28:00.9062002+02:00 [INF] Logging Level: Information
2026-09-06T08:28:01.4500733+02:00 [INF] Application started. Press Ctrl+C to shut down.
2026-09-06T08:28:01.4502313+02:00 [INF] Hosting environment: "Production"
2026-09-06T08:28:01.4502541+02:00 [INF] Content root path: "C:\Users\Tarnyko\Desktop"
Event Viewer -> Application shows nothing.
Creating a new user account changes nothing.
Using the "Mono" (with bundled .NET) version changes nothing.
The same combination of software runs fine on Windows 11 24H2.
Downgrading to 3.8 on Windows 10 22H2 runs fine.
Idea: the app or its UI code may silently rely on something specific to newer versions of Windows.
I have the following problem:
when running CompactGUI 4.0.0 beta 10 on Windows 10 22H2 with .NET 10.0.11 Desktop Runtime installed.
The window is white, but I can:
so I guess the GUI is kinda active - just not shown.
I deleted the "%LOCALAPPDATA%\IridiumIO" folder beforehand.
"%LOCALAPPDATA%\IridiumIO\CompactGUI\log-20260906.log" now just shows:
Event Viewer -> Application shows nothing.
Creating a new user account changes nothing.
Using the "Mono" (with bundled .NET) version changes nothing.
The same combination of software runs fine on Windows 11 24H2.
Downgrading to 3.8 on Windows 10 22H2 runs fine.
Idea: the app or its UI code may silently rely on something specific to newer versions of Windows.