E-MU 1616m, 1212m, 1820m, 0404 Audio Interface - Complete Windows 10 (1903 & Above) Installation Guide

[planetearth]

I installed this patch to get my PCIe 1616m going again in Windows 10; it worked fine.

After I updated to Windows 11 I had to do it again, and it worked fine.

But I am now running Windows 11 version 23H2 - why? - because any attempt to install the feature updates to 24H2 or 25H2 using Windows Update fails. They are blocked by "an incompatible driver", and Windows Update automatically rolls back. I can install those versions fresh, which loses the patched driver, but if I patch the driver again, Windows 11 will no longer boot, and I have to manually roll back to 23H2.

Has anyone else been able to keep their 1616m working in a version of Windows 11 later than 23H2?

Paul

Also interested. Is it possible to run EMU 1820 in latest W11 ? (I am running mine in latest W10, with new power supply capacitors and everything works SO well!). Any experience?

I have my 1820m working on the latest version of Windows 11. PatchMix is working fine, too.

Steve

[parapentep70]

I have my 1820m working on the latest version of Windows 11. PatchMix is working fine, too.

Steve

Thanks! W11 25H2 sure? This would be good news, I want to make sure before going to W11

[planetearth]

I have my 1820m working on the latest version of Windows 11. PatchMix is working fine, too.

Steve

Thanks! W11 25H2 sure? This would be good news, I want to make sure before going to W11

Not Win11-25H2, no; that wasn't out when I installed Win11 onto a fresh SSD back in July. But I had no problems with the installation—and this was on a 10-year-old processor.

Steve

[parapentep70]

Steve,

Thanks for your help. I am still concerned because of pwhodges' post. W11 + old processor / board = no problem in my case (I already modified BIOS settings). Old EMU-1820 with late W10 or early W11 --> No problem nowadays (the reason for this thread to exist, dozens of happy users).

Latest W11 + old EMU cards with the solution in this thread --> Not for pwhodges, nobody to confirm new W11 versions are NOT deleting non-official drivers (I know older versions don't delete old drivers). Hence my question.

I don't know if there are more people like pwhodges throwing the towel and finally retiring EMU cards (I believe we are not so many 20 years after) or perhaps pwhodges managed to solve the issue and it is as easy as 1 year before and everybody is happy updating their W11 version.

[NicoCava99]

Hi, I'm completely new to this, I've just bought an e-mu 1212m pcie and I'm trying to follow the steps, but I got stuck right at the beginning... Basically when I try to install the driver a message appears that says: "setup is unable to detect a supported product on your system" and I can't get past it. The card is on and both the blue light where there's the e-mu logo and the adat out port are on, so it'd look like everything is fine hardware-wise... I'm running the latest version of Windows 11 pro. Thank you in advance!

[NicoCava99]

All sorted now; a few of the old "try something a little different" attempts and BOOM, my 1616 has risen from the ashes. THANK YOU, THANK YOU, THANK YOU sherwoodsound!!!

Can you explain what you did exactly? I have an error saying "setup is unable to detect a supported product on your system" when i try to install the first driver, maybe the solution could be the same.

Thank you

[my03]

Thought i could report my own success story with latest W11 25H2 and my 0404-pci. It works fantastic using the steps outlined by OP

I thought she was a goner and that i had to reply on my Presonus USB, but i was wrong

[Sweppe]

Thanks for all the hard work making this amazing soundcard compatible with the software and hardware today! I use the 1616m/PCI. I have an issue since a couple of years . When using DOCK Phones/Out 1 I get a slight pan to the left (both rear outputs and in the headphones), and when using DOCK 2 Out, i get the opposite. But DOCK Out 3 works perfectly with both speakers, and stero out/rear, although signal is too low for headphones. Any clues of what the problem is, and if anyone would have a solution I would greatly appreciate it. Thanks!

[_niko_]

Got mine up and running again too, Windows 11 Pro 24H2, 1616m PCMCIA with a PCI adapter card (also bought almost 20 years ago). So far it seems to work fine, I haven't tested everything yet though, since I really only need two ins/outs currently.

Thanks for all the info provided here!

[Bajsz]

Hi all! I tried to install this patch and I have an issue when I type this line into the PowerShell window: set-executionpolicy unrestricted -scope localmachine. The PowerShell says 'set-executionpolicy' is not recognized as an internal or external command, operable program or batch file'. I don't understand what could be wrong. Windows 10 first update.

Thanx in advance!

[planetearth]

Hi all! I tried to install this patch and I have an issue when I type this line into the PowerShell window: set-executionpolicy unrestricted -scope localmachine. The PowerShell says 'set-executionpolicy' is not recognized as an internal or external command, operable program or batch file'. I don't understand what could be wrong. Windows 10 first update.

Thanx in advance!

Are you sure you're running PowerShell as an administrator?

What do you mean by "Windows 10 first update"?

Steve

[Bajsz]

Steve,

Yes, I'm running PowerShell as an administrator.
Windows 10 Pro, version 22H2, build 19045.3086

But it's an experimental for me. If it's working fine, I'm going to Windows 10 latest version.

[Bajsz]

Solved.
But: the PatchMix doesn't work. I use 1820m.

[kodebode2]

Still working OK, on Windows 11 24H2, Build 26100.7623.

Some notes :

1. No need for the audio device disable and re-enable commands in the script, cos the EMU device is NOT loaded in safe mode, on Windows 11.

2. Run the following command in Windows Powershell, to re-enable security in safe mode, before restarting, which takes you back to normal mode.

set-executionpolicy restricted -scope localmachine