Winhance Release #5 (version 25.05.05) added in-app version notifications, a fully resizable window, fixes for app installs that were stuck at 66% or 78%, and improved Windows Explorer restart handling. This release shipped on May 7, 2025 — newer versions of Winhance are available on the downloads page.
Applies to: Winhance 25.05.05 on Windows 10 (22H2) and Windows 11 | Last updated: May 4, 2026
Note: This is a historical release post for Winhance Release #5 from May 2025. For the latest features, see the main Winhance guide, the major improvements update, and the Release #24 new settings post. Always grab the most recent build from winhance.net.
Key Takeaways
- Built-in version notifications — Winhance prompts you when a new build is available, so you no longer have to check manually
- Fully resizable window that scales to 90% of the screen by default and reflows into a single column on smaller displays
- App install hang fixed — installs no longer freeze at 66% or 78% during WinGet-based deployments
- Theme and taskbar cleanup no longer freezes — Explorer process restarts are handled cleanly
- Config import is more reliable — settings now apply to the correct state every time, not only when a change is detected
Quick Steps to Update
- Go to winhance.net and download the latest installer
- Run the installer — no need to uninstall an earlier version first
- Launch Winhance as administrator
- Once on Release #5 (or later), Winhance will notify you about future updates automatically
Requirements
- Windows 10 (22H2, 64-bit) or Windows 11
- Administrator privileges
- Internet connection (for downloading and installing external software)
Why Release #5 Mattered
If you have been using Winhance to keep Windows 11 debloated and optimized, Release #5 was the version that fixed the most-reported issues from the first four releases. The new versioning system means you no longer need to revisit the downloads page to check for updates — Winhance will tell you when there is something new.
The window-sizing rework also made Winhance practical on lower-resolution laptops where the original layout was clipped off-screen. Both changes were direct responses to user feedback on GitHub.
What Changed in Winhance Release #5
Versioning Support
The biggest addition in Release #5 was an in-app version check. Once you are on 25.05.05 or later, Winhance prompts you to download the next update as soon as one ships.
Versioning only takes effect once you are running 25.05.05. If you are on an older release, you have to grab Release #5 manually from the Winhance downloads page first. After that, future updates are auto-detected.
Improved Window Sizing and Responsiveness
Lower-resolution laptops were the biggest pain point before this release — the Winhance window opened larger than the screen and could not be resized down. Release #5 fixed that:
- The main window now opens at 90% of available screen space
- The window is fully resizable — drag any corner to make it smaller or larger
- UI elements reflow into a single column when the window narrows
App Install Hang Fixed (66% / 78% Stall)
A handful of users reported app installations stalling at 66% or 78% completion. The fix involved three changes:
- Removed unnecessary pre-installation checks that caused the process to stall
- Improved progress reporting during WinGet-based installs
- Apps now reinstall cleanly even if a copy is already on the system
I tested these fixes on both Windows 10 22H2 and Windows 11 24H2 virtual machines before shipping the release.
Cleaner Windows Explorer Restart Handling
Earlier Winhance versions sometimes froze when changing themes or running the taskbar/start menu cleanup, because the Windows Explorer restart was not waited on properly. Release #5 reworked that handling so the following actions no longer stall:
- Changing Windows themes
- Cleaning the taskbar
- Cleaning the start menu
Improved Config File Import
Config import got two improvements. First, Winhance now asks whether you want to clean up the taskbar and start menu when importing a configuration file.
Second, every imported setting is now applied to its correct target state, not just updated when a change is detected. That fixes a quiet bug where a few registry keys were being skipped during config imports.
Code Refactoring and Optimization
Behind the scenes, I refactored several settings modules to remove duplication and improve the overall structure. None of this is visible in the UI, but it makes the codebase easier to extend in future releases.
Where to Go Next
Release #5 was a stability milestone, but Winhance has shipped many releases since. Useful next reads:
- The main Winhance guide — what Winhance does and how to use it
- Winhance v25.05.22 — major improvements
- Winhance Release #24 — new settings overview
- UnattendedWinstall — pair Winhance with a custom answer file for a debloated install from first boot
If Winhance has saved you time, you can support development on Ko-Fi — every contribution funds more development time.
Frequently Asked Questions
Do I need to uninstall the previous version of Winhance before installing Release #5?
No. Just download and run the new installer. It updates the existing installation in place and preserves your settings. This is true of every Winhance release, not only Release #5.
Does Winhance Release #5 work on Windows 10?
Yes. Winhance is primarily developed for Windows 11, but most settings and modules also work on a fully updated Windows 10 22H2. Settings that depend on Windows 11-only features (the new Start menu layout, for example) are skipped or hidden on Windows 10.
How do I check which version of Winhance I am running?
From Release #5 (25.05.05), Winhance does not display the current version directly in the UI — the in-app version banner only appears when a newer build is available. Later releases added a visible version label in the title bar; if you do not see one, you are on Release #5 or earlier and should update from winhance.net.
Does Winhance fully remove News and Interests from the taskbar?
Release #5 still had partial removal because of protected registry keys that resist the standard methods. Newer Winhance releases address this more aggressively — see the Release #24 changelog for the current state.
How can I support Winhance development?
The simplest way is Ko-Fi. Bug reports and pull requests on the Winhance GitHub repository also help — every reproducible report makes the next release better.
