Problem with sending BTC from Electrum with Ledger

[peterpiper23]

Hoping someone can help me with this problem:

I have an older Electrum wallet (linked to a Ledger wallet) with some BTC that I am trying to send to a different wallet address.

However, every time I try to send the BTC, the Ledger wallet says: 

*  "This derivation path is unusual

*  Confirm public key.....Path 44'/5757'/0' (followed by a Public Key). I am then given the option to either "Approve" or "Reject if you're not sure". 

After I click "Approve" (since I recognize the Public Key), the Ledger wallet says:

*  "Register Wallet" (with options to either Approve or Reject).

*  Then (after I click "Approve"), the same Public Key appears (with the option again to either Approve or Reject).

*  After I click "Approve", the Ledger goes back again to #1 and says "Register Wallet" (thus forcing me to go through #1 and #2 repeatedly unless I click "Reject").


Perhaps related, is my lack of understanding for how exactly the Electrum Wallet work with regards to sending BTC.  For example, under "Fee Policy", there is a dropdown menu with 3 options: Feerate, ETA, and Mempool.

Which one do I select and what is the quantity of Fee Policy that I should put (in vMB from tip)?  Regardless of which quantity I select (on the sliding scale), a message says "The fee for this transaction seems unusually high" (ranging from 5.81 to 23.4 percent of the amount)

Not sure if my lack of understanding here may be causing an issue with sending the BTC.

Two key questions I have:

Question #1: Is there another wallet that I can use (other than Electrum Wallet) to access these BTC so I can send them?

*  The problem is that I do not have the Private Keys for the Electrum Wallet (as it is just linked to my Ledger)

NOTE 1: When I previously sought help online for this issue several years ago, some poster on a different forum said: "You have the option to restore the seed to a cold-storage set-up with that 'script type' and 'derivation path'. It is arguably safer than your Ledger if everything is setup correctly. If nothing worked, you can consider it via Electrum and an offline (air-gapped) machine"

NOTE 2: I previously tried using Sparrow Wallet with my Ledger to create a new wallet using the same derivation path (m/44'/5757'/0'), however, I ran into problems. After I attempted to send the BTC to a different wallet, I selected the Public Server and:

*  Clicked on "Create a Transaction", "Finalize a Transaction for Signing", and then "Sign"

*  Then a small popup box appeared showing my connected Ledger plus another button that said "Sign" (which I clicked on)

*  It then said "Signing" but then gave an error message: '0x6982', 'Error in command'   (Not sure what this could mean?)

Should I not have chosen the "Public Server"?  The problem is, I recall that the other 2 server options were unable to connect.


Question #2: Is there any other way of regaining control over this wallet (without updating the firmware on my Ledger to the latest version to avoid updating the Ledger Recover protocol, which I do not trust)?

Thank you!!

[nc50lc]

Perhaps related, is my lack of understanding for how exactly the Electrum Wallet work with regards to sending BTC.  For example, under "Fee Policy", there is a dropdown menu with 3 options: Feerate, ETA, and Mempool.

Should I not have chosen the "Public Server"?  The problem is, I recall that the other 2 server options were unable to connect.

These shouldn't be related to the signing issue, in both clients.
Because the selected server has nothing to do with the signing and the resulting fee rate is just the difference between the input(s) and output(s)'s amounts.

*  Confirm public key.....Path 44'/5757'/0' (followed by a Public Key). I am then given the option to either "Approve" or "Reject if you're not sure".  
-snip-
*  After I click "Approve", the Ledger goes back again to #1 and says "Register Wallet" (thus forcing me to go through #1 and #2 repeatedly unless I click "Reject").

In that transaction, how many addresses are displayed in the "Inputs" part of the advanced transaction preview?
Because you'll have to repeat it as much as the number of addresses, thus unusual pubKey paths to approve.

[rdluffy]

What model of Ledger do you have?

In your case, I would try the easiest option: download Ledger Live and transfer the BTC to the wallet you want
After clearing your funds, create a new wallet, WRITE DOWN THE SEED this time, and stay safe

Not all Ledgers have the recovery service. As far as I know, the Ledger Nano S, for example, does not

[peterpiper23]

Unfortunately, I have the Ledger Nano S. 

I have used Ledger Live, however, I don't see these BTC anywhere so not sure how I could transfer the BTC to the wallet that I want - please explain how to do this, considering that I only have the seed for the Ledger Wallet - not the Electrum wallet where I deposited the BTC.

[rdluffy]

Unfortunately, I have the Ledger Nano S. 

I have used Ledger Live, however, I don't see these BTC anywhere so not sure how I could transfer the BTC to the wallet that I want - please explain how to do this, considering that I only have the seed for the Ledger Wallet - not the Electrum wallet where I deposited the BTC.

Since Ledger Nano S does not support Ledger Recover, it is good for you if you do not want to use the service or are afraid of something

Now I am more confused by your explanation, let's try to break it down into parts

Do you remember how you created your wallet?
When you set up your Ledger, did you write down the Seed and then use Electrum as well?

Try using Ledger Live now with your seed and see if your balance appears

It doesn't matter if you deposited the balance while using Electrum or Ledger Live, as long as you wrote down the seed correctly, you have control over the generated BTC addresses. The wallet is just an interface

Give us more details so we can understand better.

[nc50lc]

-snip- considering that I only have the seed for the Ledger Wallet - not the Electrum wallet where I deposited the BTC.

So you lost the software wallet.. it's not much of a problem if you still remember the derivation path displayed when you tried to spend.

First, read this to know how to set-up it with Electrum: https://support.ledger.com/article/115005161925-zd
But since you were using a non-standard derivation path, you must edit the displayed derivation in step8 of "Connect to Ledger Device" instructions.

So, After selecting the same script type that you've used before (refer to the examples in step 8), edit the derivation path to your previously used path: m/44h/5757h/0h
Finish creating the wallet, let it sync for a minute then re-try spending your coins.
And this time, check the number of inputs in the "preview" of your transaction and as I've noted, when you want to sign, you must approve as much (different) address shown.

Also, I'd recommend you to update your Ledger Nano S' firmware to the latest version (instructions) in case it's caused by an outdated firmware incompatibility.
It should be safe since you have your seed in case you need to restore it.

[dkbit98]

Question #2: Is there any other way of regaining control over this wallet (without updating the firmware on my Ledger to the latest version to avoid updating the Ledger Recover protocol, which I do not trust)?

If you have seed words backup you can easily import them to different hardware or software wallet.
I would not recommend purchasing new ledger or any other hardware wallets that are not open source.

I have used Ledger Live, however, I don't see these BTC anywhere so not sure how I could transfer the BTC to the wallet that I want - please explain how to do this, considering that I only have the seed for the Ledger Wallet - not the Electrum wallet where I deposited the BTC.

Do you at least know addresses with coins and can you see them on blockchain explorer?
You can try using alternative software wallet connected to y<our ledger device, Sparrow wallet would be a good alternative.

[peterpiper23]

Reply to nc501c:

Quote from: peterpiper23 on August 22, 2025, 12:52:39 AM
*  Confirm public key.....Path 44'/5757'/0' (followed by a Public Key). I am then given the option to either "Approve" or "Reject if you're not sure". 
-snip-
*  After I click "Approve", the Ledger goes back again to #1 and says "Register Wallet" (thus forcing me to go through #1 and #2 repeatedly unless I click "Reject").

In that transaction, how many addresses are displayed in the "Inputs" part of the advanced transaction preview?
Because you'll have to repeat it as much as the number of addresses, thus unusual pubKey paths to approve.

There are 27 Input addresses listed and 2 Output addresses listed (these appear once I click "Reject").  Are you saying that I have to go through the Register Wallet sequence twenty seven (27) times before it will allow me to sign the transaction?

Thanks

[nc50lc]

In that transaction, how many addresses are displayed in the "Inputs" part of the advanced transaction preview?
Because you'll have to repeat it as much as the number of addresses, thus unusual pubKey paths to approve.

There are 27 Input addresses listed and 2 Output addresses listed (these appear once I click "Reject").  Are you saying that I have to go through the Register Wallet sequence twenty seven (27) times before it will allow me to sign the transaction?

Yes, unlike a wallet with standard derivation path, those pubKey paths aren't "known" by your ledger device, so it's prompting you to approve them one at a time.

The good news is: since you only have two outputs this time, I'd assume that it's the recipient and change.
If you don't have any other UTXO left displayed in the 'Coins' tab, your next transaction will only use one input (that txn's change).

That's unless it's caused by firmware and client version incompatibility issue.

[peterpiper23]

Thanks for your help everyone.

Just to close out this chat, I ultimately updated the firmware on my Ledger and the BTC app and then used the Ledger seed recovery phrase to create a new wallet on Electrum using the BIP39 seed option and it worked!  Once the new wallet was synchronized, I was finally able to send my BTC. 

I recommend anyone else having this trouble to do the same.