<p><code>-zapwallettxes</code> removes all wallet transactions that are not in the blockchain. It can remove "stuck" transactions, although you don't need this feature in normal operations mode.</p>

<p><strong>Solution A)</strong></p>

<p>On Windows, you need to start the command line prompt (cmd.exe), go to your window search and enter "cmd" and start <code>cmd.exe</code>.
Start bitcoin-qt with <code>--zapwallettxes=1</code></p>

<pre><code>C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe --zapwallettxes=1
</code></pre>

<p>(maybe adapt the program files path)</p>

<p><strong>Solution B)</strong></p>

<p>Create a <code>bitcoin.conf</code> file (normal textfile) here:</p>

<pre><code>C:\Documents and Settings\YourUserName\Application data\Bitcoin (XP)
C:\Users\YourUserName\Appdata\Roaming\Bitcoin (Vista and 7)
</code></pre>

<p>Place....</p>

<pre><code>zapwallettxes=1
</code></pre>

<p>... in the <code>bitcoin.conf</code> file, start Bitcoin-Qt, remove the <code>zapwallettxes=1</code>, restart Bitcoin-Qt.</p>

CC BY-SA 3.0
2017-11-13T21:55:23.697Z
This solution worked initially,  but after a day,  the unconfirmed transaction reappeared in the wallet.  My suspicion is that it came back because it is already in the mempool and is being rebroadcast back to the client...
user3892260
CC BY-SA 3.0
2017-11-14T03:17:43.207Z
The solution that worked for me was using a transaction accelerator service.  For $4, I got the transaction unstuck
user3892260
CC BY-SA 4.0
2018-06-13T23:22:55.923Z
how is this not documented at all?
tobi
CC BY-SA 3.0
2016-06-17T14:19:56.453Z
2016-06-17T14:19:56.453Z
Jonas Schnelli
<p>On May 27 I tried to sell some Bitcoins(for the first time). Since that day the transaction is in the status "unconfirmed". The amount is booked from my wallet, but isn't booked to my bank account.</p>

<p>The solution I found to solve my problem was to start the Bitcoin core wallet with "<code>-zapwallettxes</code>". I'm using Win10 and don't find a way to do this.</p>

<p>Has anyone got any idea on what can I do to sell or to get back the Bitcoin? Answers in German are welcome too.</p>

CC BY-SA 3.0
2016-06-17T11:22:44.577Z
where did you sell the Bitcoins ? You can contact that Bitcoin exchange with the matter.
jgm
<bitcoin-core><unconfirmed-transactions><windows>
How do you apply "-zapwallettxes" on Windows?
Nick
# How do you apply "-zapwallettxes" on Windows?

(Asked by: username_0 on 2016-06-17)

On May 27 I tried to sell some Bitcoins(for the first time). Since that day the transaction is in the status "unconfirmed". The amount is booked from my wallet, but isn't booked to my bank account.

The solution I found to solve my problem was to start the Bitcoin core wallet with "`-zapwallettxes`". I'm using Win10 and don't find a way to do this.

Has anyone got any idea on what can I do to sell or to get back the Bitcoin? Answers in German are welcome too.

**Tags:** bitcoin-core, unconfirmed-transactions, windows

> **Comments:**
> **username_1**: where did you sell the Bitcoins ? You can contact that Bitcoin exchange with the matter.  

---

## 1 answers

### Answer by username_2 on 2016-06-17. Score: 8

`-zapwallettxes` removes all wallet transactions that are not in the blockchain. It can remove "stuck" transactions, although you don't need this feature in normal operations mode.

**Solution A)**

On Windows, you need to start the command line prompt (cmd.exe), go to your window search and enter "cmd" and start `cmd.exe`.
Start bitcoin-qt with `--zapwallettxes=1`

```
C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe --zapwallettxes=1

```

(maybe adapt the program files path)

**Solution B)**

Create a `bitcoin.conf` file (normal textfile) here:

```
C:\Documents and Settings\YourUserName\Application data\Bitcoin (XP)
C:\Users\YourUserName\Appdata\Roaming\Bitcoin (Vista and 7)

```

Place....

```
zapwallettxes=1

```

... in the `bitcoin.conf` file, start Bitcoin-Qt, remove the `zapwallettxes=1`, restart Bitcoin-Qt.

> **Comments:**
> **username_3**: This solution worked initially,  but after a day,  the unconfirmed transaction reappeared in the wallet.  My suspicion is that it came back because it is already in the mempool and is being rebroadcast back to the client...  
> **username_3**: The solution that worked for me was using a transaction accelerator service.  For $4, I got the transaction unstuck  
> **username_4**: how is this not documented at all?  

---

