This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
We have an application which was working okay till last month. But after the last windows update our clients are getting issues with access database. access database got corrupted. We ran compact and repair. But it still getting corrupted again and again. This issue started right after the window update. clients are on different OS. Like server 2018, server 2012 and windows 10.
Is there anything i have check in new windows update or any other step to prevent database corruption?
A family of Microsoft relational database management systems designed for ease of use.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
The server fix appears to be an official MS workaround. At least that is how it appears on their website.
Thank you, but what is this latest Jul 9, 2020 update. It seems there is an issue again despite the fix.
It is their only fix for over two years with this new note:
July 1 update: We have been testing a fix for this issue but have discovered problems as currently written. We are working to resolve these
issues and will then engage in further testing.
Microsoft's credibility is almost non-existent now. I'll rely on what actually works.
July 1 update was 2019, 2018. nothing new since Nov 2019.
The server reg hack is the only official Microsoft workaround, but requires admin privileges on the backend server, this is why many privilege the client side file caching reg hack instead.
There is no actual fix after more than 2 years now.
Thank you, but what is this latest Jul 9, 2020 update. It seems there is an issue again despite the fix.
I'm not sure. Depends on how you read it. The reg "fix" is a workaround and not an actual fix. That July 9 post could be referring to a proper fix that they have been working on which has undesirable side effects. I really don't know.