server 2019 a media driver your computer needs is missing

May I ask what an x86 machine running Windows with issues has to do with the Raspberry Pi Forum ? Stating the Pi-Imager software trashed your machine is baloney. There was no malware (it was a greenfield windows 10 install with latest updates (1 week old) and unused I did use the usb key in an other computer and was able to fix the sd card (initially the mac crashed, i have never seen that) It's possible your machine was infected with some sort of malware that triggered when it went to sleep. When you rebooted are you sure you did a hard power off and not standby? As yours is still working, albeit slowly, I think there is a good chance you'll recover it. In my case the system suddenly stopped working when I plugged the cable in. I never figured out whether it was static electricity or a short that caused the problem, but it was irritating to be replacing a motherboard for no other good reason. I've only destroyed one motherboard while I'd definitely suggest not trying the same USB adapter in another computer. I was able to clear the SSD with diskpart during the windows repair modus but it still won't let me install windows (or ubuntu)Īre you sure that the USB adaptor is not damaged, such that it is shorting pins? I decided to reinstall windows again but the computer did not let me. After a reboot windows was so slow that it could not be used. I was able to get out of sleep mode but i could not resume the imaging process.

at that point windows was tired, entering sleep mode.

The process was running fine, i could see the usb key blinking and it was already at +_ 60%. Are you sure that the USB adaptor is not damaged, such that it is shorting pins? 'Bricked' = dead, as in a non recoverable hardware level issue.Įven if the SD card was very very messed up, the act of plugging it in should not cause a mac to power off. Also, even if you overwrote the OS, such that it could not boot, its is not bricked, it just needs the OS reloaded. I am sure you could select the wrong device as the target and overwrite the OS but that is a separate (PEBCAK) issue.

Given that the imaging process reads from somewhere (local or internet) and writes to the SD, I cannot possibly see how this process could have 'bricked' your laptop.

Server 2019 a media driver your computer needs is missing