Article - CS295508
Creo View 5.0 fails to completely uninstall using the Control Panel “Add/remove programs” utility, resulting in an invalid installation of Creo View 5.1 or later release
Modified: 10-Dec-2018
Applies To
- Creo View 5.0 to 5.1
- Upgrade installations from Creo View 5.0 to Creo View 5.1 or later
Description
- Using the Windows Control Panel > Add/remove programs utility to uninstall the Creo View 5.0 client, does not completely clean-up the installation:
- The PTC Creo View 5.0 product may temporarily disappear from the Control Panel Apps & Features list, but this entry reappears after a refresh
- A further uninstall of the PTC Creo View 5.0 product will then remove it from the list, but:
- Not all import filter related files and their containing sub-folders are removed from the installation folder (e.g. recipe/*2pv.pvr, adapters/*2pv.inf, etc.)
- MSI Component entries are not removed from the Windows Registry
- This only affects installations of Creo View 5.0 that were originally installed using the InstallAnywhere installer (setup.vbs) from the Creo View Client installation media
- Attempting to then install Creo View 5.1 (or later) using the Windows MSI Installer or updating an existing Creo View 5.0 installation directly using it, will fail to update all the residual Creo View 5.0 files to their later versions
- In Creo View, click File > Help > Customer Service Information and select the Installation file Version list
- It will list import filter related files with the version 15.0.0.26 or 0.19.0.16 (Creo View 5.0) instead of version 15.1.0.28 or 0.25.0.27 (Creo View 5.1)
- The Windows MSI Installers are typically used in the following Creo View installation scenarios:
- Download and installation using CreoView_64.exe or CreoView_32.exe from the Windchill Software Downloads page
- Creation and distribution of custom silent installation packages by IT organizations
- This can result in unexpected behaviour, such as the Import Filters not opening the most recent versions of CAD files or throwing errors relating missing or updated API’s
This is a printer-friendly version of Article 295508 and may be out of date. For the latest version click CS295508