Install Error
By Richard Rost
11 days ago
Fix Database Engine x64.exe Install Errors and Solutions In this video, we address the common "You cannot install the 64-bit version of Microsoft Access Database Engine" error, explain why 32-bit and 64-bit Microsoft Office component mismatches occur, and discuss several approaches to resolve the issue. We talk about options like extracting the database file, trying the 64-bit Access Runtime, updating older VBA code, reinstalling the correct Office version, and ensuring proper network connections to backend data. Suggestions for seeking additional help are also covered if the problem persists. Miriam from Lincoln, Nebraska (a Platinum Member) asks: Many years ago I paid a consultant to develop an Access database for my company, and it's been working great this whole time. We just bought all new computers, and they came with Microsoft Office already installed. Now we're trying to reinstall our Access database from the original disk he gave us, and we're getting this error: "You cannot install the 32-bit version of Microsoft Access Database Engine because you currently have 64-bit Office products installed." What do we need to do to get this working? The consultant is out of business, and no one here really knows much about Access, so we found you online and figured we'd ask the Access guy. LinksNote- Eagle-eyed viewers might feel like they're seeing double here. This topic was also featured in this week's Quick Queries #88, but since it's something a lot of people are searching for, I pulled it out as its own standalone video so you don't have to sit through the full episode just to get this fix.
Keywords TechHelp Access, You cannot install the 64-bit version of Microsoft Access Database Engine, Access Database Engine install error, 32-bit vs 64-bit Office mismatch, ACCDB file, ACCDE file, MDB file, Access Runtime, VBA compile error, relink Access frontend to backend, shared network path, SQL Server connection, upgrade old Access database
Subscribe to Install Error
Get notifications when this page is updated
Intro In this video, we address the common "You cannot install the 64-bit version of Microsoft Access Database Engine" error, explain why 32-bit and 64-bit Microsoft Office component mismatches occur, and discuss several approaches to resolve the issue. We talk about options like extracting the database file, trying the 64-bit Access Runtime, updating older VBA code, reinstalling the correct Office version, and ensuring proper network connections to backend data. Suggestions for seeking additional help are also covered if the problem persists.Transcript Are you getting the "You cannot install the 64-bit version of Microsoft Access Database Engine" error and wondering what the heck it even means?
Welcome to another TechHelp video brought to you by AccessLearningZone.com. I am your instructor, Richard Rost. Today, we are going to talk about that Access Database Engine install error, why you are getting that 32-bit versus 64-bit mismatch, and how you can fix it so you can actually get your database up and running again.
Today's question comes from Miriam in Lincoln, Nebraska, one of my platinum members. Miriam says, "Many years ago, I paid a consultant to develop an Access database for my company and it has been working great this whole time. We just bought all new computers and they came with Microsoft Office already installed. Now we are trying to reinstall our Access database from the original disk he gave us and we are getting this error: 'You cannot install the 32-bit version of Microsoft Access Database Engine because you currently have 64-bit Office products installed.' What do we need to do to get this working? The consultant is out of business and no one here really knows much about Access, so we found you online and figured we would ask the Access Guy."
Well, I appreciate that. I like "the Access Guy." I just checked online, and theaccessguy.com and accessguy.com are both taken, so that's out.
Anyway, this is a very common situation. This was more common a few years back, like in 2020, when everybody was still switching between 32-bit and 64-bit Office products.
What's basically happening here is a mismatch between 32-bit and 64-bit Microsoft Office components. Your new PCs probably all came with Windows 11 and 64-bit Microsoft Office, which is the new version. Your old Access application was probably built in a 32-bit version of Microsoft Access, probably like 2013 or 2010 or 2007. However old it is, you did not really specify.
The problem is you cannot have two different versions of the same Microsoft Office on one computer. It has to be all 32-bit or all 64-bit. Even if you do not have Microsoft Access with your new computers, you still cannot install an old 32-bit version of any Office application as long as you have 64-bit versions of any Office applications like Word or Excel or PowerPoint on the new machines.
So you have some options. You mentioned that you are trying to install it off an old disk that your consultant built for you. If you can, try taking the database file off that disk if it is exposed and available. A lot of those old setups bundled the Access Runtime with the database using something like InstallShield, so it might just be an EXE bundle, some kind of a package, or even a ZIP file. It could just be any number of things.
If you can get just the ACCDB or ACCDE file, or if it's really old, the MDB file, then you should be able to just install a new version of Access and work with that. The database file may just run as it is with the new version of Access. Sometimes it does, sometimes it does not.
You should not have to purchase a copy of Access for each of those machines if it is not included already. You can try installing the Access Runtime. Again, if your new machines have 64-bit, you can try installing the 64-bit Access Runtime and see if that runs your database. It may not. Try it on one machine first and see if it works. If the database opens and runs fine, great, you are done.
If you get errors, especially compile errors in the VBA code, that means the database was built specifically for 32-bit, and the VBA might need to be updated for 64-bit. I did a video on this back in 2020 when a lot of people were having problems with this.
If neither you nor anyone on your staff is very familiar with Access, this might be a little bit over your head for now. You might need to find a consultant to do this for you.
If you get compile errors, you basically have two choices. Either have someone go in and update the code so it works in 64-bit, or the easier route in a lot of cases is simply to uninstall Office--the Office that came on your new machines--and reinstall the 32-bit version so everything matches what the database expects. You would want to have the same version of Office that your database was built with.
Worst case scenario, what I do is take one older machine that you might have, if you still have an old computer laying around. Uninstall Office completely, install everything from the Access disk that your consultant gave you, just grab the database file, and move that over to your new systems. Then reconnect it to your backend. Hopefully, your backend is still sitting safely on your server. I am assuming you did not just nuke the server where your data is sitting.
Since you said you got new office computers for everybody, I am assuming that you are using a shared database system where everybody in the office is connecting to the same backend file, where your data is--your tables and such. I am also assuming you did not just wipe out the server and that your data is still safely sitting there. If not, that is a whole different conversation altogether.
If it's an Access backend, just an Access file containing the tables, you will need to make sure everyone has a proper connection to it, whether it's the same mapped drive letter or a shared network path, so that the file can be found. If you do not know how to set that up, I have a video on that.
If you have SQL Server, you need to make sure that each machine can connect to your server. You will likely have to relink your front-end databases to that backend. That is a separate step, but it is part of getting everything working again.
I used to work with a lot of companies back in the day when I was a consultant. Yes, back in the day was a Tuesday, and they had their old system running and everything was humming along, but they wanted to upgrade their computers--put all new hardware in there. I said, "Okay, great, no problem. We can bring all the new hardware in, we can set it all up, take me about an hour, but then we have to go through, install Access, install whatever other applications you need, configure them, set up the drive letters, and point everything to the server. It is a lot of work to get done. Buying the new hardware is the easy part. It is all the service and configuration that comes after that point, and that is something that a lot of companies do not consider."
The good news is your database is not broken. It is just an old setup clashing with modern 64-bit Office, and sometimes a little bit of code needs to be edited too for the new versions.
If you are still having trouble after all that, post the details of your setup in the forums on my website. The moderators and I hang out in there all the time. We might be able to help you get things sorted out. If it turns out you need more hands-on help, I do not provide one-on-one assistance myself. I got out of the consulting game years ago, but I do have a solid network of consultants I can point you to who deal with this kind of thing all the time, so check out that. I will put links to all this stuff down below.
All right, so the fix here is making sure your Office and Access components all match. Either go all 64 across the board or switch everything back to 32-bit, and in a lot of cases you can skip that old installer completely and just run the database with the proper runtime.
If this helped you out, post a comment down below and let me know, and feel free to share any questions you have for future videos.
But that's going to be your TechHelp video for today, brought to you by accesslearningzone.com. I hope you learned something. Live long and prosper, my friends. I will see you next time.Quiz Q1. What is the main reason for the "You cannot install the 64-bit version of Microsoft Access Database Engine" error?
A. Mismatch between 32-bit and 64-bit Office components
B. Corrupted Microsoft Office installation
C. Outdated Windows operating system
D. Insufficient hard drive space
Q2. What is NOT a solution for running an old 32-bit Access database on new computers with 64-bit Office?
A. Install the 64-bit version of Access Runtime and see if the database works
B. Update the VBA code in the database to be compatible with 64-bit
C. Uninstall the 64-bit Office and install the 32-bit version
D. Ignore the error and continue installation
Q3. What file types might your Access database be stored as?
A. ACCDB, ACCDE, MDB
B. DOCX, XLSX, PPTX
C. EXE, MSI, BAT
D. ZIP, RAR, 7Z
Q4. If you experience VBA compile errors after upgrading to 64-bit Office, what does that likely mean?
A. The database was built specifically for 32-bit Access
B. The database is corrupted and cannot be repaired
C. The disk drive is failing
D. The Access license has expired
Q5. What is a possible method to retrieve your old Access database file if the installer is bundled?
A. Find the ACCDB, ACCDE, or MDB file within the install package or disk
B. Download Access from the internet for free
C. Ask Microsoft Office support for a new file
D. Reset your computer's operating system
Q6. When setting up a shared Access database, what do users need on their computers?
A. Proper connection (mapped drive letter or network path) to the backend file
B. Administrator privileges for Windows only
C. No Office products installed
D. Access to the internet
Q7. What should you do if you cannot fix the problem and no one in your company is familiar with Access?
A. Find and hire a qualified Access consultant
B. Switch to using Microsoft Excel instead
C. Delete all Access database files
D. Repair Office installation
Q8. Which of the following would NOT resolve the 32-bit vs 64-bit mismatch in Office installations?
A. Ensure all installed Office components are the same bitness (32 or 64)
B. Reinstall everything using only the 64-bit versions
C. Reinstall everything using only the 32-bit versions
D. Run both 32-bit and 64-bit Office products together
Q9. If your backend data is stored on a server, what must be done after moving the frontend database to a new machine?
A. Relink the frontend database to the backend file or server
B. Install SQL Server locally on every machine
C. Reinstall Windows on the server
D. Change all file extensions to .TXT
Q10. What is the main troubleshooting advice given for resolving Office bitness conflicts with an Access database?
A. Make sure all Office and Access components match in bitness (all 32 or all 64)
B. Run the installer multiple times
C. Install upgrades for Windows only
D. Delete system32 files
Answers: 1-A; 2-D; 3-A; 4-A; 5-A; 6-A; 7-A; 8-D; 9-A; 10-A
DISCLAIMER: Quiz questions are AI generated. If you find any that are wrong, don't make sense, or aren't related to the video topic at hand, then please post a comment and let me know. Thanks.Summary Today's video from Access Learning Zone addresses a common problem many people encounter when updating their computers: the "You cannot install the 64-bit version of Microsoft Access Database Engine" error. I'm Richard Rost, your instructor, and in this lesson I will explain why this error happens, what causes the mismatch between 32-bit and 64-bit Office installations, and what you need to do to resolve the issue so your Access database runs as it should.
This situation often comes up when a business, like the one mentioned by Miriam from Nebraska, buys new computers that come preloaded with the latest 64-bit version of Microsoft Office. Meanwhile, their existing Access database was built several years ago using a 32-bit version of Access. Now, they're trying to reinstall the database and run into an error saying that the 32-bit Access Database Engine can't be installed alongside an existing 64-bit Office.
This type of mismatch can really disrupt your workflow. Essentially, Microsoft Office will not allow both 32-bit and 64-bit versions of its applications to exist on the same machine. You have to stick with one kind across all your Office programs. Even if the new machines don't actually have Access installed, if any Office app like Word or Excel is running in 64-bit, you won't be able to install any 32-bit Office components.
So, what can you do about it? Your first step is to see if you can copy out the actual database file from your original installer disk, whether that's an ACCDB, ACCDE, or even an old MDB file. Sometimes, installers bundled Access Runtime and the database together as an EXE or other package. If you can extract just the database file, you should try installing a current version of Access or the Access Runtime in 64-bit and open the file. Test this on a single workstation before rolling it out more widely. If everything works, you're all set.
However, if you run into compile errors (especially related to VBA code), it generally means the original database was built specifically for a 32-bit environment. Some updates or changes to your code may be required to get things functioning on 64-bit Office. If you or your staff aren't comfortable working with Access or VBA, you may need to bring in a consultant to help.
If updating the code isn't practical, another solution is to remove the pre-installed 64-bit Office and instead install the 32-bit version, which should match what your database expects. Make sure that the Office version you install matches the one in use when your database was first created.
As a last resort, you might set up an old computer with a clean installation just to extract the necessary files before moving them over to the new machines. After moving the files, you'll need to ensure all your systems can reach the backend, which might be on a shared server. Rest assured, as long as you haven't deleted your data server, your information should still be intact.
If your backend is just a regular Access file, you'll need all users to connect to it properly, either using a mapped drive letter or a shared network path. I have separate lessons on how to set up those connections if you need more guidance. In cases where your backend is using SQL Server, you'll need to relink your front-end database files so each client machine can access the data.
From my years in consulting, I can tell you that switching hardware is usually the easy part. Getting all your software and configurations set up for the new systems often requires more attention and effort, and it's something businesses often overlook.
The most important takeaway is that your core database is likely still fine. It's just a compatibility issue with newer Office versions, and perhaps some code tweaks are needed to make everything work smoothly on a 64-bit setup.
If you're struggling after trying these steps, I encourage you to post in my website's forums. Both myself and the moderators are active there, ready to help with troubleshooting. If you need one-on-one assistance, I no longer provide direct consulting but I can connect you with professionals who specialize in these transitions.
To fix this error, make sure all your Office and Access programs use the same bitness: either all 32-bit or all 64-bit. Often, you don't need to run old installers and can simply open the database with the appropriate version of Access or Access Runtime.
For a complete video tutorial with step-by-step instructions on everything discussed here, visit my website at the link below. Live long and prosper, my friends.Topic List Explanation of the 32-bit vs 64-bit Office mismatch error
Why the Access Database Engine cannot install with mixed Office versions
Extracting just the ACCDB, ACCDE, or MDB file from an old installer
Using Access Runtime as a possible solution
Testing the database with 64-bit Access Runtime
Dealing with VBA compile errors from bit-version differences
Options for updating VBA code for 64-bit compatibility
Uninstalling 64-bit Office to reinstall 32-bit Office
Migrating the database file from an old computer
Reconnecting front-end databases to Access or SQL Server backends
Ensuring network paths or drive mappings for shared backend filesArticle If you are trying to install Microsoft Access or the Access Database Engine and getting the error message that says "You cannot install the 32-bit version of Microsoft Access Database Engine because you currently have 64-bit Office products installed," you are not alone. This is a common issue that many users encounter when moving from an older computer setup to a new one, especially during major upgrades like switching to Windows 11 or Office 365.
This error is caused by a mismatch between the bit versions of your Office products. Microsoft Office comes in both 32-bit and 64-bit variants, and you cannot mix and match components of different bit types on the same computer. For example, if your new computer came with 64-bit Office pre-installed, you cannot install a 32-bit version of the Access Database Engine or a 32-bit Access Runtime. Everything, including any add-ins, has to match: all 64-bit or all 32-bit.
This problem usually comes up when you have an older Access application, possibly developed years ago in 32-bit Access (for example, Access 2010, 2013, or even earlier), and you are now trying to install it on a new machine that only has 64-bit Office components. You might be using an installer or setup package that your consultant created, which contains the 32-bit Access Runtime bundled together with your database.
The first step you should try is to see if you can extract just the database file from the disk or installer your consultant gave you. The database file is usually named with an ACCDB or ACCDE extension, or if it is very old, MDB. If you can get just the database file on its own, you may be able to open it using a modern version of Access, either the full program or the runtime version, as long as the version and bit type match what is installed on your machine.
If your new computers have 64-bit Office and you are missing Microsoft Access, you can try installing the 64-bit Access Runtime. Download it from the official Microsoft website and install it on one machine as a test. If your Access database opens and runs with the 64-bit runtime, you are in luck. However, if you run into errors - especially compile errors when running VBA code inside your database - that means the database was written specifically for 32-bit Access. Some VBA code, especially anything involving Windows API calls, often needs a few changes to function properly in 64-bit Access.
If you do encounter those VBA errors or cannot get the database to run, you have two options. The first and most flexible is to update the VBA code in your database so that it works in the 64-bit environment. This is a common task but does require some knowledge of Access VBA. If no one at your company has that experience, you might need to hire a consultant who can update the code for you. The easier but more disruptive solution is to uninstall all 64-bit Office components from your new computers and instead install the 32-bit Office suite, making sure that everything matches the environment your database was originally designed for. This way, you can use the setup package or installer as you did previously, and your database will behave as expected.
If you still have an old computer that runs the Access database successfully, you can use it to extract the database file. Uninstall any Office components from that old computer, install the full setup or installer that your consultant provided, and then just copy the database file over to your new systems. After that, make sure connections to your data are working. If your setup uses an Access backend with split front-end and backend files, everyone will need to have access to the shared backend, which is often on a server or a network share. Make sure all users have the correct network drive mapped, or the correct path set up, so the front-end database can find and connect to the backend file. If your Access database instead uses SQL Server, you will need to ensure every workstation can access the server.
One important thing to remember is that your data and actual database file are not broken. The error is only about the mismatched versions of Office and Access components and, possibly, the need for code updates to support a new bit architecture. If you suspect your database uses tables hosted on a server or another backend, do not overlook setting up the file links or ODBC connections again on your new machines.
If all else fails and you are stuck, consider seeking help from Access experts or online forums. There are consultants and communities online familiar with these migration issues who can assist you in getting your database working again. This issue comes up frequently when businesses upgrade their computer hardware and software, but the solution is almost always about matching the version and bitness of your Office and Access components - either all 32-bit or all 64-bit.
The takeaway here is straightforward: avoid mixing 32-bit and 64-bit Office components, and match your runtime or full Access installations to your system. If you can get a plain copy of your Access database file, you can often skip over those old installers entirely and just use the appropriate runtime or Access version. With a bit of troubleshooting and possibly some code tweaks, your Access database should be up and running on your new computers. |
