User sends a number of e-mails. All are delivered without any problems.
User creates first calendar event (and sends invitation). It is delivered at once.
Five minutes later user creates another calendar event. Invitation is not delivered at all.
User, again, sends a number of e-mails. All, again, are delivered without problems.
Program does not inform user about errors in delivering that calendar event's invitation for five hours since event creation, i.e. until program closure.
Calendar marks that invitation was delivered even though it still sits in "Outbok" folder.
And the cherry on the top: After learning about above problem, user sends an e-mail to its IT Support that it can't send one, single calendar event's invitation. E-mail is delivered without any problems.
Microsoft released a Windows 10' update that virtually kills your computer. That is -- upon restart your PC is unable to boot and keeps restarting to Repair Mode.
This is because some morons at Microsoft figured out that it will be so cool if an update to Windows will also fuck up boot sequence in your BIOS. Windows Boot Manager is thus set as first boot device and for some evil reason it is unable to find actual SDD disk which was (in my case) device number 7 in BIOS' boot sequence.
Booting device to BIOS (for which Repair Mode has even a cool button) and throwing Windows Boot Manager hell out of boot sequence or at least putting it into one of latest positions actually solves the problem.
You only have to eat your lunch then because this particular update also installs itself nasty long even on fast PCs.
Microsoft Outlook's offers a support for Free/Busy functionality -- a nifty feature for sharing your calendar details with others, which helps you organise meetings in the moment when every attendee is free for joining it.
Actually, this is an unspoken standard that is also supported in Thunderbird and many other calendars/mail clients. Only in Outlook it is so badly fucked up.
Because Microsoft must always mess up and change simple things into complex one, with Windows 10 they have introduced two display off timeouts, i.e. amounts of time after which your screen is turned off:
lock-off screen one.
First is set to 10 minutes (desktop PCs and laptops on AC power) or 5 minutes (laptops on battery). Second one is set to... 1 minute. Yes, every mother fucking minute after you lock-off your Windows your screen will be turned off.
Here you have 3,5 year old post that counts eighteen points to prove you that MTP protocol is a huge shit. Three+ years later nothing changed except for the fact that Microsoft and Google itself finally realized what they've invented:
It's error coming from MTP protocol-based file transfer and description of the protocol itself in one!
Among many other stupidities in OneDrive here comes this:
File is downloaded, but... not.
The second counter (bottom one, with smaller font) went from 0 to 1 019,5 MB in the exactly the same period as first counter (top one, with bigger font) doing the same. Then -- magic! -- The smaller counter got frozen 1 019,5 MB while bigger counter started counting from 0 to 1 019,5 MB again.
To make yourself (itself?) sure OneDrive decided to download everything twice! :>
According to fastmail.com ("SSL/TLS vs plaintext/STARTTLS port numbers" part) and thousands of other sources in the Internet (emphasis mine):
IMAP uses port 143, but SSL/TLS encrypted IMAP uses port 993.
POP uses port 110, but SSL/TLS encrypted POP uses port 995.
SMTP uses port 25, but SSL/TLS encrypted SMTP uses port 465.
That doesn't count to morons who produced Microsoft Outlook 2010. They've decided that switching encryption method for IMAP between None to SSLwill change port from 143 to 993 and back (correct!). While, doing exactly the same for SMTP won't change port at all.
This way Outlook is problably the only mail client in the world who is trying (unless you manually correct it) to establish secure, encrypted SMTP connection over port 25. An attempt which is doomed by its definition. Congrats again, Microsoft fucks!
The stupidity of Power Point itself and all those fucks with "I'm working for Microsoft" tattooed on their foreheads is simply beyond imagination. You actually cannot change language of all PowerPoint slides at once. You have to:
do this manually (each and every slide and text box separately!),
mess up with outline view (won't work for future-written text!),
On just a little bit slower computers running Windows 7 you may experience a really strange "blurry" behavior of Windows Update main screen, when downloading or installing a large amount of updates. But, that's not the only problem with this service. It also get completely wako, if you install certain fixes using offline installation packages.
I was forced to change my phone to Microsoft Lumia 535. It was my first Windows Phone based device. The phone is generally a good pick (better in many aspects than all my Android-based phones used before). But, since it is (now) designed and produced by Microsoft, it would be impossible for it, to not have some serious fuckups. Here you'll find a list of biggest ones, that I found so far. Most of them are not too closely tight to Lumia 535 and there is a high chances of possibility, that you will find similar or the same in any other Lumia phone.
I have never been using Microsoft Outlook, because this piece of software is huge, ugly and stupid. And most of all, it is a local, desktop program, thus (on contrary to all kind of webmails) you must install it anywhere in order to use it. Few days ago I was forced to start using this crap and I must admit, that Microsoft Fucks continues their long journey of bringing stupidity and fuckabillity to the highest levels.