Issues installing driver, need troubleshooting help

Hi all,

Firstly, I apologize if this isn’t the correct place for this request. I realize this isn’t technically related to driver development, but I’m in need of assistance from folks who understand drivers inside and out, and the other forums I’ve asked have been unable to help. Frankly, I’m a bit desperate.
Please understand that while I’m fairly well versed in Windows navigation and operations in general, I know next to nothing about driver debugging or how to read log files and such, so please bear with me when I use incorrect terminology or if I ask for a bit of handholding on what might seem to be a basic process to you.

Here’s my issue:
I recently had to reformat my desktop PC and reinstall Win7 x64.
It’s been a while now (about a month), and everything is back up and running just fine for the most part.
However, the other night, I decided to reinstall my 3D printer, which is a Monoprice Select Mini.
This printer seems to use a simple inf file to point to the built-in Windows USB->Serial drivers.
For reference, I’m able to install this printer on my laptop (also running Win7 x64) with no issues, so I know it’s something specific to this installation of Windows.
When I plug the machine into my PC and power it on, I get the standard ‘USB connected’ sound, and the hardware wizard notifies me that it’s attempting to find the driver. It fails to find anything on Win Update, which is expected. Once it’s done, I go into device manager and right click on the new hardware entry, and choose to update the driver. I point to the provided inf file, and it proceeds with the install. I get a message about an unsigned driver, which I accept. I should mention that the driver failed to install at all with a “file not found” (or similar) error until I hunted down the fact that it was looking for usbser.sys and manually copied it from my laptop into the same folder as the inf. Not sure why it wasn’t there before. I suspect this has something to do with the root cause of my troubles here.
Anyway…at this point, the driver fails to load, because of the unsigned issue. If I reboot and disable driver signing enforcement, then reinstall the driver, it will complete the installation, but then I get a (code 39) error telling me the driver is corrupted.
I finally found a reference to the setupapi.dev.log file and found in there where the driver install is failing, but I can’t read it clearly enough to understand what exactly is the failure point.
I’m at a loss here. I’ve done countless uninstalls and reinstalls of the driver. I’ve even tried system restores back to a point before I installed any version of the 3D printer driver, thinking maybe I did something in the wrong order, but it made no difference. I’ve also run the SFC, and apparently no errors were detected, since the tool closed with no messages.
I can post any portion of the devlog file or any other information you think would be helpful, if you’ll direct me how to extract it.
Thanks in advance for any assistance you can provide. This has had me pulling my hair out for several days now. I usually pride myself in my ability to solve most any computer issue with a combination of enough Googling, intuition and trail and error, but this one has me totally stumped.
-Mike P.

Hi Mike,    You are right that this really isn’t the place for this kind of question.  That being said, I think you need to follow the user manual that for your 3d printer.  It wants you to install the driver first using the installation program provided. Beyond that i suggest you contact Monoprice for support.  I’d agree that copying usbser.sys from your laptop is probably part of the issue.
Hope this helps.Eric

From: “xxxxx@hotmail.com
To: Windows System Software Devs Interest List
Sent: Wednesday, April 19, 2017 11:33 AM
Subject: [ntdev] Issues installing driver, need troubleshooting help

Hi all,

Firstly, I apologize if this isn’t the correct place for this request. I realize this isn’t technically related to driver development, but I’m in need of assistance from folks who understand drivers inside and out, and the other forums I’ve asked have been unable to help. Frankly, I’m a bit desperate.
Please understand that while I’m fairly well versed in Windows navigation and operations in general, I know next to nothing about driver debugging or how to read log files and such, so please bear with me when I use incorrect terminology or if I ask for a bit of handholding on what might seem to be a basic process to you.

Here’s my issue:
I recently had to reformat my desktop PC and reinstall Win7 x64.
It’s been a while now (about a month), and everything is back up and running just fine for the most part.
However, the other night, I decided to reinstall my 3D printer, which is a Monoprice Select Mini.
This printer seems to use a simple inf file to point to the built-in Windows USB->Serial drivers.
For reference, I’m able to install this printer on my laptop (also running Win7 x64) with no issues, so I know it’s something specific to this installation of Windows.
When I plug the machine into my PC and power it on, I get the standard ‘USB connected’ sound, and the hardware wizard notifies me that it’s attempting to find the driver. It fails to find anything on Win Update, which is expected. Once it’s done, I go into device manager and right click on the new hardware entry, and choose to update the driver. I point to the provided inf file, and it proceeds with the install. I get a message about an unsigned driver, which I accept. I should mention that the driver failed to install at all with a “file not found” (or similar) error until I hunted down the fact that it was looking for usbser.sys and manually copied it from my laptop into the same folder as the inf. Not sure why it wasn’t there before. I suspect this has something to do with the root cause of my troubles here.
Anyway…at this point, the driver fails to load, because of the unsigned issue. If I reboot and disable driver signing enforcement, then reinstall the driver, it will complete the installation, but then I get a (code 39) error telling me the driver is corrupted.
I finally found a reference to the setupapi.dev.log file and found in there where the driver install is failing, but I can’t read it clearly enough to understand what exactly is the failure point.
I’m at a loss here. I’ve done countless uninstalls and reinstalls of the driver. I’ve even tried system restores back to a point before I installed any version of the 3D printer driver, thinking maybe I did something in the wrong order, but it made no difference. I’ve also run the SFC, and apparently no errors were detected, since the tool closed with no messages.
I can post any portion of the devlog file or any other information you think would be helpful, if you’ll direct me how to extract it.
Thanks in advance for any assistance you can provide. This has had me pulling my hair out for several days now. I usually pride myself in my ability to solve most any computer issue with a combination of enough Googling, intuition and trail and error, but this one has me totally stumped.
-Mike P.


NTDEV is sponsored by OSR

Visit the list online at: http:

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at http:

To unsubscribe, visit the List Server section of OSR Online at http:</http:></http:></http:>

Hi Eric,
Thanks for the reply.
That’s the issue, there isn’t really an installation package for the driver.
There is control software, but it doesn’t install a driver at all. To install the driver, you have to plug in the device, let it fail to find the driver, then update it manually, pointing to the inf provided.
That’s where it all falls apart.
My problem is that I’m not able to interpret the output of the setupapi.dev.log file accurately enough to determine what exactly is failing.
Can you suggest a forum that would have folks who are versed in that level of troubleshooting?
Thanks again and sorry to jump into a dev forum to ask for user-level support, but I’m at a real loss for options here and no one seems to even understand the issue.
-Mike