Configuring Creo Startup Extensions

How Creo Parametric startup files (.psf) determine which licenses and extensions are requested at launch.

Creo Parametric startup configurations determine which licenses and extensions are requested when Creo launches. These configurations are stored in PTC Startup Files (.psf) and are normally created or modified through PTC's configuration tools.

For most users, we recommend using PTC's Reconfigure workflow to modify startup extensions. CAD administrators who manage standardized Creo environments across multiple users may also choose to maintain and distribute PSF files directly.

What Is a PSF File?

A PSF (PTC Startup File) defines how a Creo application starts. Depending on the configuration, the file can contain information such as:

The Creo startup configuration name and description
The primary Creo license package
Startup extensions
License sources
Environment variables used when Creo launches

For Creo Parametric, PSF files are typically located in:

<Creo Load Point>\Parametric\bin

For example:

C:\Program Files\PTC\Creo <version>\Parametric\bin

Note: A PSF file serves a different purpose than config.pro or config.sup. Configuration files such as config.pro control Creo options and behavior, while the PSF primarily defines the Creo startup environment and licensing configuration.

Recommended Method: Configure Extensions Using PTC Reconfigure

For individual installations or when making standard Creo licensing changes, we recommend using PTC's Reconfigure workflow rather than manually modifying the PSF file.

PTC's Creo Parametric Configuration Knowledge Hub covers topics including:

Reconfiguring an existing Creo installation
Creating and modifying startup commands
Adding or removing licenses from startup configurations
Adding license servers
Configuring Creo to use specific license packages
Troubleshooting extensions that are unavailable after startup

PTC Documentation:
Creo Parametric – Configuration (CS60577)

Using the PTC workflow is generally preferred because Creo generates the appropriate startup configuration based on the licenses and extensions selected during reconfiguration.

CAD Administrators: Manually Managing PSF Files

For organizations managing Creo installations across many users, manually maintaining PSF files can be useful.

For example, a CAD administrator may want all users in a department to launch Creo with the same:

Base license configuration
Startup extensions
License server
Environment variables
Startup configuration name

Instead of configuring each workstation individually, an administrator can create and validate a standard PSF configuration and then distribute that configuration to the appropriate Creo installations.

Understanding the PSF Contents

A PSF file is a text file and can be opened with a standard text editor. Its contents define the startup environment that Creo uses when a particular startup command is selected.

The exact contents of a PSF will vary depending on the Creo version, installed products, and licensing configuration, but there are several entries that CAD administrators will commonly encounter.

DESC

The DESC entry provides the name or description of the startup configuration.

For example:

wide1800true

Using meaningful descriptions is helpful when an organization maintains multiple Creo startup configurations.

For example:

wide1800true

CREOPMA_FEATURE_NAME

The CREOPMA_FEATURE_NAME entry defines the Creo Parametric license configuration associated with the startup command. This can include the primary Creo license package as well as extensions that should be requested when Creo starts.

A PSF may contain an entry similar to:

wide1800true

The exact feature names available to your organization depend on your PTC licensing.

Because of this, administrators should not copy feature names from another organization's PSF or from an unrelated example. A better approach is to use PTC Reconfigure to create a valid startup configuration and then use the resulting PSF as the starting point for any administratively managed configuration.

PTC_D_LICENSE_FILE

Of particular importance to CAD administrators is PTC_D_LICENSE_FILE, which can be used to define the license source that a PTC application uses when communicating with FlexNet.

For a network license server, an entry may resemble:

wide1800true

This setting serves a different purpose from CREOPMA_FEATURE_NAME.

In simple terms:

CREOPMA_FEATURE_NAME helps determine which Creo license package and startup extensions are requested.
PTC_D_LICENSE_FILE helps determine where the PTC licensing system looks for the license.

This distinction can be particularly useful in managed environments. For example, a CAD administrator may distribute a standardized PSF that identifies both the appropriate startup license configuration and the organization's FlexNet server.

If your organization changes license servers, server ports, or licensing architecture, review these entries before distributing an existing PSF to users.

Other ENV Entries

A PSF can contain additional lines beginning with:

wide1800true

These lines define environment variables that are established when Creo is launched using that startup configuration.

Because PSF files can therefore influence more than just license selection, CAD administrators should compare and test the entire PSF when creating a standardized startup configuration rather than modifying only a single line.

When possible, use a PSF generated by PTC Reconfigure as the known-good baseline, make only the administrative changes required for your environment, and validate the resulting startup configuration before deploying it to other users.

Creating a Standard PSF for Your Organization

For organizations managing multiple Creo users, CAD administrators can maintain a standard PSF rather than configuring each workstation individually.

A simple approach is to:

Create the desired configuration using PTC Reconfigure.
Verify that Creo launches with the correct licenses and extensions.
Locate the generated PSF in the Creo Parametric\bin directory.
Make any required organization-specific changes.
Test and save the validated PSF as your organization's master copy.

Using a PSF generated by PTC as your starting point helps ensure the configuration is valid before making administrative changes.

Multiple Startup Configurations

You may choose to maintain multiple PSFs if different groups require different Creo extensions.

For example:

Standard — General Creo users
Piping — Users requiring piping extensions
Simulation — Users requiring simulation extensions
Manufacturing — Users requiring manufacturing extensions

If most users require the same configuration, keeping a single standard PSF will generally be easier to manage.

Distributing PSF Files

Once validated, a standard PSF can be distributed to user workstations using your organization's normal deployment method, such as endpoint-management software, scripts, installation packages, or manual deployment.

The PSF will typically be deployed to:

<Creo Load Point>\Parametric\bin

Because this location is commonly under C:\Program Files, administrative permissions may be required. Keep your master PSF in a controlled location so it can be updated and redeployed when necessary.