Look what they do with IMAP support in Outlook 2016. Pre-loading just the "Subject" (a feature supported since 1990s) got dropped, instead of the whole email incl attachments is downloaded.
And now we learn POP3 got crippled too. The common Microsoft tactics to lock-in end-user and enterprise customers to proprietary ever changing protocols only fully supported by their most recent server software - their Exchange and Outlook.com/Office365 cloud eco-system.
Microsoft wants you to upgrade to Windows 10 on PC, adopt it on smartphones (even it has just 1.1% market share), on servers, SQL-Server 2016, Exchange 2016, Office365 (subscription based Office 2016 client, cloud based SharePoint 2016 = OneDrive for Business on Azure), Skype for Business (=rebranded Lync), etc. Oh, and they ask you to install their telemetry services for Office on your clients, to get a "full picture". The telemetry and other phone home stuff cannot be turned off, except in the expensive LTSB license version. And several IPs and URLs are white lists in the kernel mode network layer, in all versions.
It's up to you, to help Microsoft to create another monopoly. Or you out smart them and say no.
To be fair, oOo and LO always warn you when you want to save a file in MS Office format. Mind you, you can turn the notification off.
Food for thought: one of my employers now deploys OpenOffice as well as MS Office after years of resisting that because of fears of user confusion. Guess what? No confusion apparent.
Oh, you use Autodesk products, you'll need Windows for that.
"We created a shared Word doc / PowerPoint in OneDrive for the report" - only editable with MS Office.
My choice is work or no work.
It's so sad, because LTSB is quite a good system. My home system was eligible for Windows 10 upgrade, which I did - then loaded LTSB as soon as I found out about it and replaced it, so my conscience is somehow clear about running it.
It reminds me of good old Windows 7 days and updates aren't breaking the system weekly.
You still have to disable various telemetry crap though.
That said, yeah, this is something they definitely should be testing. The fact that the article updated yesterday with a new knowledge base article and the status of the problem says they are looking into it, means they've been notified but not yet fixed it. If they haven't stopped that update from rolling out, someone at MS may come back to very unhappy managers on Monday, and have to explain why they thought leaving a data destroying bug live over the weekend was the right call...
I was trying to fix email for a friend recently. Her UK ISP's email service is a rebranded Yahoo Mail account.
It works fine on her iPad, but LiveMail in Win7 (she doesn't want Win10) regularly chokes on attachments.
Turns out LiveMail can't cope if there's spam in a Yahoo trash account. And this bug has been around for years now.
Not sure if incompetence, corporate dementia, or some nefarious plot to get users to switch to <whatever Microsoft's mail service is called this year.>
Either way, I suggested she switch to Gmail.
Empirically, it seems to be less of this problem occurring on the connection to the Exchange server, back when I was forced to use before. (Though at that time didn't have had so much of the connection, but had plenty of issues some involving broken database and such, I wouldn't touch with a ten foot pole myself...)
Look, I know that mistakes can be made. But in this case, I just can't think of a single excuse that would be satisfactory.