Bitcoin core says this is my first time opening the program- when it isn't

[Bittothefuture]

Bitcoin Client Software and Version Number:0.20.1
Operating System: Windows 10
System Hardware Specs:8 GB Ram/120 gb ssd - 2TB External SSD
Description of Problem: I downloaded the entire blockchain up to dec 27, 2020 but today when I went to open bitcoin core, it seemed like if it was the first time I was opening the program when in fact it is not. I had created and backed up 2 wallets and have many gigabytes of the blockchain. how do I resume syncincg? I did not check to have it pruned, given I wanted the whole blockchain. Help

After it opened I clicked on a different folder (external ssd->chainstate (looking back I should have probably selected a different folder because now within that chainstate folder I now have another chainstate folder that was created today ) to redownload the blockchain, but I dont want to redownload it since I am only like 4 days out of sync instead of years.

I am very new to the technical aspects, Liberal arts major, not cs major, so all of this is kind of digging into the weeds for me. https://ibb.co/VC0dkwc  [edit: added image]
Any Related Addresses: none
Any Related Transaction IDs: none
Screenshot of the problem:
Log Files from the Bitcoin Client: will get these if someone can tell me what folder to dig into?

thanks for help in advance!

[1713568958]

1713568958

[ranochigo]

Thanks for using the format. You don't need to have the log file.

You can go to the chainstate folder and delete the folders/files which doesn't belong there. Don't delete those with .ldb extension, CURRENT, LOCK and manifest.

If you want to select the data directory again, find your Bitcoin Core shortcut which is created by default during the installation. Or if you want, just go to Program Files/Bitcoin, right click on Bitcoin-qt.exe and select create shortcut. After finding the shortcut, select and right click on it, select properties and in the target field, add -choosedatadir at the end and click OK. Start your Bitcoin Core and it should prompt you for a new data dir. Afterwhich, delete the -choosedatadir from the target. You only have to do this once.

[Bittothefuture]

OH MY GOODNESS !!!  it worked!

2 Notes for posterity;
1: copy pasting -choosedatadir unto the shortcut for some reason would not work, it worked if one types it in manually.
2: I forgot to mention previously, bitcoin core had not detected the already present directory in the external ssd, hence me choosing a new place to place the new directory. But after doing the steps above as you mentioned, now it has recognized the directory in the ssd and we are back in business!! Now I am only 3 days behind.

RANOCHIGO thank you so much !!!! 

[HCP]

2: I forgot to mention previously, bitcoin core had not detected the already present directory in the external ssd, hence me choosing a new place to place the new directory. But after doing the steps above as you mentioned, now it has recognized the directory in the ssd and we are back in business!! Now I am only 3 days behind.

Was the external SSD disconnected at some point after you had synced to 27th Dec?

If it was unplugged, then plugged back into a different USB port, or after other devices/drives were connected, it might have been due to Windows assigning it a new drive letter. This is one of the hazards of trying to use "external" devices for "(semi)permanently" connected data storage

At least you now know how to rectify the issue, should it happen again.

[Bittothefuture]

2: I forgot to mention previously, bitcoin core had not detected the already present directory in the external ssd, hence me choosing a new place to place the new directory. But after doing the steps above as you mentioned, now it has recognized the directory in the ssd and we are back in business!! Now I am only 3 days behind.

Was the external SSD disconnected at some point after you had synced to 27th Dec?

If it was unplugged, then plugged back into a different USB port, or after other devices/drives were connected, it might have been due to Windows assigning it a new drive letter. This is one of the hazards of trying to use "external" devices for "(semi)permanently" connected data storage

At least you now know how to rectify the issue, should it happen again.

yes I sure had disconnected it!

but yes! got it solved wohooo!!!!! im so happy.