Yeah, as the diagnostic says, these kind of issues can almost always be fixed by running Core with -reindex (or -reindex-chainstate if only chainstate is corrupted).
But, what actually fixed it is by renaming the chainstate folder which is somehow restricted by a certain Microsoft product, then
--reindex after.
The log and the errors in the second reply are the ones he got after using
--reindex without renaming it first.
Why rename it? Old, corrupted chainstate folders still use a few GB.