[German]Microsoft Office security updates released on Patchday (November 12, 2019) cause Access to fail to access databases. An error 3340 ‘Query is corrupted’ will be dropped. Addendum: I reported the issue to Microsoft, a fix is in preparation – see inside. Addendum 2: A fix for Access 2016 is available.
or a list of updates released for November 2019 for the MSI versions of Microsoft Office, see this Microsoft page.
Error 3340: “Query” is corrupted
Within my German blog I got this night the first comments from blog readers claiming an issue with Access, after installing Office security updates released on November 12, 2019.
Report #1: Error in Access 2010
German blog reader Ollat wrotes with reference to the Access 2010 he uses, the following:
Again something seems to have changed when accessing Access databases, this time Access 2010.
There was a similar problem last with 97’er DBs
Uninstalling Office 2010 Security Update seems to help the first customers.
This concerns Microsoft Access 2010 in a specific case – uninstalling Office 2010 Security Update KB4484127 fixed the error.
Error in Access 2010, 2013, and 2016
At the same time I received a message from Annette via e-mail reparting the same issue with Access. She wrote (I’ve translated the German texts within this English blog post):
Do you already have information about the updates from 13.11.2019? I have received some messages that Access reports “3340 query is corrupted”. I guess it concerns Office 2013 but I’m not sure.
What’s certain is that it’s not the database, it must be a bug that was introduced with the update..
She supposed that Office 2013 and its Access version is affected. But later Annette left another comment with further information:
if I just thought it concerns Office 2013, I now know that Office 2010 and 2016 are also affected.
Workaround: Uninstall Office security update
It appears that a security update for the CVE-2019-1402 vulnerability in each version of Microsoft Office causes this error. Here is the list of Office security updates that you can uninstall.
- Office 2010: Description of the security update for Office 2010: November 12, 2019 (KB4484127)
- Office 2013: Description of the security update for Office 2013: November 12, 2019 (KB4484119)
- Office 2016: Description of the security update for Office 2016: November 12, 2019 (KB4484113)
At least from what I’ve seen so far, uninstalling this security update seems to allow database access again. See also my addendum at the article’s end – Microsoft will ship a fix and propose a workaround.
Addendum: Uninstalling the updates
Because it has been asked on both (German, English) blog posts, how to uninstall the update and prevent from reinstalling, here are some hints.
- Microsoft has provided the support article Information about the ability to uninstall Office updates. This works for Updates shipped for MSI installs.
- If you use Office 2019 or Office 365, try the hints given within the support article How to revert to an earlier version of Office 2016 Click-to-Run.
In Windows 7/8.1 go back to Windows Update window and use the context menu to hide the problematic update package for further installs (if you have automatic update installation enabled, change the settings to ‘ask for update installation’). If you are using Windows 10 and may prevent Windows Update from re-installing uninstalled updates, try to block the update using wushowhide.diagcab (hope that works, I’ve never tested it). Another option may be the ‘defere updates’ option in Windows 10.
I’ll see if I can get this reported to Microsoft. Addendum: I have reported the issue to US Microsoft support. There was the case number and the promise to take care of it.
Addendum: There is now a support article from Microsoft dealing with that – a fix is in progress and they propose a workaround.
Addenum 2: A fix for Access 2016 is available – read the details at Fix for Error 3340 in Access 2016 (Update KB4484198)
Addendum 3: There is a new article Addendum: Fixes for Access Error 3340 (Nov. 22, 2019) with additional information.
Cookies helps to fund this blog: Cookie settings