It was shut down normally, I did wait until the dialog box disappear.
How do you run this command?

bitcoin-qt.exe -reindex-chainstate?

All went good (sync) till 99.96% then it froze ..
I looked at the debug.log, and there are some problems.
Can you help to address them?

Here is the last section of the debug.log:

2021-04-21T12:20:38Z loadblk thread start
2021-04-21T12:20:38Z upnp thread start
2021-04-21T12:20:38Z Bound to [::]:8333
2021-04-21T12:20:38Z Bound to 0.0.0.0:8333
2021-04-21T12:20:38Z Bound to 127.0.0.1:8334
2021-04-21T12:20:38Z init message: Loading P2P addresses...
2021-04-21T12:20:38Z torcontrol thread start
2021-04-21T12:20:38Z Leaving InitialBlockDownload (latching to false)
2021-04-21T12:20:38Z Loaded 65711 addresses from peers.dat  328ms
2021-04-21T12:20:38Z ERROR: DeserializeFileDB: Failed to open file C:\Bitcoin\anchors.dat
2021-04-21T12:20:38Z 0 block-relay-only anchors will be tried for connections.
2021-04-21T12:20:38Z init message: Starting network threads...
2021-04-21T12:20:38Z net thread start
2021-04-21T12:20:38Z dnsseed thread start
2021-04-21T12:20:38Z Waiting 300 seconds before querying DNS seeds.
2021-04-21T12:20:38Z addcon thread start
2021-04-21T12:20:38Z opencon thread start
2021-04-21T12:20:38Z msghand thread start
2021-04-21T12:20:38Z init message: Done loading
2021-04-21T12:20:38Z GUI: Platform customization: "windows"
2021-04-21T12:20:38Z Imported mempool transactions from disk: 13 succeeded, 4711 failed, 4117 expired, 0 already there, 0 waiting for initial broadcast
2021-04-21T12:20:38Z loadblk thread exit
2021-04-21T12:20:40Z New outbound peer connected: version: 70015, blocks=680009, peer=0 (full-relay)
2021-04-21T12:20:40Z No valid UPnP IGDs found
2021-04-21T12:20:40Z upnp thread exit
2021-04-21T12:20:41Z New outbound peer connected: version: 70015, blocks=680010, peer=1 (full-relay)
2021-04-21T12:20:48Z New outbound peer connected: version: 70015, blocks=680010, peer=3 (full-relay)
2021-04-21T12:20:48Z New outbound peer connected: version: 70016, blocks=680010, peer=4 (full-relay)
2021-04-21T12:20:49Z P2P peers available. Skipped DNS seeding.
2021-04-21T12:20:49Z dnsseed thread exit
2021-04-21T12:20:55Z New outbound peer connected: version: 70015, blocks=680010, peer=5 (full-relay)
2021-04-21T12:20:56Z New outbound peer connected: version: 70016, blocks=680010, peer=6 (full-relay)
2021-04-21T12:20:56Z New outbound peer connected: version: 70015, blocks=680010, peer=7 (full-relay)
2021-04-21T12:20:58Z Pre-allocating up to position 0x6000000 in blk02545.dat
2021-04-21T12:21:00Z UpdateTip: new best=0000000000000000000606abd0f162b2810543e958e16e51011a7478121fe7ad height=679936 version=0x20400000 log2_work=92.822271 tx=635561064 date='2021-04-20T18:40:48Z' progress=0.999649 cache=1.4MiB(10411txo)
2021-04-21T12:21:00Z UpdateTip: new best=00000000000000000007b55ff74a0f08fb99eedff7bf94b12db84e196a5c0f9f height=679937 version=0x2fffe000 log2_work=92.822288 tx=635563426 date='2021-04-20T18:55:28Z' progress=0.999654 cache=3.7MiB(27145txo)
2021-04-21T12:21:00Z UpdateTip: new best=00000000000000000006198a87c0fb87fcbf1f9e6c4cbc0ea1e6211e510ded09 height=679938 version=0x2fffe000 log2_work=92.822304 tx=635566200 date='2021-04-20T18:58:45Z' progress=0.999655 cache=5.0MiB(37950txo)
2021-04-21T12:21:01Z LevelDB read failure: Corruption: block checksum mismatch: C:\Bitcoin\chainstate/398969.ldb
2021-04-21T12:21:01Z Fatal LevelDB error: Corruption: block checksum mismatch: C:\Bitcoin\chainstate/398969.ldb
2021-04-21T12:21:01Z You can use -debug=leveldb to get more complete diagnostic messages
2021-04-21T12:21:01Z Error: Error reading from database, shutting down.
2021-04-21T12:40:57Z socket sending timeout: 1201s

Thanks mate, it solved the problem!!!

Here is part of today's log:

2021-04-01T04:31:21Z New outbound peer connected: version: 70016, blocks=677251, peer=0 (block-relay)
2021-04-01T04:31:22Z New outbound peer connected: version: 70016, blocks=677251, peer=1 (block-relay)
2021-04-01T04:31:22Z ERROR: AcceptBlockHeader: block 00000000000000000000570cd87702ae5d9979f17543b38ca62937f2858bc091 is marked invalid
2021-04-01T04:31:22Z Disconnecting and discouraging peer 0!
2021-04-01T04:31:23Z New outbound peer connected: version: 70016, blocks=677251, peer=2 (full-relay)
2021-04-01T04:31:24Z ERROR: AcceptBlockHeader: block 00000000000000000000570cd87702ae5d9979f17543b38ca62937f2858bc091 is marked invalid
2021-04-01T04:31:24Z Disconnecting and discouraging peer 1!
2021-04-01T04:31:24Z New outbound peer connected: version: 70015, blocks=677251, peer=3 (full-relay)
2021-04-01T04:31:25Z ERROR: AcceptBlockHeader: block 00000000000000000000570cd87702ae5d9979f17543b38ca62937f2858bc091 is marked invalid
2021-04-01T04:31:25Z Disconnecting and discouraging peer 2!
2021-04-01T04:31:25Z New outbound peer connected: version: 70015, blocks=677251, peer=5 (full-relay)
2021-04-01T04:31:26Z ERROR: AcceptBlockHeader: block 00000000000000000000570cd87702ae5d9979f17543b38ca62937f2858bc091 is marked invalid
2021-04-01T04:31:26Z Disconnecting and discouraging peer 3!
2021-04-01T04:31:26Z New outbound peer connected: version: 70015, blocks=677251, peer=6 (full-relay)
2021-04-01T04:31:27Z New outbound peer connected: version: 70016, blocks=677251, peer=7 (full-relay)
2021-04-01T04:31:28Z ERROR: AcceptBlockHeader: block 00000000000000000000570cd87702ae5d9979f17543b38ca62937f2858bc091 is marked invalid
2021-04-01T04:31:28Z Disconnecting and discouraging peer 6!
2021-04-01T04:31:28Z New outbound peer connected: version: 70015, blocks=677251, peer=8 (full-relay)
2021-04-01T04:31:29Z ERROR: AcceptBlockHeader: block 00000000000000000000570cd87702ae5d9979f17543b38ca62937f2858bc091 is marked invalid
2021-04-01T04:31:29Z Disconnecting and discouraging peer 7!
2021-04-01T04:31:34Z New outbound peer connected: version: 70016, blocks=677251, peer=9 (full-relay)
2021-04-01T04:31:35Z ERROR: AcceptBlockHeader: block 00000000000000000000570cd87702ae5d9979f17543b38ca62937f2858bc091 is marked invalid
2021-04-01T04:31:35Z Disconnecting and discouraging peer 9!
2021-04-01T04:31:51Z New outbound peer connected: version: 70016, blocks=677251, peer=11 (full-relay)
2021-04-01T04:31:52Z New outbound peer connected: version: 70015, blocks=677251, peer=12 (full-relay)
2021-04-01T04:31:53Z P2P peers available. Skipped DNS seeding.
2021-04-01T04:31:53Z dnsseed thread exit
2021-04-01T04:32:10Z New outbound peer connected: version: 70015, blocks=677251, peer=13 (full-relay)
2021-04-01T04:32:10Z New outbound peer connected: version: 70015, blocks=677251, peer=14 (full-relay)
2021-04-01T04:32:22Z New outbound peer connected: version: 70015, blocks=677251, peer=15 (full-relay)
2021-04-01T04:32:23Z New outbound peer connected: version: 70015, blocks=677251, peer=16 (full-relay)
2021-04-01T04:32:29Z New outbound peer connected: version: 70015, blocks=677251, peer=17 (full-relay)
2021-04-01T04:32:35Z New outbound peer connected: version: 70015, blocks=677251, peer=18 (full-relay)
2021-04-01T04:32:42Z New outbound peer connected: version: 70015, blocks=677251, peer=19 (full-relay)
2021-04-01T04:32:42Z New outbound peer connected: version: 70015, blocks=677251, peer=20 (block-relay)
2021-04-01T04:32:49Z New outbound peer connected: version: 70016, blocks=677251, peer=21 (full-relay)
2021-04-01T04:32:55Z New outbound peer connected: version: 70015, blocks=677251, peer=22 (block-relay)
2021-04-01T04:32:56Z New outbound peer connected: version: 70015, blocks=677251, peer=23 (block-relay)
2021-04-01T04:33:05Z New outbound peer connected: version: 70015, blocks=677251, peer=24 (block-relay)
2021-04-01T04:33:07Z New outbound peer connected: version: 70015, blocks=677251, peer=25 (block-relay)

For the last 9 days my computer is trying to update blocks; I can see 18 active connections to Bitcoin Network, but my machine is stuck at 95.54% ...
Any suggestion on how to force it to update itself to the current date?
 

I decided to delete the blocks and let the updated software to download the database from scratch.
The data files that I just deleted were in the range of 260GB, divided in approx. 131MB blocks.

As for now, I'm 4Y 32W behind, and it tells me that the operation should be finished in roughly 2 days .. fingers crossed .. 

Thanks ... 
It's Bitcoin Core.
After 2 days of reloading blocks, still 36 weeks behind, I have a "fatal error" and the software shuts down.
Here is the last part of debug file:

2019-12-16T04:45:57Z ERROR: ConnectTip: ConnectBlock 00000000000000000023712d268712147475cc3ee028ca514e3f74799b20696e failed, bad-txnmrklroot, hashMerkleRoot mismatch (code 16)
2019-12-16T04:45:57Z Failed to connect best block (bad-txnmrklroot, hashMerkleRoot mismatch (code 16))
2019-12-16T04:45:57Z [default wallet] Submitting wtx 4302c64fab0f323fe845e0f0d290e2d9fb8ed1c649cb7979c0235987c60fde78 to mempool for relay
2019-12-16T04:45:57Z [default wallet] Submitting wtx 29803ea363c61975cace8800529c52c65f458aaa3b0ddc46c0037f5a0df8a0b9 to mempool for relay
2019-12-16T04:45:57Z GUI: Platform customization: "windows"
2019-12-16T04:45:58Z GUI: QObject::connect: Cannot queue arguments of type 'size_t'
(Make sure 'size_t' is registered using qRegisterMetaType().)
2019-12-16T04:45:58Z tor: Thread interrupt
2019-12-16T04:45:58Z Shutdown: In progress...
2019-12-16T04:45:58Z opencon thread exit
2019-12-16T04:45:58Z addcon thread exit
2019-12-16T04:45:58Z torcontrol thread exit
2019-12-16T04:45:58Z net thread exit
2019-12-16T04:45:58Z msghand thread exit
2019-12-16T04:45:58Z scheduler thread interrupt
2019-12-16T04:45:59Z [default wallet] Releasing wallet
2019-12-16T04:45:59Z Shutdown: done

What to do next?
Uninstall and re-install?
Thnx
 

BitCore Error: corrupted data base ---
How to  fix -->

2019-12-13 07:01:10 init message: Rewinding blocks...
2019-12-13 07:01:12 Corruption: block checksum mismatch
2019-12-13 07:01:12 *** System error while flushing: Database corrupted
2019-12-13 07:52:16 Aborted block database rebuild. Exiting.
2019-12-13 07:52:16 scheduler thread interrupt
2019-12-13 07:52:16 Shutdown: In progress...
2019-12-13 07:52:16 StopNode()
2019-12-13 07:52:16 Corruption: block checksum mismatch
2019-12-13 07:52:16 *** System error while flushing: Database corrupted