News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon

Daily Archives: January 24, 2019

  • Office 365 experiences widespread outages Thursday, January 24, 2019

    Posted on January 24th, 2019 at 16:02 PKCano Comment on the AskWoody Lounge

    Microsoft Office 365 has been having problems since 9:21 AM EST today. Users have been unable to access their email. Reports have been widespread. The Register reported that Users in the UK and much of Europe were affected.

    There have also been reports from South America and Africa.  And shows an even wider outage.

    cbronline gives this analysis

    At the time of writing it had yet to update its public-facing status page, which showed normal service, but an update for administrators blamed a “subset of mailbox database infrastructure [that] became degraded, causing impact.”

    At 1.54pm it changed that attribution, with Microsoft 365’s status account on Twitter instead saying “a subset of Domain Controller infrastructure is unresponsive, resulting in user connection time outs” and pledging mitigation.

    Have any of you experienced a problem?  Let us know.

  • Microsoft explains the confusion over .NET 1809 update KB 4481031

    Posted on January 24th, 2019 at 09:45 woody Comment on the AskWoody Lounge

    This is refreshing. Not the bugs, but the fact that we got a full explanation.

    (See Susan Bradley’s “Bring it on” post below.)

    You’ll recall my puzzlement over the .NET patch for Win10 1809, KB 4481031, released two days ago:

    • The patch was identified as a “Preview”
    • It was being sent out to seekers, and
    • It was also being sent out over Windows Update

    Which is a bizarre set of circumstances. At the time I guessed it was a big mess-up in the documentation. In fact, there was a little bit more happening.

    Per a new .NET blog post:

    The term “Preview” was removed from non-security Cumulative .NET updates for Window 10 version 1809 and Windows Server 2019.

    That explains the incorrect documentation. But there’s more.

    Per the updated KB 4481031 article:

    For 24 hours, this Jan 22, 2019 Cumulative Update for .NET Framework 3.5 and 4.7.2 (KB4481031) was made available broadly on Windows Update as an automatic update. As of January 23, 2019, this update is no longer offered on Windows Update as an automatic update, but rather only to “seekers” who go to Settings > Update & Security > Windows Update, and then select Check for updates, as is expected.

    I take great umbrage at that “as is expected” stinger. I would guess that 99.99% of all the folks who click Check for updates don’t realize that they’re going to get all of the patches currently waiting in the queue – without a chance to review or accept them.

    Anyway, it appears as if everything is now working the way it’s meant to work. Seekers and all.

    Thanks to Francis, posting anonymously.