WinPath | cli tool to quickly and safely manage | Command Line Interface library

Short Answer: On features like TelnetClient which return a [Microsoft.Dism.Commands.AdvancedFeatureObject]:

• RestartRequired denotes whether a restart could be required after installing or enabling the feature
• RestartNeeded is used to show whether a restart is currently pending for the feature.

Long Version: The AdvancedFeatureObject type never actually gets this value set though. Instead, the property is only used by Microsoft.Dism.Commands.ImageObject which is returned from Enable/Disable-WindowsOptionalFeature. For example:

I think this can be solved with setting the environment variable within the ~/.bash_profile file and then restart your cygwin terminal window.

Add this line to your .bash_profile file:

export crntproj=$(cygpath -w $PWD)

I can't test it right now, but the goal is to set the environment variable each time you start your bash terminal.

The Windows Task Scheduler allows you to specify a user to run as (for privilege reasons), but does not give you the environment (PATH and other environment variables) that are configured for that user.

So, when running programs from the Windows Task Scheduler, it's important to not make any assumptions about what's in the environment (particularly the PATH). If my program depends on certain things in the environment, I will sometimes change my Task to be a .BAT file that first sets up the environment as needed and then launch my program from there.

Among other things, the simplest way to not rely on the path is to specify the full path to the executable you are running rather than assuming it will be found in the path somewhere. But, you also need to make sure that your executable can find any other resources it might need without any environment variables or you need to configure those environment variables for it before running.