Independent Microsoft criticism
Microsoft sucks.
Here's why.
One account holds your email, your files, your licences and the machine you work on — and the machine will reboot when it decides to, advertise to you in the start menu, and lock you out of all of it if the account is flagged.
The record
Everything, newest first.
Marked Verified means it was written up here with the evidence attached. The rest are public submissions, posted unedited by the people they happened to.
Locked out of the account your computer signs in with
When the login for your email is also the login for your laptop, your Office licence and your encrypted drive, one account decision reaches into the machine sitting in front of you. Here is what to do — and what to set up now so it cannot.
Verified anonymous
Randos welcome
Post the story. Bring receipts if you have them.
No account. No signup. No email required. Write it, post it, it goes live. Firsthand accounts are best. Redact anything that could hurt someone who did not ask to be part of the story.
Worth having in front of you
- Which account: personal, work, or one that used to be both.
- What the device does now, and whether a local login still works.
- Whether the recovery key was ever stored anywhere but that account.
- The licence or subscription that stopped working, and on what date.
Write it anyway if you do not have all of it. A story with gaps still counts; a story you never posted does not.
Not about Microsoft? Name whoever it was on sucks.is — same rules, same anonymity, any company.
What gets published
Claims need receipts. Anger gets edited into evidence.
Anger is fine — it is usually the honest reaction. Sloppiness is not. One wrong technical detail is all anyone needs to dismiss an entire story, so the standard here is simple: say what you measured, say what you were told, and keep the two apart.
Screenshots
Images are checked before they publish. Text isn't.
A paragraph can be wrong and then corrected. A screenshot can carry a live access key, a twelve-digit account id, a customer list, or a face — and once it is published it is scraped, mirrored and archived within minutes, so taking it down an hour later takes nothing down. That asymmetry is the whole reason images wait and text does not.
Before an image is uploaded, the black boxes you draw on it are burned into the pixels in your own browser — the original never leaves your device. The server then rebuilds the image from scratch, which destroys the location data, device serial and the hidden thumbnail that phone editors leave behind holding the uncropped picture. Then a person looks at it. Then it goes up.
Getting something removed
If a story exposes you, say so and it comes down.
Stories publish immediately, which means the wrong thing can go up before anyone reads it. If a post contains your personal information, someone else's private data, or a claim about you that is false, send it here with the link and what is wrong with it. Personal data comes down on sight, no argument required. Everything else gets read and answered.
A form, not a ticket queue, and no support tier gating it. Nothing to sign up for, nothing to verify, no case number.
A request still sitting after a day trips an automated check, so it cannot be quietly forgotten. There is no case number because there is nothing to look up: when it is done the link stops working, and you can check that yourself.