If you have access to a local nerd friend/nerd for hire, have them try booting to a USB drive and see if they can access the drive that is failing to boot. If the problematic installs are starting to load Windows before failing it seems like the drive isn't completely dead/may be fine and its the OS install that's corrupted.
If you're up for trying it yourself:
If you have a working Win10 computer, you can create a bootable USB drive with recoverydrive.exe . Boot from that drive and select troubleshoot. Then select the command prompt option. Check if you can see the hard drive. Run chkdsk with repair on that drive. Run sfc /scannow targeting the Windows install on your main hdd. Then remove the USB drive and try booting from the drive.
https://www.tenforums.com/tutorials/...dows-10-a.html
If the HDD is viewable while booted to USB, you can also copy off any files and documents you wish to keep to a USB drive (the bootable drive if there's enough space or a different thumb drive or USB HDD).
I'm assuming you don't have current backups since attempting a backup restore hasn't been mentioned to this point. Once you get back up and running, you should at least get a USB HDD of sufficient size and run weekly full drive backups. I use Macrium Reflect free version.
Having 2 backup drives to alternate between is a great idea if you can afford it, it gives you some additional ransomware protection (more likely to have a copy of data from pre-infection), as well as adding protection against a failed or corrupted backup disk.
Using a live cloud backup solution for the most important files gets you to full 3:2:1 backup status (3 copies, 2 media types, 1 offsite). I use OneDrive since I have O365, Google Drive or DropBox can be suitable for this tier as well as well as some of the more backup dedicated services. OneDrive integration into Win10 is pretty slick and you can get 1TB for $10 a month with an Office 365 Home subscription (also gets you Word/Excel,etc.).
https://www.macrium.com/reflectfree
Last edited by headtrauma; 07-29-2020 at 10:58 AM.
Reason: Add file recovery comments.