Skip to main content

“Visual Studio” family 3.0 installer does not remove existing product version when updating

  • July 24, 2017
  • 0 replies
  • 0 views

Problem:

During an upgrade from an earlier release, the existing entry in Programs and Features / Add Remove Programs is retained (highlighted below):

 


If the user subsequently selects to remove the older release (e.g 2.3.2), the newer release (i.e. 3.0) is removed from upgraded areas on disk (i.e. Program Files). This results in an incomplete install of the newer release.

This affects Pre-release versions only of the following:

  • Visual COBOL for Visual Studio 2012
  • Visual COBOL for Visual Studio 2013
  • Visual COBOL for Visual Studio 2015
  • Enterprise Developer for Visual Studio 2012
  • Enterprise Developer for Visual Studio 2013
  • Enterprise Developer for Visual Studio 2015

Solution:

The problem is resolved in newer builds of the affected 3.0 installers. Using these versions to upgrade an older release (i.e 2.3.2) will result in the correct removal of the older release entry in Programs and Features / Add Remove Programs, and therefore prevent the scenario described above from occurring.

In some cases, 2.3.2 HotFix entries may still be present in ‘View Installed Updates’ but these are orphaned, harmless and can be ignored. If a HotFix entry is still present, and is a HotFix to the older/upgraded release, the entry can be removed by Uninstalling the HotFix – NOTE: in this situation, only the entry is removed – no product files are affected.

Affected builds - Installer EXE ‘Date modified’: EARLIER THAN 04/07/2017

Resolved build - Installer EXE ‘Date modified’: 04/07/2017 :


Additionally, the Digital Signing Timestamp can be examined. This is visible from the ‘Digital Signatures’ tab of the Installer EXE Properties e.g:


#EnterpriseDeveloper
#MFDS

0 replies

Be the first to reply!