Firmware Update Issue with WIN10

[Resthome]

Thought I would start a new thread for Win10 issues with firmware upgrades since there are bits and piece in various threads. Since the current MidNite position is we do not currently support Win10. My goal is to try to figure out what USBSER driver worked in the past (Win8.1) and to verify if is the same one that does not connect with Win10 OS. Anyone who can shed some light on the issue or wants to share their experience is encouraged to do so.

There are two usbser.sys files and they are different file versions on my Win 8.1 machine. Note that the Win8.1 OS works perfect with COM8 and firmware updates. One is in the C:\MidNiteSolar directory and the other is in C:\Windows\system32\drivers. If I look at the drivers list on the system for usbser.sys on my Win 8.1 system it appears to be using the one in C:\Windows\system32\drivers. It looks like in my case it used OEM3.INF as the install file and that file is one that was modified by boB with Midnite information. But OEM3.Inf is not in the C:\MidniteSolar directory so I’m assuming since you only need to install the driver once it was installed on the Win8.1 machine when I first used it and that would have been March of this year. From the event logs it looks like it was installed in March and then uninstalled in May and re-installed in September of this year for some reason. There is an USBSER.INF and a Classic_USB.INF in the C:\MidNiteSolar directory that appears to be identical to the OEM3.INF

BTW I am using the exact same laptop with two different HD and OS. One HD with WIN8.1 and one that had the WIN10 update applied to the WIN8.1 OS. The Win8.1 works perfectly and the Win10 does not.


I’ll have to switch to the Win10 HD and see how it differs but may have to wait as I do not have a Classic available at home to play around with drivers.

[Halfcrazy]

Just a side note but Matt one of our engineers is making good progress towards a new updater and it is much much easier to use I understand. Stay tuned

[Westbranch]

Ryan, will this work for other versions of Micro-slop-ware (W7)?

[Resthome]

Just a side note but Matt one of our engineers is making good progress towards a new updater and it is much much easier to use I understand. Stay tuned

You have my attention!!! Thanks Ryan. 

[ClassicCrazy]

Seems like eventually something will have to work with Windows 10 since there are so many out using that out there now.
I don't get why the usb drivers worked fine to see the Classic spit out data using terminal program but the updater didn't seem to think the Classic even existed. Must be a bootloader issue ?

Larry

[Resthome]

Seems like eventually something will have to work with Windows 10 since there are so many out using that out there now.
I don't get why the usb drivers worked fine to see the Classic spit out data using terminal program but the updater didn't seem to think the Classic even existed. Must be a bootloader issue ?

Larry

I agree Larry. Because the Classic does connect, you can see it in the Device Manager and as you say the terminal program can connect. But the DOS batch files that load the firmware does not see it for some reason. Timing ?? Who knows? It's been a hit a miss for a long time so a different approach would be nice. My best luck was with Win 8.1 for some strange reason.

[Halfcrazy]

Yes this updater will work in all windows.

[Resthome]

Yes this updater will work in all windows.

+10

[Halfcrazy]

Yes 10 for sure 

[mike90045]

Just a side note but Matt one of our engineers is making good progress towards a new updater and it is much much easier to use I understand. Stay tuned

Huzzah !  Can't wait for the s/w install instructions to become realistic again, instead of +15 pages to install the driver. (it ended up being easier to resurrect a win xp to install the updates from)