![\"\"](\"https:\/\/sitesdev.net\/articles\/wp-content\/uploads\/2018\/12\/outlook_patch_resized.jpg\")
Back in October, Microsoft issued an update for Windows 10 that was a bit of a disaster.\u00a0 It wound up deleting some user files and sparked a completely justified outrage.\u00a0 The company pulled the update back, taking it offline so more people wouldn’t be impacted. Then they recently re-released it, this time, without the file deletions.<\/p>\n
Unfortunately, that wasn’t the first time the company had stumbled where updates were concerned.\u00a0 In fact, many of Microsoft’s recent patches and updates have been problematic.\u00a0 The company has promised to make changes in the way they’re doing things and to be more transparent about their processes.<\/p>\n
They’ve taken a few preliminary steps in that direction. It hasn’t seemed to help, at least not based on their rollout of a recent patch designed to “fix” Outlook 2010.<\/p>\n
The November 13 security update, Kb4461529 addressed several flaws and vulnerabilities.\u00a0 In one instance, however, the company addressed a security flaw which would allow a hacker to remotely execute code via a specially crafted Word document.\u00a0 The company’s “fix” to protect Outlook 2010 users was to simply disable the program entirely.<\/p>\n
Needless to say, Outlook 2010 users were not amused. To make matters worse, Microsoft advised users not to uninstall the patch, but rather, to wait for the next patch (released on November 21st).\u00a0 That patch, KB4461585, the company promised would fix the crashing issue.<\/p>\n
Sure enough, the second patch worked as advertised, but sadly, people who took Microsoft’s advice were without their email for two weeks and that’s simply unacceptable.<\/p>\n
All companies stumble.\u00a0 All companies make mistakes.\u00a0 That’s inevitable.\u00a0 Unfortunately, Microsoft can’t seem to stay out of its own way where patches and security updates are concerned.\u00a0 The last several months have been a parade of blunders.\u00a0 Here’s hoping the company can identify the flaw in its process sooner, rather than later.\u00a0 For all our sakes.<\/p>\n","protected":false},"excerpt":{"rendered":"
Back in October, Microsoft issued an update for Windows 10 that was a bit of a disaster.\u00a0 It wound up deleting some user files and sparked a completely justified outrage.\u00a0 The company pulled the update back, taking it offline so more people wouldn’t be impacted. Then they recently re-released it, this time, without the file […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"yoast_head":"\n