I too am getting this. Rewire is broken for Max 8 on my Win 10 machine. Even though Max 8 shows up in the ReWire registry keys (HKLM\Software\Propellerhead...\ReWire), when I select any ReWire host, reaper, bidule, etc, only the previous version, 7 is showing up. I uninstalled Max 7 and 8, cleared the ReWire registry keys, reinstalled only 8 today with the latest install, and ran Max for the first time as an admin to install the ReWire device. It oddly, from within the Max 8 console, said that it was installing ReWire for Max 7! Whatever the cause, I'm sadly still stuck with this error.

Ok, then I'm not alone in having issues with Rewire in Max 8. I'd rather stay away from the registry if I can but I might try out the same thing.

Are you able to use Rewire still?

Sadly no dice. I reinstalled and I still have the same error message. Looking at the registry won't fix anything, so I wouldn't suggest bothering if you aren't familiar with it anyway (My day job is a sysadmin)

I also have a 2012 MBP running a clean install of Mojave for music on the go. I installed Max 8.04 and I still had the same problem with ReWire. "no driver midi_adrewire" shows up in the console. So I wonder if this is a common problem with Max 8?

I'm going to try the 8.05 installer later today, and if that still doesn't work, contact support. Or I'll have to go back to version 7. Right now I can't use Max in any of my ReWire applications :(

I'm on 8.05 with the same error but hopefully it'll work for you...let us know if it does. I can send audio to Ableton Live (I haven't tried my other DAW's yet) and record the audio but other than that I have no idea what might go wrong. Sort of new to this so will just wait it out and see if it gets fixed soon. It's a weird issue for sure.

I tried it--no luck with 8.05 for me either. Still the same error.

Getting same error here, on Max 8.05 on windows. (And yes I can send audio out , but no midi in. GRRR)

I submitted a support request for this, let's see if its a config issue or bug that needs to be patched...

I submitted as well.

Support got back to me , and they said it appears to be a bug introduced in 8.0.4 (they will add it to the list) and in the meantime you can roll back to 8.0.3 if you need this capability. They provided a link (and gave me permission to share it here) for 8.0.3: https://akiaj5esl75o5wbdcv2a-maxmspjitter.s3.amazonaws.com/Max803_190108.dmg

Thanks for the info Ronald...makes sense, around the time I upgraded to 8.04 I started having issues.

Looks like it's been fixed in 8.0.6! :)

Confirmed, working again!