Comments

Answers

0

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..

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.