How to Update Velin on Windows (It's Manual for Now, Here's Why)
Auto-updates are one of those things nobody thinks about — until they break. On macOS, Velin quietly fetches and installs updates in the background. On Windows? For now, you have to do it yourself. One click, but yourself.
I want to explain why, exactly what to do, and what I'm doing about it.
Can't Find the App? Search for "V Module"
If you've updated recently and suddenly can't find Velin anywhere — it didn't disappear. It just looks different now.
The app was renamed to V Module in your taskbar, Start menu, and anywhere Windows shows app names. If you search for "Velin" and nothing comes up, search for V Module instead and it'll be right there.
This is intentional, and it's actually good news for you. If you're using Velin during a live interview, an online exam, or any kind of screen-shared session, the last thing you want is an app called "Velin AI" sitting in your taskbar. That name answers every question someone might ask about it before they even ask it.
V Module looks like a dev tool. Nobody questions a dev tool. You're in an interview, you have a bunch of stuff open — V Module is just one of them. That's the point.
Your settings, API keys, notes, and custom prompts are all exactly where you left them. Nothing was wiped. Only the name visible to the outside world changed.
Why Windows Updates Are Manual Right Now
Here's the honest version: Windows has a security requirement that macOS doesn't enforce the same way. For an app to silently download and swap in a new version of itself, Windows needs the installer to be digitally signed — cryptographically verified by a trusted certificate authority.
The Velin Windows build isn't signed yet.
Not because I skipped it carelessly. Code signing certificates cost money (a real amount, not "buy me a coffee" money), require identity verification with a CA, and have to be wired into the entire release pipeline before they work reliably. It's on my roadmap. I'd rather ship a working manual update flow than ship a broken auto-update that silently crashes and leaves you on an old version.
When I tried to make auto-update work on an unsigned Windows build, the error was brutal: the updater was trying to stage files into a path that only existed on my CI runner — not on your machine. Every Windows user who triggered a download would just get an error. That's worse than manual.
So: manual it is, until signing is done.
How to Update Velin on Windows
This takes about two minutes.
Step 1. Open V Module (or Velin — same app). It checks for updates in the background. If there's something new, you'll see a notification popup. Or go to Settings → Updates to check manually.
Step 2. When an update is available, you'll see a "Download from Website" button instead of the usual "Download Now." Click it. It'll open your browser and take you to the download page, which will auto-detect Windows and start the download.
Step 3. Run the downloaded installer (.exe). You do not need to uninstall the old version first. Install right over it.
Step 4. Open V Module. You're on the new version.
That's it. Everything is preserved — your API keys, your notes, your custom prompts, your settings. The installer doesn't touch any of that. It just swaps the app binary.
Staying Updated Matters More Than You Think
If you're using Velin for interviews or exams, you want the latest version. New releases fix bugs, improve AI response quality, and occasionally ship features that make a real difference when you're under pressure and need an answer fast.
The app will always tell you when there's a new version. You won't have to remember to check. When you see that notification, two minutes to install it is worth it.
What's Coming
Proper code signing for Windows, proper auto-update. Same flow macOS users already have: app downloads in the background, you get a prompt to restart, done. I want to get there.
Until then — one click, download the installer, run it, you're done. I know it's not invisible. I'm working on it.