Roland, who make the venerable MIDI to USB interface the UM-1, and its more recent version the UM-1X, claim that they will not support Windows 10. And, indeed, when you install Windows 10 onto a machine with the UM-1X plugged in, it remains unrecognised by the new operating system.
You can fix this with a text editor. Remember also you must set your Windows installation NOT to enforce driver signing. Please see the comments (below) for how to do this.
- Download from Roland the driver archive for Windows 8.1. Its filename is um1_w81d_v101.zip.
- Unpack the archive.
- If you have a 64-bit machine, browse within the archive to this folder:
um1_w81d_v101\Files\64bit\Files - Open the file RDIF1009.INF in your favourite text editor.
- Edit line 33, changing:
%MfgName%=Roland,NTamd64.6.2,NTamd64.7…to
%MfgName%=Roland,NTamd64.10.0,NTamd64.7 - Edit line 42, changing:
[Roland.NTamd64.6.2] …to
[Roland.NTamd64.10.0] - Save this file and exit the editor.
One successful user reported that he plugged-in the UM-1 at this point. - Browse to your Device Manager by holding down the ‘Windows’ key, pressing ‘R’, then selecting “Device Manager” from the menu that appears.
- Double-click on your non-functioning UM-1, which will be labelled “Unknown device”.
- Select the second tab: “Driver”
- Click the “Update driver…” button
- Click “Browse my computer for driver software”
- Browse to the folder containing the file you have just edited
- Click ‘OK’ to select the directory, then click ‘Next’
- When Windows complains “Windows can’t verify the publisher of this driver software”, click “Install this driver software anyway”
- Wait until you see “Windows has successfully updated your driver software.
Done! You’ve installed the Windows 8.1 driver for the Roland/Edirol UM-1X on Windows 10, even though Roland state they don’t support this device. I can confirm that the MIDI input works just fine.
Thanks! One thing worth mentioning is that you need to make sure to disable the Driver Signature Enforcement option in Advanced Startup – once that was done this solution worked perfectly.
Great. That was getting on my nerves… now everything’s working. Hoorah!
I tried a couple of times without any success it comes out that the hash of the file is not present in the specified folder, etc.
I ve done this now as mentioned but not been lucky.
I might be doing something wrong but I have no idea to what.
Thank you so much!!! I have an Edirol UM-2 and by doing something similar I made it work on Windows 10 too.
One thing to note though – there was an extra step that I had to do as I am using a 64-bit OS and by default it will refuse to install driver that has been tempered with / are not properly signed or certified.
Stumbled across this page after a bit of searching: http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/
In summary this is what I had to do:
1. Hold down ‘shift’ while choosing ‘restart’ to reboot the machine
2. There will be some sort of a boot menu after restarting (because of the ‘shift’ key in the previous step). Pick ‘troubleshoot’
3. ‘advanced options’
4. ‘startup settings’
5. hit ‘restart’ button
6. after restarting again you will be given a list of startup settings that you can change this time. Press the “F7” key which should stand for ‘disable driver signature enforcement’
7. After starting windows this time try installing the driver per the instructions in your blog.
That was the trick, thank you! Working now. Thank you!!
This is the important step!!!!
100 OK! THX!
blog+‘disable driver signature enforcement’ – for UM-1EX
Gentlemen, thank you for replying. You are perfectly correct: I forgot that, in order to make a non-standard graphics driver work, my system is already set not to enforce driver signing.
I have downloaded the driver, made the changes you said to do, saved the file, but my computer still won’t recognize it.
I also disabled driver signature verification.
Any idea why it is not working?
Hi Travis. Can you show me any error message you’re seeing, please?
I read the article above and edited the RDIF1003.inf file. There is no 1009 file. Is there another version of um2_w81d_v101?
Installing the driver does not work as plugging the Edirol is not recognised. I have an Edirol UM – 2 (without switch) and am using Win10 32bit. Can I get it to work with this configuration?
same thing here ! i downloaded the file from roland website and there is NO 1009, only 1003. what to do ?
Hi John
I have just seen this post
Will it work for windows 11
Thank you so much!
Works exactly the same way with EDIROL UM-1S
Great!
Grazie….. Funziona!!
Works perfectly fine 🙂 thx
So thankful to have found the answer to keeping the interface working in Windows 10. Kudos to you.
I’d not had my EDIROL UM-2 that long so was very annoyed when the Windows 10 support was not there and I’d tried every workaround thinkable.
Thank you so much for this.
Shaun
@limitedbudgetmusic
John, I just wanted to say thank you for providing this workaround for installing the driver. I found out the hard way yesterday that this problem existed when I dusted off my UM-1SX for a small project on my Surface Pro. Thanks again, I owe you a beer.
I’m a novice at this stuff, but am desperate so am going to try this workaround to get my UM-1x working with Windows 10. However, I’m stuck on step 2: “Unpack the archive” What does that mean?
Hello, and I hope you can get this sorted out ok.
Unpacking the archive means unzipping it, in this case. Your Windows machine should automatically open a .zip file if you double-click on it, and then you can copy (drag and drop) the content of the .zip archive into a fresh location for further work.
Thank you, thank you, thank you! Followed the steps meticulously (even though I don’t understand what I’m doing). My UM-1X midi now works again. Very grateful.
You’re a lifesaver, friend!
Happy to help. More than ever before, we need to fill the world with good music.
It was said very well by Leonard Bernstein in November 1963.
I stumbled on your page while searching for a midi interface advertised as compatible with Win 10, to replace my Edirol UM-1EX that had stopped working in the switch from Win 7. I had already tried the Win 8 driver, without success of course. Armed with your instructions and a 10 second edit, I reinstalled the Win 8 driver and my Yamaha keyboard is connected again! Many thanks for sharing your expertise:)
Extremely helpfull my friend , my UM-1S lives to see another day. Also thx to Sam for the very clear instructions to switch of driver signature enforcement
I tried that with UM-3EX to win 10 32 bit. It is work well, so thanks very mutch for your great help!
Tamás
Thank you very much; I have been using the UM 1 for years and have just bought a new Lenovo ideapad with Windows 10 and an i7 processor to run Cubase elements 8.
I was mortified when I couldn’t load the Roland driver but have everything has now lit up after following your instructions to the letter. I can now connect the tc-helicon vocalist and my old midi keyboard.
Thanks once again,
Ivor
This is Bonnie again. I don’t use my midi very often — every 2-3 weeks. It’s been working fine, but I just hooked it up tonight, and my computer is not finding the device! I tried rebooting, and it’s still not showing. Any suggestions?
When I plug into the USB port, it’s making a sound, but the device doesn’t appear on my Midi Set-up screen like it did before.
Just thought of this: there may have been an auto Windows update…. Boo. Do I need to go through the steps above again to restore the driver?
Hello Bonnie — I’m sorry to hear of this trouble. I must admit, this problem hasn’t occurred here, even though the system is kept up-to-date with the automatic updates provided by Microsoft.
Now, a couple of weeks ago, it was necessary to re-install another, unrelated, old driver to overcome a Windows upgrade mess (Open GL 2.1 became unsupported on an old graphics card), and it is just possible that you need to re-install the patched Roland driver for a similar reason.
However, I’d also email Roland to put pressure on them to update the driver for this popular MIDI interface, anyway.
Please let me know if a re-installation of your driver works for you.
Hi John. I was thrown off at first because when I got to the “unknown device” and tabbed to the “update driver” button, it was greyed out. I finally found something on another screen that allowed me to update the driver, and it looks like it is working. I will follow your suggestion to email Roland about this, but it doesn’t seem like they are interested in updating the driver. And I’m still confused about why it reverted back to “unknown device” when the edited .inf file was still in tact. Thanks for your help and encouragement.
Glad to hear it’s working again. Thank you for letting me know.
I heard back from Roland. It was a courteous response, saying they won’t be creating any new drivers for these devices. I guess I wasn’t very convincing 🙂 However, he did say that the device has an on/off “advanced driver” switch that can be turned to “off” (mine is in the “on” position, and I’ve never touched it) and that supposedly allows the device to function without a driver. I’m not sure just how functional it would be. But if my driver disappears again, I might give that a try and see what happens.
Thanks John and Andrew! Worked like a champ!
I think Roland should hire you as an adviser ,this kind of customer neglect is no way to treat Roland users ,whithout you we would be forced to throw away a perfectly good MIDI interface , maybe thats what Roland wants : us buying a new one !! Is that the thanks we get for years and yea
years of faithfullness to the brand ( i have a D20 ,a Roland Midi controller , a GR series synthesiser Guitar and a UM-1
Oh and i forgot my pc-300 midi keyboard , no driver or support for that one either (luckely i can get it to work through the UM-1s thnx to John)
Some companies have (I think) good reason for letting old products drift off after a certain number of years, e.g. Windows 3.1 whose underlying memory model could not possibly be financially viable to support. But as you, Pascal, point out, it’s disappointing to see a largely respected manufacturer neglect a piece of hardware that countless musicians use because it perfectly does its job, and needs do nothing more. Roland have made many good choices, and I happily play their instruments; but to drop support for this interface is a bad choice.
Thank you so much! Es funktioniert auch in Deutschland…
purtroppo pur avendo seguito alla lettera le spiegazioni il mio UM-1 non funziona e nell’istallatre il driver rileva che il file è stato maneggiato
Grazie per il vostro rapporto, Giovanni. C’è un interruttore sul lato del UM-1, con l’etichetta “Advanced Driver”? Si prega di eliminare il driver, regolare questo interruttore, e quindi reinstallare il driver.
Se questo non funziona, non so che cosa il problema è. Si prega di essere il più dettagliato è possibile con tutte le segnalazioni di errori.
Thank you for your report, Giovanni. Is there a switch on the side of your UM-1, labelled “Advanced Driver?” Please delete the driver, adjust this switch, and then reinstall the driver.
If that does not work, I do not know what the trouble is. Please be as detailed as you can with all error reports.
Many, many thanks for this information and thread.
I have a Roland SD-90 Sound Module and when I updated from 8.1 to 10 I immediately hit the problems described.
A polite request to Roland basically said, in the nicest possible way, sod off.
Why they don’t publish this sort of information even with a health warning I have no idea.
Anyway it is all working just fine on Windows 10 so again many thanks to everyone
I can’t tell you how blessed I am to have found this website. Having just upgraded to Win10, I found my UA1ex and my UM1ex both not working. I was very disappointed.
The steps you gave absolutely worked. 😀 PTL!
Oh yes you are the man!
Partial Success.
The procedure worked fine on a laptop, but so far, no joy on a Dell tablet.
On navigating to the folder containing the edited .inf file , windows notifies …
“Windows could not find driver software for your device”
On right-clicking the .inf file and selecting “install” , confirming ok to proceed with unsigned driver, the driver appears to be being installed. Windows reports “the operation completed successfully”
Device manager still shows “unknown device” and “the drivers for this device are not installed (code28).
If anyone could suggest any further steps I could try, I’d be much obliged.
Ian
oops…..
Just realised the tablet is running 32 bit windows 10 Home
Man! Thank you so much, you are a life saver! Very clear instructions.
Many Thanks John!
Believe it or not, I’m now running Cubasis VST 5 on W10 64-bit, connected to my Roland via the UM-1. Happy. I can listen to my son’s ancient recordings safe in the knowledge that they should be safe for another decade or so.
Time to migrate to Cubase. 🙂 I’m trying to find out from Steinberg re migration options…
All the best.
MAKE THE EDIROL UM-2 WORK ON WINDOWS 10
Hello; I have an Edirol UM 2 put there ‘s no driver wondows 10, I read your post on the UM1, What would be the handling to be performed for the windows driver or 8 can run under Windows 10
Sincerely Alain
Hello Alain,
I am sorry, but I do not have a UM-2 to test. However, I would begin by downloading the most recent Windows driver for the UM-2 you can find, and then open the file archive and edit it in a similar manner to my instructions for the UM-1.
Good morning, John,
Thank you for your valuable conseils.J’ai tried to manipulation but that did not fonctionné.Je’ll repeat and I’ll tell you if it works. Sincerely Alain
Good morning, John,
Thank you for your valuable conseils.J’ai tried to manipulation but it did not work .I will do it again and I would say if it works you. Sincerely Alain
Many many thanks for this info and detailed guiding to install UM1x for windows 10!!
Works perfect, thank you
Ninos
John
Thanks so much for this brilliant piece of information. How sad that a change that takes minutes, couldn’t be done by Roland to support customers. I guess they want to sell us all a new interface at fifty pounds a shot. When the change is just 6 digits – it’s a bit cheeky.
A word for people working with the UM-1SX. Make sure the Advanced Driver switch is set to OFF otherwise the device doesn’t see the edited driver.
Thanks again.
Thanks so much for this. It works exactly as described with EDIROL UM-1S.
it was working fine but suddenly it appears again as unidentified device…i did the same process but now it appears a warning message saying that windows had found a driver but the file has been manipulated…help please
Hi, I’m having issues when installing the driver, I have tried everything I could think of but when I try to update it, windows say that the device is already up to date. I have tried uninstalling the driver and installing it again, turning on and off the advanced driver switch, as well as disabling the driver signature setting. No matter what I do it just won’t work and it’s extremely frustrating, so if anybody can help me with this it would be greatly appreciated. Oh, and by the way, I have a Roland Edirol UM-1SX. Thanks.
I didn’t have to go through this. At first when I plugged the UM1-X in it was not accepted. However after a reboot the UM1 works fine. Looks like Windows 10 found a driver…
Win10 PRO 64-bit (Swedish) ver 10586.420 July 03 2016.
Note: UM1 was had the ‘Advanced switch’ in ‘No’ position (don’t know if it matters.)
Hi man, somtimes life is beautiful. Works like a charm! Thanks!
UM-1ex ans focusrite scarlett next gen ake a good pair for me.
Unfortunately these steps did not work for me.
Device manager states
‘The best driver software for your device is already installed’.
‘Windows has determined that the driver software for you device is up to date.’
‘Unknown USB Device (Device Descriptor Request Failed)’
If anyone has further ideas I would love to hear them.
kind regards
Thank you VERY much for this info! I now have my loyal UM-1SX back and running. It’s one of the few ‘simple’ USB interfaces that can drive a MIDI Solutions box for programming.
And an open comment to Microsoft: Could you folks possibly make it any harder to disable signed driver checking? I mean, THREE reboots? Gawd!
Thank You so much, You made my day.
I did a simliar edited installation in July last year, after my change from W7 Pro 64 to W10 Pro 64.
After the upgrade to W10 1607, my UM-1EX no longer likes to work.
Now, I used Your step-by-step info and it works !
My Roland Juno and my GT-8 works .. just great.
Thanks again.
Remo
Hi all.
I need some help please.
“UM-1X driver 64 bit”
I followed instructions:
– disabled driver signature verification
– downloaded um1_w81d_v101.zip.
– changed the RDIF1009.INF file lines as instructed
I still get an error updating driver through device manager.
“windows found driver software for your device but encountered an error while attempting to install it.
UM-1
The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.
Help is highly appreciated.
Thank you 🙂
Repeated steps and all worked fine this time.
Thank you for the information. Definitely great to have edirol UM-1X working again.
Highly appreciated. Thank you.
Very kind of you to tell me you have solved the problem. The error message you quoted is new to me, and I would not know how to progress with it.
Google for “Windows 10 Disable driver signature verification”.
It involves booting into troubleshooting mode etc.
Once you’ve booted without driver signature verification, the procedure in the original post will work.
When the installation is done, you can reboot and driver signature verification will be on again.
UM-3ex works perfectly! So easy. Thank you
Omg so simple and yet …anyway i love you john warburton for that !
Man if i ever come out with my album the thank yous list is going to be so long lol.
Thanks, John. It also works on two UM3-EX connected in series.
Hi. I can’t get this working on my Windows 10. I used this (or a similar guide) a while back to get my Roland PC-300 working on Windows 7 and was excited to see people getting it working on Windows 10 but, I can’t get it to work. I get the message “Windows was unable to install your Unknown Device” with sub message “Windows could not find driver software for your device”. I am gutted… someone in these comments got it working for their Roland PC-300… any help would be massively appreciated.
I am sorry not to know the answer to this one, not having the PC-300 hardware myself, but perhaps someone else might like to reply below?
I went out and bought a new keyboard, M-Audio Code61 and am very happy with it. However, I would like to update on the progress of the PC-300 because I just recently managed to get it to work and hope it will help someone else.
I used the UM-1 driver for Windows 8 (downloaded from Roland). Edit the .ini file as explained in the original instructions on this page (replacing 6.2 with 10)… BUT ALSO change “PID_0009” to PID_0008″… this was at the end of line 44 in my .ini file. Save the file.
Now rename the file to “RDIF1008.INI”.
Reboot and disable the driver signature enforcement by searching for “change advanced startup options” from the start menu. Choose Restart Now under Advanced Startup. Then choose Troubleshoot then Advanced options then Startup Settings and then press Restart. Your computer will restart but will give you some options…. choose option 7 to disable the driver signature enforcement. The computer will boot with this mode. I found that using registry key changes didn’t quite work whereas this worked first time.
Once booted in, do the driver update as normal by selecting the non working device in device manager and updating the driver… choosing manually the location of your edited and renamed .ini file. It should work and your PC-300 will appear as UM-1 and work again as a MIDI keyboard.
Thanks for this! I hope your notes will help others in the same situation with USB/MIDI interfaces.
Hi,
I have followed your steps and after modifying the UM-1 driver my PC-300 now appears as a UM-1, but I still cannot get it to make any sounds or work as midi input.
Any further advice?
Hey, I followed these instructions but having reached step 14 I’m greeted with the error message “Windows found driver software for your device but encountered an error while attempting to install it.
The hash for the file is not present in the specified catalogue file. the file is likely corrupt or the victim of tampering.
If you know the manufacturer of your device, you can visit it’s website and check the support section for the driver software.”
Any suggestions?
Thanks.
I have not seen this message myself, but you have quoted it fully which allows me to find some help for you. It is possible that you did not switch off the requirement for device driver signing. Now, please be sure of what you’re doing when you follow instructions like these, because this makes it much easier for other, malicious, drivers to be installed…
http://www.technipages.com/enable-disable-device-driver-signing
Hello John I had the same problem with UM1S with Windows 10 Prof. 64bit. I’ve disabled the driver signing and I’ve fixed everything. Thank you very much for your commitment and for solving this UM1 problem
Angel
Neither can I get my UM1X installed.
W10 can not find any driver.
I’m sorry I don’t know how to help with a UM1X. This hardware is something not in the studio here. 🙁
I fiddled with this for hours before finding your blog. Worked like a charm for UM 2. Thanks mate.
Thank you for letting me know how you got on! It’s good to know some decent, but old, kit can still work on our modern computers. I hope you have much enjoyment continuing to make music.
Thanks for the program update information. This worked great! The only thing I would add to the instructions is between step 7 and 8 is to plug in the UM-1 into the USB port. It took me a while to figure this out because my device manager was not recognizing Unknown Device until I plugged in my UM-1. I am using a windows 32-bit machine for my UM-1 and the instructions were spot on. Thanks again
Bob, thank you very much for letting me know about this. And for testing a 32-bit driver, which I have not yet done.
Hi guys, so I have tried to get this working but I get the error
‘The best driver software for your device is already installed’
I have the latest version of windows 10 and the way around this is to select some different options when searching for drivers through the Device Manager;
1) Choose “Update Driver Software”
2) Choose “Browse my computer for driver software”
3) Choose “Let me pick from a list of device drivers on my computer”
4) Click “Have Disk” button
5) Select the directory with the correct drivers
After doing this I still get an error ‘The folder you specified doen’t contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.’
Any thoughts?
Thank you for your question, Sab. Have you modified the driver in the unpacked directory, with the changes indicated in my post, before attempting the installation? If you have done so, then I don’t know why Windows 10 isn’t picking up the correct code.
When you issue the command “winver”, which version is reported?
Hey there. It’s me again. I hadn’t used my midi for a few weeks, and when I attempted today, it was a totally unrecognized device. I started from scratch, and I’m now bogged down at the point of trying to save the modified .INF file. I can’t get it to save the changes. It’s telling me (sometimes) that the file is read-only, by I changed the properties of the file so it is not read only. It acts like it is saving it, but when I check, the changes are not being saved. Any clues?
John, after getting your email last night, I closed all the windows that had the .inf file text (yes, there were 3 open), and I was successful in getting the revised file saved. However, when I attempted to update the driver, I got the error message:
“Windows found driver software for your device but encountered an error while attempting to install it.
UM-1
The system cannot find the file specified.”
I checked to make sure that my changes to the .INF file were saved, and they were.
I see a similar error message above, and the suggestion to be sure to disable the driver signature enforcement. I did disable that yesterday. The machine has not been rebooted since, so it would not have gotten enabled again, would it? Your email referenced the Windows “anniversary” update. ? Thanks for your help.
Bonnie
I think I’m ready to purchase a different midi interface. I feel like I need to get something that will be compatible with Windows 10 from the get-go. I have had this midi for many years, so I think it’s time to say goodbye. Do you have a recommendation for an inexpensive, basic midi? Part of me wants to boycott Roland for their unwillingness to keep current drivers for this product. However, they may have the most solid product (and customer support, in spite of my frustration about this one situation). Your thoughts?
Very intersersting, but i try my Edirol UM-1SX with the “advanced driver” switch in “off” position and it seem to work fine. note i have no drivers installed from roland, just the universal original drivers coming with install of W10.
But thank fo your help it’s very nice for over interface.
Thank you very much worked for UM-2. on 64 bit and 32 bit.
For the 32 bit to work look in:
um2_w81d_v101\um2_w81d_v101\Files\32bit\Files for RDIF1003.INF
go to line 33 and change %MfgName%=Roland,NTx86.6.2,NTx86.7 to
%MfgName%=Roland,NTx86.10.0,NTx86.7
go to line 42 and change [Roland.NTx86.6.2] to
[Roland.NTx86.10.0]
save and follow the rest of the instructions, not forgetting to point the installation at the edited 32 bit file. Once again thank you very much.
Hi,
Do you have a work around for os10.12 sierra and the um-1x?
I’m sorry, but I don’t have an Apple device so can’t help with this one.
Thanks so much for posting this. Worked for me like a charm!
Win10 AU user here, just adding thanks and confirmation that with the “unsigned driver” instructions, and the instructions in the main article, that the driver seems to get installed successfully, and function successfully.
What an simple, elegant fix. You are a wonderful person for posting this. Thanks so much! Your generosity is a great antidote to the corporate greed of Roland.
Did this get broken with the new Creators Update?
Hello Vic. After each major update of Windows, I need to re-install the driver. For example, a new Windows Insider Build arrived yesterday, so the driver was uninstalled and reinstalled manually. As of this morning, it’s working fine.
Ok, I’ll re-do everything as it didn’t seem to work. Good know it’s still ok. Thanks Roland!!
No thanks to Roland. Roland have abandoned their driver support for this perfectly sensible piece of kit. I still don’t know why. My support query some years ago was never answered. My solution is only a hack, and requires the user to knock a temporary hole in Microsoft Windows’ security, which is undesirable in general.
Damn, I tried everything again and again since I got the Creators Update on my PC and it still won’t see my midi device attached, but I can get the UM1 to install ok in Device Manager.
To double check I did a clean install on my laptop and the fix worked just fine, but no go on my regular PC for some reason. I tried going through the registry and removing anything Roland, after uninstalling the driver, but it still didn’t work. I may have to start again on this PC to get it to work. Thanks Roland!!!
I also found my Edirol UM-1X was uninstalled with a recent major Windows 10 update.
Having tried to reinstall a couple of times and failed, I realised I had to restart in the special mode to allow unsigned drivers.
(also need to remember to uninstall any previous attempts to install first)
So does Windows 10 somehow uninstall any unsigned drivers in major updates? Do they ever tell anyone?
Yes, Rick: I have found this to be the case. After each update (I’m using Insider Builds, fast ring), the driver needs to be re-installed using the same procedure. Still, I’m very glad it’s working for you.
J
Thanks for posting this mod. The driver now works for me on Windows 10. I have had a UM1 for probably a decade and it’s great to keep it working through all the versions of Windows.
This is good news! And keep on stargazing!
many thanks!!!
Thanks for the report, Paulo. Glad to know you’re making music with it again.
Thanks so much! Last time I tried my edirol it said No to win10 -I nearly threw it in the trash! Needing it again, and I found this page…I dug it out, followed your steps, and it’s working! Saved me a lot of work, Thank you.
Very glad to hear this, Roger. I’m still mystified as to why Roland won’t propagate the fix. Oh well…!
This totally worked, Thanks man!
Thanks. works with my UA-1EX, too!
It looks like your advice has been widely appreciated. I’ve just had to reinstall Roland UM-1 and it, also, didn’t install. Thanks to your blog and some of the additional comments it is now fully functioning again. Thanks heaps
John Wilkins
Worked like a charm! Thanks for the info! Saved me from having to buy a new midi interface.
Looks like the official support has finally come: https://www.roland.com/global/support/by_product/um-one/updates_drivers/09a08c60-40fd-46d6-b2d4-47f1781dbc2e/
My UM-1X installed automatically on Windows 10 (when the Advanced Driver switch was set to off) .
Heya,
Thanks … just saved me going out and buying a new one!
Here we are – it’s 2019 and the Roland UM-ONE MK2 still doesn’t automagically install its driver to Windows 10.
Enter the solution above: Thanks a bunch for helping out !!
A couple of years ago I successfully got my old UM-1x working with Roland’s drivers under Windows 10 by following the above instructions — thanks John! But this set-up has been regularly broken by about every second Windows update, requiring me to go through the procedure again. I was never quite sure what I had done that got it working again.
Yesterday the Feb 2019 update again cut off relations with the UM-1x and I could not get Windows to recognise Roland’s drivers. What worked this time was to set the Advanced Driver switch OFF, uninstall the device, and reboot. The UM-1x is now listed in the Device Manager as UM-1 under Sound, video and game controllers and it is using Microsoft’s driver not Roland’s.
This is very interesting. Thanks for the update, Kim! Pity the advanced switch must be turned off, though. I’m not sure what it does, however. JW
Microsoft’s July 2019 update again rendered the UM-1x non-functional. Uninstalling the ‘unrecognised device’ and rebooting seems to be the way to fix it, at least on my system (64-bit Windows 10).
Any suggestions for getting a UA-1EX up and running? My issue is that whenever I try to install the modified Roland drivers I get to a point where it prompts me to connect my device so that installation can finish. Whenever I do so, Windows 10 automatically installs its own driver (which allows me to use the device for output but not for input) and the installation of the Roland 8.1 drivers never completes. If I try to update the drivers manually it tells me that I already have the best drivers.
I’ve even tried disabling the automatic installation of drivers but it doesn’t stop it. It’s getting to be pretty tedious uninstalling, rebooting and then rebooting again to turn off driver signature enforcement so I’m at my wit’s end. Any suggestions would be greatly appreciated!
Of course immediately after posting, another comment gave me an idea which ended up solving my problem. I turned on the Advanced Driver switch which prevented Windows from recognizing the device and allowed the Roland driver to complete its installation. Now Audacity recognizes it as an input device and I’m able to utilize the optical input once again! Thanks for providing this guide John!
I got it working (my UM-1S), and that brought me to the idea if this would work also for the V-Synth GT driver which is also not supprted by Roland under Windows 10.
I changed the RDiF1073.INF file for the V-Synth GT in the same way as described for the RDiF1009.INF file for the UM-1. And it works. I can use the USB-interface on the V-Synth for MIDI and Sound.
If you try this, you still have to change the Advance Driver switch as described before.
Now (i hope) maybe Roland will come with a driver for the V-Synth GT that works under Windows 10, as they did for the UM-1.
Thanks to all of you for providing the information
Enjoy the music, have fun, keep on rocking
What a useful addition to know about! Thank you for your note about the synth driver.
JW
I own the Roland G-1000 arranger work station, does anyone know how to enter data from a Zip disk into a computer.
I would be very grateful.
Lester K.
hi.I have tried several times, but my UM-1ex edirol does not work on my windows 10
This device cannot start. (Code 10)
Insufficient system resources exist to complete the API.
received this after taking all this above steps please help am using UM-ONE ROLAND
the same here, have tried several times, but my UM-1ex edirol does not work on my windows 10.
Great! It Works! Thank you!
Greetings from Germany.
Woohoo! great instructions, thanks for sharing! This 5 year old tip is still giving 😉
SUPERDUPER!
Works 100% and directly for me!
Great that I can use this interface again with W10…!!!
Many thanks and greetings from Belgium
Just a brief not to thank you for this amazingly useful tip. Why Edirol don’t just publish the driver with a ‘try it if you like but we don’t support it’ caveat, I don’t know…
after many failed attempts, I finally got it to work on Win10.
None of this worked for me.
I’ve seen two other internet posts on how to make the Edirol UM-1s get installed on a Windows 10 machine and I’ve done everything recommended: Disable signature, change the INF file text, install by updating the driver from Device Manager . . . nothing works. At best, a “Roland” link shows up in both my list of programs and in the system tray but they are unresponsive. The midi interface device does NOT show up in my Sonar X3 Producer program.
The other posts I’ve found are:
http://forum.cakewalk.com/The-ultimate-guide-to-get-your-RolandEdirol-devices-to-work-with-Windows-10-Updated-m3267234-p3.aspx
and
https://answers.microsoft.com/en-us/windows/forum/all/windows-10-midi-input/1cd31191-ab68-4064-94cf-abe515698ef7
. . . and nothing enables the installation.
Would a similar workaround work for w11? Has anybody tried?
I have to agree with the previous poster. I have done everything recommended with my Edirol UM-1S and all I get is the device is installed and connected, but not working because it is not configured correctly. I’ve finally given it up as a bad job and bought a highly recommended interface from Amazon that has very positive feedback for more than 1000 buyers-all for less than £20. The Edirol can go in the bin-I am disgusted that Roland can’t be bothered to support their own haradware.
An update on my previous post.
I realised-eventually-that I had failed to alter the Korg M1R Global Midi setting EXC from DIS to ENA. As soon as I did that, the driver worked for the Edirol UM-1S, and I managed to send Sysex banks to the module flawlessly.
So many thanks for the editing guidelines, which I only applied to the 64x file since that is how my laptop is set up.
I had also been berating Roland for NOT providing a Windows 10 driver, and when I explained yesterday that I had now found instructions to edit the earlier driver to make it work under Windows 10, they asked where I had found the information. So I gave them the link to this website, and sent them a copy of my edited RDIF1009 file as well. I also mentioned the need to disable the Windows Driver Signature Enforcement setting, and the reminder to enable the EXC setting under the M1/R global midi settings. I also mentioned that when using MidiOx I altered the buffer settings to 1024 bytes, and increased the delay between buffers to 1000 milliseconds ( 1 second!) as a precaution, although the latter steps might not be needed.
I tried this on windows 11. I was able to install the driver, and I can select UM1 in Ableton Live.
However, I get no incomming midi.
Anybody could use UM-1 on windows 11 ?
Well actually it works great ! I just had to put :
– advanced driver switch on OFF,
– Thru switch on OFF.
Thank you so much, and to the fine gentleman as well who pointed out the Advanced Startup fix. It all works great!
Did this on a recent fresh install of Windows 11 having had it work fine on Windows 10. Everything worked perfectly on 11, apart from one problem: every few minutes the desktop blanked with a white screen and refreshed. This was happening even if the interface wasn’t connected. Once I’d uninstalled the driver and rebooted, the system was back to normal. Any ideas?
Windows 11 Pro v. 22H2
Thanks for this, however there’s a much easier way to do this – use the Windows Vista driver! Since it doesn’t have any specific versioning information in the driver, you can install this on Windows Vista through to 11 without any issue. The only thing you need to do is find the device in device manager and install the driver manually, instead of using the setup application.
The driver is digitally signed so will install as-is without any issues!
Thanks a lot 🙂
been able to make very old Roland PC 300 (not PCR) working under windows x64 !!
create a restore point
connect keyboard and in config panel, USB driver=> check PID/VID
edit RDIF1009.inf from UM-1 driver change 6.4 to 10 and change PID/VID (see bottom .inf file)
[bios] : desactive sécure boot
Terminal as admin
BCDEDIT -Set LoadOptions DISABLE_INTEGRITY_CHECKS
BCDEDIT /set nointegritychecks ON
BCDEDIT -Set TESTSIGNING ON
[Security Windows]: kernel isolation / desactivate memory sep
restart
install RDIF1009.inf (right click / install)
driver should be OK / keyboard recognized
BCDEDIT -Set LoadOptions ENABLE_INTEGRITY_CHECKS
BCDEDIT /set nointegritychecks OFF
BCDEDIT -Set TESTSIGNING OFF
restart change back BIOS
; Installation inf for the Roland PC-300
;
; Copyright (c) 2013 Roland Corporation
;
[Version]
Signature=”$Windows NT$”
Class=MEDIA
ClassGUID={4d36e96c-e325-11ce-bfc1-08002be10318}
Provider=%MfgName%
CatalogFile=RDID1009.CAT
DriverVer=10/01/2013,1.00.01.0000
;—————————————————————;
[DestinationDirs]
RDID0009.Files.User = 11
RDID0009.Files.Inst = 11
RDID0009.Files.Ext = 10,system32\drivers ; %SystemRoot%\system32\drivers
DefaultDestDir = 10,system32\drivers ; %SystemRoot%\system32\drivers
[SourceDisksNames]
1=%RDID0009DiskName%,,
[SourceDiskSFiles]
RDWM1009.SYS=1
RDDP1009.EXE=1
RDCP1009.CPL=1
RDCI1009.DLL=1
;—————————————————————;
[Manufacturer]
%MfgName%=Roland,NTamd64.10
;[ControlFlags]
;ExcludeFromSelect=*
[Roland]
;; Windows7 – Windows XP 64
;; not supported
[Roland.NTamd64.10]
;; Windows8
%RDID0009DeviceDesc%=RDID0009Install, USB\VID_0582&PID_0008 ; PC-300
;===============================================================;
[RDID0009Install.NTamd64]
Include=ks.inf,wdmaudio.inf
Needs=KS.Registration,WDMAUDIO.Registration
CopyFiles=RDID0009.Files.User,RDID0009.Files.Ext
AddReg=RDID0009AddReg
[RDID0009Install.NTamd64.CoInstallers]
AddReg=RDID0009CoInstallers.AddReg
CopyFiles=RDID0009.Files.Inst
[RDID0009CoInstallers.AddReg]
HKR,,CoInstallers32,%REG_MSZ%,”RdCi1009.dll,ProcCoInst”
[RDID0009AddReg]
HKR,,DevLoader,,”*ntkern”
HKR,,AssociatedFilters,,”wdmaud”
HKR,,Driver,,rdwm1009.sys
HKR,,NTMPDriver,,”rdwm1009.sys”
HKR,Drivers,SubClasses,,”midi”
HKR,Drivers\midi\wdmaud.drv,Driver,,wdmaud.drv
HKR,Drivers\midi\wdmaud.drv, Description,,%RDID0009DeviceDesc%
[RDID0009Install.NTamd64.Services]
AddService = RDID1009, 0x00000002, RDID0009_Service_Inst
[RDID0009_Service_Inst]
DisplayName = %RDID0009DeviceDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %10%\system32\Drivers\rdwm1009.sys
;;;
;;
[RDID0009.Files.Ext]
Rdwm1009.sys
[RDID0009.Files.User]
RDCP1009.CPL
RDDP1009.EXE
[RDID0009.Files.Inst]
RdCi1009.dll
[RDID0009Install.NTamd64.Interfaces]
AddInterface=%KSCATEGORY_AUDIO%, %KSNAME_Md11%, WDM.Interface.Md11
AddInterface=%KSCATEGORY_RENDER%, %KSNAME_Md11%, WDM.Interface.Md11
AddInterface=%KSCATEGORY_CAPTURE%, %KSNAME_Md11%, WDM.Interface.Md11
[WDM.Interface.Md11]
AddReg=WDM.Interface.Md11.AddReg
[WDM.Interface.Md11.AddReg]
HKR,,CLSID,,%Proxy.CLSID%
HKR,,FriendlyName,,%WDM.Md11.szPname%
;—————————————————————;
[Strings]
MfgName=”Roland”
RDID0009DiskName=”Roland PC-300 Driver Installation disk”
RDID0009DeviceDesc=”Roland PC-300″
Proxy.CLSID=”{17CCA71B-ECD7-11D0-B908-00A0C9223196}”
KSCATEGORY_AUDIO=”{6994AD04-93EF-11D0-A3CC-00A0C9223196}”
KSCATEGORY_RENDER=”{65E8773E-8F56-11D0-A3B9-00A0C9223196}”
KSCATEGORY_CAPTURE=”{65E8773D-8F56-11D0-A3B9-00A0C9223196}”
KSNAME_Md11=”Midi1-1″
WDM.Md11.szPname=”Roland PC-300″
REG_MSZ = 0x00010000