As part of the package we add a SYSTEM variable to PATH. On some machines, by adding this path we have exceeded the maximum length of the Path variable allowable by Windows.

How do we resolve this issue ?

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Hey GUys,

Any ideas on here? I am also waiting for an aswer for this problem... My only fix for this is to use an Application Path in the registry or maybe use an isolation method like .local or manifest for the executables. If you have any better ideas please post it here..
Answered 10/17/2006 by: dj_xest
Fifth Degree Black Belt

Please log in to comment
Have you considered making the addition to the path in short filename format ?

e.g. instead of adding C:\Program Files\LongFolderName\EvenLongerSubFolderName

just use


This might buy you some time, but sooner or later you may need to rationalize the size of the PATH environment variable on the machines affected. Searching for and removing duplicate or obsolete entries is one step you could take.

As an aside, some repackaging software suites - you know who you are [;)] - have an annoying habit of creating duplicates in the Environment table, when snapshotting legacy applications. So make sure any future packages you develop create only the additions they really need to the PATH variable.


Answered 10/17/2006 by: spartacus
Black Belt

Please log in to comment