Windows · Neovim · Zero config

Neovim for Windows,
done right.

LazyVim is incredible. But it assumes you're on Unix. WIM is what LazyVim would be if Windows was a first-class citizen — every edge case pre-solved, two commands to working.

Quick install · PowerShell (Admin)
PS> git clone https://github.com/its-dhaya/wim.git
PS> cd wim

Then follow the two-step install →

View on GitHub Read install guide ↓
The problem

Every Neovim config breaks on Windows.
WIM fixes that.

Mason installs LSPs that silently fail. Telescope needs ripgrep that nobody told you to install. Clipboard breaks after sleep. Treesitter needs a C compiler. WIM ships answers to all of it — found by running on real Windows hardware, not guessed from docs.

📦
Mason LSPs fail silentlyServers install but aren't in PATH — invisible outside Neovim.
🔍
Telescope missing depsripgrep and fd are required — but no config tells you that.
📋
Clipboard breaks after sleep+y randomly stops working. No error. No warning.
🐢
Defender scans on startupEvery file scanned on launch. Editor feels painfully slow.
↔️
CRLF vs LF conflictsGit and formatters fight on every save with no clean resolution.
🔤
Font setup downloads 200MBNerd Fonts installers pull entire families. You need 4 files.
How WIM solves it

Eleven Windows bugs.
All fixed, out of the box.

Problem How WIM fixes it
fixedFont installs 200MB Downloads only 4 required TTF files (~1.2MB)
fixedDefender slows startup Auto-adds nvim folders to exclusion list
fixedCRLF / LF conflicts 3-layer fix: git config + editorconfig + plugin
fixedMason LSPs invisible Mason bin added to system PATH permanently
fixedWSL paths break LSP Auto-converts /mnt/c/ to C:\ at URI level
fixedClipboard breaks after sleep Auto-reconnects win32yank on focus + :WimClipboardFix
fixedTerminal colours vary Auto-detects WT / Alacritty / ConEmu and configures
fixedPATH stale after install Two-phase installer guarantees clean PATH before setup
fixedPS5.1 incompatible scripts All scripts tested on PowerShell 5.1 and above
fixedlspconfig v3 API change Pinned to stable v2, upgrade handled cleanly
fixedLuaSnip submodule fails Build disabled; snippets work without native module
What's included

A complete Neovim & LazyVim setup.
Nothing to configure.

WIM ships a curated LazyVim-compatible stack of plugins that work together on Windows, first launch.

Plugin manager
lazy.nvim
Colorscheme
Catppuccin Mocha
File explorer
neo-tree.nvim
Fuzzy finder
Telescope + ripgrep
Syntax
nvim-treesitter
Autocompletion
nvim-cmp
LSP — Python
pyright
LSP — JS/TS
typescript-language-server
Formatter
conform.nvim + prettier + black
Terminal
toggleterm → PowerShell
Git
gitsigns + lazygit
Statusline
lualine
Key bindings

Muscle memory from day one.

WIM follows LazyVim conventions on Windows. If you're coming from VSCode or LazyVim on Linux/macOS, you'll feel at home immediately.

Find files<leader>ff
Live grep<leader>fg
Toggle file tree<leader>e
Toggle terminal<leader>t
Open LazyGit<leader>gg
WIM health check<leader>wh
Hover docs (LSP)K
Go to definitiongd
Rename symbol<leader>rn
Code action<leader>ca
Save fileCtrl+S
Update plugins<leader>wu
Installation

Two steps.
Then just run nvim.

Windows PATH changes require a fresh terminal after dependencies are installed. WIM is honest about this — two phases, zero silent failures.

1
Clone the repo and run the dependency installer
# Open PowerShell as Administrator git clone https://github.com/its-dhaya/wim.git cd wim powershell -ExecutionPolicy Bypass -File installer\install.ps1
Installs Neovim, Git, Node.js, Python, ripgrep, fd, fzf, Zig, win32yank and repairs PATH.
2
Close the terminal, open a new one as Administrator, then run setup
# Fresh terminal required — PATH must reload cd wim powershell -ExecutionPolicy Bypass -File installer\setup.ps1
Deploys config, installs fonts, adds Defender exclusions, configures git line endings, runs health check.
3
Launch Neovim — plugins auto-install on first open
nvim
Requires Windows 10/11, Windows Terminal (recommended), and PowerShell 5.1+.