Debilitating “Outlook needs to close” bug linked to a likely bad Windows cumulative update

Topic

New Reply

Don’t you just love it when Microsoft fails to test its latest version of Outlook with its latest version of Windows? Of course, Outlook can’t fix you
[See the full post at: Debilitating “Outlook needs to close” bug linked to a likely bad Windows cumulative update]

7 users thanked author for this post.

r1ma, MayankParmar, abbodi86, Elly, WildChild, dgc-art, lmacri

Reply | Quote

Replies

Thankfully not seeing this bug on Windows 10 Pro 1909 (18363.900) and using Office Pro Plus 2016 with Outlook Version 2005 (Build 12827.20336 Click-To-Run).

1 user thanked author for this post.

r1ma

Reply | Quote

How can businesses survive this incompetence level from Microsoft?

Reply | Quote

Businesses don’t use PST files.

Reply | Quote

That’s not really accurate, but Microsoft probably appreciates the thought.

Reply | Quote

OK. PST files have been regarded as bad business practice for close to a decade:

PST Files in Email Archiving: An Information Management Risk

10 reasons to avoid using PST files

Outlook .PST Files – Why They are Evil

Why is using PSTs in 2016 a bad idea?

So most businesses don’t use them.

Reply | Quote

I use PST AND run Microsoft 365 version 2005 release 12827.20336, AND have installed the June 2020 Win10 cumulative update 2004 (19041.329). The problem is not seen here.

2 users thanked author for this post.

howardagoldberg, woody

Reply | Quote

[howardagoldberg]

I am also on Microsoft (Office) 365 Version 2005 (12827.20336) – 64bit, running on Win10 1909 x64 with the June patches.

All of my Email accounts are OST files (Gmail/IMAP) or Exchange (MSN), but my contacts, calendar, and email folders (from rules I’ve setup) are stored on a local PST file (42GB and growing).

Thus far, I have not encountered this issue, and I have Outlook running about 12-18 hours a day.

I am wondering … could the issue be with 32-bit Office installs running on a 64-bit install of Windows? Maybe something wonky happening there?

• This reply was modified 4 years, 11 months ago by howardagoldberg.

2 users thanked author for this post.

r1ma, woody

Reply | Quote

That’s a possibility. MS hasn’t provided any information other than the warning referenced in the article.

Reply | Quote

I use PST files to archive prior messages.

What I don’t do is keep everything up to date, because I follow Woody’s MS-DEFCON advice to wait until month+1’s update is just about out before taking the prior month’s updates. I don’t yet have the June Windows Updates, and thankful for it.

I guess that applies to Office updates too, as they’re all tied together? I’m trying to correlate the Office version I have – 16.0.11929.20836 – with Woody’s published versions:

Microsoft 365 version 2005 Current Channel release 12827.20268 (from June 2) or Current Channel release 12827.20336 (from June 9);

Should I compare the 11929.20836 part of 16.0.11929.20836 against Woody’s numbers? If so I guess mine’s quite a bit older?

Happy as always not to be on the bleeding edge.

-Noel

Reply | Quote

Hi Noel:

I use MS Office Home and Business 2019 Click-to-Run (C2R). Control Panel | Programs | Programs and Features shows I currently have v16.0.12827.20336, which matches the version I see if I open Outlook 2019, go to File | Office Account and look under Product Information [Version 2005 (Build 12827.20336 Click-to-Run)]. That is also the latest update version listed for the retail edition of MS Office 2019 C2R update history <here>; the Microsoft 365 update history for both Current Release and Enterprise channels is <here>.

However, when I click the About Outlook button to see the full Microsoft Office 2019 version number and product ID, the version is shown as v16.0.12827.20328. I’m not sure why there is a discrepancy between the MS Office (MSO) version number associated with the product ID and the version number listed at Programs and Features.

I have a Win 10 Pro v1909 OS and the delivery of my C2R updates for MS Office 2019 don’t seem to be stopped when I pause or defer Win 10 quality updates in my advanced Windows Update settings, although I have noticed my Office updates often don’t arrive until one or two weeks after their official release date. See further details in my 23-Jun-2020 post in TonySca’s Updates for Office 2019 Should I Install?.
————-
64-bit Win 10 Pro v1909 build 18363.836 * MS Office Home and Business 2019 C2R v2005 build 12827.20336

2 users thanked author for this post.

Noel Carboni, r1ma

Reply | Quote

b wrote:

Businesses don’t use PST files.

Many small and medium sized businesses do in fact use .pst files, not only for archiving, but also for POP accounts.

3 users thanked author for this post.

Microfix, Noel Carboni, woody

Reply | Quote

From what I’ve seen it’s a mixed bag, but almost all individual users have PSTs.

1 user thanked author for this post.

r1ma

Reply | Quote

Unrelated question: Is Windows Update deferral setting (“Choose when updates are installed”) still missing in Windows 10 version 2004 even after June 2020 Patch?

Reply | Quote

That’s off-topic.
But yes, the pulldowns are gone in v2004.

2 users thanked author for this post.

Microfix, woody

Reply | Quote

By the way, Woody, have you been getting my emails? I did send you but never heard of you. Thank you if you update me on that. Thank you so much.

Reply | Quote

Not sure which emails. You can always contact me at woody at askwoody.com or customersupport at askwoody.com.

1 user thanked author for this post.

r1ma

Reply | Quote

I’m sorry to be a disappointment (not really), but I have

• Windows 2004
• Microsoft 365 version 2005, build 12827,20336
• PST files
• Installed KB4557957

And do not have the problem.  My one difference is that my PST files are not in the default location but are on a separate data disk.  Could be a clue there?

Windows 10 Pro 64 bit 20H2

2 users thanked author for this post.

woody, r1ma

Reply | Quote

dgc-art wrote:

Thankfully not seeing this bug on Windows 10 Pro 1909 (18363.900) and using Office Pro Plus 2016 with Outlook Version 2005 (Build 12827.20336 Click-To-Run).

Me too turned on my PC after a day, and my Office says its:

Version 2005 (Build 12827.20336 Click-to-Run) Current Channel

So hopefully somehow I am lucky that did not the get the latest update for Office which is:

version 2005 Build 12827.20268

Reply | Quote

You have the latest. 20268 came a week before that.

1 user thanked author for this post.

r1ma

Reply | Quote

Had this issue at one client and he was not using PST files – just OST. The repair tool kept on pointing to one of his OST files (he has 7 O365 email accounts). Even editing the registry did not work – problem keeps coming back. Eventually had to change all his email accounts to not use cached mode for now – until I can find a better solution.

1 user thanked author for this post.

woody

Reply | Quote

I hadn’t heard of that one before.

I sure hope somebody at MS has figured this out!

Reply | Quote

Ran into this exact problem last week. even removing the kb and nuking the account in outlook the proper way failed to correct it. what happened in my users case was this corrupted the user profile in windows which MS confirmed on a support call.  creating a New profile fixed it. Windows 10 2004. Office 2016 Home and Business stand alone not the o365 version but Microsoft is hosting their mail.

Reply | Quote

An update of Office 365 was pushed out late yesterday … Version 2005 (Build 12827.20470) | https://docs.microsoft.com/en-us/officeupdates/current-channel#version-2005-june-24 … which according to the release notes, provides a fix to this issue.

2 users thanked author for this post.

r1ma, lmacri

Reply | Quote