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.
"In one of the a friend with better operating system understanding applied the 3 registry changes to FileInfoCacheLifetime, FileNotFoundCacheLifetime and DirectoryCacheLifetime."
Are these normally applied on the server or on each client? Can you please link me to them?
The file leasing is done on the server, the file cache is done on each client pc. They are 2 different and distinct workarounds.
https://www.devhut.net/2018/06/13/access-bug-database-is-in-an-unrecognized-format/
Thanks Daniel. Much appreciated.
For anyone that it monitoring this thead for updates on the issue, this started to happening to my DB very recently (two users only, Win 10 PCs, back-end on a Linux NAS). No real problems before.
I tried the registry hack that involves the FileCache - it seemed to work to stop the corruption, but made the DB so slow it wasn't worth persevering with, I ended up reverting back, and just C&R the back-end when the corruptions happens.
Sadly therefore not a viable workaround for me!
And as I have a NAS for the back end, not Windows/Windows server, I can't try the DisableLeasing hack. I have today tried this on one front-end machine though, see how that goes....
@Duncan B - we appear to have a similar issue. Although it does seem more stable with the backend file share on Linux than it was on the Windows 10 machine we were using last year. Have not tried the FileCache solution yet.