noobgoldberg

I had the same problem and a google search led me to this thread. Although the old "Local State" method no longer works, in that same "User Data" directory I opened up the "Profile 1" subdirectory (I have multiple Chrome profiles so perhaps you only have one, or it's called Profile 2, or even just "Profile") and opened the "Preferences" file in Notepad++. Then I searched for "nxm" and it was embedded in the JSON array, like so: "news":false,"nntp":true,"nxm":false,"shell":true,"snews":false,"vbscript":true I deleted (including the comma!): "nxm":false, ...saved the file, started Chrome, and when I clicked on the big green button in Nexus it properly asked me if I wanted to use the MO2 handler again. Everything is now back to the way it should be. It looks like the file location has simply moved from "User Data\Local State" to "User Data\Profile 1\Preferences" (or whichever profile number you are currently using). EDIT: Easiest way to identify the profile you're currently using is to check the "Preferences" file modification date, which should be today's date (because you just closed Chrome before you edited the file).