Access database in an inconsistent state...Windows 10 1803 update
Access database in an inconsistent state....since the release of Windows 10, 1803 our significant percentage of our 3500 customers have consistently lost connection to the back-end database and been forced to stop work during the day to repair their database. Only recently did we discover the leasing fix. In the meantime, our product reputation has been adversely affected. Please release a production update since many of the IT people have refused to make the lanmanserver registry entry and are waiting for the Windows update. HELLO MICROSOFT PLEASE HELP!!
We are well aware of this issue and are working closely with the Windows team on resolving it. Although we believe we have a solution to the problem, it introduces some new issues that we need to investigate and resolve before we can deploy the fix.
Guys, this is a two year old bug and we're coming up on our 4th version of windows 10. Can we please be provided some more insight into this?
Ali B. commented
I'm glad you are working on it since October 17, 2018, when can we expect a fix by? 2030?
No update since 2018 really show the community you are on top of things. Keep up the great work and leave us to figure things out for ourselves for another 2 years.
Hans (Netherlands) commented
Same as "Fix Windows 10 1803 Frontend - Backend corruption issues" which has a lot more votes. Is there a moderator who can merge these two registrations of the same issue?
Alan Cossey commented
How are you getting on working closely with the Windows team on resolving this issue which came up in October 2018, please?
This issue appeared on threads at the end of last June. The amount of damage and time lost to addressing this issue continues to mount and decision makers at my place of work want to move away from Microsoft solutions, because of this problem. Here's a summary of the issue https://www.devhut.net/2018/06/13/access-bug-database-is-in-an-unrecognized-format/
Microsoft - MS Access inconsistent state Status?!?!?
Months of waiting.
Peter Rühm commented
One of my clients had the same problem. IT refused to do any registry change for us !
Converting the .accdb backend to .mdb made it possible to work with the frontend again. Luckily, I had installed some lines of code to manage the backend connection. But this solution is not satisfying: many other files are connected to the backend and can not be changed that easy...