Event ID 2025 — Psxrun Availability

Event ID 2025 — Psxrun Availability

Updated: November 14, 2007

Applies To: Windows Server 2008

Subsystem for UNIX-based Applications (SUA) Psxrun Availability indicates the ability of the Psxrun utility to start and run SUA processes.

Problems that can occur with Psxrun Availability include API call failures, incorrect path names or command line parameters, and low virtual memory.

Event Details

Product: Windows Subsystem for UNIX-based Applications
ID: 2025
Source: Microsoft-Windows-SUA-Psxrun
Version: 6.0
Symbolic Name: GFPN_FAILED
Message: GetFullPathName failed for “%1”: %2

Check CurrentDirectory path length

Psxrun attempted to obtain CurrentDirectory information during initialization, but the character length of the path returned for the current directory was greater than the maximum character length allowed in the environment variable PATH_MAX. To solve this problem, run psxrun from another directory that has a path length of fewer characters than the maximum allowed.


Because multiple instances of Psxrun can be running at once, it is best to verify Psxrun in Windows Task Manager not by checking on a particular instance of Psxrun, but by verifying that the specific POSIX process or application launched by using Psxrun is running.

To verify that Psxrun is running:

  1. Open Windows Task Manager by pressing CTRL+ALT+DEL, and then clicking Start Task Manager.
  2. On the Processes tab, select the Show processes from all users check box.
  3. Verify that a specific POSIX process you have started by using Subsystem for UNIX-based Applications is running.

If the POSIX application or process that has been launched by using Psxrun is indicated as running in Task Manager, then Psxrun is fully available. If the process is not running, critical errors are preventing Psxrun from being available.

Related Management Information

Psxrun Availability

Subsystem for UNIX-based Applications


Leave a Reply