No they didn't.
That's nonsense! It is completely free! It is even completely free for commercial use by small businesses with up to 10 computers!
What's obvious is distrust and dislike of Microsoft, the company, feeds into typing fingers and that distrust and hate of the company bleeds over into opinions of their products.
MSE is free. Period.
I see no problem with Microsoft (or any company) checking to see if you are using a Genuine copy of their product. In fact, I applaud them for it. Why? Because (1) pirated copies of Windows and other software are common sources of malware, and (2) the software thieves who use illegally obtained software or licenses often fail to keep their systems patched and updated for fear of being caught. Either way, that makes those users and their vulnerable machines PRIMARY TARGETS of the badguys seeking easy pickings to compromise, draft into their bot armies, and turn into major threats against the rest of us as spamming machines, DDoS attacks or distributors of malicious code. And Microsoft, tired of years of relentless, unwarranted, and opportunistic bashing for a security situation they did NOT cause, is doing something about it.
Sure, they are tired of losing $100s millions in annual sales. Lost sales, like shoplifting, is something everyone has to pay for. But the sullied security situation they did not cause hurts (you, me, taxpayers, and them) more.
That said, it
IS a problem when genuine copies are tagged as non-genuine. But "
false positives" (which is what I think happened here) happen - and no product maker likes them. Whether it be your spam blocker, virus checker, or genuine product identifier. Users don't like them. And in fact, too many false positives is one reason (albeit a small reason) I no longer use AVG.
But the reality here is Windows often does this because multiple system files it checks have been modified - often by malware activity, collateral damage from malware or its removal, or some other unfortunate circumstance besides a bad database entry at Redmond. Often, running sfc /scanow can fix that.
Sadly, I have seen this caused by misguided users and computer repair "pros" too - who don't use the correct disk during a recovery/repair process.
I was going to suggest something a bit more drastic - uninstall MSE, then download and reinstall
MSE again. This will ensure a fresh rewrite of the files and settings.
@andsome - If you run Windows Update, do you get the genuine validation warning?