By all accounts, it appears that Office365/2016 update 9029.2167 is flawed and causing some user to not be able to launch Access at all and instead receive the following error message
Automatic configuration of the current version of Microsoft Access has failed. Your database might not function correctly. This can occur if you do not have the necessary permissions to install Microsoft Access on this computer
In the last week (more now) there have been a whole slew of posts that have appeared on the subject, for instance:
- Microsoft Access is failing to start with ‘automatic configuration of the current version of Microsoft Access has failed’
- Fresh installed Access 2016 reports error “Automatic configuration of the current version of Microsoft Access has failed. Your database might not function correctly …”
- MS Access; Error message 3/3/2018
- Access problem:
- Cannot start Access today. Get error “Automatic configuration of the current version of Microsoft Access has failed.”
- Automatic configuration of the Microsoft Access has failed
- Microsoft Access Won’t Start
- Lancement Access impossible avec Office 365
- Office 365 : impossible de lancer Access
- Lancement ACCESS impossible depuis la dernière maj d’OFFICE 365 (Win 10 Pro)
- Après 5 mois d’utilisation, de ma suite Office 365, MS ACCESS ne veut plus s’ouvrir…
Worse is the fact that this was reported through the Insiders Program back in January!
Microsoft Fix
Also, should you still experience this problem after implementing the above mentioned build, please report back here by leaving a comment below so I can forward this information to Microsoft.
So How Do you Update Access If You Can’t Start Access?!
You have 2 Options:
- If you have Office, not just Access, you could open Excel, Word, … and manually update it. See: http://www.devhut.net/2017/11/23/ms-access-how-to-manually-update-access-office-2016/ for all the details.
- If you only have Access, then the other method would be to use good old DOS to tell office to update itself. Here are the instructions that worked for me:
- Open a Command Prompt (should have administrative priviledges) and then execute the following command
- Naviagte to %programfiles%\Common Files\Microsoft Shared\ClickToRun by issuing the cd command
- cd %programfiles%\Common Files\Microsoft Shared\ClickToRun
- Run the office2rcclient to revert your office build
- officec2rclient.exe /update user updatetoversion=16.0.9029.2253
Possible WorkArounds
Better safe than sorry!
As it stands right now based on what I have managed to find by combing through various threads and personal experience there are 2 workarounds while we wait for Microsoft to identify and fix the root cause of this issue:
- Uninstall the Latest Office Update (confirmed by multiple users)
- Install the Microsoft Access Database Engine 2016 (does not work for all users)
Uninstall the Latest Office Update
As such, see: http://www.devhut.net/2017/10/04/microsoft-office-uninstall-an-update/ and try reverting to build 9001.2138.
To do so, you need to open a Command Prompt (should have administrative priviledges) and then execute the following command
- Naviagte to %programfiles%\Common Files\Microsoft Shared\ClickToRun by issuing the cd command
- cd %programfiles%\Common Files\Microsoft Shared\ClickToRun
- Run the office2rcclient to revert your office build
- officec2rclient.exe /update user updatetoversion=16.0.9001.2138
Then, do not forget to disable Automatic Updates
- Click File, and then click Account.
- Under Product Information/Office Updates, click Update Options, and then click Disable Updates.
Also, if you do not feel comfortable doing the above and have the CTR version (ie: Office 365) then simply contact the Office 365 support and ask them to revert your Office installation for you.
Lastly, do not forget to check the various threads or Microsoft’s website to find out when a new update to fix this issue is released so you can reactivate the Automatic Update, or, if you prefer continue to manage things yourself manually. Just note that Microsoft will not be advising you when they come out with a fix, it is up to you to figure it out and manage things.
Install the Microsoft Access Database Engine 2016
A secondary, but less reliable proposed solution has been to download and install the Microsoft Access Database Engine 2016 Redistributable which you can get from https://www.microsoft.com/en-us/download/details.aspx?id=54920
There are conflicting reports about the installation of the Microsoft Access Database Engine 2016 Redistributable as some people have reported that all attempts generate an error and they never manage to install it. So beware it doesn’t appear to work for everyone.
I also do note believe it wise to go and install a new piece of software on a system when a much simpler workaround exists (uninstalling the latest update as previously mentioned). Why add more registry entries, have another piece of software that could get messed up somehow, …
If you can confirm any of the above, or can offer another workaround please drop me a line by leaving a comment below so I can update this post with the information.
Conclusions
I think with this most recent bug, and the many other bugs we have experienced with Office365, and the major delay in seeing Microsoft adequately respond to such issues one has to seriously consider permanently disabling Automatic Updates and rather regularly (perhaps on a monthly basis) manually applying new builds only once they have been released for several weeks (or even months) to ensure they are actually safe for consumption.
Some Useful References:
- Microsoft Office 365 – Uninstall an Update
- How to revert to an earlier version of Office 2013 or Office 2016 Click-to-Run
- Fixes or workarounds for recent issues in Access (nothing here yet, but hopefully soon we get some official solution/support directly from Microsoft)
- Error: “Automatic configuration of the current version of Microsoft Access has failed.” occurs when you try to start Microsoft Access after updating to Version 1802
Was Microsoft Informed About This Issue?
Yes, I passed this information along to the Access Dev team (2018-03-03), but have yet to hear back from anyone.
Update (2018-03-06) I followed-up and finally heard back that the Dev Team is looking into the matter, but I have yet to see them post any information about this issue on their Fixes or workarounds for recent issues in Access webpage which would be the logical place to see some form of communication with the public on this matter. Fingers crossed though!
Update (2018-03-09) I’ve been sent a few e-mails regarding an update from the Dev Team and sadly I’ve heard nothing more on the subject and truthfully I probably won’t. That said, they still haven’t even added it to their Fixes or workarounds for recent issues in Access webpage which either means they or too busy, but then what’s the point of the page if it doesn’t carry current problem or they still haven’t deemed this to be a problem? Your guess is as good as mine when it comes to what is going on and when we might see some communication or action out of Redmond.
Update (2018-03-13) Microsoft has finally added the issue to their Fixes or workarounds for recent issues in Access webpage and created a webpage specifically regarding this issue, see Error: “Automatic configuration of the current version of Microsoft Access has failed.” occurs when you try to start Microsoft Access after updating to Version 1802
I have just experienced the same problem. Access won’t start because of the “Automatic configuration ……….”
Contacted Microsoft Office Support via telephone and received the biggest runaround that I have ever
experienced, being transferred at least 6 times to different departments, etc. without any of the personnel having the slightest clue as to what to do, other than transfer you to someone else equally in the dark.
Please keep me posted on what you learn. Hopefully someone will garner the attention of someone in the Development Department. My finger are crossed!!!!!!!
Thank you for all of your efforts Mr. Pineault.
Thank you Daniel – worked perfectly after searching the net for some time!
Please send me your paypal and I’ll gladly gift you a beer!
Thank you for confirming that the workaround worked for you. I’m sure it will help others.
Reverting to 9001.2144 worked!! After 4 hours of trying all the other fixes – manual Office removal, registry editting, etc, this is the one that did it. THANK YOU!
I’m glad I could help and thank you for confirming that the workaround worked for you. I’m sure it will help others.
Installing Microsoft Access Database Engine 2016 worked for me! I had just some issues with installing is stating about compatibility issues with 64/32 bit version (other people have encountered it).
Installing this tool in quiet mode did the job. Just run in cmd $> AccessDatabaseEngine.exe /quiet then launch Access app. Issue should be resolved now.
I’m glad that solved your issue, but why install new software when all you need to do is revert the build to 9001.2138 and turn off automatic updates? What is the advantage of having to install a new piece of software on your PC?
Thank you so much!! have a nice week
Many thanks for the suggestions Daniel. Reverting to build 9001.2167 got my Access 2016 going again.
That was after a long fruitless session with a MS support chat agent who re-installed Office but that did not fix it. I also tried Restoring the PC to the earliest Restore Point I could but that didn’t work either.
Cheers!
I’m having the same problem and lack of support from Microsoft on this issue. However, I’m not techie enough to apply what you’ve posted in this thread, and I can’t seem to convince the techie Microsoft chat techs to look at it and do it for me. They just tell me to call support (that isn’t working on Saturdays!) and then cut me off. Very disappointed in Microsoft on this one, but that goes along with much of their reputation. I’m hoping that I can find someone with enough technical skills to apply this fix to my computer so that I can get Access up and running again.
If you have Office365 then be sure you are contacting the Office365 support and not Microsoft’s general support.
Daniel: Might this have something to do with what I’m experiencing with the Access 2016 runtime on a new Windows 10 machine? I never had Office installed on the machine, and the runtime use to work, but suddenly, every time I try to open a database with the runtime, I get a message that I need to install Office and there is no way out but to 3-finger it! I either have to buy and install Office or turn the machine off!
Your thoughts….
I truly have no clue.
I’d try running an Office Repair, but I don’t even know if that option exists in the runtime (I will have to explore).
You could try reverting your installation, but once again, I don’t even know if that option exists in the runtime (another thing to explore).
As a last resort you could uninstall and then reinstall runtime.
Hi Daniel
In your “Uninstall the Latest Office Update” instructions above are you saying that Office does not have to be uninstalled first AND then a prior version downloaded AND then the prior version installed?
Are you saying a prior version is installed over a newer version.
The use of the word UNINSTALL is really confusing me here and also in the thread that I started (and you replied to many times – thank you) https://answers.microsoft.com/en-us/msoffice/forum/msoffice_access-mso_winother-mso_2016/cannot-start-access-today-get-error-automatic/43a2f5f7-0ced-4bed-8f0a-8c75bd76c7e7
With Office365/2016 you don’t uninstall office, you revert it. By running the required code, Office reconfigures itself and removes whatever patches it previously installed until it gets back to whatever build you specify. I don’t know the inner working, but you simply execute the command and it does whatever it has to do to get to the build you specified in the command line.
Installing the workaround fixed my issue and I was able to open Access immediately. Thank you!!! Especially thank you for providing the command prompts. I’m a computer abuser, not an IT guy, so I need very specific instructions! Thanks again. Hopefully MS will get their mess fixed soon.
You are most welcome and thank you for confirming the workaround worked for you.
Thank you so much! It was exactly what needed to be done. I just wish I would have found your post five hours earlier.
We had a versión of Skype for business basic. And uninstalling it and reverting to the previous versión did the trick. Thanks for the post.
Thank you so much for the workaround. Reverting to build 9001.2138 worked for me.
I had the same problem. What I did was removing my 64-bit Office version completely and installing the 32-bit. That worked. I have synchronized my computer with One Drive. After installing the 32-but version, the small slider in the left upper corner was gone although my computer was still synchronized. Because this workaround is perfect for me, I decided, with my fingers crossed, to again install the 64-bit version. And hé, everything functioned like before. Even the small slider was present again. Before Access after trying to open the application, a small square appeared in my screen with two options. The one on top was blue and contained a lot of characters like %*&live&% etc. The one at the bottom was a clear field. Before I could read the text properly, the error message appeared. Maybe the bug has something to do with the cloud connection.
How do you update the build?
“I just received (2018-03-15) a notification from the Access Dev Team that they have identified the underlying issue and created a fix. So if you update your build to 9029.2253 the problem should be resolved.
Also, should you still experience this problem after implementing the above mentioned build, please report back here by leaving a comment below so I can forward this information to Microsoft.”
It’s the same process as reverting the build. I’ve updated the post to include the necessary instructions in the update section.
The new version of Office works! (unbelievable.) Thanks for the updates. This page has been very helpful.