Hold on - ok so now Windows is up, and we need to use another method to tell it not to install the wrong drivers.

Just a second and I will post the few steps to do that - be right back.

Bob

That's a deal!

Don't be stressed - We KNOW what the problem is.  All we have to do is get Windows to play along, and we can do that too.

The only reason it is taking so long is because we have to do it all with typing.  But, no problem.

OK here are some steps to tell Windows NOT to do these driver installs anymore.  (We will turn this back on when we are done, because most of the time we WANT Windows to keep things up to date for us).

1.  Click Start, type devices and printers in the search box, and then click Devices and Printers.


2.  All the devices connected to the computer are listed, including monitor, keyboard, mouse, printer, and so on.  Under Devices,     right-click the icon for the computer, and then click Device installation settings.


3.  A new window pops up asking you whether you want Windows to download driver software.   Click to select No, let me     choose what to do, select Never install driver software from Windows update, and then click Save Changes.


4.  Click Yes when you are prompted for confirmation. (It will give you that do you want to let this program make changes message box - just click Yes).


5.  That's IT for these changes - when we are done we will change them back and I will list THOSE steps to reverse the changes.


6.  Take a BIG drink of beer - you are drinking for me too, since I don't have any here with me.


But do the above changes, then let me know you have finished.  When you have finished, Windows should STOP tring to beat us to the installation of the drivers WE want to put on your system.


OK - so, get to it and let me know when you are done with those steps above.


Bob

Yes, I have done what you said, rebooted, checked that "Never" is still there, but the driver is still provided by Microsoft

Hold on - do not worry.

We TOLD Windows not to do it again, but it had ALREADY loaded those drivers from before.

We are going to manually install the drivers now that windows is out of the way.

Quick question.

You told me earlier that Windows wanted you to uninstall, and then to reboot.  At what point in the process was all of that?

Once you answer that, I will quickly detail the few steps it will take to get your correct driver installed.

Bob
 

ok - so you had to reboot?

And your drivers are uninstalled?

And windows is back up?

And you still have some beer?

And you are READY to get this finished?

Bob

Yes, Iam hugging the next bottle. I just read Keith Richards memoirs and he had not slept for 8 days in order to get the recording finished so I can give up at least one night, its almost 3am here.

To clarify previous post: when I plug USB "setup" or "Roland" installation is interrupted by automatic installation. The "setup" installation is then not finished. When I try to close the window it offers to unplug and uninstall. If I choose so it will reboot

Nevermind. 

OK, Nevermind

Actually, Dave is trying to save me from myself, and I THANK him profusely.

I got myself in WAY over my head as far as getting into a bunch of threads while we have been working on this one.

I have dropped out of those or wrapped them up, and will  NOT be repeating that over-extension anytime soon.

THIS is the thread I have been trying to nurture through. 

Thanks again Rob, AND Dave, and everyone else.

OK - let's get this working so we both can call it a day.

1. UN-plug the interface

2.  We want to then start your driver installation program

3.  I believe it will ask you to plug in your interface and then to click next - or maybe it will auto-detect that you plugged it in.  It is at THIS step that we should have disable that WIndows attempt to install its stupid drivers.  SO, please let me know what happens after you start your driver install program and THEN plug in the interface.

I won't go anywhere or answer any other threads - so do the above and tell me what happens.

Bob 

I didnt (and couldnt) click NEXT. So it performs automatic Microsoft installation anyway

Bob, thanks, I owe you one!  Anytime tomorrow, I go Keith Richards way

I am going to have to do some digging at my end - which I will do in the next couple of hours.

I'll be having a GIANT cup of coffee shortly, then after some of my neurons fire up I will see what's what with this.

The only stupid part of this is getting Windows to stop trying to get its own stupid drivers installed.  Once we get you past that, you will be in FINE shape.

Hang in there, 

Bob Bone

Actually I used to have this same problem with my old ua25.

I've not read everything else however, I changed the driver mode from WDM to ASIO and bingo all sorted. 

It may be the other way round but, you get the idea.

Give ia go.  HTH

This is an alternative method of control the auto-install of the drivers by Windows.

First, we need to undo the other settings change we made:

1.  Hit the Windows Start button
2.  Click on Devices and Printers
3.  Right click on the computer icon for your computer
4.  Click on Device Installation Settins
5.  Click on the radio button for Yes, Do this Automatically (Recommended)
6.  Click on Save Changes

OK, with that done, we move on to set up the alternative method of controlling Windows device installation actions:

1.  Unplug your interface
2.  Hit the Windows Start button
3.  Type gpedit.msc and hit enter - this opens the Local Group Policy Editor.
4.  If the Do you want tolet this program make changes message pops up, click Yes


You should now be in the Local Group Policy Editor, and we can make our settings changes:

1.  On the left side, Expand Computer Configuration, expand Administrative Templates, expand System, expand Device Installation, and then click Device Installation Restrictions. 


2.  In the right window, double-click Prevent installation of devices not described by other policy settings.   This opens up that policy for editing.


3.  Click to select Enabled, and then click OK.  This tells Windows that unless you specifically enter a device, it will not attempt to install any device drivers, such as your interface.  This policy overrides all other policies.


4.  Restart the computer


5.  Hit the Windows Start button


6.  Type Device Manager and hit enter.


7.  Navigate to where your interface is listed, under Sound, Video, and Game Controllers.


8.  Right-click on the interface device, and click on uninstall.  This should uninstall the device.  If this makes you also have to restart again, go ahead and do so.


At this point, the interface device should no longer be present on your system, and we should be able to run the proper device driver program:


1.  With the device unplugged, start your device driver installation program
2.  When it asks you to plug in your interface, do so.
3.  Follow the instructions for the install.  The Windows Device Driver Installation may start, but that should only be in connection with your proper driver install program's running, and should not be Windows trying to auto-install any drivers.


At the end of the above, if all goes well, you should have the proper drivers installed.  Please then go check under device manager at the driver details, and post back with that info, Driver Date, Version, etc...


OK?  I HOPE this works, and am anxious to see what happens this time around.


Bob Bone

Afrodrum


Thanks, same as my X1 the computer is three days old and its not completely finished yet. It has some monster 12 core processor, 24GB RAM, Windows 7.  I will attach specs to my ID as soon as its finished.

The moment I plugged UA-25 in the system recognised it as the soundcard and I could play with no problem mp3's, you tube and X1 samples.

I went to EDIT->PREFERENCES->AUDIO->PLAYBACK AND RECORDING and switched to ASIO.

Then I went to EDIT->PREFERENCES->AUDIO->DEVICES and my UA-25 is not listed in INPUT DRIVERS window neither in OUTPUT DRIVERS windows. Both windows are empty. I downloaded UA-25 driver from Roland site and the installation went knowhere in the middle - at one point NEXT button went grey.

This was one of the first things he was told to check, and above he seems to say he has done that, although I am not sure of where the above was left.  Maybe he needed to APPLY the change to ASIO mode to then be able to see the it in the devices list?


Please review and post back, 


Thanks, 


Bob Bone