Microsoft Access Memory Issue after December 6 2022 Build15831 Office Update

I 100% agree that everyone should be on Semi-Annual....especially after the snafu's over the last year or so. We went for years with no issues with Office Updates and I'd say there were at least 3 really bad bugs last year.

Not sure how/why but we have been dealing with semi-annual users getting the bad version. Painfully working through each one until we have a fix.

Scott

Hi Scott,

So you can confirm that even with the semi-annual channel set, some or all of your users are getting version 2211? Because my intentional update yesterday, in a virtual machine (VMWare Workstation guest machine) left me with a higher build number of version 2202.

There should be a way for an administrator to create a group policy, for all computers on the same domain, that brings relief to having to update all computers one-by-one.

I 100% agree that everyone should be on Semi-Annual....especially after the snafu's over the last year or so. We went for years with no issues with Office Updates and I'd say there were at least 3 really bad bugs last year.

Not sure how/why but we have been dealing with semi-annual users getting the bad version. Painfully working through each one until we have a fix.

Scott

The semi-annual channel is a different beast.

This is a question that is on the minds of several affected people, because unfortunately the semi-annual channel has been updated yesterday, which means that the updates will be rolled out gradually over the course of this week. So, the question is whether the problem causing change from version 2011 has now also arrived in the semi-annual channel or not.

Servus

Karl

Yes, the semi-annual channel is a MUCH MORE stable beast. If folks want to be on the cutting edge, then sure, stay with the Current Channel. But they shouldn't complain when they get cut and bleed! In the past 1-2 years, there's just been too many SNAFU's (I'll leave it to the reader to look up the meaning of that WWII-era term) to justify remaining on Current Channel for business-critical applications.

I was curious what would happen if I updated my 32-bit Microsoft 365 subscription that I have installed on a virtual machine (my host machine has the 64-bit version of Microsoft 365). My starting version was 2202, with updates automatically downloaded and installed (on the VM only):

After performing an update on 11-January-2023, which is one day past the second Tuesday of the month you mentioned earlier, my version is 2202 (Build 14931.20858), so only the minor version changed in my case (20806 to 20858):

That said, even if I were to get the problematic version 2211, it should still be possible to roll back to a stable version, and then disable automatic updating.

Karl, following up on your question. We had changed a majority of our customers to the semi-annual channel to temporarily fix the issue.

I've had about 10 customers today report that the problem is back. When we connect the semiannual update has brought the bad version back.

Scott

Hi David,

Many people have reported that the problem goes away when they revert back to version 2010 in the Current Channel of Office 365.

The semi-annual channel is a different beast. If you manage to be changed to semi-annual then please report if the problem goes away.

This is a question that is on the minds of several affected people, because unfortunately the semi-annual channel has been updated yesterday, which means that the updates will be rolled out gradually over the course of this week. So, the question is whether the problem causing change from version 2011 has now also arrived in the semi-annual channel or not.

Servus

Karl