Thanks guys. I just update to Win 10 Pro from Win 7 Pro, on the last free day, today. When booted Sonar, it said my midi was missing. I have a Edirol UM-550, which was the fastest midi interface using 5 parallel output ports instead of the normal series method for more precise timing. I forgot they moved to Roland like my old Delta 1010LT cards, they are terrible with providing drivers and I will NEVER buy anything from them again. I thought it was a typo when I found they had no Win 10 drivers, and boldly said they are not making one. So I took the Win 8/8.1 driver and remained stuck after I turned the unit on after I uninstalled the Win 7 driver. I tried to follow the instructions here, but found they were missing a few steps maybe, so I hope I can make it clear to how I got it to work with Win 10. First I uninstalled the Win 8 driver I put in, use the uninstall to get rid of the Win 7 driver. The Win 8 Driver comes in Zip form. Unzip it to another folder you name like; "Ediunzip", etc. After it is unzipped. you will see a .exe file, and one folder named; "files" and "Readme". Take that folder "files", then the 64 bit folder, and use the Windows Wordpad, and open it with the all file extension pulldown (*.*). You will see a bunch of files and one with a .INI extention (RDIF1020.INF). Now take the Windows Wordpad and open that file. You will see a few places where it has; "Windows 7" in the text, I changed them to Windows 10. I also changed wherever I saw that 6.2 to a 10. Saved and closed. Next step, restart the computer using the start button while holding the space key down. Click troubleshoot, to get to the option to boot without signature screen (#7), on next screen after the options are shown. Turn off the UM-550 before the computer will re-boots in the without looking for signatures mode, if you turn off the UM-550 you wont have to remove the USB cable. After the computer boots, do not use the setup.exe file outside the files folder, but use the one in the 64 bit folder (I have 64 bits, I can't say if the 32 bit folder would work for 32 bits, but use that for 32 bits and change the INI folder in there not in the 64 bit folder. When the setup.exe 64 file is executed you will be prompted to continue to load this driver. Click to use it, and after it is loaded you will be asked to connect the USB cable which I never removed, and turn on the UM-550 via the power button. After a few seconds your driver should be working.  
Thanks, saved me from buying another midi interface to my keyboards and midi sound hardware. A Motu 5 x 5 midi interface is $139, and the only thing wrong with the UM-550, is that no one updated the driver. The last thing I was thinking about was buying a midi interface. Keep that modified Win 8 to Win 10 driver file, in a safe place.   
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
164 bit folder.      

Hi Folks,
Just wanted to say a big thanks for the tips here. I got my old Edirol UA-25 working again after upgrading to Windows 10 and in case it helps, I did the following:
 
1) made the amendments to the .INF file as per that shown by OGG
2) Disabled the signing using the Win 10 interface as follows - rather than via the direct code insert, which did not seem to work for me:

1. Select the Start
2. Open  Settings
3. Click on the Update & Security
4. Click on Recovery
5. Click on the Restart Now button under Advanced startup
6. Select Troubleshoot
7. Select Advanced Options
8. Select Startup Options
9. Select Restart
10. A menu will appear where you can press 7 on your keyboard to choose Disable driver signing enforcement

Now Device Driver Signing should be disabled. You need to restart your Windows 10 computer before you can try installing that the driver again.
3) Went into Device Manager and found the UA-25 under "Other Devices" with its little exclamation mark.
4) Updated the driver and clicked "install anyway" at the big red Windows warning window.
 
The driver installed ok and the UA-25 now appears correctly in Device Manager under "sound, video and game controllers" Made a quick voiceover recording with my Rode NTG1 via ch1 + 48v power; and it all worked as before. So like others, I want to say again a very big thanks; I got there in the end!
Hope this helps.
Peter

The Windows 10 anniversary update uninstalled the driver. Edit: just needed reinstallation, no changes to .inf files needed.

Hi People,
 
I just opened an account here to say 'Thank you so much' to you all.
 
This morning Windows 10 started it's upgrade to the 'Anniversary Edition' with no warning. Took some 40 minutes for the upgrade itself, then the fun started. Most of my original Win 10 tweaks had been erased, including the driver tweak for Edirol UA-25, my old faithful that has performed perfectly for years.
 
Pleased to say, method 2 setup from Windows driver install worked well again using the drivers for 8.1 I did modify the inf file but that may not have been needed as driver signing was disabled as per the method 2 list.
 
A few more hours and I may have this PC set up as I want. Fixed the Office Upgrade nag, fixed the Edge nuisance, shut up stupid Cortana (oops, it just came back), printer work next. Oxygen II keyboard is not working yet. It shouldn't be like this...
 
I'm glad so many folk take the time/trouble to help us regain at least a small amount of control over the computers we own.
 
Thanks again.

Thank you. This worked for my modest A-500S controller. I did as you said:
 
- Advanced Restart and disable the driver signature enforcement only on the next session.
- Downloaded last official driver for Windows 8.
- Replaced text in the .INF file ("6.1" to "10").
- Installed driver as normal.
- Working A-500S in Windows 10.
 
I'm very disappointed with Cakewalk/Roland.

Siggimund
Thank you very much
It worked with my Edirol PCR 300 midi keyboard controller on Windows 10  anniversary.
Can anyone tell me if the "Disable driver signature enforcement" are now permanently disabled or is this only for this driver install (what I would prefer for security reasons)?

I guess it is permanently. Perhaps the driver would stop working at the next restart if it was not permanently.

Better late than never... HUGE thanks to a topic starter who brought my tried and true SonicCell back to life (Win 10, all updates, blah blah..)
Method 1 (replacing 6.2 with 10) did all the magic. Previously working .inf file did NOT work with updated Win10.
Shame on you, Roland!
 

soens
What about deleting all references to Windows versions or using Compatibility Mode? I'm using Windows 7 drivers for my interface under compatibility mode with Windows 10. They work fairly well but I do have to reinstall them periodically.
 

I did the moded driver install as outlined in this forum and only had to reinstall once (after the anniversary update). maybe that reinstalling you need to do periodically derives from issues with the compatibility mode???

Just a quick for what its worth.
 
up until recently I was working on an M audio interface with an old version of sonar and old copy of windows(either XP or 7....  cant remember at the moment).
 
Anyhow all was well til the PC died.
 
I chose to update everything.  I got a new windows PC with windows 10, bought sonar platinum, and bought the roland studio capture(for my interface).
 
I was not aware that there were any windows 10 issues at all(as a matter of fact roland was advertising the studio capture as something that integrates very well with sonar and works on windows 10 just fine).
 
in this case...  ignorance is bliss.  Had I seen this thread I may have had reservations about the roland unit and went a different way.
 
But I didnt so I bought the roland and zero issues to date with this rig as a whole.
 
although there may be some bugs out there with older roland gear...  it seems like at least the current gear coming out does indeed play well with windows 10.
 
Just thought Id throw that out there for anyone contemplating anything new from roland.
 
As a side note....  this thread just might be the reason that the new gear seemingly integrates just fine :) 

The CEO of Roland Corporation is Junichi Miki, President and CEO.
[font="'helvetica neue', arial, helvetica, sans-serif; font-size: 22px"]Corporate Information
Address:
2036-1 Nakagawa Hosoe-cho
Kita-Ku Hamamatsu
Shizuoka, 431-1304
Japan

Phone: 
Fax: 
Web url:  dot roland dot co dot jp
 
 

greg_moreira
Just thought Id throw that out there for anyone contemplating anything new from roland.
 
As a side note....  this thread just might be the reason that the new gear seemingly integrates just fine :)

Studio capture drivers are "automatically downloaded when needed"... so I can can not quickly check myself.
 
But you have it installed. Find relevant INF file and check there is no "time bomb" (empty "not supported" section with not existing Windows version, like NTamd64.10.10... or NTamd64.11.0).
 
If there is no such section, that was a good point to "throw that out".
 
If you see such section, wait till MS change the version ID and your device become nice looking door stopper
 
See my explanation before, so far Roland has declaring drivers OBSOLETE FOR NEWER WINDOWS VERSION, long before that new version is even planed by MS, obviously without checking the driver for "compatibility" (with not existing version).
 
And one more thing. Most drivers (at least for older devices) are effectively the same, for the same hardware (Edirol). You can check Linux kernel source code... Still some are "supported" under Win10, other not. Is that not funny?

I'm looking for the Edirol UA-3D driver. Does anyone know where to get it?

Thank you this works perfectly for FA-101 on Win 10 Creators/Latest update

Hello, i have Edirol UA-5 interface, after WIndows 10 anniversary update dont work anymore, they only have Windows Vista and Seven drivers support in Roland´s Page. Can i try to do the same method??? sorry for my english. I'm from Venezuela need this interface working again cuz here is toooooo difficult to get a new one. thx for reply