How Do I Safely Update n8n on Windows?

To update n8n on Windows, save a backup of your work, check the software n8n needs, install the chosen update, and test a small task before turning your automatic workflows back on. Take it one step at a time. If something does not match this guide, stop before changing more.

I use n8n on my Windows laptop for BlogPilot, which helps move blog content into WordPress. During my recent update, I saw several warnings before n8n was working again on version 2.37.10.

This guide brings together that experience and the official instructions. I have not tested every step below, updated to the example version 2.38.7, or completed a full recovery from a backup.

Is this guide right for you?

This is for an existing n8n 2.x installation on your own Windows computer, installed using npm and saving its data in the usual .n8n folder. npm is the tool used to install n8n. Node.js is the supporting software n8n runs on.

If someone set up n8n for you, confirm these details with them first. This guide does not cover n8n Cloud, Docker, or setups that save data or security keys elsewhere.

New to the platform? Start with my guide to getting started with n8n.

How do I update n8n on Windows?

1. Write down what you have now

Open the Windows Start menu, type Command Prompt, and open it. Copy each command below, then press Enter.

This shows your n8n version:

n8n –version

This shows your Node.js version:

node –version

This checks whether npm has n8n installed in the way this guide expects:

npm list -g n8n –depth=0

Save the results in a note. If the last command does not list n8n, or Windows says a command is “not recognized,” stop and ask whoever installed it to check the setup.

2. Pause your workflows and stop n8n

A workflow is the set of steps n8n carries out for you. Some run automatically, such as a daily blog-writing task.

Note which workflows are running automatically. In the n8n editor, unpublish them, or deactivate them if your version uses that wording. Wait for any work already running to finish.

Next, go to the Command Prompt window running n8n. Press Ctrl+C and wait for it to stop. Closing the browser alone does not stop n8n. If it runs through another window or a background service, stop that too; get help if you are unsure.

3. Make a separate copy of your saved work

In the standard setup, the .n8n folder holds your workflows, saved connections and settings. Its security key helps n8n unlock those saved connections. Keep the whole folder together. See n8n’s guidance on where your data is stored and protecting saved connections.

With n8n stopped, run this in Command Prompt:

xcopy “%USERPROFILE%\.n8n” “%USERPROFILE%\n8n-backup-before-update-01” /E /I /H /K

This copies the folder into a separate backup beside it. %USERPROFILE% means your Windows user folder, so you do not need to type your username. Microsoft documents the options in its xcopy reference.

Use a new backup name every time. If that name already exists, change the ending to 02 or another unused number before running the command. If copying fails, copies no files, or asks to replace files, stop.

Open the backup in File Explorer. Check that it contains database.sqlite, config and the other files and folders from the original. Do not open or share their contents. Keep a protected second copy off the laptop if this work matters to your business.

Why stop n8n first? Copying files as they are being changed can leave an unreliable backup. SQLite’s backup guidance explains this risk.

Seeing copied files is not proof that a backup can restore everything. I have not completed that recovery test for this article.

4. Check that Node.js matches the update

For the example below, use Node.js 24 LTS. LTS means long-term support.

n8n 2.38.7 requires Node.js 24 or newer, according to its published software details. The general installation guide gives a broader range, ending at 24.x. Node.js 24 fits both.

If your saved Node.js result begins with v24., it is in that version family. If not, use the official Node.js download page to find the Node.js 24 LTS Windows installer. If you cannot identify the matching installer, get help before proceeding.

After changing Node.js, close Command Prompt, reopen it, and run node –version again. If Node.js supports other software you use, check that software’s requirements before changing it.

5. Install the chosen n8n version

Read the n8n 2.38.7 release notes first, including any changes affecting your workflows. With your backup complete and n8n still stopped, run:

npm install -g n8n@2.38.7

This asks npm to install that exact n8n version. It is a dated example, not an instruction to use it indefinitely or install an older version over a newer one. I have checked the documentation, not tested this update myself.

Let the command finish. When you can type again, check:

n8n –version

For this example, the result should be 2.38.7. If you see an error or a different version, stop and keep the message for troubleshooting. Do not force another installation.

6. Start n8n and test one small task

Run:

n8n start

When n8n says the editor is available, open n8n on your computer in your browser. Leave the Command Prompt window running.

Keep automatic workflows paused. Confirm your workflows are there, then test a small task using sample data. Check the result in the app receiving it, not only the success message in n8n.

For BlogPilot WordPress automation, a useful test would create one WordPress draft from a test topic. Use a copy of the topic sheet and set WordPress to Draft so you do not change the live queue or publish an article.

That is a proposed check, not a test I have documented completing here.

Once the checks pass, turn your previously paused workflows back on and watch their next automatic run. My practical n8n workflow examples show the different jobs worth checking.

What if a warning appears?

“Packages are looking for funding” is a request to support software developers. It does not mean the update failed. Check the final result.

“Install scripts were blocked” means some setup instructions were not allowed to run. Parts of n8n may be unfinished. Get help reviewing the exact warning; do not approve a long list copied from another computer. See npm’s approval guidance.

“Failed to start Python task runner” concerns the part that runs Python, a programming language. My editor opened despite this warning. That does not prove a workflow using Python will work. Such workflows need a separate check using n8n’s task-runner guidance.

For unfamiliar warnings, save the exact wording and your version numbers. I have not tested the storage-folder change mentioned in my startup log, so this guide does not tell you to apply it.

What if n8n no longer works?

Stop n8n and get help before making more changes. Keep the original backup untouched and preserve the files from the failed update separately.

Going back may involve more than reinstalling an older version. The saved data and security key must work with that version too. Follow the official recovery guidance for the versions involved.

I have not tested going back to an earlier version or restoring the full setup from a backup. This article does not claim a complete recovery test.

Will this guide apply to n8n 3?

No. As checked on the date above, n8n plans version 3 for October 2026, with future updates moving to Docker, a different way of running the software. Existing npm installations keep working for now.

The official setup page is for new installations. It does not move your existing work for you. Treat that move as a separate project.

Your first step

Before running an update command, write down your current versions and confirm where your saved n8n work lives. Start there.

FAQs