Install 32 Bit Visio With 64 Bit Office

  • Download visio windows 7 32 bit for free. Office Tools downloads - Microsoft Office Visio by Microsoft and many more programs are available for instant and free download.
  • From the Office home page select Install Office Other install options. (If you set a different start page, go to admin.microsoft.com/account#installs.) From My installs, under Visio, choose your language and the 64-bit or 32-bit version, then select Install Visio.
  • These 32-bit products are not supported with 64-bit installations: If you want to install 64-bit Office 2010, you must uninstall all 32-bit Office products first, and then run setup.exe in the x64 folder. If you want to install 32-bit Office 2010, close this Setup program, and then either go to the x86 folder at the root of your CD.
-->

Pertama, Download Microsoft Office Visio 2013 (32 Bit atau 64 Bit) klik disini. Extract files tersebut, lalu buka folder dan pilih setup.exe 3.

In many cases, you can install Office, Project, and Visio on the same computer. But, there are some combinations of Office, Project, and Visio that can't be installed together on the same computer.The two main things that determine whether Office, Project, and Visio can be installed together on the same computer are the version of the product and the installation technology used to install the product. What governs whether an installation scenario is supported are these two rules:

  • You can't install two products together that have the same version but use different installation technologies.
  • You can't install two products of different versions together if both products use Click-to-Run as the installation technology and those products have overlapping Office applications.

See the example installation scenarios section for several examples of installation scenarios that are supported and not supported, along with an explanation of why they are or aren't supported, based on the rules listed above.

Office releases and their version number

The following table shows Office releases that are currently supported by Microsoft, their associated version, and all the possible installation technology. The information listed in the table also applies to releases of Project and Visio. For example, the subscription version of the Project desktop app or Visio Professional 2016.

Download 32 bit or 64 bit
Office releaseVersionInstallation technologies
Office 365
(and Microsoft 365)
16.0Click-to-Run
Microsoft Store
Office 201916.0Click-to-Run
Microsoft Store
Office 201616.0Click-to-Run
Windows Installer (MSI)
Microsoft Store
Office 201315.0Click-to-Run
Windows Installer (MSI)
Cannot install office 64 bit

You can find this version information by going to Control Panel > Programs > Programs and Features. You can also find this version in the About dialog for the Office app. For example, open Word, and go to File > Account > About Word. On the top line of the About Microsoft Word dialog box, you will see the version number. For example, Microsoft Word 2019 MSO (16.0.10336.20044) 32-bit. For steps to find this version in different Office releases, see Find details for other versions of Office.

Note

  • Office 365, Microsoft 365, Office 2019, and Office 2016 all have the same version: 16.0
  • Office 2010, which is no longer supported, had a version of 14.0 and used Windows Installer (MSI) as the installation technology.

Installation technologies used by Office

There are different ways to purchase Office, Project, and Visio. For example, you can purchase them as part of an Office 365 (or Microsoft 365) plan, as a one-time purchase from a retail store, or through a volume licensing agreement. How you purchase them, along with which Office release you purchased – for example, Office 365 or Office 2016 – determines what installation technology is used to install Office.

The three installation technologies are:

  • Click-to-Run
  • Windows Installer (MSI)
  • Microsoft Store

In newer releases of Office, you can go to File > Account in any Office app, such as Word, and the type of installation technology is listed under the Product Information section.

Another way to tell which installation technology was used to install Office is to File > Account in any Office app. Under the Product Information section, if you see an Update Options choice, Office was installed by using Click-to-Run. If you don't see an Update Options choice, and you don't see any mention of Microsoft Store, then Office was installed by using Windows Installer (MSI).

The Microsoft Store installation technology is only used when you purchase and install Office from the online Microsoft Store.

You can't rely on just the product name and release to determine the installation technology used by Office. For example, if you purchase Visio Standard 2016 from a retail store, it uses Click-to-Run. But, if you purchase Visio Standard 2016 through a volume licensing agreement, it uses Windows Installer (MSI).

Example installation scenarios

Here are some example installation scenarios, whether they're supported, and an explanation of why they are or aren't supported.

Products to installSupported?Explanation
Microsoft 365 Apps
Project Professional 2013 (volume licensed)
YesThey use different installation technologies (Click-to-Run and MSI) and they are different versions (16.0 and 15.0)
Microsoft 365 Apps
Access 2013 (retail purchase)
NoThey both use Click-to-Run and they are different versions (16.0 and 15.0), but Microsoft 365 Apps already includes Access.
Microsoft 365 Apps
Visio Professional 2013 (retail purchase)
YesThey both use Click-to-Run, they are different versions (16.0 and 15.0), and there is no overlap in applications.
Office Professional Plus 2019 (volume licensed)
Visio Professional 2016 (volume licensed)
No, but there is an alternative installation method available.They use different installation technologies (Click-to-Run and MSI), but they are the same version (16.0).
For more information about the alternative installation method that's available, see Use the Office Deployment Tool to install volume licensed versions of Project 2016 and Visio 2016.
Office Standard 2019 (volume licensed)
Visio Standard 2013 (volume licensed)
YesThey use different installation technologies (Click-to-Run and MSI) and they are different versions (16.0 and 15.0).
Microsoft 365 Apps
Visio Professional 2016 (volume licensed)
No, but there is an alternative installation method available.They use different installation technologies (Click-to-Run and MSI), but they are the same version (16.0).
For more information about the alternative installation method that's available, see Use the Office Deployment Tool to install volume licensed versions of Project 2016 and Visio 2016.
Microsoft 365 Apps
Project Professional 2019 (volume licensed)
Yes, but with a caveat. 1They both use Click-to-Run and are the same version (16.0).
Microsoft 365 Apps
Visio Standard 2019 (retail)
Yes, but with a caveat. 1They both use Click-to-Run and are the same version (16.0).

1 You must be using at least Version 1808 of Microsoft 365 Apps, because that's the earliest version that recognizes Office 2019 products, including Project and Visio. Version 1808 or later is available in Current Channel, Monthly Enterprise Channel, Semi-Annual Enterprise Channel (Preview), and Semi-Annual Enterprise Channel. For Microsoft 365 Apps release information, see Update history for Microsoft 365 Apps.

Additional information

  • All installed products must be either the 32-bit version or the 64-bit version. For example, you can't install a 32-bit version of Visio on the same computer with a 64-bit version of Office.
  • Even though a particular installation scenario is supported, it might not be recommended. For example, we don't recommend having two different versions of Office installed on the same computer, such as Office 2013 (MSI) and Office 2019 (Click-to-Run).
  • Volume licensed versions of Office 2013 and Office 2016 use Windows Installer (MSI). Volume licensed versions of Office 2019 use Click-to-Run. The same is true for volume licensed versions of Project and Visio.
  • For Office 365, Microsoft 365, and Office 2019 products, all products installed on the computer must be using the same update channel. For example, the volume licensed version of Office Professional Plus 2019 can only use the PerpetualVL2019 update channel. Therefore, it can't be installed on the same computer that has the subscription version of the Project desktop app using Semi-Annual Enterprise Channel or on the same computer that has the subscription version of the Visio desktop app using Current Channel.

Related articles

-->

Up to now, if you had the 32-bit version of Microsoft 365 Apps installed on a device and you wanted to change to the 64-bit version, you needed to uninstall the existing 32-bit version and then install the 64-bit version. It also required that you account for all the other deployment settings configured for that device, such as the update path and the installed languages, so that those settings would be included when you did the 64-bit installation.

But now, to make it easier to change from a 32-bit to a 64-bit installation of Microsoft 365 Apps, the Office Deployment Tool and its configuration.xml file supports an optional attribute named MigrateArch. If the MigrateArch attribute is set to True, then your installation of Microsoft 365 Apps will be changed to the architecture (sometimes referred to as the bitness) that is specified in the OfficeClientEdition attribute.

With MigrateArch, you don't have to account for all the installed products and languages or other deployment settings. The migration process will preserve those during the migration process. But, if you want to make any changes to the installed products and languages, or other deployment settings, you can do that as part of the migration process by explicitly specifying those settings in your configuration.xml file. For more information, see Sample configuration.xml file to use with the Office Deployment Tool.

Note

The 32-bit version will be uninstalled and then the 64-bit version will be installed.

Requirements for using the MigrateArch attribute

OfficeInstall 32 Bit Visio With 64 Bit Office

To use the MigrateArch attribute, you need the following:

  • At least Version 1902 of Microsoft 365 Apps installed on the device that you want to change the bitness of.
  • At least version 16.0.11615.33602 of the Office Deployment Tool from the Microsoft Download Center.
  • A location that contains all the product and language files for the architecture that you are changing the installation to.

Before starting the migration process to a different bitness, you must have Version 1902 or later installed on the device that you want to change the bitness of. Migration is allowed to the same version, or to any later version, but you must have at least Version 1902 installed on the device before beginning the migration process.

Version 1902, or later, is available in Current Channel, Monthly Enterprise Channel, Semi-Annual Enterprise Channel (Preview), and Semi-Annual Enterprise Channel.

Providing a source location to be used with the MigrateArch attribute

When using the MigrateArch attribute, you need a location that contains the installation source files of the bitness that you're moving to.

For this location, if network bandwidth or internet connectivity is not an issue, we recommend that you use the Office Content Delivery Network (CDN), because the CDN will always have the most up-to-date program and language installation files that you need.

If you are using a location that's on your local network, be sure to use the Office Deployment Tool to download all the necessary product and language files ahead of time. You can download the 32-bit and 64-bit installation files to the same share for a given update channel. For example, you can download the 32-bit and 64-bit installation files for Semi-Annual Enterprise Channel to server01sec. But, you need to download the installation files for Current Channel to a different location, such as server01current.

2007

If your local network location doesn't contain files of the correct bitness, the migration fails and the bitness of the installation will remain as-is. If this location doesn't contain all the necessary language source files – for example, the French language files are missing – the migration will fail. To avoid this situation, we strongly recommend that you include AllowCdnFallback='True' in your configuration.xml file. This will use the Office Content Delivery Network (CDN) on the internet as a backup source from which to install the language files.

Sample configuration.xml file to use with the Office Deployment Tool

The following is a sample configuration.xml that will change an existing 32-bit installation of Microsoft 365 Apps to a 64-bit installation. All existing products, languages, and other deployment settings, such as update path, will be preserved.

Then, run the Office Deployment Tool in /configure mode and specify this configuration.xml file to make the change from 32-bit to 64-bit. The 32-bit version will be uninstalled and then the 64-bit version will be installed.

If you want to change the products or languages installed, or want to change other deployment settings, you need to specify those in your configuration.xml file. For example, if you want to change a 64-bit installation of Microsoft 365 Apps for enterprise in English to a 32-bit installation that includes English and German, changes the update path, and adds Visio in English, you would use a configuration.xml file that looks similar to the following example.

Additional information about using MigrateArch attribute

  • Before changing to a different architecture, especially when changing to 64-bit, make sure that your existing add-ins, macros, and complex Office files work on the new architecture. For more information, see Use the Readiness Toolkit to assess application compatibility for Microsoft 365 Apps.

  • The MigrateArch attribute can also be used to change the architecture of the subscription versions of the Project and Visio desktop apps.

  • The MigrateArch attribute won't migrate the bitness of Office programs on the device that were installed by using Windows Installer (MSI). Those programs can be removed by the using the RemoveMSI element in your configuration.xml file.

  • The MigrateArch attribute can only migrate Office products installed by using Click-to-Run and have a version number that starts with 16.0. For example, you can't use the MigrateArch attribute if Visio Professional 2013 was installed on the device by using Click-to-Run, because the 2013 version of Visio has a version number that starts with 15.0. You can find this version information by going to Control Panel > Programs > Programs and Features. If there are any Office products on the device that were installed by using Click-to-Run, and whose version number starts with 15.0, then the migration will fail.

  • If the architecture that you specify to move to is already the architecture of the currently installed products, then no migration takes place when you run the Office Deployment Tool. Your existing installation will not be removed and reinstalled. But if your configuration.xml includes other changes, such as adding a language, then those changes will be implemented.

  • If a user has an Office app, such as Word, open when the migration process begins, and the Level attribute is set to Full for the Display element in your configuration.xml file, then the user will be prompted to close the app. If they cancel the prompt, the migration is canceled. If the Level attribute is set to None, and Office apps are running on the device, then the migration will fail. You can use the FORCEAPPSHUTDOWN property in your configuration.xml file, but that will close the user's apps without any warning.

Run 64 Bit Programs On 32 Bit

Related articles