... but thats all most likely a digression. If you had a driver, any driver, installed that was working and now you reconnect the interface after potentially zapping it with an uh creative power source if the device is showing up as unknown then it may be fried.. as Dave said way earlier here.
But sure try uninstalling all drivers that were installed and reinstall new clean copies of the correct drivers for whatever interface you have now. Try with a different known working USB cable, try different USB ports.
Windows tries to read some basic device ID info over USB and load the appropriate driver for that ID. Then the driver may do some very basic communication with the hardware. And the driver will do a lot more once it's opened by an application. But if drivers are installed before and Windows is not loading them them and nothing else was messed with then it can be as simple as that hardware that provides the initial device ID over USB may be just fried or maybe the internal power that drives that circuitry is fried.
If that's not it then your mAudio interface may just be pining for the fjords:
https://www.youtube.com/watch?v=vnciwwsvNccas