Edirol/Roland USB legacy driver hack for Windows 10

[jeset]

Worked fine for me, thanks win 10 pcr-50

[nicomahe]

Recently purchased a new PC (thanks 3XS) and migrated to Win 10.

Hi,
Sadly it didn't work on my Win10 for PCR-M30. I followed every step, i can see it in Ableton Live11 but no interaction allowed....

[adrian_k]

Recently purchased a new PC (thanks 3XS) and migrated to Win 10.

Hi,
Sadly it didn't work on my Win10 for PCR-M30. I followed every step, i can see it in Ableton Live11 but no interaction allowed....

If you can live with basic functionality (keyboard, pitch/mod, sustain, expression) you can change the keyboard to “Generic MIDI” - check the manual for how to do that - and you don’t need the Roland driver, it just uses the one that ships with Windows.

I’ve been using my PCR-M30 like this in both W10 and W11 no problem.

In fact I’m pretty sure you can get the knobs and faders working as well because I can see midi activity when you move them, but I never had the need or time to figure out how to map them in my DAW.

[Kwinton]

UPDATE: Edirol FA-101 Firewire Audio Interface WORKING with all Windows 10 Versions!!!!

the procedure, in brief, is as follows:

1. Disable Driver Signature Enforcement (two methode)
2. Edit *.inf files of downloaded edirol fa-101 windows 8 64 bit drivers
3. run driver installation setup
4. Check driver installation on device manager.
5. Reenable Driver Signature Enforcement.

Step by Step guide

1. Disable Driver Signature Enforcement

Methode 1: open elevated command prompt (run cmd as administrator) and run the commands

Code: Select all

BCDEDIT -Set LoadOptions DISABLE_INTEGRITY_CHECKS
BCDEDIT -Set TESTSIGNING ON

Methode 2

• Click Windows Start, and type "Change advanced start-up options" and execute it. This will take you to the Windows 10 Settings Recovery options.
• On the right, where it says Advanced Startup, choose "Restart Now"
• Once it takes you to the blue menu screen, click: "Troubleshoot", followed by "Advanced Settings" > "Startup Settings" > "Restart".
• Once PC has restarted, press the number 7 to 'Disable driver signature enforcement'.
a graphical guide here:
https://www.simple-shop.si/en/disable-e ... windows-10

2. Edit *.inf files of downloaded edirol fa-101 windows 8 64 bit drivers

Download the driver for windows 8 64bit from Roland Website: fa101_864d_v100.zip. Entpack it and edit the two *.inf files locates in folder files.
https://www.roland.com/global/support/b ... 89fff744d/

RRIF0001.INF before Changes

Code: Select all

[Manufacturer]
%S_Provider%=_Devices,NTamd64.6.2

;******************************************************************************
; Models sections
;------------------------------------------------------------------------------
; x64-based systems
[_Devices]
;; WindowsVista 64 or Windows XP 64
;; not supported

[_Devices.ntamd64.6.2]
%S_DeviceDesc%=_Install, 1394\EDIROL&EDIROL_FA-101

RRIF0001.INF after Changes

Code: Select all

[Manufacturer]
%S_Provider%=_Devices,ntamd64.10.0

;******************************************************************************
; Models sections
;------------------------------------------------------------------------------
; x64-based systems
[_Devices]
;; WindowsVista 64 or Windows XP 64
;; not supported

[_Devices.ntamd64.10.0]
%S_DeviceDesc%=_Install, 1394\EDIROL&EDIROL_FA-101

RRAU0001.INF before Changes

Code: Select all

[Manufacturer]
%S_Provider%=_Devices,NTamd64.6.2

;******************************************************************************
; Models sections
;------------------------------------------------------------------------------
; x64-based systems
[_Devices]
;; WindowsVista 64 or Windows XP 64
;; not supported

[_Devices.ntamd64.6.2]
%S_rrau0001_audio_device%=_rrau0001,rrau0001_ENUM\Edirol&Edirol_FA-101&AVS

RRAU0001.INF after Changes

Code: Select all

[Manufacturer]
%S_Provider%=_Devices,ntamd64.10.0

;******************************************************************************
; Models sections
;------------------------------------------------------------------------------
; x64-based systems
[_Devices]
;; WindowsVista 64 or Windows XP 64
;; not supported

[_Devices.ntamd64.10.0]
%S_rrau0001_audio_device%=_rrau0001,rrau0001_ENUM\Edirol&Edirol_FA-101&AVS

3. run driver installation setup

save the these files and run setup ignoring any ‘driver not certified’ warnings. Follow any on-screen prompts and insert the Edirol/Roland USB device when requested to complete the installation. Restart PC after completion

4. Check driver installation on device manager.

Click Windows Start, and type "devmgmt.msc" and execute it. This will take you to the Windows 10 Device Manager.
check if under 61883 devices --> FA-101 Sub --> right click if the driver provider is Roland, Driver Date 09/11/2012 and Driver version 1.0.0.0

5. Reenable Driver Signature Enforcement.

open elevated command prompt (run cmd as administrator) and run the commands

Code: Select all

BCDEDIT -Set LoadOptions ENABLE_INTEGRITY_CHECKS
BCDEDIT -Set TESTSIGNING OFF

that's all ...

B.

I really wanna kiss you right now, i thought i would never be able to get this to work <3

[TheOldies_n_Goodies4208]

Guys, I'm at the end of my rope here. I have an SD-90 and I've been trying to install it on my Windows 11 device and it never installs properly. It's like, everywhere I look it's only Windows 10 that gets it and never Windows 11. I've tried literally everything and I still can't get it to install properly.

I check the Start menu and it says SD-90 under "Recently added", but when I click on it, it just says "To make settings, connect the device and execute again." Meanwhile, I'm stuck on the screen where it says "Ready to install driver. Please use a USB cable to connect the SD-90 and your computer, and then turn on the power of the SD-90, and wait. The driver will be installed automatically."

What do you guys think? Am I forcing a square into a circular hole here? I really hope someone can help me because I'm at my wit's end here.

[iitmfl]

Will this work for a Edirol SD-90?

Here's the issue for us. To get this sound module's MIDI-vendor mode to work in Windows 10, we had to use the Vista driver 64 for it. It TOTALLY worked but since BEING FORCED to Windows 11, it is deemed "incompatible". The only way SO FAR to get it to work is to shut off the core isolation which makes it vulnerable to a WHOLE LOTTA CRAP. The SD90 is just ONE of MANY MANY MANY that we have in the studios which makes hundreds of thousands of dollars in equipment TOTALLY worthless and unuseable.

ANY IDEAS ON HOW TO GET IT TO WORK IN WINDOWS 11?

[Eddy Deegan]

Will this work for a Edirol SD-90?

It would seem worth a try to find out if there is no better option.

Here's the issue for us. To get this sound module's MIDI-vendor mode to work in Windows 10, we had to use the Vista driver 64 for it. It TOTALLY worked but since BEING FORCED to Windows 11, it is deemed "incompatible". The only way SO FAR to get it to work is to shut off the core isolation which makes it vulnerable to a WHOLE LOTTA CRAP. The SD90 is just ONE of MANY MANY MANY that we have in the studios which makes hundreds of thousands of dollars in equipment TOTALLY worthless and unuseable.

I get the frustration at having a legacy piece of equipment (Roland themselves describe it as a "discontinued product") that doesn't have modern driver support but in all honesty if you rely on 22+ year-old gear which doesn't work on modern operating systems then it shouldn't come as a surprise given the age of the equipment.

The SD-90 is a sound module with a USB Audio/MIDI interface combined but neither of those aspects of its implementation are going to match cheaper modern equivalents and this has been the case for years.

Even the Sound On Sound review from 2002 states:

The Studio Canvas concept is a great idea and has been successfully implemented in the SD90. However, the SD90's price tag will seem too high to many desktop musicians, and you can buy better sound modules and interfaces for less money.

I'd buy a modern audio/MIDI interface and play your SD-90 using the MIDI DIN ports it has on the back instead of USB. It'll still make the same sounds it always did and as such is far from useless in that regard.

[iitmfl]

The MIDI sounds are only 1/3 of what this unit can do. The other part is an interface for inst/mic and there's a HUGE amount of adjustments the user is able to make to each tone/s (128 polyphony on ours) and effects for same. The only 'modern' MIDI sound module that comes even closer is the Integra7 which we have plenty of those (those work in Win11) but those don't have a input side that is able to make adjustments. Not real 'up' with MIDI 'up to date' interfaces b/c most everything we (and everybody else) use is interfaced via USB (which is normal today). Got any recommendations wiring up via MIDI setup with something that has CURRENT (and I mean as of TODAY) drivers that would work with Win11? Roland Corp. gave us a case of Roland UM-ONE-MK2's (32) but haven't tried yet or know of anyone that uses those to get their opinion. They're MIDI to USB cables with 2 MIDI plugs each. The thing I'm hesitant on hooking up the SD90's via MIDI is the hang time I remember it having. Sticking notes out of nowhere and all kinds of stuff. That's why up until last night they've been a powerhouse for us (FORCED to switch from Win10 to 11). Use quite a few of these and they've been working flawlessly forever. Whatever help or suggestions you can give would DEEPLY appreciated - tks!

...this is the kind of stuff you have to deal with using Windows. Most of our studios are all Mac-based and Mac/Apple doesn't screw people outta being able to use equipment hooked into their systems. Microsoft...all about the $$$$$.

[BillB]

@iitmfl, I share you frustration. I have an Edirol UA-25EX as an audio interface to a Win11 machine. I use a mic with phantom power as my main audio input to the PC. As the UA-25EX is a solid little audio device, I decided to turn off core isolation on the basis that I didn’t have it on my preceding Win10 PC, so it’s not essential on my Win11 PC. I exercise a high degree of care and suspicion about all emails, websites etc so anticipate that I can avoid the nasties that core isolation is meant to be protecting against.

However, noting Eddy’s comments about relying on old gear, I think it is probably time for me to upgrade, and there are many low cost options out there that would do the same kind of job, although I’ll need to check for Win11 compatible drivers.

As for the SD90, it obviously has a bundle of features in the one box that suits you. But it would appear that, to enable the Win 11 core isolation, you are at least going to have to separate the the sound module functions (basically a GM/GS/JV/XV type sound engine) from the audio/midi interface. Can you retain the SD90 as a sound module but connect it via another audio/midi interface? Not sure why you should be having any issues with sticking notes via MIDI…

I don’t have any specific advice on models compatible with Win11 but I would be looking at Focusrite, Behringer and M-Audio. Other manufacturers are available. You’ll just have to check their driver download pages for compatibility. Please let us know if you find any workable solutions.

[James Perrett]

If you want something that is most likely to work in the future then there's only one choice...

RME

Yes, they're more expensive than many others but they have a proven track record for long term support and their drivers really do work better than others in my experience.

[deyv]

UPDATE: Edirol FA-101 Firewire Audio Interface WORKING with all Windows 10 Versions!!!!

the procedure, in brief, is as follows:

1. Disable Driver Signature Enforcement (two methode)
2. Edit *.inf files of downloaded edirol fa-101 windows 8 64 bit drivers
3. run driver installation setup
4. Check driver installation on device manager.
5. Reenable Driver Signature Enforcement.

Step by Step guide

1. Disable Driver Signature Enforcement

Methode 1: open elevated command prompt (run cmd as administrator) and run the commands

Code: Select all

BCDEDIT -Set LoadOptions DISABLE_INTEGRITY_CHECKS
BCDEDIT -Set TESTSIGNING ON

Methode 2

• Click Windows Start, and type "Change advanced start-up options" and execute it. This will take you to the Windows 10 Settings Recovery options.
• On the right, where it says Advanced Startup, choose "Restart Now"
• Once it takes you to the blue menu screen, click: "Troubleshoot", followed by "Advanced Settings" > "Startup Settings" > "Restart".
• Once PC has restarted, press the number 7 to 'Disable driver signature enforcement'.
a graphical guide here:
https://www.simple-shop.si/en/disable-e ... windows-10

2. Edit *.inf files of downloaded edirol fa-101 windows 8 64 bit drivers

Download the driver for windows 8 64bit from Roland Website: fa101_864d_v100.zip. Entpack it and edit the two *.inf files locates in folder files.
https://www.roland.com/global/support/b ... 89fff744d/

RRIF0001.INF before Changes

Code: Select all

[Manufacturer]
%S_Provider%=_Devices,NTamd64.6.2

;******************************************************************************
; Models sections
;------------------------------------------------------------------------------
; x64-based systems
[_Devices]
;; WindowsVista 64 or Windows XP 64
;; not supported

[_Devices.ntamd64.6.2]
%S_DeviceDesc%=_Install, 1394\EDIROL&EDIROL_FA-101

RRIF0001.INF after Changes

Code: Select all

[Manufacturer]
%S_Provider%=_Devices,ntamd64.10.0

;******************************************************************************
; Models sections
;------------------------------------------------------------------------------
; x64-based systems
[_Devices]
;; WindowsVista 64 or Windows XP 64
;; not supported

[_Devices.ntamd64.10.0]
%S_DeviceDesc%=_Install, 1394\EDIROL&EDIROL_FA-101

RRAU0001.INF before Changes

Code: Select all

[Manufacturer]
%S_Provider%=_Devices,NTamd64.6.2

;******************************************************************************
; Models sections
;------------------------------------------------------------------------------
; x64-based systems
[_Devices]
;; WindowsVista 64 or Windows XP 64
;; not supported

[_Devices.ntamd64.6.2]
%S_rrau0001_audio_device%=_rrau0001,rrau0001_ENUM\Edirol&Edirol_FA-101&AVS

RRAU0001.INF after Changes

Code: Select all

[Manufacturer]
%S_Provider%=_Devices,ntamd64.10.0

;******************************************************************************
; Models sections
;------------------------------------------------------------------------------
; x64-based systems
[_Devices]
;; WindowsVista 64 or Windows XP 64
;; not supported

[_Devices.ntamd64.10.0]
%S_rrau0001_audio_device%=_rrau0001,rrau0001_ENUM\Edirol&Edirol_FA-101&AVS

3. run driver installation setup

save the these files and run setup ignoring any ‘driver not certified’ warnings. Follow any on-screen prompts and insert the Edirol/Roland USB device when requested to complete the installation. Restart PC after completion

4. Check driver installation on device manager.

Click Windows Start, and type "devmgmt.msc" and execute it. This will take you to the Windows 10 Device Manager.
check if under 61883 devices --> FA-101 Sub --> right click if the driver provider is Roland, Driver Date 09/11/2012 and Driver version 1.0.0.0

5. Reenable Driver Signature Enforcement.

open elevated command prompt (run cmd as administrator) and run the commands

Code: Select all

BCDEDIT -Set LoadOptions ENABLE_INTEGRITY_CHECKS
BCDEDIT -Set TESTSIGNING OFF

that's all ...

B.

I really wanna kiss you right now, i thought i would never be able to get this to work <3

FA-101 Sadly does not install drivers after following the method, clicking yes to unsigned driver install. FW on ext ps and via bus power doesn't work.

Works fine pnp on my old 32bit mac mini.

Still sad. Forced obsolescence is a real problem.

W10 Pro 19041-vb_release.191206-1406

[OneWorld]

I ended up having to abandon FireWire, much to my regret, I’d invested quite a lot, I guess I backed the wrong horse

[stllr]

it's 2026 and this guide is still helping people, thank you so much

i made an account specifically to report that i just set up my dad's old PCR-M30 and it works great with ableton. he's an old gig musician and was complaining about the keyfeel of the newer midi controllers when i asked for one for christmas. i'm inclined to agree after feeling how this works. always glad to see an old piece of tech working on new hardware if there's no reason for it to be thrown out. especially when it's better than the new stuff!!! you're a hero for this, the vdrums thread is gone and this is the only thing to save it. excited to start playing again!!!

[ajay_m]

Core isolation was introduced to resolve the problem that certain critical windows processes, most notably lsass, held sensitive credentials in memory which could potentially be retrieved by other processes. The mimikatz suite of utilities demonstrates how easy it was to obtain this information.
Core isolation virtualises these processes, thus protecting sensitive credentials.
However while this is a valid concern, it was much more of an issue with large organisations where privileged local admin accounts shared common passwords across multiple devices. An attacker could therefore "pivot" across an entire estate if credentials could be obtained from one machine. Maersk Shipping found this out the hard way and lost nearly 50,000 machines as a consequence.
These days we use PIN access and biometrics like fingerprint readers which effectively unlock a local certificate instead of passwords in most large organisations, along with physical security devices like yubikeys. We also use Microsoft LAPS to allow local accounts for maintenance without sharing passwords.
Core isolation has a CPU cost which can approach 10%. Unless you think Mr Xi is personally interested in your subversive lyrics then given that attackers can get your credentials by other methods including intercepting keystrokes, really, turning off core isolation is unlikely to expose you to significant vulnerability. You are not a target for nation state attackers.
(I do this stuff for a living in my day job).