Trust.Supply Unofficial analytics suite Docs
Docs · Upgrade · Windows

Update trustmnw-cli to 1.2.1 on Windows

Version 2.1 · 18 Nov 2026 Needs Node 26
!

Not yet tested on a real Windows validator. This follows the Ubuntu procedure that was tested on Ubuntu validators. Try it on one Windows validator first.

i

Update one validator at a time. Open PowerShell. Only step 3 needs PowerShell as administrator.

  1. Check and back up

    nvm list
    trustmnw-cli --version

    Shows which Node versions nvm-windows has. Write the CLI version down. Make a backup or restore point if you can.

    If PowerShell says "running scripts is disabled on this system", run once and answer Y:

    Set-ExecutionPolicy -Scope CurrentUser RemoteSigned

  2. Log out and stop

    trustmnw-cli logout
    trustmnw-cli stop
  3. Check Node, install Node 26 if needed

    node -v

    Shows v26 or higher? Skip to step 4. Only install Node 26 if it is older or missing. In PowerShell as administrator:

    nvm install 26
    nvm use 26

    Close it, open a normal PowerShell, and check node -v: expected v26.x. (No nvm? Install Node 26 from nodejs.org instead.)

  4. Install trustmnw-cli 1.2.1

    npm install -g @morpheusnetwork/trustmnw-cli@1.2.1 --loglevel verbose

    Lines keep scrolling while it works. Wait until you get your prompt back. Don't press Enter or Ctrl+C.

    trustmnw-cli --version

    Expected: 1.2.1

  5. Log in and check

    trustmnw-cli login
    trustmnw-cli status

    Log in with your KYC email and the code you receive. login also starts the node.

    Expected: node connected.

    On trust.supply the node should show online. Then move on to the next validator.

!

Moving to another server? Run trustmnw-cli logout then trustmnw-cli stop (two lines) on the old one just before you run trustmnw-cli login on the new one. Never run the same validator on two machines at once.

Old machine no longer accessible? If you could not log out there: go to Trust.Supply, unlock MetaMask, connect your wallet and press Reset on Node Details (picture). Then run trustmnw-cli login on the new machine.

Keep it running

The PC must not sleep: Settings → System → Power & battery → Screen and sleep → set sleep to Never when plugged in.

The validator runs in the background, so you can close PowerShell. Check it any time with trustmnw-cli status in a new PowerShell window. After a restart of the PC, run trustmnw-cli login again.

!

Don't accept npm's offer to upgrade npm, and don't use npm update.

To go back to the old version

If you installed Node 26 with nvm, your old CLI is still installed under Node 20.9.0. Switch back to it:

trustmnw-cli logout
trustmnw-cli stop

In PowerShell as administrator: nvm use 20.9.0. Then in a new normal PowerShell:

trustmnw-cli login
trustmnw-cli status

Node already v26 or from nodejs.org: log out and stop, run npm install -g @morpheusnetwork/trustmnw-cli@<old version> --loglevel verbose, then log in.

If you reinstall the CLI on Node 20 and npm says ENOTEMPTY, delete the leftover .trustmnw-cli-… folder in v20.9.0\node_modules\@morpheusnetwork inside the folder shown by nvm root.

Based on the Masternodes Setup Guide by @trippledutch and tests of 17–18 Nov 2026 · Version 2.1 (18 Nov 2026): Node 26 only installed if missing or older; logout and stop before the install, login after it · v2.0: 1.2.1 on Node 26.