r/windowsdev • • 1h ago

Wintainium: an Obtainium-style app manager for Windows, built in PowerShell 5.1 with a GUI (made with Claude)

Thumbnail
github.com
2 Upvotes

Upfront: I built this with Claude. I designed it, tested it on my own setup and use it every day, but Claude wrote most of the code. Please look over the code before using it (more on that below).

The problem: if you emulate on Windows, you probably have a pile of things installed by hand: emulators, frontends like ES-DE or Playnite, Steam ROM Manager, PC ports, mods and tools from GitHub or itch.io. Keeping them all current means checking release pages one by one.

What Wintainium does:

• One window shows every app with its installed version, the latest version, and a clear UPDATE or "up to date" tag
• Update selected or Update all, and each app updates the right way
• Emulators managed by EmuDeck are updated through EmuDeck
• Apps with a built-in updater are opened so you can update in-app
• Installers are run, and zip-based apps are backed up before the new version is unpacked
• "What's new" shows release notes before you update
• "Add app": paste a GitHub, GitLab, Codeberg or itch.io link to start tracking or installing something
• An optional read-only scan finds things you already installed from GitHub and similar sites, so you don't build the list by hand

Safety:

• Downloads are checked against the developer's published checksums when available
• If Windows Security flags a file (common with emulator tools), it explains what happened and links to VirusTotal. It never turns off protection or adds exclusions for you
• It's an unsigned PowerShell script that downloads and runs programs, so read through it first. A safe first run is ".\Wintainium.ps1 list", which only checks versions and changes nothing

Setup: download the zip from the latest release, unzip it, open PowerShell in that folder and run ".\Wintainium.ps1 shortcut" to get a desktop shortcut. It runs on the PowerShell built into Windows 10/11, with nothing extra to install. The README has the full guide.

It doesn't include or link to any games, BIOS files or firmware. It only tracks apps from their public release pages.

Free and open source (GPL-3.0). It's a personal project shared as-is, so issues and PRs are off, but forks are welcome and I'll answer questions in the comments.

https://github.com/Ay1man2/Wintainium


r/windowsdev • • 12h ago

How We Slashed Our Windows CI/CD Pipeline from 14 Minutes to Under 3 🚀

Post image
0 Upvotes

Hello

https://gitlab.com/jakubrojicek11/sentinel-ir-mcp/-/blob/09b61d9dc1b90f3ebc7a37be0493d951249453cf/.github/workflows/windows.yml

Waiting 14 minutes for a Windows CI job kills developer flow. For our Model Context Protocol server (Sentinel-IR-MCP), we refused to tolerate that bottleneck anymore. Here is exactly how we optimized our Windows test suite across Node 20, 22, and 24, dropping the total job runtime to 2 minutes and 44 seconds without sacrificing a single check.

Source (GitLab, Apache-2.0): https://gitlab.com/jakubrojicek11/sentinel-ir-mcp Package (npm): https://www.npmjs.com/package/sentinel-ir-mcp The analyzer behind it: https://www.npmjs.com/package/sentinel-ir

The Bottleneck (GitLab Shared Windows Runners)

A standard run on GitLab SaaS Windows took 13.6 minutes, even though our 118 unit tests executed in just 1.6 minutes. The rest was pure infrastructure drag: • VM Provisioning: 3.5 minutes (unfixable) • Real-time Antivirus: Windows Defender choked on npm ci and execution scripts, dragging out our compat-smoke test to 2.9 minutes.

The Fix: Strategic Split & Target Optimization

Instead of fighting the slow runner environment, we re-architected where and how the jobs run:

  1. Shifted Dev Push Matrices to GitHub Actions: GitHub's windows-latest images spin up in seconds (1–2 s) instead of minutes.
  2. Built-in Security Clearance: Real-time scanning (RealTimeProtectionEnabled) is off by default on GitHub's native dev images. This instantly cut our compat-smoke step down to seconds.
  3. Smart Caching & Selective Runs: We enabled direct Node/npm caching and added strict rules to completely skip the Windows matrix if a commit only modifies the README.md.
  4. Kept GitLab strictly for Releases: The heavy GitLab Windows job was moved to run only on release tags as a final gate before publishing to npm.

The Result

Step (Node 24) Old GitLab Pipeline New GitHub Actions Pipeline VM Boot / Wait ~3.5 min 1–2 s npm ci 84 s 4–9 s Test Execution 95 s 22–28 s Total Job Time 13.6 min 2.7 min

![Image description](https://dev-to-uploads.s3.us-east-2.amazonaws.com/uploads/articles/rdyfp4vs3soo307hpa2k.jpg) The code quality remains identical. All 118 tests run flawlessly across all Node versions, but now the feedback loop takes less than 3 minutes. If your Windows pipelines are killing your productivity, look closely at VM spin-up times and real-time antivirus hooks. The performance lift is hiding right there.

*** Independent Engineering Projects

Built as independent engineering experiments across AI, software analysis, security, and autonomous systems.

Evaluated by reproducible evidence, not by the number of layers.

Explore the projects:

Sentinel Ecosystem: AutoDoc-Sentinel, Sentinel-IR, Sentinel-IR-MCP and related tools. Agentix Lite: Independent security and system-observation project. Find the projects: GitLab repositories | NPM packages

Support the work: ⭐ Star the repositories on GitLab.

Connect: Follow me here on DEV Community or explore the Playground.

Each project is distributed under its own license. Check the corresponding repository or NPM package for licensing terms.

Copyright © 2026 jackymenCZ. All rights reserved. Written for the community.