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.
Thank you so much,
Do I need to revert back for all users or just the main admin ? Just saw today's update by Microsoft for this type of issue, very frustrating.
I am not sure it will work as our IT department controls all the update etc.
In my case, I have the front end database running on users' laptops, so I needed to rollback all the users to Access 2013 (Note there is a 32-bit and a 64-bit version. I needed to go with 32-bit). Not sure if you have a similar setup.
I know what you mean about IT departments controlling all updates, revisions, etc. I work for a very large corporation with many levels of bureaucracy. It's taken me since Nov 2019, when the database corruptions started happening after the Windows 10/Office 2016 upgrades,
to get them to review my numerous requests and rollback my users to Access 2013 32-bit. I also had to enlist my boss, his director and the CIO to assist me. IT will finally be starting the rollback next week. Persistence pays off.
They will be moving to a new system in the future, but I have to keep this Access database working in the meantime.
Wouldn't it have been simpler to either employ the server reg fix or the client reg fix?
Can you point me to the server fix please?
They both didn't work. I have tried all solutions posted, which I why I resorted to rolling back to Access 2013.