Winslop WinUI3 – International

Previously built on WinForms now fully rewritten in WinUI 3 (.NET 10). This release marks a significant architectural departure from the Winslop WinForms / .Net Framework version (Legacy). Approximately 50% of the codebase was rewritten from scratch and not just ported.

🚀 Winslop (WinUI3) now speaks German and Français. Most of the app is now fully localizable.

Full honesty, I cheated a little

The new .resw translation files were generated with help from a language model. Right now Im deep in the weeds learning and building around WinUI3, so I chose speed over perfection here. That means some strings may still sound a bit weird, stiff, or slightly cursed.Please dont take it personally.
Im sure people with a better feel for proper wording will jump in sooner or later and help clean up the remaining AI-flavored nonsense. Until then, this gets the job done and gets Winslop one big step closer to proper localization. Also,the full WinUI3 codebase will be pushed to the repository soon

---

If you've been following this project, you already know the drill.
If you're new: welcome to the most overthought Windows tweaker on GitHub 😄

The community poll is still sitting at a near-perfect 50:50.
The Microsoft emails keep coming.
I still havent picked a side.
But I did rewrite about 50% of the codebase, so make of that what you will.

🗳 Still haven't voted? Now's the time:
#36

What’s new

• Language switcher in Settings (English, Deutsch, Francais)
• UI localized: menus, navigation, dialogs, tooltips, search
• 45+ feature names translated
• Log messages and status summaries localized
• Major dialogs translated (restore, migration, donation, plugin manager)

For translators

Want Winslop in your language?

Copy Strings/en-US/Resources.resw into a new locale folder, translate the values, and open a PR.

Guide: LOCALIZATION.md

---

Technical notes

• Fully rebuilt UI: WinUI 3 (Windows App SDK 1.8)
• Migrated from .NET Framework 4.8 (WinForms) to .NET 10 (Preview)
• Mica backdrop, page-cached navigation, MVVM TreeView, plugin manager
• Portable: No installer needed, just unzip and run

Included in the package:
• Winslop.exe (main app)
• Compiled XAML pages (*.xbf)
• Plugins folder (optional)
• .NET 10 runtime (self-contained, no install required)
• Only English language resources
• No MSIX/Store assets

Requirements:
• Windows 10/11 (1809 or newer)
• Windows App SDK Runtime (may need to be installed once)
• No .NET installation needed
• Windows App SDK DLLs (UI framework) needed

Release package:
Winslop-26.03.110.zip
The classic WinForms version is available as a legacy asset Winslop-26.3.31-legacy.zip for download.
The program folder now also includes Winslop.Legacy.exe if you still want to enjoy the classic version

📦 Full release details:
https://github.com/builtbybel/Winslop/releases/tag/26.03.100

Winslop – WinUI3 Release IV

Previously built on WinForms now fully rewritten in WinUI 3 (.NET 10). This release marks a significant architectural departure from the Winslop WinForms / .Net Framework version (Legacy). Approximately 50% of the codebase was rewritten from scratch and not just ported.

🚀 Winslop – WinUI3 Release IV

"I told myself I'd stop after Release III. I lied."

---

So here we are. Release IV.

If you've been following this project, you already know the drill.
If you're new: welcome to the most overthought Windows tweaker on GitHub 😄

Release III was the one where I finally felt like I understood WinUI 3. Release IV is the one where I actually did something useful with that understanding.

The community poll is still sitting at a near-perfect 50:50.
The Microsoft emails keep coming.
I still havent picked a side.
But I did rewrite about 50% of the codebase, so make of that what you will.

🗳 Still haven't voted? Now's the time:
#36

Whats new?

Added

• Keyboard shortcuts for all major menu actions:
  • Ctrl+T – Toggle All
  • Ctrl+Z – Undo last changes
  • F5 – Refresh
  • Ctrl+L – Copy log to clipboard
  • Delete – Clear log
• Zoom support for the Home page > Feature tree (Ctrl+Scroll). So WinUI 3 controls carry significantly more padding and spacing than their WinForms equivalents; a ZoomMode was added as a practical workaround to let users reclaim vertical space on smaller screens
• Context menu on right-click for individual tree nodes: Analyze, Fix, Restore, Help
• Plugin analysis now included in the combined analysis summary dialog
• Combined analysis summary after full inspection showing native features and plugins separately:
  • Windows Features : X of Y OK
  • Plugins : X of Y OK
  • Total : X of Y OK
• Hyperlink to Online Log Inspector directly in the analysis result dialog
• "No plugins selected" message in log when plugin analysis is skipped
• Profile ComboBox with built-in Export, Import, and "Open profiles folder" actions
• [CRITICAL] Search filter respects IsVisible state, so context menu actions (Analyze/Fix/Restore) now correctly skip hidden nodes
• Log output now color-coded by severity using RichTextBlock and not TextBox
  • 🔴 Red – Errors
  • 🟠 Orange – Warnings
  • Gray – Info (theme-sensitive via TextFillColorPrimaryBrush)
• Nav highlight auto-refreshes on Windows light/dark theme switch
• Per-page menu state: Export, Import, Undo, Manage Plugins disabled on non-Features pages
• More options flyout button (⋯) replaces separate Toggle/Undo/Refresh buttons and old log actions ComboBox
• Log actions submenu under More options: Inspect online, Copy, Clear, Log checked/unchecked/summary
• Plugin counters (TotalChecked, IssuesFound) added to PluginManager so it mirrors FeatureNodeManager
• [CRITICAL] UnhandledException + TaskScheduler.UnobservedTaskException handlers to prevent silent crashes

Improved

• Analysis summary moved to end of log (after dialog closes) so auto-scroll always lands at the bottom
• More options menu replaces three separate icon buttons. Should bring a cleaner toolbar, less visual noise
• LogActionsController removed and actions are now wired directly as MenuFlyoutItem handlers, no ComboBox dependency
• Nav buttons theme-aware highlight via NavigationService.UpdateHighlight() so it reacts to live theme changes
• ApplyFilter now iterates item.Children.ToList() snapshot to prevent collection-modified crashes
• ApplySearch guards against _rootItems == null during page initialization
• Analysis dialog now uses a StackPanel content with a HyperlinkButton instead of plain string

Removed

• Log actions ComboBox (comboLogActions) is eplaced by flyout submenu
• LogActionsController class is no longer needed
• Separate Toggle All / Undo / Refresh buttons is consolidated into More options flyout
• Intermediate analysis dialog shown before plugin analysis are replaced by single combined dialog after both complete

Fixed

• Context menu Analyze/Fix/Restore now respects active search filter (IsVisible check added to AnalyzeFeature, FixFeature, RestoreFeature)
• Plugin nodes correctly skipped during native feature analysis and vice versa
• Summary log entry no longer appears before plugin results

Migration note

WinForms allowed direct, compact tree manipulation via TreeNode.ForeColor, NodeFont, and AfterCheck –
all handled imperatively in a few lines. WinUI 3 has no equivalent built-in tree node model,
requiring a full custom FeatureTreeItem ViewModel with INotifyPropertyChanged, XAML value converters,
a RichTextBlock-based logger, and a NavigationService to replicate what was previously trivial.

Additionally, this project served as a hands-on migration from C# 7.3 to C# 14
adopting modern patterns including:

• record types and init-only properties
• Nullable reference types (string?, Button[]?)
• Switch expressions (status switch { ... })
• Target-typed new() and collection expressions
• is not null pattern matching
• Top-level using directives and file-scoped namespaces

For anyone coming from the WinForms version: the concepts are the same,
the implementation is almost entirely new.

Technical notes

• Fully rebuilt UI: WinUI 3 (Windows App SDK 1.8)
• Migrated from .NET Framework 4.8 (WinForms) to .NET 10 (Preview)
• Mica backdrop, page-cached navigation, MVVM TreeView, plugin manager
• Portable: No installer needed, just unzip and run

Included in the package:
• Winslop.exe (main app)
• Compiled XAML pages (*.xbf)
• Plugins folder (optional)
• .NET 10 runtime (self-contained, no install required)
• Only English language resources
• No MSIX/Store assets

Requirements:
• Windows 10/11 (1809 or newer)
• Windows App SDK Runtime (may need to be installed once)
• No .NET installation needed
• Windows App SDK DLLs (UI framework) needed

Release package:
Winslop-26.03.100.zip
The classic WinForms version is available as a legacy asset Winslop-26.3.31-legacy.zip for download.
The program folder now also includes Winslop.Legacy.exe if you still want to enjoy the classic version

Winslop – WinUI3 Release III

Want to see a really ugly app? 😄https://t.co/Epr9a14vSY#Winslop #WinUI3 #Microsoft #app pic.twitter.com/izVnCvw6vG

— Belim (@builtbybel) March 10, 2026

🚀 Winslop – WinUI3 Release III

So… here we go again.

This is now the third WinUI3 release of Winslop.
And yes even though Im still not entirely used to this whole stack, I somehow keep going.

The community poll is currently sitting at almost a perfect 50:50 split between the classic WinForms version and the new WinUI build. At the same time, I've been receiving quite a few emails politely suggesting that I should fully embrace the Microsoft way and focus on WinUI going forward.

Coincidence? Microsoft employees? I'm not saying anything… 😄

🗳 Help decide Winslop's future.
Please join the poll and cast your vote here:
#36

My overall stance on this whole journey is already written down here:
#36 (comment) and https://github.com/builtbybel/Winslop/blob/main/CHANGELOG.md

But after spending more time with the framework, this is the first release where I feel I was actually able to properly dissect and refine the UI.

---

UI Changes

One of the biggest complaints was space usage.
WinUI loves padding. A lot of padding.

So this release introduces a more compact layout:

• Navigation moved from the top to a left sidebar
• More dense controls and spacing

Anything else (flyout controls) simply didnt make much sense within the WinUI layout model.

---

New Feature "Profiles"

Winslop can now save configuration profiles.

In the Home tab you can now:

• Save your current Winslop configuration
• Load saved profiles anytime via the dropdown menu

This makes it much easier to switch between different setups.

Fixes

• Fixed profile import/export when running with admin rights (#39)
  The WinUI3 FilePicker failed to initialize correctly in elevated contexts.

---

⚖️ The Experiment Continues

So yes, the WinUI experiment continues.
Whether Winslop ultimately becomes a modern Windows 11-style tool or remains a lean retro power utility is still up for debate.
For now, both worlds coexist.
And honestly… that might not be the worst outcome.

Release package:
Winslop-26.03.60-win-x64.zip
The classic WinForms version is available as a legacy asset Winslop-26.3.31-legacy.zip for download.
The program folder now also includes Winslop.Legacy.exe if you still want to enjoy the classic version

🗳 Help decide Winslop's future.
Please join the poll and cast your vote here:
#36

Winslop – WinUI3, Round Two

++++ Winslop – The WinUI3 Experiment Continues – Migration: WinForms > WinUI 3 (.NET 10) +++

Well… yesterdays post was written at peak frustration.

But I didn't want to let it go.
So I sat down, kept pushing, and after one long night and half a day more, I actually managed to migrate Winslop from its classic WinForms / .NET Framework base to a working WinUI 3 version.
Was it fun?
About 90% of it was a miserable experience.
But, and this is the annoying part, the remaining 10% was actually kind of satisfying. Once I got deeper into it, things slowly started clicking, I got faster, more confident, and piece by piece the app began to come together.

That still does not mean I'm suddenly a fan of this UI stack.

But the port now exists, and that means theres something real to look at and judge

So heres the deal:
Try it, break it, judge it, and let me know what you think.

Because this is probably the point where Winslop needs to choose its path:

• Go down the modern Microslop road with WinUI 3
• Or stay what it has always been at heart: a classic retro desktop app lean, fast, efficient, and without half the universe attached to a button

🗳 Help decide Winslop's future.
Please join the poll and cast your vote here:
#36

Below is yesterdays slightly emotional write-up, preserved for historical accuracy.

Yesterday's WinUI meltdown

Read more

🎉 So after some experiments, frustrations, and a few choice words directed at Microslop's UI stack, Winslop ultimately stays true to its roots.

I need to vent about WinUI.
I moved Winslop from .NET Framework 4.8.1 to .NET 10 first and honestly, that still felt like half a solution.
So I went straight for the next "logical" step: a WinUI conversion

Here's the thing: I'm a minimalist. I like lean code, direct control, and software that doesn't require a small religion to maintain. That's why, in the Microsoft .NET ecosystem, I still stick with WinForms. Without WinForms, I probably wouldn't even keep a second OS partition just to run Windows 11. WinForms is one of the few things in the whole stack that still feels... sane.

So, WinUI. "Modern Windows 11 UI experience", right? (Screenshot below)

After about five hours, I had a working MainWindow.xaml and a connected feature page that sort of worked. But the scope and ceremony were insane. To me it felt like migrating a classic VB6 application to VB.NET back in the day. You know, back before Microsoft also decided to slowly suffocate VB.NET for sport.

And I'm sorry, but why is everything so Microslop?
There was a time when you could build a full Windows app with a few forms and some logic. Now it feels like you need three frameworks, four patterns, and a ceremonial XAML ritual just to show a button. We managed to land humans on the moon in 1969 with computers weaker than a modern toaster — but in 2026 a simple Windows UI apparently requires half the Microsoft ecosystem and a small architectural thesis.

F*ckkkk... Like… no, seriously. I'm not doing this. WinUI is a monster. It's not "modern", it's unbounded complexity disguised as progress.
It's a stack that constantly demands more structure, more glue, more patterns, more XAML rituals until your simple little utility starts looking like a corporate enterprise app with a thousand moving parts.

Sure, I could have made it easy and let a coding agent brute-force the conversion. But what's the point?
Programming is something I genuinely enjoy. It relaxes me. But not like this. I'm not 19 anymore, chasing the Silicon Valley fantasy of a multimillion-dollar startup fueled by vibe-coding and buzzwords. I want to build software, not manage a labyrinth.

And honestly, I should have known better.

If you want to understand what WinUI is, just look at the "fancy" Windows 11 Explorer:
pretty? maybe. but sluggish, inconsistent, and occasionally bizarre. It's the perfect demo of the WinUI promise and the WinUI reality.

The slow parts are WinUI 3, and the buggy parts are Win32

Microslop in a nutshell.
No wonder 80% of Microslop apps are web apps now — even those often feel faster than WinUI.

So yeah. Sorry, folks. Winslop stays a classic WinForms app.
I'm not spending my limited time on this kind of bullshit.

Whats new?

Winslop v26.03.45 – Migration: WinForms > WinUI 3 (.NET 10)
• Fully rebuilt UI: WinUI 3 (Windows App SDK 1.8)
• Migrated from .NET Framework 4.8 (WinForms) to .NET 10 (Preview)
• Mica backdrop, page-cached navigation, MVVM TreeView, plugin manager
• Portable: No installer needed, just unzip and run

Included in the package:
• Winslop.exe (main app)
• Compiled XAML pages (*.xbf)
• Plugins folder (optional)
• .NET 10 runtime (self-contained, no install required)
• Only English language resources
• No MSIX/Store assets

Requirements:
• Windows 10/11 (1809 or newer)
• Windows App SDK Runtime (may need to be installed once)
• No .NET installation needed
• Windows App SDK DLLs (UI framework) needed

Release package:
Winslop-26.03.45.zip
The classic WinForms version is available as a legacy asset Winslop-26.3.31-legacy.zip for download.
The program folder now also includes Winslop.Legacy.exe if you still want to enjoy the classic version

🗳 Help decide Winslop's future.
Please join the poll and cast your vote here:
#36

Winslop – WinUI3 Rebuild

++++ Winslop v26.03.41 – Migration: WinForms > WinUI 3 (.NET 10) +++

Well… yesterdays post was written at peak frustration.

But I didn't want to let it go.
So I sat down, kept pushing, and after one long night and half a day more, I actually managed to migrate Winslop from its classic WinForms / .NET Framework base to a working WinUI 3 version.
Was it fun?
About 90% of it was a miserable experience.
But, and this is the annoying part, the remaining 10% was actually kind of satisfying. Once I got deeper into it, things slowly started clicking, I got faster, more confident, and piece by piece the app began to come together.

That still does not mean I'm suddenly a fan of this UI stack.

But the port now exists, and that means theres something real to look at and judge

So heres the deal:
Try it, break it, judge it, and let me know what you think.

Because this is probably the point where Winslop needs to choose its path:

• Go down the modern Microslop road with WinUI 3
• Or stay what it has always been at heart: a classic retro desktop app lean, fast, efficient, and without half the universe attached to a button

🗳 Help decide Winslop's future.
Please join the poll and cast your vote here:
#36

Below is yesterdays slightly emotional write-up, preserved for historical accuracy.

Yesterday's WinUI meltdown

🎉 So after some experiments, frustrations, and a few choice words directed at Microslop's UI stack, Winslop ultimately stays true to its roots.

I need to vent about WinUI.
I moved Winslop from .NET Framework 4.8.1 to .NET 10 first and honestly, that still felt like half a solution.
So I went straight for the next "logical" step: a WinUI conversion

Here's the thing: I'm a minimalist. I like lean code, direct control, and software that doesn't require a small religion to maintain. That's why, in the Microsoft .NET ecosystem, I still stick with WinForms. Without WinForms, I probably wouldn't even keep a second OS partition just to run Windows 11. WinForms is one of the few things in the whole stack that still feels... sane.

So, WinUI. "Modern Windows 11 UI experience", right? (Screenshot below)

After about five hours, I had a working MainWindow.xaml and a connected feature page that sort of worked. But the scope and ceremony were insane. To me it felt like migrating a classic VB6 application to VB.NET back in the day. You know, back before Microsoft also decided to slowly suffocate VB.NET for sport.

And I'm sorry, but why is everything so Microslop?
There was a time when you could build a full Windows app with a few forms and some logic. Now it feels like you need three frameworks, four patterns, and a ceremonial XAML ritual just to show a button. We managed to land humans on the moon in 1969 with computers weaker than a modern toaster — but in 2026 a simple Windows UI apparently requires half the Microsoft ecosystem and a small architectural thesis.

F*ckkkk... Like… no, seriously. I'm not doing this. WinUI is a monster. It's not "modern", it's unbounded complexity disguised as progress.
It's a stack that constantly demands more structure, more glue, more patterns, more XAML rituals until your simple little utility starts looking like a corporate enterprise app with a thousand moving parts.

Sure, I could have made it easy and let a coding agent brute-force the conversion. But what's the point?
Programming is something I genuinely enjoy. It relaxes me. But not like this. I'm not 19 anymore, chasing the Silicon Valley fantasy of a multimillion-dollar startup fueled by vibe-coding and buzzwords. I want to build software, not manage a labyrinth.

And honestly, I should have known better.

If you want to understand what WinUI is, just look at the "fancy" Windows 11 Explorer:
pretty? maybe. but sluggish, inconsistent, and occasionally bizarre. It's the perfect demo of the WinUI promise and the WinUI reality.

The slow parts are WinUI 3, and the buggy parts are Win32

Microslop in a nutshell.
No wonder 80% of Microslop apps are web apps now — even those often feel faster than WinUI.

So yeah. Sorry, folks. Winslop stays a classic WinForms app.
I'm not spending my limited time on this kind of bullshit.

Whats new?

Winslop v26.03.40 – Migration: WinForms > WinUI 3 (.NET 10)
• Fully rebuilt UI: WinUI 3 (Windows App SDK 1.8)
• Migrated from .NET Framework 4.8 (WinForms) to .NET 10 (Preview)
• Mica backdrop, page-cached navigation, MVVM TreeView, plugin manager
• Portable: No installer needed, just unzip and run

Included in the package:
• Winslop.exe (main app)
• Compiled XAML pages (*.xbf)
• Plugins folder (optional)
• .NET 10 runtime (self-contained, no install required)
• Only English language resources
• No MSIX/Store assets

Requirements:
• Windows 10/11 (1809 or newer)
• Windows App SDK Runtime (may need to be installed once)
• No .NET installation needed
• Windows App SDK DLLs (UI framework) needed

Release package:
Winslop-26.03.41.zip
The classic WinForms version is available as a legacy asset Winslop-26.3.31-legacy.zip for download.

🗳 Help decide Winslop's future.
Please join the poll and cast your vote here:
#36

Winslop 26.3.31

🎉So after some experiments, frustrations, and a few choice words directed at Microslop*s UI stack, Winslop ultimately stays true to its roots.

I need to vent about WinUI.
I moved Winslop from .NET Framework 4.8.1 to .NET 10 first and honestly, that still felt like half a solution.
So I went straight for the next "logical" step: a WinUI conversion

Heres the thing: I'm a minimalist. I like lean code, direct control, and software that doesn't require a small religion to maintain. Thats why, in the Microsoft .NET ecosystem, I still stick with WinForms. Without WinForms, I probably wouldn't even keep a second OS partition just to run Windows 11. WinForms is one of the few things in the whole stack that still feels...sane.

So, WinUI. "Modern Windows 11 UI experience", right? (Screenshot below)

After about five hours, I had a working MainWindow.xaml and a connected feature page that sort of worked. But the scope and ceremony were insane to me it felt like migrating a classic VB6 application to VB.NET back in the day. You know, back before Microsoft also decided to slowly suffocate VB.NET for sport

And I'm sorry, but why is everything so Microslop?
There was a time when you could build a full Windows app with a few forms and some logic. Now it feels like you need three frameworks, four patterns, and a ceremonial XAML ritual just to show a button. We managed to land humans on the moon in 1969 with computers weaker than a modern toaster but in 2026 a simple Windows UI apparently requires half the Microsoft ecosystem and a small architectural thesis

F*ckkkk...Like… no, seriously. Im not doing this. WinUI is a monster. It's not "modern", its unbounded complexity disguised as progress. Its a stack that constantly demands more structure, more glue, more patterns, more XAML rituals until your simple little utility starts looking like a corporate enterprise app with a thousand moving parts

Sure, I could have made it easy and let a coding agent brute-force the conversion. But whats the point?
Programming is something I genuinely enjoy. It relaxes me. But not like this. I'm not 19 anymore, chasing the silicon-valley fantasy of a multimillion-dollar startup fueled by vibe-coding and buzzwords. I want to build software, not manage a labyrinth

And honestly, I should have known better.

If you want to understand what WinUI is, just look at the "fancy" Windows 11 Explorer
pretty? maybe, but sluggish, inconsistent, and occasionally bizarre. Its the perfect demo of the WinUI promise and the WinUI reality.

The slow parts are WinUI 3, and the buggy parts are Win32

Microslop in a nutshell.
No wonder 80% of Microslop apps are web apps now even those often feel faster than WinUI.

So yeah. Sorry, folks. Winslop stays a classic WinForms app.
Im not spending my limited time on this kind of bullshit

What's new

*This release replaces the previous 0.60 development version and marks the first stable build after a rather intense modernization phase.

• Much faster startup (~2×): Removed a duplicate initialization that was running twice
• Apps tab refactor: Replaced WinRT API calls with PowerShell-based queries for improved reliability and compatibility
• Smoother UI: reduced Feature tree redraws to prevent some flickering
• Cleaner event handling: merged duplicate selection handlers
• Fixed: Corrected swapped values in VisualFX so apply/undo now behaves as intended

Download

Version	File	Type	Download
26.3.31	Winslop-26.3.31.zip	Ready-to-use binary	Download

❤️ Support Development

If Winslop has helped you, consider supporting its continued development.
Every bit helps keep the project alive and improving. 🙏💌☕

👉 Donate here

Winslop 26.03.22

🎉 Major Update – First Stable Release

Warning

Unofficial domain notice: I do not own or operate winslop.com and I'm not affiliated with whoever registered it.
Even if it currently redirects to this GitHub repo, a third-party domain can be changed at any time (phishing, fake releases, malware links).
My only official pages are on GitHub: github.com/builtbybel/ (repo + releases).
Download Winslop only from GitHub Releases.

What's new

This release replaces the previous 0.60 development version and represents the first stable major update

• Improved: Install tab refined and improved. It now loads and displays Winget apps with available updates during initialization
• Improved: Winget install functionality moved to plugins; the winget-apps.ini can now be updated anytime via Main Menu > Manage Plugins
• Added: Feature to disable Silent App Installation (prevents apps from being installed automatically in the background)
• Improved: Feature to disable Tailored Experiences (prevents Microsoft from using diagnostic data for personalized tips and suggestions). Tailored Experiences feature now also applies policy-level settings for stronger enforcement
• Improved: Feature to disable suggested content in the Settings app
• Added: Feature to disable Windows Spotlight rotating images on the lock screen
• Added: Feature to disable Lock Screen slideshow suggestions
• Added: Feature to disable Start menu app launch tracking
• Added: Feature to disable Online Speech Recognition services
• Added: Feature to disable Narrator online services
• Improved: Feature to limit Windows diagnostic data to required level only. Diagnostic data feature with expanded registry coverage for more consistent telemetry control
• Improved: Several privacy features now apply multiple registry values to ensure settings remain enforced
• Improved: Updated naming of privacy features to better reflect recommended configuration states
• Improved: UI modernized in several areas, including a new hamburger menu replacing the classic Windows 95/98-style start menu

Download

Version	File	Type	Download
26.3.22	Winslop-26.3.22.zip	Ready-to-use binary	Download

Important:
Download the file listed above. Do not use the "Source code (zip)" option (that is only for developers).

Instructions:

1. Download Winslop-Version.zip
2. Extract the zip file
3. Run Winslop.exe

❤️ Support Development

If Winslop has helped you, consider supporting its continued development.
Every bit helps keep the project alive and improving. 🙏💌☕

👉 Donate here

Winslop 26.03.30 – The .NET 10 Release

🎉 Major Release: .NET 10 Migration

What's New

• .NET 10 Migration: Full move to modern .NET (C# 14) with a modernized, SDK-style project setup and overall performance improvements
  Heads-up: this inevitably loses a bit of the classic Winslop/WinForms retro charm (look & feel, packaging, some UI behavior). If we want to move forward, its the trade-off
• Native Dark Mode: System theme detection with smooth light/dark switching
• PowerShell SDK Updated: Bumped to 7.5.4
• Versioning Improvements: Cleaner, more reliable version management
• Modernized project structure with SDK-style
• Numerous Improvements: Better stability, improved async behavior, and a generally modernized codebase

Please try this version and let me know how it works for you. Your feedback will help decide which direction Winslop should take going forward.

Download & Installation

Requirements: .NET 10 Desktop Runtime (x64)

Download

Version	File	Runtime	Type	Download
26.03.30	Winslop-26.03.30.zip	.NET 10 (Modern)	Ready-to-use binary	Download
26.3.23	Winslop-26.3.23-Legacy.zip	.NET Framework 4.8	Legacy build	Download

The .NET Framework 4.8 build is provided for compatibility and retains the classic Winslop look and behavior.
The .NET 10 build is the modern version with improved performance and native dark mode support.

❤️ Support Development

If Winslop has helped you, consider supporting its continued development.
Every bit helps keep the project alive and improving. 🙏💌☕

👉 Donate here

Winslop 26.03.20

Winslop 26.03.20 is out!
- Remove ALL the slop
- Extend it with plugins
- Built-in full Winget app installer
Some cleanups just feel personal😏https://t.co/O5G730MUsh#Windows11 #microslop #winslop #DevTools #app pic.twitter.com/mhs4WrXZtd

— Belim (@builtbybel) March 2, 2026

🎉 Major Update – First Stable Release

Warning

Unofficial domain notice: I do not own or operate winslop.com and I'm not affiliated with whoever registered it.
Even if it currently redirects to this GitHub repo, a third-party domain can be changed at any time (phishing, fake releases, malware links).
My only official pages are on GitHub: github.com/builtbybel/ (repo + releases).
Download Winslop only from GitHub Releases.

What's new

This release replaces the previous 0.60 development version and represents the first stable major update

Added

• Integrated Winget Install Center for managing apps directly via Windows Package Manager
• Bulk install / upgrade / uninstall for selected applications
• System inspection via winget list and winget upgrade to detect installed apps and available updates
• Category filtering, live search, and quick toggles: Installed only / Updates only

Improved

• Optimized the "Disable Bing Search Results" feature
• Numerous UI improvements and small modernizations

Note: Application list parsed and adapted from the WinUtil project by Chris Titus Tech

Download

Version	File	Type	Download
26.3.20	Winslop-26.3.20.zip	Ready-to-use binary	Download

Important:
Download the file listed above. Do not use the "Source code (zip)" option (that is only for developers).

Instructions:

1. Download Winslop-26.3.20.zip
2. Extract the zip file
3. Run Winslop.exe

Winslop 26.02.02

🎉 Major Update – First Stable Release

Warning

Unofficial domain notice: I do not own or operate winslop.com and I'm not affiliated with whoever registered it.
Even if it currently redirects to this GitHub repo, a third-party domain can be changed at any time (phishing, fake releases, malware links).
My only official pages are on GitHub: github.com/builtbybel/ (repo + releases).
Download Winslop only from GitHub Releases.

What's new

This release marks the first stable milestone of the project and introduces a new versioning scheme.

Changed: Versioning scheme updated from 0.x to date-based format YY.MM.Patch
New format example: 26.02.01
Patch number increases with each release within the same month

This release replaces the previous 0.60 development version and represents the first stable major update

• Added OS applicability system to prevent unsupported features from running on incompatible Windows versions. Non-applicable features are automatically skipped during Analyze/Fix/Restore operations
• Added even more robust Windows version detection (incl. UBR like 26200.7921) and helpers for Windows 10/11 checks
• Added: Taskbar: Always show all system tray icons (Windows 10)
• Added: Taskbar: Remove “Meet Now” button from system tray (Windows 10)
• Added: Taskbar: Disable Widgets (Windows 11)
• Added: Taskbar: Disable News & Interests (Windows 10)
• Added: Taskbar: Make taskbar small (Windows 10)
• Added: Action: Clean Taskbar (removes all pinned items; clears Taskband\Favorites)
• Improved: Analysis/Fix/Restore now skip non-applicable features to avoid invalid changes
• Changed: Versioning scheme updated from 1.x.x to date-based format YY.MM.Patch (e.g. 26.02.01)
• Added a Select profile... placeholder to prevent auto-loading on startup and ensure profiles are only applied when explicitly chosen
• Reduced memory usage and improved overall resource efficiency
• Updated docs
• Minor bug fixes

Download

Version	File	Type	Download
26.02.02	Winslop-26.2.2.zip	Ready-to-use binary	Download

Important:
Download the file listed above. Do not use the "Source code (zip)" option (that is only for developers).

Instructions:

1. Download WinslopApp-26.2.2.zip
2. Extract the zip file
3. Run Winslop.exe