Asked By
Rananadeem
0 points
N/A
Posted on - 08/14/2011
Why Microsoft Office 2010 needs Windows Installer 3.0 or more before Installation?
Microsoft Office 2010 needs Windows Installer 3.0 for Installation
Hi,
As far as I know, Office 2010 has two architecture versions of the OCT, first one is for 32-bit office 2010 and the second is for 64-bit office 2010. Version 64-bit OCT supports 64-bit client editions in Office 2010, it offers the same user interface, and configurable capabilities settings as the 32-bit version. OCT files is located I the Admin folder beneath the x86(32-but) and x64 (64-bit) folders correspondingly.
Office 2010 requires Windows Installer 3.0 on computers that runs the 64-bit versions of the OCT, customization a 64-bit setup .msp files. Windows installer 3.0 released with Windows Vista and Windows Server 2008.
Microsoft Office 2010 needs Windows Installer 3.0 for Installation
Â
Not all software need Windows Installer in order to install them and the same goes to Microsoft products, not all of them require installing of Windows Installer. But there are ones that will really require you to install a certain version of Microsoft Windows Installer and that’s the reason why I keep myself up-to-date on the latest version of Windows Installer to have a better compatibility.
The Windows Installer or Microsoft Installer is the software component of Windows that is used in installation, maintenance, and removal of programs on modern versions of the Windows systems. In Windows XP Professional Service Pack 2 and earlier, the need to install Windows Installer is still possible and is required by some applications before the installation. But this component is already integrated when you upgrade your system to Service Pack 3 and installing Windows Installer is no longer required. Like for example, if you are running Microsoft Windows XP Professional Service Pack 3, even if a software requires installing of Windows Installer as what was stated in its system requirements, Windows will not ask you to install it because that component is already running on the system.
