Monero Wallet Not Syncing? 9 Fixes for a Stuck XMR Wallet

A wallet that sits at “Synchronizing” for hours, or freezes at the same block number, is the single most common complaint on Monero support forums. The good news is that it almost never means your coins are at risk. It means one of two things has stalled: the connection to a node, or the scan of the blockchain on your device. This guide explains how Monero syncing works and walks through nine fixes, from the quickest to the most thorough.

Why Monero syncing is different

On Bitcoin, a light wallet can ask a server “what is the balance of this address?” and get an answer in seconds. Monero does not work like that. Addresses are never written to the blockchain, so nobody, including a node, can look up your balance directly.

Instead, your wallet downloads block data from a node and tests each output with your private view key to see whether it belongs to you. A new block arrives roughly every two minutes, so a wallet that has been closed for a month has around 21,600 blocks to catch up on. On a fast desktop that takes minutes. On an older phone over a slow connection it can take much longer.

There are two separate progress bars to keep in mind:

If you use a remote node, you only ever see the second stage. If you run your own node, the wallet cannot finish until the node itself is up to date.

Key point: A stuck sync is a software or network problem, not a loss of funds. Your coins are recorded on the blockchain and can be found by any wallet that has your seed.

1. Update your wallet first

Old wallet versions are a frequent cause of strange behaviour, especially after network changes. As of November 2026:

• Monero GUI and CLI are on v0.18.5.4. Version 0.18.5.3 was flagged as “highly recommended” and fixed several issues including SOCKS5 proxy handling.
• Feather is on v2.9.1 (2 November 2026).
• Cake Wallet is on the 6.5.x series. Its sync guide notes that recent updates made syncing more than 30% faster.

Updating takes a minute and rules out a whole class of bugs.

2. Switch to a different node

If the wallet is stuck at “Connecting” or the block count stops moving, the node you are using may be overloaded, offline or behind the network.

• Feather: open the node settings (the connection icon in the status bar) and pick another node from the list, or add one you trust.
• Cake Wallet: go to Settings, then Connection and sync, then Manage nodes, and choose another node.
• Monero GUI: in Settings, Node, select a different remote node, or switch from simple mode to advanced mode with your own node.

Note: Cake Wallet 6.5.0 moved its onion node to a new address named “Cake Wallet (Tor)”. If you had the old “Cake Wallet (Onion)” node selected, your wallet will not connect until you select the new one.

3. Check Tor, VPN and firewall settings

Tor and VPNs protect your network privacy, but they add latency and some exit points are slow or blocked. If syncing is crawling:

1. Temporarily disable the VPN or Tor routing to confirm that the network is the cause.
2. If that fixes it, try a different VPN server, a different Tor circuit, or an onion node rather than a clearnet node over Tor.
3. On desktop, make sure your firewall is not blocking the wallet or monerod.

Do not leave privacy features off permanently just because one session was slow. Find a node and route that works well together.

4. Let your own node finish syncing

If you run Monero GUI in advanced mode or use monerod, your wallet shows “Waiting for daemon to sync” until the node catches up. First-time syncs are the slow part. As of October 2026, the Monero documentation lists a pruned node at about 105 GiB and a full node at about 265 GiB.

Tips for a faster node sync:

• Use an SSD. A spinning hard drive is the most common reason a first sync takes days.
• Use a pruned node if disk space is tight. You still verify everything; you just keep less historical data.
• In the GUI, Simple mode (bootstrap) lets you use a remote node while your own node downloads in the background.
• In monerod, type status to see how far along the node is.

5. Fix your restore height

The restore height tells the wallet where to start scanning. Getting it wrong causes two different problems:

• Too low (for example 0 for a wallet created in 2024): the wallet scans years of blocks it does not need, which feels like a stuck sync.
• Too high (after your first incoming transaction): the sync finishes quickly, but your balance is wrong or zero.

In Monero GUI, go to Settings, Info, and click “(Change)” next to Wallet restore height. You can enter a block number or a date in YYYY-MM-DD format; the wallet then rescans from that point. Feather shows the current restore height under Help, Debug info. Polyseed wallets (16 words) carry their creation date, so they normally get this right automatically.

6. Open the wallet regularly

Wallets that sit unopened for many months have a large backlog to scan. The Cake Wallet team suggests opening your wallet at least once a month, and enabling background sync on mobile so it keeps up without you. If you keep a savings wallet that you rarely touch, plan for a longer sync when you open it.

7. Rescan or rebuild the wallet cache

Sometimes the local wallet cache gets corrupted, typically after a crash, a forced shutdown or a full disk.

• Feather: use Wallet, Advanced, Rescan spent, or restore the wallet from seed as a last resort.
• Monero CLI: run rescan_bc to rescan the blockchain from the restore height, or rescan_spent to refresh which outputs are spent.
• Monero GUI: changing the restore height clears the cache and triggers a full rescan; the old cache is kept as a backup file in your wallet folder.

Tip: Before rescanning or restoring, make sure you have your seed written down and that you can read every word. A rescan does not touch your keys, but a restore needs them.

8. Check your device and storage

Monero scanning is CPU-bound. Cake Wallet’s own guide recommends a phone from the last four years, or a computer with four or more CPU cores and an SSD. Low free storage can also break syncing, because the wallet cache and any local node need room to write. Free up space, close heavy apps and try again.

9. Move to a fresh wallet

If you have a very old wallet with a low restore height and long history, every restore means a long scan. A clean fix is to create a new wallet (preferably Polyseed), send your funds to it, and back up the new seed. Future restores then only cover recent history. Keep the old seed until you have confirmed the new wallet works and shows the full balance.

When the wallet says “synchronized” but something is still wrong

A finished sync that shows the wrong balance is a different problem from a stuck sync. Common causes:

• Restore height set after your first deposit.
• Frozen coins in Feather (they are excluded from the total until you thaw them).
• Funds that are still locked: incoming XMR needs about 10 confirmations, roughly 20 minutes, before you can spend it.
• You restored a different wallet than the one you sent to, for example a different seed type or account.

Privacy note on remote nodes

Using a remote node is fine for most people, but understand the trade-off. With a normal (locally scanning) wallet, the node never sees your view key or balance. It does see your IP address and the transactions you broadcast through it. For better privacy, connect over Tor or I2P, or run your own node. Our Privacy & OpSec section covers node privacy in more depth.

Quick checklist

If none of this helps, post on the r/monerosupport subreddit or Monero StackExchange with your wallet name, version, node type and the exact message you see. Never share your seed or private spend key with anyone offering help.

More step-by-step guides live in the Wallets category.