Great thanks to everyone for the comments !

Sparrow automatically shows all accounts for the seed in case of Legacy type
but for SegWit it has to be add accounts manually one by one

Unless OP changed the derivation path manually in Sparrow, there shouldn't be any problem with the derviation path.
I could generate the same addresses as OWNR wallet in Sparrow using standard derivation paths.

m/44'/0'/0' for legacy wallet, m/49'/0'/0' for nested segwit wallet and m/84'/0'/0' for native segwit wallet.
[/quote]

Thanks for the comment !

Could you also write the correct "wallet output descriptor" for native segwit

I do hope for this

one idea - I input wrong derivation path - is it possible to understand the correct one by looking at transactions protocol in blockchain explorer ? - in Jason format may be ?

Thank's for the reply - but there are no "segwit wallets" just segwit transactions - could you make input BTC transaction to this fresh OWNR wallet and then output it ?

I've got the following situation:

I worked with BTC transaction in OWNR wallet for 4 last years - last successful one was made on July 14
Next day OWNR has stopped broadcast BTC transactions and the problem is still active (no adequate response from wallet support)
It correctly shows transaction history with all required details according with any blockchain explorer

Surely I've tried to open my wallet in Sparrow by seed phrase with BIP39 passphrase
Sparrow correctly restore all Legacy transactions and addresses so I've transferred the balances to the new wallet

but when I've tried to do the same procedure in Sparrow with SegWit addresses it shows no addresses at all - even for fresh transaction from July 14
Of course I've checked every word in seed and made import procedure several times, tried all SegWit protocols in Sparrow - results are the same

could you provide helpful comments for the situation ?