[AccessD] New KB breaks Access

Thu Nov 14 20:10:16 CST 2019

I thought HIPAA security had been abandoned?...given Google and the hospitals?

Jim 

----- Original Message -----
From: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com>
To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com>
Cc: "John R Bartow" <jbartow at winhaven.net>
Sent: Thursday, November 14, 2019 9:47:05 AM
Subject: Re: [AccessD] New KB breaks Access

Being involved in the patch management of hundreds of client computers, I can tell you that it's getting worse rather than better, so the answer may just be "no one". 

A couple of proven methods:
-Only apply security patches and decide on a case by case basis for all others.

-In Windows 10 upgrade settings put yourself on the delayed list for new Windows versions. Currently we've barely got everyone upgraded to 1903 and 1909 is already breaking out (yes, that's a pun).

-Monitor all patches for a couple of weeks before applying them. Panicking because of vulnerabilities is akin to cutting oneself because thieves are in the street. 
-Many patches break things. You probably just don't realize it because you don't utilize that particular functionality. RE: the original Spectre vulnerability patches had major problems and broke millions of PCs causing them to not boot. Most PCs are still vulnerable to similar types of attacks, those patches addressed one method, not the underlying problem.

I monitor lists of patching and upgrading pros (similar to this one but with a different focus) and I would guess I've had 30-40 messages come through this year. I search on each patch to see what it breaks before applying. Even so, I've had 4 laptops this year that black screened on my clients. They weren't listed as affected by that problem but apparently I was the lucky one who got to find out. The resolution was fairly easy but ONLY because I was aware of it happening to other models.

Caveat - if you have to meet certain feel good regulations like HIPAA, PCI or your local govt's feel good security measures, then make sure you get the security updates installed before the regulatory scans.

John Bartow
WinHaven Consulting

-----Original Message-----
From: AccessD <accessd-bounces at databaseadvisors.com> On Behalf Of Ryan W
Sent: Wednesday, November 13, 2019 9:18 AM
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Subject: Re: [AccessD] New KB breaks Access

Thanks for that.  What a headache.  Who's doing QA over at MSFT these days?

On Wed, Nov 13, 2019 at 9:15 AM Gustav Brock <gustav at cactus.dk> wrote:

> Hi Ryan
>
> I had this explanation:
>
> This is not a Windows update problem, but a problem that was 
> introduced with the November Patch Tuesday Office release.  A change 
> to fix a security vulnerability causes some legitimate queries to be reported as corrupt.
> Because the change was a security fix, it impacts ALL builds of 
> Office, including 2010, 2013, 2016, 2019, and O365.
>
> The bug has been fixed in all channels, but the timing of delivery 
> will depend on what channel you are on.
>
> For 2010, 2013, and 2016 MSI, and 2019 Volume License  builds, and the
> O365 Semi-annual channel, the fix will be in the December Patch 
> Tuesday build, Dec 10.
> For O365, Monthly Channel, and Insiders, this will be fixed when the 
> October fork is released, currently planned for Nov 24.
>
> For the Semi-Annual channel, the bug was introduced in 11328.20468, 
> which was released Nov 12, but doesn't roll out to everyone all at once.
> If you can, you might want to hold off on updating until Dec 10.
>
> The issue occurs for update queries against a single table with a 
> criteria specified (so other types of queries shouldn't be impacted, 
> nor any query that updates all rows of a table, nor a query that 
> updates the result set of another query).
> Given that, the simplest workaround in most cases is to change the 
> update query to update another query that selects everything from the 
> table, rather than updating the query directly.
>
> I.e., if you have a query like:
>
>     UPDATE Table1 SET Table1.Field1 = "x" WHERE ([Table1].[Field2]=1);
>
> Then, create a new query (Query1) defined as:
>
>     Select * from Table1;
>
> and update your original query to:
>
>     UPDATE Query1 SET Query1.Field1 = "x" WHERE ([Query1].[Field2]=1);
>
> The page "Fixes or workarounds for recent issues in Access":
>
>
> https://support.office.com/en-us/article/Fixes-or-workarounds-for-rece
> nt-issues-in-Access-54962069-14f4-4474-823a-ff7e5974a570
>
> will be updated to reflect this.
>
> /gustav
>
> -----Oprindelig meddelelse-----
> Fra: AccessD <accessd-bounces at databaseadvisors.com> På vegne af Ryan W
> Sendt: 13. november 2019 16:07
> Til: Access Developers discussion and problem solving < 
> accessd at databaseadvisors.com>
> Emne: [AccessD] New KB breaks Access
>
>
> https://support.microsoft.com/en-us/help/4484119/security-update-for-o
> ffice-2013-november-12-2019
>
> This KB really broke our system this morning.  Just had to run around 
> and uninstall it for everyone.
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com