Microsoft Windows Installer Version 3.1 Free Download

Azure DevOps pipeline task that downloads and installs the latest .NET Core runtime and hosting bundle.

The Microsoft Windows Installer works for Windows 10 and its most current version is 4.5 XP 32 Bits. If you are unable to use the installer that comes with the program you wish to load and if you are unable to use the add/remove programs tool that comes with Windows then the Microsoft Windows Installer may be just what you need.

.NET Core coming to Microsoft Update

Starting in December 2020 .NET Core has been added to Microsoft Update. Before you proceed and use this custom extension, have a look at .NET Core coming to Microsoft Update.

Supported .NET Core versions

  • 2.1
  • 2.2
  • 3.0
  • 3.1
  • 5.0
  • 6.0

YAML snippet

Arguments

NameDescription
version
Version
Version of .NET Core to download and install.
Options: 2.1, 2.2, 3.0, 3.1, 5.0, 6.0
useProxy
Use a proxy server
Enabling this option will make it possible to specify a proxy server address that will be used to download the installer.
proxyServerAddress
Proxy server address
The URL of the proxy server to use when downloading the installer. Needs to include the port number.
Example: http://proxy.example.com:80
norestart
No Restart
Enabling this option will pass the /norestart argument to the installer to suppress any attempts to restart.
iisReset
Perform IIS reset
Enabling this option will reset IIS after installation.
The reset is recommended for all changes to take effect.
installArguments
Install arguments
Optional arguments that will be passed to the installer. Example: 'OPT_NO_ANCM=1 OPT_NO_X86=1'. See these options for more information.

Examples

YAML pipeline

  1. Install the Install .NET Core Runtime & Hosting Bundle extension from the Marketplace in your Azure DevOps organization.
  2. Create a new Environment with the name 'net-core-test'. Select 'Virtual machines' as the resource type.
  3. Register a machine in the new Environment and give it the tag 'net-core'.
  4. Create a new YAML pipeline with the following content.
  1. Save and run the pipeline.

Release pipeline with a Deployment group job

  1. Install the Install .NET Core Runtime & Hosting Bundle extension from the Marketplace in your Azure DevOps organization.

  2. Create a Deployment group.

  3. Register a machine in the new Deployment group.

  4. Create a new Release pipeline.

  5. Add a Deployment group job for the new Deployment group.

  6. Add the Install .NET Core Runtime & Hosting Bundle task to the Deployment group job.

  7. Configure the version you want to install.

  8. Save and run the pipeline.

Q & A

How does it work?

The task wraps a PowerShell script that:

  1. Retrieves the latest available .NET Core version from the appropriate releases.json, like https://dotnetcli.blob.core.windows.net/dotnet/release-metadata/3.0/releases.json.
  2. Looks in the releases.json for the download URL of the .NET Core Runtime & Hosting bundle installer (dotnet-hosting-win.exe).
  3. Downloads the installer.
  4. Executes the installer.
  5. Uploads any logs created by the installer.
  6. Performs an IIS reset if specified.

The task does not use PowerShell remoting so it will download and install .NET Core on the server where the task is run.

Does it uninstall older versions of .NET Core?

No.

What OS is supported?

The .NET Core runtime and hosting bundle is only available for Windows.

What to do when I get an error downloading the installer?

In some cases you might get an error like the one below because the task is unable to download the installer.

There are several reasons that might cause an error like this to occur:

  • The site https://dotnetcli.blob.core.windows.net, with the releases.json that has the download URL for the installer, is not a trusted site.
  • The site https://download.visualstudio.microsoft.com/, where the installer is hosted, is not a trusted site.
  • The server does not have outgoing internet access.

Depending on the reason adding a site to the trusted sites might do the trick.

Open source

This task is open source on GitHub.

Windows 3.x was the first to gain significant development and commercial traction. It combined the 8086, 286, and 386 modes of Windows 2 in to one package. It replaced the MSDOS Executive with a Program Manager and File Manager similar to those in OS/2 1.x. Much of its success was spurred by the availability and success of Microsoft Office. Although Microsoft would have had you believe otherwise, Windows 3.x was the direct foundation for Chicago/Windows 95.


Screenshots

PreviousNext

Release notes

Microsoft Windows 3.1 was an evolution to Windows 3.0 and undoubtably the most popular, poster child version in the Windows 3.x series. Among the changes in Windows 3.1 include a drop of real mode support (see more below), the removal of the Reversi game, updated icons with richer colors, an improved setup process with better hardware detection, and the introduction of batch install. The File Manager was completely revamped and a revamped hypertext help system was introduced.

Applications could talk to each other not only through the DDE (Dynamic Data Exchange) protocol, also used by OS/2, but also by the new Windows-only OLE protocol which allows for applications to share any type of object more seamlessly. Write, Paintbrush and the new Object Packager have support for this technology which remains with us today in Windows 8.

Windows 3.1 also came with support for TrueType fonts which provide more realistic font rendering as they are outline fonts that can scale to any point size. With TrueType users could finally have a good grasp that what was shown on the screen would be what was printed without blocky outlines. TrueType survives today along with its close cousin OpenType.

Multimedia support was now fully integrated along with the expandable Control Panel into Windows 3.1. In Windows 3.0 this was provided by a Multimedia PC add-on which usually came with new Multimedia PCs, sound cards and CD-ROM drives of the day. Common supported cards include Adlib and Sound Blaster 16.

Windows Installer Version 3.1

BETA During development Windows 3.1 was under the development codename Janus and 3 prerelease versions have surfaced, two beta candidates and a release candidate. The final beta was compiled on December 17, 1991 and expects a BIOS date of the 18th or later. Purple was replaced with blue and the boot screen was overhauled to the modern 3.1 variant.

Windows 3.2 was a Chinese language specific release. The only difference from 3.1 was additional support for Chinese characters and was released in late 1993.

On 386 systems and greater you can run a limited subset of 32-bit Windows applications (mostly those for Windows NT 3.5 and 95) with the Win32s (Win32 subset) patch.

Microsoft Windows Installer Version 3.1 Free Download

Installation instructions

To Install: Windows 3.1 requires an installation of either MS-DOS or PC-DOS and we recommend using MS-DOS 6.22 if you are unsure of a version.

Real Mode is no longer supported in Windows 3.1 requiring at least an Intel 80286 or equivalent to run. No 8086 or 8088 systems will run Windows 3.1