Haven't tried it on my systems but I could test it on a VM and just do a snapshot to roll back any changes. Saw a few people saying Edge doesn't work but there may be more to those reports.
Here's a list of known issues posted less than an hour ago:
If you are running an earlier Alpha or Beta, and your upgrade to Malwarebytes 3.0 fails for any reason, simply uninstall the earlier version and then reinstall new version.
Occasionally, after installing, the user will see a “protection layer is off” warning while the protection is being or has already been automatically turned on.
Occasionally, after installing, the user could see a “failure to connect to service” error, usually a reboot or rerunning the installer will correct the failure.
Microsoft Security Essentials running alongside Malwarebytes 3.0 might cause system lockdowns under Windows 7 due to a buggy Microsoft update.
Some translated strings may still appear in English.
Clicking some of the help “?”s throughout Malwarebytes currently does not do anything.
Some Windows Insider Preview builds blue-screen at Malwarebytes 3.0's Web Protection.
Custom Scan options are not persisted for subsequent scans.
If Malwarebytes 3.0 is closed, a context menu scan does not open up to scan page.
New scans don't reset "Threats Quarantined" counter on Scan Summary page.
The correct date and time format is not enforced when adding or editing a scheduled scan.
Web protection can take a long time to start in Windows XP after upgrade from 2.x.
Custom anti-exploit shields are not enabled by default.
Website block notification appears multiple times on Windows XP.
Windows Vista: Post Expiration Notification for manual renewal appears after each reboot.
On Windows XP selecting a folder in Exclusions does not actually allow selecting a folder.
Currently allowed to add a Domain Exclusion on Windows XP but since this is not supported it will be ignored.
There may be some quirky behavior when resizing the user interface.
Some dialogs are improperly formatted with high DPI settings.
Any User Access Policy created in MBAM 2.x is not migrated when upgrading from MBAM 2.x to Malwarebytes 3.0; a new policy will have to be created.
Malwarebytes 3.0 Installation can fail if installed from an imdisk virtual disk.