I can confirm that, on two different computers (Dell XPS laptop, plus custom-built desktop), this did NOT work.
As for everyone's complaints against Microsoft, I can say you are 100% correct. An ex-g/f of mine (from many years ago) was the Project Manager for MS Office 2000...and, two of the reasons she chose to leave the company were due to lack of support, and lack of communication. She told me that there was extreme difficulties in fixing problems because they received very little, if any, information provided by those having problems. Put another way, we can report all the problems we want, and even provide proof of said problems...but, very little of that information ever reaches the programmers. It's not-so-much that they (meaning, the programmers) "don't care" about fixing the problems. It's more that the 'chain', from the lowest-level customer support personnel, up to the actual programmers responsible for correcting the code, has MULTIPLE "broken links", all of which were 'created' by Microsoft management (or, should I say, mismanagement). She got fed up with the problems that management was the core cause of, left the company, and returned to the SF Bay Area.
The moral of this (as I'm sure 99.999% of you will understand) is, when it comes to Microsoft, we can, literally, "expect" products to be 'broken' (probably several times) throughout the life of said product. And, don't hold your breath expecting MS to 'fix' whatever they 'break'. In the end, their ultimate "solution" will be to release a new version, and figure out a way to 'force' as many users to 'upgrade' to the new version. Ever since Bill Gates stepped down as CEO, this appears to be the 'philosophy' that the company operates under.