Hi all. I mixed up two USB ports (PCR300 and UA-25) on my W7 laptop and although I have now switched the two USB back the way they were originally, upon opening a project my MIDI track Input settings were scrambling (Sometimes but not always)
In total I use the following...

• Roland PCR300
  
• Roland UA-25
  
• Alesis Control Pad
  
• Digitech USB Mouse
  

 I found a workaround by changing the PCR to the USB Mouse port, but that leaves me without a mouse...Ouch!
 While trying to resolve this back to how it was I came across this article...
http://www.harmonycentral.com/t5/Technology-Computers/Solving-the-Windows-MIDI-Port-Problem/ba-p/34667124
And this...
http://www.tech-recipes.com/rx/504/how-to-uninstall-hidden-devices-drivers-and-services/
 
I've followed the instruction carefully but only connected USB drivers are displayed,I cannot get the device manager to show any greyed out none connected divers in the “sound,video and game controllers” section.
 
I know for a fact that I have a Line6 pod-xt among others MIDI drivers installed (but not connected) but they don't show up greyed out or at all. So I started unpluging the none greyed out drives one by one, each time repeating the the full procedure as explained in the two articles, but each time they did not show up greyed out.
 
So I tried this procedure on my desktop W8 and this proses works fine and I can see all devises that are present (highlighted) or not connected (greyed out ) Strange!
 
Has anyone any thoughts on whats happening?
 

In Win 7, Device Manager will only show connected devices.

Hi Mike... AS I understand the articles, Using the Batch file as below...
 
set devmgr_show_nonpresent_devices=1
start Devmgmt.msc

 
Will open “Device manager”. Then click on “view” and select “show hidden devises” and they should be there.
 
This is well documented in the first link I posed . The article was writen by the man himself … Craig Anderton

Ok. I didn't look up the links and referred only to default Windows behaviour

I used to have a midi driver that was port-specific, on a computer I used for gigging.  I would sometimes plug the USB cable into the wrong port, and it would not load the appropriate driver.
 
I seem to recall I would re-install the drivers, as it was quicker than plugging into the different ports until the correct one was found.  This would then associate the midi device with whatever the new port was, and all would work thereafter.
 
I always thought it was pretty stupid on the driver designer's part to tie a midi driver to a specific midi port, but then again, I was an idiot for not writing down which ports were tied to which devices.
 
Bob Bone
 

Perhaps the commands in this batch file don't work in Win 8??

robert_e_bone
I used to have a midi driver that was port-specific, on a computer I used for gigging.  I would sometimes plug the USB cable into the wrong port, and it would not load the appropriate driver.
 
I seem to recall I would re-install the drivers, as it was quicker than plugging into the different ports until the correct one was found.  This would then associate the midi device with whatever the new port was, and all would work thereafter.

 
Yep... done that and all's well. Thanks Bob

robert_e_bone 
I always thought it was pretty stupid on the driver designer's part to tie a midi driver to a specific midi port, but then again, I was an idiot for not writing down which ports were tied to which devices.
 
Bob Bone

Ha! I wrote down the ports, but my mistake was lack of mindfulness. Oh well another mistake made and some more knowledge gained, so I suppose it some good has come from it. :)

Good news, indeed.
 
I like my Sundays to start out cheerfully - play on, Sir, play on.
 
Bob Bone