Windows 10: Two Win10 computers, and they both recognize my hardware differently.?

I plug my hardware into my Win10 laptop and it recognizes it correctly in the device manager, calling it by its correct name, "AKM322". It works fine.

I then plug the same hardware into my desktop and it recognizes it and calls it, "AKM322_Bootloader", and the device does not work properly.

Two Win10 machines, updated to the same level, and two different interpretations of the same hardware.
How can this be?

:)

 

HOMEGROUP WITH NEW WINDOWS 10

Mohan Suryanarayan:

The two articles you cited are for Win8 and Win7 only. I just upgraded my laptop to Win10, but my main PC is still on Win7.

I have tried leaving the homegroup on both computers, then setting up a new one on the laptop. since it's Win10. I carefully copied the password, but the Win7 computer doesn't recognize that homegroup, although it tells me I've joined a homegroup.

It would be wonderful if someone would post the steps for networking Win7 and Win10 computers.

 

Curious About Insider Account And Upgrades

When Win10 was first released last October I quickly signed up and installed it on one of my two computers. I set it up with a Microsoft account and began using it. I have since installed Win10 on my second computer and set it up with a local account and
password.

Is the second computer recognized as part of the insider program for a free upgrade or do I need to create a Microsoft account on it?

Can two computers be set up with the same Microsoft account name and password or would I need to create a second Microsoft account for the second computer. I have provided feedback from both the first and second computers.

I'm trying to insure that I don't run into any glitches being able to upgrade both machines from within the Win10 installs.

 

For those (like me) that didn't know, the AKM322 is a Midi keyboard: http://www.midiplus.com.tw/AKM322.htm and its pdf manual is here.

I would open Device Manager on the problematic desktop and uninstall the 'AKM322_Bootloader'. See if it will recognise it correctly the next time. Also, as this appears to be a USB2 device, try it in an actual USB2 socket rather than USB3 if you have one.

 

Drivers appear to be here:
http://www.midiplus.com.tw/MIDIPLUS-Download.htm

Consider downloading and installing the appropriate one, if you can identify it.

However this says
http://www.midiplus.com.tw/AKM322.htm

Note Win 10 is not mentioned.

Could one of your machines be 32 bits and the other 64?

 

Thanks Dal, (and @Bree) -- I did download these drivers but they were'nt for the AKM322 specifically and so didn't work.
My Win10 laptop is 64bit, my Win10 Desktop is 64bit. Both are updated to the same level.
I think its a USB2 device but it should still work in a USB3 slot. If its actually a USB1 device then it won't.

 

Some USB3 slots have been known to behave 'oddly' with a USB2 device, hence the suggestion to try a real USB2 slot, at least for the first time it's plugged in. The manual seems to say it's a USB2 device.

 

A brief look at Amazon reviews suggests it's plug 'n play- so maybe no drivers needed..

 

The specs page you linked to earlier says that too...

 

I just checked Bree, the slots on my desktop are mainly 3.0 but this midi controller is actually plugged into a 2.0 slot.The device is plug and play, it worked fine on my laptop without the need to download any drivers.

 

Try uninstalling it in Device Manager. Hopefully it will load the correct driver second time round. I've had to do that on occasion for memory sticks that were not correctly recognised the first time.

 

I've uninstalled/installed it multiple times and tried different slots too.

 

There may be a clue in log files. On each machine, zip C:\WINDOWS\inf\setupapi.dev.log and upload to next post. Then also report the hardware IDs for the device. Right click device in Device Manager->Properties->Details tab. Use pull down to select Hardware ID. Copy/paste the ids into next post. I expect they'd be same on each machine but may as well report from each machine as well