Noto 2.0 fonts are marred by incompatibility with certain applications due to the fonts themselves. See the following issue that was opened on the project's Github: https://github.com/googlei18n/fontmake/issues/304
Microsoft was not at fault. Noto's font builder wasn't automatically specifying a value (ulCodePageRange) required by convention, and the fonts were built without anyone manually doing so. This has been fixed in the latest build uploaded a few days before your question, 2.001. Unfortunately, Google's main website for downloading the fonts still serves the previous build so you will need to download them from Github. I can confirm that they now work with applications that were incompatible.