AskWoody

Microsoft finally confirms that buggy Nov security patch KB 4461529 causes Outlook 2010 to crash on startup

I reported on the problem on Nov. 14. MS finally got around to acknowledging it officially.

After updating Outlook 2010 to the November 2018 Public Update KB 4461529 Outlook crashes or closes suddenly on start up. The issue only affects 64-bit installations of Outlook 2010.

More Information

In the Application Event Viewer the following event details are observed:

Faulting application name: OUTLOOK.EXE, version: 14.0.7224.5000, time stamp: 0x5bcb80d1
Faulting module name: olmapi32.dll, version: 14.0.7224.5000, time stamp: 0x5bcb809a
Exception code: 0xc0000005
Fault offset: 0x000000000001e4b9
Faulting process id: 0x3998
Faulting application start time: 0x01d47d3befb78cd8
Faulting application path: C:\Program Files\Microsoft Office\Office14\OUTLOOK.EXE
Faulting module path: C:\Program Files\Microsoft Office\Office14\olmapi32.dll

STATUS: INVESTIGATING

Microsoft is investigating the issue and we will update this page when further details become available. As a workaround, you could try using Outlook Web Access.

Caution: We do not recommend removing security update KB 4461529.

Took ’em long enough….

Outlook.com won’t let some people log on – 401 error

This has been going on since last night, US time.

@MikeyD215 reports:

Anyone here experiencing issues trying to sign in to Outlook.com?

Attempted sign-in results in “401 error: Unauthorized: Access is denied due to invalid credentials.”

I have succeeded in signing into one account, but cannot sign into a second one. Softies claim problem almost 100% solved as of 10:45 a.m. EST, but complaints still pouring in.

Affects some accounts, but not all. Occurring around the world. Been going on for over 15-16 hours now. Type of connection not a factor, type of browser not a factor. I am signed into MSN.com and can see my “@msn.com” emails, but I cannot access them in that one email account, but no problem with a different “@msn.com” email account.

The Office 365 Service health page reports:

Title: Can’t access email

User Impact: Users may be unable to access their email.

Current status: Restarting the affected infrastructure has resolved the issue. We’re continuing to monitor the service and are reaching out to some of the affected customers to validate resolution.

Start time: Thursday, November 15, 2018, at 10:05 PM UTC

Next update by: Friday, November 16, 2018, at 7:30 PM UTC

Thx  @b, @BobbyB, Günter Born.

The folks running Win10 1809 seem to know what they’re doing

I know it’s a controversial observation, especially around here, but I’m starting to hope that the current regime (whomever they may be) are using the tools they have to roll out Win10 1809 in a much more sane way.

My most recent cause for hope: The “C week” or “D week” non-security cumulative update for Win10 version 1809, KB 4469342, is going out to the Insider Release Preview ring, for testing before broad deployment.

That’s exactly what the Release Preview ring was made for. And it’s never been used correctly. Until today.

Details in Computerworld Woody on Windows.

Windows 10 version 1809 advances to build 17763.165 – with no documentation, of course

I’m reading between the tea leaves here, but it appears as if KB 4469342 was released to the Insider Release Preview ring, then to the Win10 1809 masses at large, early this morning. It’s not showing up on my machines just yet, but there are reports popping up all over.

If you install KB 4469342, you end up with build 17763.165.

The official update page doesn’t list it, of course.

Thx @hoyty

UPDATE: The cumulative update was only distributed to the Insider Preview Ring — which is precisely what the Insider Preview Ring was built for. See https://www.askwoody.com/2018/the-folks-running-win10-1809-seem-to-know-what-theyre-doing/

Patch Lady – scanning for updates

https://www.csoonline.com/article/3321140/windows-security/how-to-use-powershell-to-scan-for-windows-10-security-updates.html

I know many of you already know this…but in case you don’t.  That’s how to scan for updates on Windows 10 without installing them.

With video too!

(look for more of these security video tips coming to csoonline.com)

Deanna’s Freeware Spotlight: Intel Microcode Boot Loader v0.3

Some motherboard manufacturers have failed to release firmware updates to patch the Spectre vulnerability which allows speculative execution side-channel attacks (CVE-2017-5715, CVE-2017-5753, CVE-2017-5754). Eran Badit has created this on-the-fly workaround which requires the creation of a bootable flash drive that is left in the system. The patch is engaged on every boot. Get the zip file from OlderGeeks.com ->

https://www.oldergeeks.com/downloads/file.php?id=2626

Patch Lady – a bit of transparancy for 1809

https://support.microsoft.com/en-us/help/4464619/windows-10-update-history

Holy cow, we have a bit of transparency.  We have a new section in the update history page that lists current blocking items and eta of a resolution.

Including my lovely one of the mapped drives issue which they indicate they are working on for 2019.

Click on that link, scroll down for the section called Current status and just have a moment of zen and transparency:

Current status of Windows, version 1809, Windows Server 2019, and Windows Server, version 1809

Oh and as a reminder, if you do want to install 1809 early and be a beta tester, watch your antivirus as clearly a/v partners aren’t quite ready.

How to upgrade Win10 Pro to the version of Win10 that YOU want

We have enough experience with the settings now that I’m confident the “defer upgrades” approach to choosing a specific version of Win10 works.

But it’s a little tricky.

Details in Computerworld Woody on Windows.