As confirmed in this Microsoft Article: https://support.office.com/en-us/article/access-error-query-is-corrupt-fad205a5-9fd4-49f1-be83-f21636caedec
Microsoft Access application users may suddenly start to receive “Error Query ‘’ is corrupt”.
Microsoft released a security update as of November 12th, which can cause the following error in Microsoft Office and Blue Link applications:
The following KB’s released by Microsoft, are known to cause the issue:
Admins who manage WSUS servers should block the three KBs listed above to prevent additional end user machines or servers from receiving these updates.
If you already have these updates installed, and have admin rights to your computer, follow these steps to remove the updates:
(1) Open Programs & Features
(2) Click on view installed updates.
(3) Search for KB KB4484119 & KB4484113
(4) Once you find the update, click on Uninstall update. Please note, this may require a server reboot.
Tip: you can search the list:
- Tip: To save time, since these KBs all start with “KB4484” searching for that will narrow the list, saving you time.
To Block the update on Windows 10 you now have to download a special tool since Microsoft removed the built-into-the-os version of the feature.
If running Windows 10, you’ll have to download the wushowhide.diagcab file from here:
Click Next, To Block the update if already un-installed, choose the hide option and then you’ll be presented with a list of updates that have NOT YET BEEN APPLIED to your machine. If the KB is in this list, you may selected it and then click through the wizard. This will prevent it from being auto-reapplied. (NOTE: This step is not required if you use a WSUS Server and have already blocked the update there).
REMEMBER TO CHECK FOR PENDING UPDATES
Click Start, Type “Check for Update”
Look at the list of pending updates – if the server has already downloaded and partially installed the update it may show as shown in this screen capture. If it does, the update is already partially installed – it is too late to block it. You must force the server restart and then after the server comes back up, then un-install the update.