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.
When I implemented the disable leasing registry workaround, it seems to have worked. No crashes since for the last 5 days. However, as someone else responded, when I access some files on the network the time it takes to load has slowed down considerably.
Nope, nothing new. About 2 weeks ago the dev team replied in another forum that they hadn't managed to replicate the issue, so I doubt a fix is forthcoming.
Has anyone heard anything new in regards to this issue? Now users at my job are not seeing updated records, which is leading to distrust in the system that we had for years now. One user will see an updated record, while another will not. It also seems like the Windows update system is contributing to this matter of inconsistent data. We have updates delayed on all of the machines, but some computers have 1803 while others have 1703. I guess the 1803 people are crashing the database for the other users.
Sorry, was hoping that would work AND be the *clue* we needed.
ACCDB file in place of our client/front end ACCDE made no noticeable difference, unfortunately. Still painfully slow.
Marty