I couldn’t quite follow whether you thought remote file damage had happened, but if you think (in retrospect) that there was more than just a DB problem, you could run restore with no-local-blocks to make sure that it went to the destination for blocks instead of using a shortcut of looking for blocks in the current source files.
I’m glad things are looking good, and hoping that someday the default service install will use a safe location:
Configuration “lost” after Windows 10 Anniversary Update when running as a service #1950
Migrating from User to Service install on Windows