**Expected behavior**
It is expected that Bitcoin Core is not shutdown automatically during startup. Moreover, it should be possible to set transaction fee at 0.

**Actual behavior**
![Bitcoin Core Error mintxfee](https://user-images.githubusercontent.com/111286121/210274894-e91adf7f-43f7-4c3f-b799-222c00dc34a0.png)

**To reproduce**

1) Click bitcoin-qt.exe.

**System information**

1) A wallet that contained unspent funds was opened previously.
2) The bitcoin.conf file contains "mintxfee=0".
3) Bitcoin Core 24.0.1 official binary for Windows (portable).
return Instance;
}
bool CWalletAttachChain(const stdshared_ptr<CWallet>& Instance, interfacesChain& chain, const bool rescan_required, bilingual_str& error, stdvector<bilingual_str>& warnings)
{
    LOCK(Instance->cs_);
    // allow setting the chain if it hasn't been set already but prevent changing it
    assert(!Instance->m_chain || Instance->m_chain == &chain);
    Instance->m_chain = &chain;
    // Unless allowed, ensur files are not reused across chains
    if (!gArgs.GetBoolArg("-crosschain", DEFAULT_WALLETCROSSCHAIN)) {
        WalletBatch batch(Instance->GetDatabase());
        CBlockLocator locator;
        if (batch.ReadBestBlock(locator) && locator.vHave.size() > 0 && chain.getHeight()) {
            // Wallet 
            // chain d
            if (chain.getBlockHash(0) != locator.vHave.back()) {
                error = Untranslated("Wallet files should not be reused across chains. Restart bitcoind with -crosschain to override.");
                return false;
            }
        }
    }
    // Register  with validationinterface. It's done before rescan to avoid
    // missing block connections between end of rescan and validation subscribing.
    // Because of  lock being hold, block connection notifications are going to
    // be pending on the validation-side until lock rele It's likely to have
    // block processing duplicata (if rescan block range overlaps with notification one)
    // but we guarantee at least than  state is correct after notifications delivery.
    // However, chainStateFlushed notifications are ignored until the rescan is finished
    // so that in case of a shutdown event, the rescan will be repeated at the next start.
    // This is temporary until rescan and notifications delivery are unified under same