OK. I didn't know that about that "disable" screen. Anyway, we discovered renaming it does let the boot proceed, but it complains about the next one. I think there will be too many to continue renaming them. These look like the myriad Microsoft services that Windows loads at boot to run in the background. Probably the system will be useless without them, even if it did boot. Let's rename that one back...
REN E:\Windows\system32\drivers\wd\WDBoot.sys.XXX WdBoot.sys
The boot process does begin. The files to load are in the right place. They are fetched. But Windows doesn't like them anymore. Why? SFC fails to initialize. DISM appears to have permissions troubles. Why? Time to hit the sack soon. I'll have to think/search more tomorrow.
Maybe try "Troubleshoot > Advanced Options > Startup Repair" 3 or 4 times in a row. I've seen some say it might eventually work. Good luck.