-
-
Notifications
You must be signed in to change notification settings - Fork 317
Description
Please confirm these before moving forward
- I have searched for my issue and have not found a similiar in the Open or Closed issues.
- I have tested that this issue has not been fixed in the latest (beta or stable) release.
- I have checked the Discussions section for solutions.
- This issue is about a bug (if it is not, please use the correct template).
Winhance Version
26.03.06
Windows version, edition, and architecture
Windows 11 Pro 10.0.26200 Build 26200
Describe your issue
I have this issue after updating to the latest version v26.03.06
When I open the application (from start menu or winhance.exe), it launches and after a few seconds of trying to load, the app windows just closes/disappears.
Also I am unable to install winhance app from my machine (tried Add or Remove programs and Winhance.Uninstaller.exe).
Steps to reproduce the issue
- Go to Start menu
- Click on Winhance app
- Click Yes for UAC permission
- Application open up briefly trying to load
- Application disappears (window goes away)
Expected behavior
After launching, the opens to the normal window/GUI
Actual behavior
app closes/quits and the window disappears
Screenshots or Logs (if applicable)
Here is the output from the startup logfile:
[11:19:21.963] [Program] === Application Starting ===
[11:19:21.984] [Program] Args:
[11:19:21.985] [Program] CurrentDirectory: C:\Program Files\Winhance
[11:19:21.985] [Program] BaseDirectory: C:\Program Files\Winhance
[11:19:21.986] [Program] Checking single instance...
[11:19:22.049] [Program] Single instance check passed
[11:19:22.049] [Program] Initializing COM wrappers...
[11:19:22.050] [Program] COM wrappers initialized
[11:19:22.051] [Program] Starting WinUI 3 Application.Start...
[11:19:22.081] [Program] Inside Application.Start callback
[11:19:22.084] [Program] Creating App instance...
[11:19:22.086] [App] App constructor starting
[11:19:22.089] [App] Exception handlers registered
[11:19:22.093] [App] InitializeComponent completed
[11:19:22.093] [Program] App instance created
[11:19:22.220] [App] OnLaunched starting
[11:19:22.221] [App] Building DI host...
[11:19:22.313] [App] DI host built successfully
[11:19:22.314] [App] LogService obtained
[11:19:22.486] [App] LogService.StartLog() called - file logging initialized
[11:19:22.487] [App] Log file path: C:\ProgramData\Winhance\Logs\Winhance_Log_20260307_111922.log
[11:19:22.489] [App] Initializing localization...
[11:19:22.526] [App] Localization initialized
[11:19:22.528] [App] Creating MainWindow...
[11:19:22.560] [MainWindow] Constructor starting...
[11:19:22.667] [MainWindow] InitializeComponent completed
[11:19:22.725] [App] MainWindow created, activating...
[11:19:22.761] [App] MainWindow activated
[11:19:22.761] [App] Initializing theme...
[11:19:22.779] [App] Theme initialized
[11:19:22.780] [App] Starting startup operations...
[11:19:22.781] [MainWindow] StartStartupOperations called
[11:19:22.821] [StartupOrchestrator] Phase 1: Initializing settings registry...
[11:19:22.854] [App] Startup operations kicked off - OnLaunched complete
[11:19:23.041] [MainWindow] NavSidebar_Loaded
[11:19:23.042] [MainWindow] Startup loading in progress, deferring navigation
[11:19:23.249] [StartupOrchestrator] Phase 1: Settings registry initialized
[11:19:23.266] [StartupOrchestrator] Phase 2: User backup config already completed
[11:19:23.269] [StartupOrchestrator] Phase 3: Checking system protection...
[11:19:23.335] [StartupOrchestrator] Phase 3: System protection check done
[11:19:23.336] [StartupOrchestrator] Phase 4: Migrating scripts...
[11:19:23.340] [StartupOrchestrator] Phase 4: Script migration done
[11:19:23.340] [StartupOrchestrator] Phase 5: Checking for script updates...
[11:19:23.353] [StartupOrchestrator] Phase 5: Script update check done
[11:19:23.353] [StartupOrchestrator] All phases complete
[11:19:23.396] [StartupUiCoordinator] CompleteStartupAsync starting
[11:19:23.492] [StartupUiCoordinator] Awaiting SoftwareApps initialization...
Additional context
No response