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.
Hi
I have applied the Server Fix to all my clients’ servers and my own. This fixed the Access corruption issue and there have been no problems with performance or connection. All good for over a year (touch wood). I have a mixture of 2008, 2012 & 2016 servers in the mix.
Hope this experience helps.
Graeme
My understanding is the DisableLeasing "FIX" causes more problems than it fixes and in many cases cannot be applied on big sites where servers are shared across many departments. The best fix is applying the simple registry change below to ALL the Windows 10 clients accessing the data - no need to apply to Win7 machines or to the Server. From experience this works and has been reported here numerous times to work. I am not sure why the Disable Leasing fix to the server is still being mentioned as a possible solution.
Here is the registry change to apply to ALL windows10 "Clients"
Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]"FileInfoCacheLifetime"=dword:00000000"FileNotFoundCacheLifetime"=dword:00000000"DirectoryCacheLifetime"=dword:00000000
If anyone has applied this and still gets problems they should report it back to this list.
I applied the fix on both server and workstations (DisableLeasing fix). Even computers that didn't have the fix had issues connecting to the server. It was messy.
I didn't realise that applying the fix on individual PCs could be problematic. Has anyone else who has employed the fix on client PCs had similar issues?
Also, what has been people's experience with employing the fix on the server? I had the IT guy for a company that I've supplied a database to employ the server fix many months ago. It fixed the corruption problem and there were no problems with slow access times. Is there some other variable in the mix that can cause slow access times when the server fix is implemented? I've read that this can occur and I'm wondering why I haven't seen it in this case.
I will shortly be installing a similar database for another client and I'm tossing up whether to ask their IT people to employ the server fix or to try the client PC fix.
New to this thread. Run into this issue with the following setup:
I applied the DisableLeasing fix and computers lost network drives, could not find the domain, needed credentials every time it restarted, the whole thing was a mess BUT Access backed was not being corrupted anymore.
I undid the DisableLeasing fix and applied the other fix:
"FileInfoCacheLifetime"=dword:00000000
"FileNotFoundCacheLifetime"=dword:00000000
"DirectoryCacheLifetime"=dword:00000000
Will post tomorrow with the results.
Official response from Microsoft was updated July 1st. Still no fix..