---
title: "Comment by Rishabh Mishra on \"Install n8n on Windows Without Docker (and the Node Version Trap)\" | Hashnode"
description: "The silent fallback to an old n8n version is the trap worth warning people about — no error, just an old install. Backing up .n8n\\config together with database."
url: "https://hashnode.com/posts/install-n8n-on-windows-without-docker-and-the-node-version-trap/6b0009c9ffa2c55a69b7e86e/comment/6b0109a5a4f5bbf8e48570fc"
---

[Discussion](https://hashnode.com/posts/install-n8n-on-windows-without-docker-and-the-node-version-trap/6b0009c9ffa2c55a69b7e86e)

Comment [Install n8n on Windows Without Docker (and the Node Version Trap)](https://hashnode.com/posts/install-n8n-on-windows-without-docker-and-the-node-version-trap/6b0009c9ffa2c55a69b7e86e)

[Rishabh Mishra](https://hashnode.com/@rushdeploy)

[1d ago](https://hashnode.com/posts/install-n8n-on-windows-without-docker-and-the-node-version-trap/6b0009c9ffa2c55a69b7e86e/comment/6b0109a5a4f5bbf8e48570fc)

The silent fallback to an old n8n version is the trap worth warning people about — no error, just an old install. Backing up .n8n\\config together with database.sqlite is the detail that saves your credentials later. If you ever need webhooks reachable from the internet, a one-click n8n deploy on RushDeploy keeps it online without keeping your PC on — the free plan covers 1 project and 50 deploys a month.

[Kausar Raza](https://hashnode.com/@knowledgemarkg)

[1d ago](https://hashnode.com/posts/install-n8n-on-windows-without-docker-and-the-node-version-trap/6b0009c9ffa2c55a69b7e86e/comment/6b0109a5a4f5bbf8e48570fc#reply-6b01447d6637355e73f2a20f)

Thanks Rishabh. Yes, that silent fallback is the part that cost me time: on an older Node, npm doesn't fail, it just installs the newest n8n release whose engines field still accepts that Node, with no warning. And agreed on the backup: the encryption key lives in .n8n\\config, so database.sqlite on its own leaves you with credentials you can't decrypt. For webhooks from outside services, a local install isn't the right place, so I'd plan for an always-on server rather than localhost.

[Rishabh Mishra](https://hashnode.com/@rushdeploy)

[1d ago](https://hashnode.com/posts/install-n8n-on-windows-without-docker-and-the-node-version-trap/6b0009c9ffa2c55a69b7e86e/comment/6b0109a5a4f5bbf8e48570fc#reply-6b015cc4a92783faad4ed997)

That engines-field detail is the part I would check first. Running node -v before installing, and pinning the Node version, stops npm quietly settling for an older n8n. For the always-on step, I would also test one webhook end to end after moving it, since a local URL that worked on your PC is the usual thing that breaks on a server.
