[General Topics] JovialQuestion:
I apologize if I came across insulting or rude. I can tell you that when the device is in Fastboot recovery or fastbootD the devices battery doesn't charge tho you should be able to unplug the device and while holding the key combo to enter bootloader including the power key still should be able to get the green droid laying on his back bootloader mode. If your batter is dead it does stay recognized in device manager. I would suggest plugging it into the wall for awhile as the USB data connection draws more power than the USB port provides haultimg the charge to the battery. You will also need to ensure that if you changed the Boot.img by flashing another to restore the stock boot IMG for the device as the wrong IMG can sometimes cause the device to malfunction in a powered off plugged state. The boot.img contains Recovery As Well as the fastbootD so having the correct boot.img is a good start in figuring it out. If you changed the vendor .IMG or flashed the wrong firmware in fastboot I know installing the wrong .IMG on the device In my hand to test did cause touch and sensors to fail so I assume the vendor .IMG would be capable of causing screen failures only if it was altered. If you can get it into the green droid on his back bootloader fastboot. I always use a OTG adapter and the Bugjaeger Premium App on another device to send the fastboot commands to it and I have yet to get a failed command due to drivers. Make sure you charged the battery with a wall outlet you will need voltage from the battery or else the device relys solely on the data connection and this will cause interrupted data and partially completed commands or just a failure. I can confirm after letting mine die via battery swap. The device acts just as you have described with a black screen and a unknown device appears "I don't have the drivers installed on the PC i am using" as for windows. I have tried several versions as I am not skilled on windows at all. Windows 7 pro was the only version I with a basic understanding of windows could get both the .IMG file extracted and tools to install as I prefer Linux and to flash the super partition in fastbootD userspace parallel to the recovery mode. This requires the correct boot.img or else it does fail for IMG size of course this is with the extracted .IMG file within the archive provided and it shows up as super.fex. also I do not change this file type to .IMG as it will flash correctly. After you "if your able to" get the stock unchanged OS to boot is when you should attempt any other alterations. I wouldn't try anything until after you have left the device plugged into the wall not PC for a day as I believe you have a dead battery however if you made changes to the boot IMG I wouldn't expect the device to even charge properly until the boot.img meant for the device is replaced. I could be wrong

Your device could also be stuck in the FEL mode. I would hope that you can if the device is recognized get the flash to complete or by making sure it's not plugged into a PC holding the power key and volume down or just power to force a reboot "plugged into wall if the battery is dead" and try to get it to either bootloader or recovery. Right now I don't remember but power and Volume down for bootloader or volume up and power. One of the key combo will give you bootloader and one is recovery. Recovery needs the boot partition so you may only get bootloader. Either option would be better than nothing for a sign of life left in it. I do know after getting one stuck in a black screen from changing the boot slot to slot B by mistake and having flashed the wrong firmware to slot a it did take awhile of me holding the power key and volume key to get it to bootloader. If I think of anything else or relevance I will try to gelp

to check the battery upon getting into fastboot try

fastboot getvar battery-voltage

I also found this

https://xdaforums.com/t/solved-stuck-in-fastboot-with-low-battery-use-this-batch-file.1658084/

I know that I can sometimes type things out in a manner that's hard to follow. That sometimes also appears to be cold and rude. I tend to type my responses fast as I tend to reply in-between a busy schedule. If you ever need clarification just ask. I know my typing skills are less than optimal for following along.