text/microsoft-resx 2.0 System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 The state of the current PowerShell instance is not valid for this operation. The operation cannot be performed because a command has already been started. Wait for the command to complete, or stop it, and then try the operation again. No commands are specified. The PowerShell instance is not in the correct state for creating a nested PowerShell instance. Nested PowerShell instances should only be created in a running PowerShell instance. Cannot perform operation because the runspace is not in the '{0}' state. Current state of runspace is '{1}'. The runspace pool specified is not in an opened state. This operation is currently not supported in the remoting scenario. Nested PowerShell instances cannot be invoked asynchronously. Use the Invoke method. The {0} object was not created by calling {1} on this PowerShell instance. When the runspace is set to reuse a thread, the apartment state in the invocation settings must match the runspace. When the runspace is set to use the current thread, the apartment state in the invocation settings must match that of the current thread. A command is required to add a parameter. A command must be added to the PowerShell instance before adding a parameter. The keys in the dictionary must be strings. There is no Runspace available to run commands in this thread. You can provide one in the DefaultRunspace property of the System.Management.Automation.Runspaces.Runspace type. The command you attempted to invoke was: {0} GetJobForCommand is not supported when there is more than one command in the PowerShell instance. The Command property of a PowerShell object cannot be empty. A job cannot be started when it is already running. Support for interactive jobs is not available A job object can be used only once. A job object cannot be reused. This PowerShell object cannot be connected because it is not associated with a remote runspace or runspace pool. The running command has been disconnected but is still running on the remote server. Reconnect to get command operation status and output data. The operation cannot be performed because the current PowerShell session is in the Disconnected state. Connect this PowerShell session, and then either wait for the command to finish, or stop the command. The operation cannot be performed because the current PowerShell session is in the Disconnected state. Connect this PowerShell session, and then try again. The connection attempt to the remote command failed. PSChildJobProxy does not support control methods. PSChildJobProxy is the name of a class and should not be localized The operation cannot be performed because a command is currently stopping. Wait for the command to complete stopping, and then try the operation again. There is no Runspace available to run commands in this thread. You can provide one in the DefaultRunspace property of the System.Management.Automation.Runspaces.Runspace type. The current PowerShell instance contains no command to invoke. A PowerShell object cannot be created that uses the current runspace because there is no current runspace available. The current runspace might be starting, such as when it is created with an Initial Session State.