Patch Lady – issue with Outlook

Topic

New Reply

To those of you in the Ask woody forums that have been hitting this (see this and this and this ) read on.. A bug in the June updates is causing “Some
[See the full post at: Patch Lady – issue with Outlook]

Susan Bradley Patch Lady/Prudent patcher

6 users thanked author for this post.

lanceboil, lmacri, rontpxz81, Chris B, woody, PKCano

Reply | Quote

Replies

Also from the article:

The Outlook Team is investigating this issue with the Windows Team. We are not sure yet if the primary fix will come from Outlook or Windows. When we have more information on fix details we will add them here.

Reply | Quote

If the fix comes from Outlook, where would that leave people using an out-of-support version of Outlook (e.g. 2007)? If a Windows patch broke it, then surely it is Microsoft’s responsibility to fix it.

Chris
Win 10 Pro x64 Group A

Reply | Quote

Being EOL, Office 2007 would not have received the May or June update that broke it. So Office 2007 is probably safe.

Reply | Quote

So it was the Office update that was the problem, was it? I had thought it was the Windows June Cumulative update.

Chris
Win 10 Pro x64 Group A

Reply | Quote

That has not been established yet. But IF it was the Office update, 2007 didn’t get updated. That was my point.

Reply | Quote

Imho it looks more on the office click to run side

Susan Bradley Patch Lady/Prudent patcher

2 users thanked author for this post.

Chris B, Elly

Reply | Quote

I wish I could give you an answer but I have patches delayed for 15 days so my Outlooks works just fine with the two active *.pst files it runs.

Reply | Quote

Thanks for the clarification. I’ll keep watching the thread.

Chris
Win 10 Pro x64 Group A

Reply | Quote

I have Outlook 365, which I think is 16, patched up to date and with the other June updates also installed, and not experiencing the problem. For what it’s worth, my PST files are not in the default location.  They are in E:\Outlook PST Files\, where E is a separate internal hard drive used for data only.

Windows 10 Pro 64 bit 20H2

Reply | Quote

I found this a couple of days ago on my wife’s PC. Dug around in the registry to finally find those two keys and delete them. That file was a subscription to her Gmail calendar. First, I just deleted the PST file after repeated “fixes”. I still got the message. Then I deleted the key with the file name. The “corrupt file” dialog box still popped up just with no file name. Then I deleted the other key. That took care of it. I just re-established the subscription and all is well. It didn’t take too long but was frustrating.

--Joe

1 user thanked author for this post.

woody

Reply | Quote

My Dell laptop did the Windows 10 2004 update last night

Now have spend 8 hours today on issues with Outlook 2013 crashing soon after starting, suffice to say no emails are being received.  I have read the forums, I went into PowerPoint, Word and Excel and did the Updates

I have also run scanPST on every PST file.

 

still have the same issue.   Windows did two more updates today, but still have the issue

When I click FILE in Outlook, I get the attached.  Its been running for 4 hours, let alone 15 mins

What else could I try please?

xxxxxx Microsoft, professional time wasters

Reply | Quote

I would roll back to the previous Windows version, after making a backup to an external USB hard disk.

cheers, Paul

Reply | Quote

Did you actually try the registry fix that Susan details? Or tried the link she provides to Diane Poremsky’s automatic registry fix? Click on Read the Full Post.

It sounds like, after hours of trying different fixes, you may be missing the actual work around if you haven’t… but, I know what that’s like!

Apologies to @PaulT… this seems to be more than a OS version issue…

Non-techy Win 10 Pro and Linux Mint experimenter

2 users thanked author for this post.

Paul T, woody

Reply | Quote

It’s both an Office problem and a Windows cumulative update bug. Article coming in Computerworld.

1 user thanked author for this post.

Elly

Reply | Quote

Hi Woody,

I see in the patch list that Win7 June security patches and Office 2010 and Office 2013 patches are  now green lighted in Susan’s master patch list.  I’ll wait for the overall defcon change, but in interim can you clarify if the Outlook PST corruption issue (and any other Outlook issue due to June’s security patches) does affect Outlook 2010 and Outlook 2013 on Win7 Pro x64 systems after installing the June security Win 7 security roll up and Office 2010 and 2013  updates (I have ESUs for Win7)?  Wasn’t clear on the latest regarding this Outlook corruption issue after we install the June security patches.  Thanks, Woody! 🙂

1 user thanked author for this post.

woody

Reply | Quote

Wait to install for the DEFCON number to be 3 or above. Woody gives instructions on safe patching at that time.

1 user thanked author for this post.

woody

Reply | Quote

PK, thanks to your and Woody’s solid advice I’ve been doing that for several yrs. 👍😊

Reply | Quote

This only affects Office Click-to-Run, and if you’ve updated to the latest CtR version, it doesn’t appear at all.

Details coming in Computerworld tomorrow morning. See

https://www.askwoody.com/2020/june-2020-patch-overview-three-different-ways-ms-is-fixing-its-bugs-this-month/

1 user thanked author for this post.

AmyO

Reply | Quote

Since the June patchapocalyptic day, all my Office 365 apps had issues with a high CPU usage on both of my computer (a one-year old HP Desktop and a brand-new Dell laptop) both are running on 1909. Starting the apps with no network connection everything was fine. Later, same thing occurred with McAfee antivirus. I finally found that issue was related to the metered internet connection. I took out the metered network setting and things went back to normal. So, since the problem occurred also with one of the McAfee components, it’s more likely to be a Windows issue.

Reply | Quote

Just an FYI that I’m not seeing this “Something is wrong with one of your data files and Outlook needs to close” error or high CPU consumption with MS Office Home and Business 2019 Click-to-Run on my Win 10 home computer. Neither Outlook 2019 Version 2005 Build 12827.20268 (rel.02-Jun-2020) or  Version 2005 Build 12827.20336 (rel. 09-Jun-2020) listed <here> in the update history have caused any noticeable problems.

However, I still have 64-bit Win 10 Pro v1909 Build 18363.836 (KB4556799, rel. 12-May 2020); the June 2020 Patch Tuesday update Build 18363.900 for my OS (KB4560960, rel. 09-Jun-2020) is delayed and hasn’t been installed yet.
————-
64-bit Win 10 Pro v1909 build 18363.836 * MS Office Home and Business 2019 C2R v2005 build 12827.20336

Reply | Quote

Just a few additional remarks.

The issue seems to happen with Outlook 2016 client in C2R-Installs (Office 365). There is a Workaround to fix that Outlook crash, caused by a broken PST file – see my blog post below from June 22, 2020:

Outlook: June 2020 updates and PST issues?

This night (June 24, 2020) Microsoft has released this support article, confirming the bug and also my explanations given in den blog post.

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

1 user thanked author for this post.

Elly

Reply | Quote