Software that installs in Program Files or Program Files(x86)

I just installed a software package published by a company that caters mainly to Mac users and (in my opinion) really doesn't understand Windows well. By default, their installer (install.exe) chooses C:\Program Files(x86)\xyz as the install directory, where let's say xyz is the name of the package. After the install, I don't see any new entries in the start menu or in Apps and Features. Looking at the contents of the install directory, I see spreadsheets, pdf documentation, and some images. There are no executables. There is no uninstaller.

Here is my question: Is there a simple way to determine if this package can be moved? In other words, is there a way to determine if a package in Program Files somehow depends on its location?

Assuming that the package does not depend on its location, would it have been better to distribute this software as a zip file that the user could simply unzip anywhere rather than an (unsafe) install.exe?

perkinw said:

Here is my question: Is there a simple way to determine if this package can be moved? In other words, is there a way to determine if a package in Program Files somehow depends on its location?

Short answer. No.

Generally the only way to know for certain is if this information were published (it usually isn't) or you had inside information from the developer. The lack of an uninstaller would seem to indicate the program can be easily moved but I wouldn't count on it. Most installers allow specifying where the application will be installed. Not all do. That is your one chance to do so. Moving an installed application can be highly problematic. Usually the only applications that can be easily moved are the so called portable applications. They are usually advertised as such.

Application developers have many options as to where and how files are stored. Support files can be and often are stored in a wide variety of locations. There are no firm rules that govern this, only conventions and guidelines. And if your assumptions about the developers are correct they may not be fully aware of these conventions.

There may be references in the registry or in files that refer to the current installation location. Theses references can be far from obvious.

There are no executables.

In case you don't know, more than EXE can be executable. COM, BAT, CMD, VBS, VBE, BAS, JS, PY, JSE, WSF, WSH, PSC1 etc.
Big list of Executables

Why not copy the folder from PF86 to a folder of your choice, and see if you can use it from the new location?

Is it listed in Apps & Features as an install?

Lugh said:

In case you don't know, more than EXE can be executable. COM, BAT, CMD, VBS, VBE, BAS, JS, PY, JSE, WSF, WSH, PSC1 etc.
Big list of Executables

Why not copy the folder from PF86 to a folder of your choice, and see if you can use it from the new location?

Is it listed in Apps & Features as an install?

It has none of those file types. After installation it is NOT listed in apps and features.

Rather than moving it after the install, I chose "Desktop" when the installer offered me an installation directory. But the default installation directory was in Program Files (x86), which is silly for a package of spreadsheets. The publisher of this package should distribute it as a zip file which can be unzipped anywhere, without requiring administrator permission to do so. Not as an .exe.

Distributing the application as a zip file makes works well for experienced users. But the business of creating a folder for the application, extracting the files there, and creating a shortcut to the executable can be quite confusing for a novice user. Using an installer makes things simpler. And there may be other reasons known only to the developer.