Fixing VirtIO Code 39

I’m recording this here in case anyone else is unfortunate enough to encounter this Code 39 message, and so that she can avoid wasting several hours of her life attempting to fix it, by instead Googling it and reading this.

Alas, it’s too late for me.

If you’re attempting to install Red Hat’s VirtIO drivers onto a virtualized Windows box, and the whole thing seems to go okay, but then you receive the message “Windows cannot load the device driver for this hardware. The driver may be corrupted or missing (Code 39),” at which point, the device doesn’t work, and you have to remove the driver and do the entire thing over again…

Well, it’s because you’re installing the wrong VirtIO version. If you’re on a Windows Server 2008 R2 box like me, and you’re thinking “Oh, I’ll use the drivers in the Win8 folder, because their aren’t any drivers explicitly for 2008 server,” you have gone astray. Windows Server 2008 R2 uses the Windows 7 drivers, not 8.

It would be nice if, you know, Windows would tell you this, instead of giving you this less-than-helpful-to-put-it-politely message, but it’s not like people pay them for this software or anything, so what do you really expect? Or, uh, wait.

You've read this far -- want more? Join the newsletter and I'll e-mail you when new articles are posted, along with the ideas that I don't share anywhere else.

Two e-mails per month. Zero spam. Unsubscribe at any time. I promise to treat your e-mail with respect.