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 An error of type "{0}" has occurred. Out of process memory. Remote PSSession enumeration with -ComputerName is only supported on Windows and not "{0}". Pipeline ID "{0}" does not match the InstanceId of the pipeline that is currently running, "{1}". Pipeline Id "{0}" was not found on the server. The remote pipeline has been stopped. The session already exists. Trying to create the session again with the same InstanceId {0} is not allowed. The specified client session InstanceId "{0}" does not match the existing session's InstanceId "{1}". Opening the remote session failed. The specified remote session with a client InstanceId of "{0}" cannot be found. Prompt response has a prompt id "{0}" that cannot be found. Remote host call to "{0}" failed. Remote host method {0} is not implemented. Remote host method data encoding is not supported for type {0}. Remote host method data decoding is not supported for type {0}. Creation of nested pipelines is not supported. Relative URIs are not supported in the creation of remote sessions. A failure occurred while decoding data from the remote host. There was an error in the network data. Only administrators can override the Thread Options remotely. PowerShell Credential Request: {0} Warning: A script or application on the remote computer {0} is requesting your credentials. Enter your credentials only if you trust the remote computer and the application or script that is requesting them. {1} A script or application on the remote computer {0} is asking to read a line securely. Enter sensitive information, such as your credentials, only if you trust the remote computer and the application or script that is requesting it. A script or application on the remote computer {0} is attempting to read the buffer contents on the PowerShell host. For security reasons, this is not allowed; the call has been suppressed. A script or application on the remote computer {0} is sending a prompt request. When you are prompted, enter sensitive information, such as credentials or passwords, only if you trust the remote computer and the application or script that is requesting the data. Received unsupported remote host call: {0}. Received remoting data with unsupported action: {0}. Received remoting data with unsupported data type: {0}. Remoting data is missing the destination property. Remoting data is missing target interface property. Remoting data is missing Session InstanceId property. Remoting data is missing RemotingDataType property. Remoting data is missing CallId property. Remoting data is missing MethodName property. The IsStartFragment flag for the first fragment is not set. Remoting data is missing {0} property. Unexpected ObjectId received. This can happen if the fragments are not properly constructed by the remote computer, or the data might have been corrupted or changed. ObjectId cannot be less than or equal to 0. This can happen if the fragments are not properly constructed by the remote computer, or the data has been changed by unauthorized users. The FragmentIDs of the same object must be in sequence, incrementally changing by 1. This can happen if the fragments are not properly constructed by the remote computer. The data might also have been corrupted or changed. Remoting data is too large to be reassembled from the fragments. This can happen if the length of the data in a fragment is greater than Int32.Max. It can also occur if the data was changed by unauthorized users. The IsEndFragment flag is not set for the last fragment. This can happen if the fragments are not properly constructed by the remote computer, or if the data was corrupted or changed. Deserialized remoting data is null. Fragment blob length is out of range: {0} Error in decoding ErrorRecord. Error in decoding PipelineStateInfo. Error in decoding RunspaceStateInfo. Received unsupported RemotingTargetInterface type: {0} Remote host method was invoked on an unknown target class: {0} Remote host method was invoked without specifying a target class. Error in decoding RunspacePoolStateInfo. Error in decoding Minimum runspaces. Error in decoding Maximum runspaces. Error in decoding PowerShellStateInfo. Unexpected type of {0} property (expected {1}, got {2}). Unexpected type of remoting data (expected PSObject, got {0}). Unexpected type of encoded command (expected PSObject, got {0}). Unexpected type of encoded command parameter (expected PSObject, got {0}). An error occurred while decoding data received from the remote computer. At least {0} bytes of data are required to decode a deserialized object that is received from a remote computer. This can happen if the fragments are not properly constructed by the remote computer, or if the data was corrupted or changed. Received packet not destined for logged-on user: user = {0}, packet destination = {1}. The client negotiation timer has expired. The negotiation time-out interval is {0} milliseconds. PowerShell client does not support the {0} {1} negotiated by the server. Make sure the server is compatible with the build {2} and the protocol version {3} of PowerShell. {0}. Negotiation with the server failed. Make sure the server is compatible with the build {1} and the protocol version {2} of PowerShell. The destination server has sent a request to close the session. The server that is running PowerShell does not support the {0} {1} negotiated by the client computer. Verify that the client computer is compatible with the build {2} and the protocol version {3} of PowerShell. The server that is running PowerShell does not support connect operations on the {0} {1} that is negotiated by the client computer. Make sure the client computer is compatible with the build {2} and the protocol version {3} of PowerShell. The server that is running PowerShell cannot process the connect operation because the following information is not found or not valid: Client Capability information and Connect RunspacePool information. The server that is running PowerShell cannot process the connect operation because the server has either not been started, or it is shutting down. The server that is running PowerShell cannot process the connect operation because the server runspace pool properties did not match the client computer specified properties. {0}. Negotiation with the client failed. Make sure the client is compatible with the build {1} and the protocol version {2} of PowerShell. The server negotiation timer has expired. The negotiation time-out interval is {0} milliseconds. The client computer has sent a request to close the session. An error has occurred which PowerShell cannot handle. A remote session might have ended. The server did not respond with an encrypted session key within the specified time-out period. The client did not respond with a public key within the specified time-out period. Connection attempt failed. Attempting to close the session. PowerShell cannot close the remote session properly. The session is in an undefined state because it was not opened or connected after being disconnected. PowerShell will try to force the session to close on the local computer, but the session might not be closed on the remote computer. To close a remote session properly, first open it or connect it. Could not close the session. The session is closed. The Wait handle type "{0}" is not supported. Received data has a stream ID index of "{0}". Only a Standard Output stream ID index of "0" is supported. The Standard Input handle is not open. Native API call to WriteFile failed. Error code is {0}. Native API call to ReadFile failed. Error code is {0}. {0} is not a valid schema value. Valid values are "http" and "https". Client side receive call failed. Client side send call failed. The command handle returned from the WinRS API WSManRunShellCommand is null. The Standard Input handle cannot be set to the 'no wait' state. The system error code is {0}. The port number {0} is not within the range of valid values. The range of valid values is between 1 and 65535. The server process has exited. The call to Windows API GetStdHandle to get the Standard Input handle resulted in an error code: {0}. The call to Windows API GetStdHandle to get the Standard Output handle resulted in an error code: {0}. The call to Windows API GetStdHandle to get the Standard Error handle resulted in an error code: {0}. Connecting to remote server {0} failed. Connecting to remote server {0} failed with the following error message : {1} Closing the remote server shell instance failed with the following error message : {0} Sending data to remote server {0} failed. Sending data to remote server {0} failed with the following error message : {1} Receiving data from remote server {0} failed. Processing data from remote server {0} failed with the following error message: {1} Starting a command on the remote server failed. Starting a command on the remote server failed with the following error message : {0} Reconnecting to a command on the remote server failed with the following error message : {0} Sending data to a remote command failed. Sending data to a remote command failed with the following error message: {0} Receiving data for a remote command failed. Processing data for a remote command failed with the following error message: {0} Error with error code {0} occurred while calling method {1}. {0} For more information, see the about_Remote_Troubleshooting Help topic. Failed to disconnect from the remote server {0}. Disconnecting from the remote server failed with the following error message : {0} Reconnecting to the remote server failed. Reconnecting to the remote server {0} failed with the following error message : {1} Inter-process communication (IPC) transport does not support connect operations. An EndpointConfiguration with Id {0} does not exist on the remote server. Contact your PowerShell administrator, or the owner or creator of the endpoint configuration. The EndpointConfiguration with the {0} identifier is not in a valid initial session state on the remote computer. Contact your PowerShell administrator, or the owner or creator of the endpoint configuration. The mandatory value {0} is not specified for the {1} registry key. The mandatory value {0} is not in the correct format for registry key {1}. The expected format is 'string'. "{0}" must specify a PowerShell script file that ends with extension ".ps1". The {0} parameter is already specified in the {1} section. Contact your administrator to make sure that {0} is specified only once. Expected "{0}" and "{1}" attributes in the "{2}" element. "{0}", "{1}" must be specified in the "{2}" section to dynamically load the assembly. Unable to load the assembly "{0}" specified in the "{1}" section. Unable to load the type "{0}" specified in the "{1}" section. Both "{0}" and "{1}" must be specified in the "{2}" section. The destination "{0}" requested the connection to be redirected to "{1}". However "{1}" is not a well formatted URI. {0}Redirect location reported: {1}. Your connection has been redirected to the following URI: "{0}" {0} To automatically connect to the redirected URI, verify the "{1}" property of the session preference variable "{2}", and use the "{3}" parameter on the cmdlet. The current deserialized object size of the data received from the remote server exceeded the allowed maximum object size. The current deserialized object size is {0}. The allowed maximum object size is {1}. The total data received from the remote server exceeded the allowed maximum. The allowed maximum is {0}. The current deserialized object size of the data received from the remote client computer exceeded the allowed maximum object size. The current deserialized object size is {0}. The allowed maximum object size is {1}. The total data received from the remote client exceeded the allowed maximum. The allowed maximum is {0}. Running startup script threw an error: {0}. Specified RemoteRunspaceInfo objects have duplicates. Specified RemoteRunspaceInfo objects have exceeded the maximum allowable limit. Opening the remote session failed with an unexpected state. State {0}. Specified Uri {0} is not valid. Remote Session closed for Uri {0}. Remote session is not available for ComputerName {0}. Remote session is not available for {0}. Remote Command: {0}, associated with the job that has an ID of "{1}". A {0} cannot be specified when {1} is specified. Wildcard characters are not supported for the FilePath parameter. Specify a path without wildcard characters. The path specified as the value of the FilePath parameter is not from the FileSystem provider. The value of the FilePath parameter must be a PowerShell script file. Enter the path to a file with a .ps1 file name extension and try the command again. One or more computer names are not valid. If you are trying to pass a URI, use the -ConnectionUri parameter, or pass URI objects instead of strings. The state of the current job instance is not valid for this operation. The command cannot find the job because the job name {0} was not found. Verify the value of the Name parameter, and then try the command again. The command cannot find a job with the instance identifier {0}. Verify the value of the InstanceId parameter, and then try the command again. The command cannot find a job with the job ID {0}. Verify the value of the Id parameter and then try the command again. The command cannot remove the job with the job ID {0} and the name {1} because the job is not finished. To remove the job, first stop the job, or use the Force parameter. The command cannot remove the job with the job ID {0} because the job is not finished. To remove the job, first stop the job, or use the Force parameter. The command cannot remove the job with the job ID {0} and the instance identifier {1} because the job is not finished. To remove the job, first stop the job or use the Force parameter. Remote Command: {0}, associated with a job that has an ID of "{1}". The command cannot retrieve the jobs of the specified computers. The ComputerName parameter can be used only with jobs created by using PowerShell remoting. The Session parameter can be used only with PSRemotingJob objects. The remote session with the name {0} is not available. The remote session with the session ID {0} is not available. {0} does not contain an item with ID of {1}. The command cannot remove the job because it does not exist or because it is a child job. Child jobs can be removed only by removing the parent job. {0} is not a valid value for the parameter {1}. The value must be greater than or equal to 0. {0} cannot be specified as a proxy authentication mechanism. Only {1},{2} or {3} are supported for proxy authentication. Proxy credentials cannot be specified when using the following proxy access type: {0}. Either specify a different access type, or do not specify proxy credentials. A {0} value must be specified for session option {1}. Session must be open. The host does not support Enter-PSSession and Exit-PSSession. Multiple matches found for session ID {0}. Multiple matches found for session ID {0}. Multiple matches found for name {0}. Enter-PSSession failed because the remote session does not provide required commands. You cannot run Enter-PSSession from a nested prompt. The maximum number of WS-Man URI redirections to allow while connecting to a remote computer Default session options for new remote sessions Name of the session configuration which will be loaded on the remote computer AppName where the remote connection will be established Contains information about the remote user starting the remote session. This variable is available only from a remote session. Either "{0}" and "{1}" must both be specified, or neither must not be specified. Session configuration "{0}" was not found. Session configuration "{0}" is not a PowerShell-based shell. Session configuration "{0}" is a PowerShell-based shell. Please use PowerShell 6+ to modify it. Session configuration "{0}" is a Windows PowerShell-based shell. Please use Windows PowerShell to modify it. No session configuration matches criteria "{0}". {0} Name: {0} Name: {0}. This lets administrators remotely run PowerShell commands on this computer. Cannot delete temporary file {0}. Reason for failure: {1}. The new shell was successfully registered, but PowerShell cannot delete the temporary file {0}. Reason for failure: {1}. Cannot write the shell configuration data into the temporary file {0}. Reason for failure: {1}. Running command "{0}" to create a new session configuration. Name: {0} SDDL: {1}. This lets selected users remotely run PowerShell commands on this computer. Running command "{0}" to remove a session configuration. Running command "{0}" to get PowerShell-based session configurations. Running command "{0}" to update the session configuration properties. Name: {0} SDDL: {1} Running command "{0}" to enable the session configuration. WinRM Quick Configuration Running command "{0}" to enable remote management of this computer by using the Windows Remote Management (WinRM) service. This includes: 1. Starting or restarting (if already started) the WinRM service 2. Setting the WinRM service startup type to Automatic 3. Creating a listener to accept requests on any IP address 4. Enabling Windows Firewall inbound rule exceptions for WS-Management traffic (for http only). Do you want to continue? Performing operation "{0}". Name: {0} SDDL: {1}. This lets selected users remotely run PowerShell commands on this computer. Running command "{0}" to disable the session configuration. Name: {0} SDDL: {1}. This denies access to this session configuration for everyone. Disabling the session configurations does not undo all the changes made by the Enable-PSRemoting or Enable-PSSessionConfiguration cmdlet. You might have to manually undo the changes by following these steps: 1. Stop and disable the WinRM service. 2. Delete the listener that accepts requests on any IP address. 3. Disable the firewall exceptions for WS-Management communications. 4. Restore the value of the LocalAccountTokenFilterPolicy to 0, which restricts remote access to members of the Administrators group on the computer. Access is denied. To run this cmdlet, start PowerShell with the "Run as administrator" option. Restarting WinRM service "Restart-Service" Name: {0} The WinRM service must be restarted before a UI can be displayed for the SecurityDescriptor selection. Restart the WinRM service, and then run the following command: "{0}" Registering session configuration The session configuration "{0}" was not found. Running command "{1}" to create the "{0}" session configuration. Running this command restarts the WinRM service. "{0}" and "{1}" parameters cannot be specified together. Specify either "{0}" or "{1}" parameter. This operation might restart the WinRM service. Do you want to continue? Cannot process an element with node type "{0}". Only {1} and {2} node types are supported. Not enough data is available to process the {0} element. Expected only two attributes with the names "{0}" and "{1}" in the {2} element. Node type "{0}" is unknown in the {1} element. Only the "{2}" node type is expected in the {1} element. Expected only one attribute with the name "{0}" in the {1} element. An unknown element "{0}" was received. This can happen if the remote process closed or ended abnormally. The specified authentication mechanism "{0}" is not supported. Only "{1}" is supported for this operation. The pwsh executable cannot be found at "{0}". Note that 'Start-Job' is not supported by design in scenarios where PowerShell is being hosted in other applications. Instead, usage of the 'ThreadJob' module is recommended in such scenarios. Cannot start a 32-bit 'pwsh' process from the 64-bit 'pwsh' installation. Install the 32-bit 'pwsh' if you need to run PowerShell in a 32-bit process. The background process reported an error with the following message: {0}. The background process closed or ended abnormally: {0}. There is an error processing data from the background process. Error reported: {0}. Data for an inactive command with the identifier {0} was received. Received data: {1}. A {0} message to a session is not supported. A {0} message can be sent only to a command. The client did not receive a response for a signal operation in the specified time interval. This can happen when a command is not responding to a Stop message in a timely manner. The client did not receive a response for a Close operation in the specified time interval. This can happen when a command is not responding to a Stop message in a timely manner. An error occurred while starting the background process. Error reported: {0}. The ThrottlingJob.AddChildJob method accepts only child jobs in the NotStarted state. {StrContains="ThrottlingJob.AddChildJob"} {StrContains="NotStarted"} The ThrottlingJob.AddChildJob method cannot be called after a call to the ThrottlingJob.EndOfChildJobs method. {StrContains="ThrottlingJob.AddChildJob"} {StrContains="ThrottlingJob.EndOfChildJobs"} {0}/{1} completed {0} is a placeholder for a number of completed child jobs {1} is a placeholder for a total number of child jobs Invoking a nested pipeline requires a valid runspace. A {1} job source adapter threw an exception with the following message: {0} The value {0} is not valid for the {1} parameter. The only allowed value is 5.1. The Wait and Keep parameters cannot be used together in the same command. The WriteEvents parameter cannot be used without the Wait parameter. PowerShell remoting endpoint versioning is not supported on PowerShell 7+. The following type cannot be instantiated because its constructor is not public: {0}. The job operation (Create, Get, or Remove) could not be performed because the JobSourceAdapter type specified in the JobDefinition is not registered. Register the JobSourceAdapter type either by using an explicit call, or by calling the Import-Module cmdlet, and then specifying an assembly. The job could not be created because the JobInvocationInfo does not contain a JobDefinition. Start the JobInvocationInfo with a JobDefinition. The state of the current job instance is {0}. This state is not valid for the attempted operation. {1} Unable to connect job "{0}" to the remote server. The Disconnect-PSSession operation failed for runspace Id = {0}. The connect operation failed for session {0}. The Runspace state is {1} instead of Opened. The Disconnected PSSession query failed for computer "{0}". Cannot connect PSSession "{0}", either because it is not in the Disconnected state, or it is not available for connection. Session connect is not supported for PSSession "{0}" on target "{1}" because the target computer type is "{2}". Cannot disconnect PSSession "{0}" because it is not in the Opened state. Session disconnect is not supported for PSSession "{0}" on target "{1}" because the target computer type is "{2}". Receive-PSSession does not support PSSession "{0}" on target "{1}" because the target computer type is "{2}". The command cannot finish because the ChildJobs property contains a value that is not valid. Cannot suspend the job that has an ID of {0}. Suspending jobs is not supported for some job types. For more information about support for suspending jobs, see the Help topic for the job type. Cannot resume the job that has an ID of {0}. Resuming jobs is not supported for some job types. For more information about support for resuming jobs, see the Help topic for the job type. You cannot use the Invoke-Command cmdlet with both the AsJob and Disconnected parameters in the same command. The remote session query failed for {0} with the following error message: {1} Attempted to create a job with ID {0}. A job with this ID cannot be created now. Verify that the ID has already been assigned once on this computer. Cannot create a job with an ID of {0}; this is not a valid ID. Provide an integer for the job ID that is greater than 0. The JobIdentifier provided must not be null. Please provide a valid JobIdentifier. The Wait-Job cmdlet cannot finish working, because one or more jobs are blocked waiting for user interaction. Process interactive job output by using the Receive-Job cmdlet, and then try again. Remote session {0} could not be connected and could not be removed from the server. The client remote session object will be removed from the server, but the state of the remote session on the server is unknown. Disconnect-PSSession operation failed for runspace Id = {0} for the following reason: {1} Job "{0}" could not be connected to the server and so could not be stopped. The command cannot find a PSSession with an InstanceId value of "{0}". The command cannot find a PSSession that has the name "{0}". PowerShell remoting is not supported in the Windows Preinstallation Environment (WinPE). Changes made by {0} cannot take effect until the WinRM service is restarted. {0} may need to restart the WinRM service if a configuration using this name has recently been unregistered, certain system data structures may still be cached. In that case, a restart of WinRM may be required. All WinRM sessions connected to PowerShell session configurations, such as Microsoft.PowerShell and session configurations that are created with the Register-PSSessionConfiguration cmdlet, are disconnected. You are running in a remote session and have selected the Force option which means the WinRM service may restart.If the WinRM service restarts then this remote session will be terminated and you will need to create a new session to continue The job was null when trying to save identifiers. Specify a job to save its identifiers. A running command could not be found for this PSSession. The Microsoft .NET Framework 2.0, which is required for Windows PowerShell 2.0, is not installed. Install the .NET Framework 2.0 and retry. The remote pipeline failed. The remote pipeline failed for the following reason: {0} One or more jobs could not be resumed because the state was not valid for the operation. No client computer was specified for the remote runspace that is running a client-side method. Name: {0} SDDL: {1}. This denies remote access to this session configuration. Enabled: False. This configures the WS-Management service to deny the connection request. Enabled: True. This configures the WS-Management service to accept the connection request. Aliases to be defined when applied to a session Assemblies to load when applied to a session Author of this document Version of the CLR to use when applied to a session Company associated with this document Copyright statement for this document Description of the functionality provided by these settings Environment variables to define when applied to a session Execution policy to apply when applied to a session Format files (.ps1xml) to load when applied to a session Functions to define when applied to a session ID used to uniquely identify this document Session type defaults to apply for this session configuration. Can be 'RestrictedRemoteServer' (recommended), 'Empty', or 'Default' Directory to place session transcripts for this session configuration Whether to run this session configuration as the machine's (virtual) administrator account Language mode to apply when applied to a session. Can be 'NoLanguage' (recommended), 'RestrictedLanguage', 'ConstrainedLanguage', or 'FullLanguage' Modules to import when applied to a session Version of the PowerShell engine to use when applied to a session Processor architecture to use when applied to a session Version number of the schema used for this document Scripts to run when applied to a session Types to add when applied to a session Type files (.ps1xml) to load when applied to a session Variables to define when applied to a session User roles (security groups), and the role capabilities that should be applied to them when applied to a session Aliases to make visible when applied to a session Cmdlets to make visible when applied to a session Could not parse visible command definition for '{0}'. The visible command definition must be a hashtable with the keys of 'Name' and 'Parameters'. The value of the 'Parameters' key must be a collection of hashtables with the keys 'Name', and optionally either 'ValidateSet' or 'ValidatePattern'. Functions to make visible when applied to a session Providers to make visible when applied to a session External commands (scripts and applications) to make visible when applied to a session PSSession Configuration file path '{0}' is not valid. The path argument must resolve to a single file in the file system with a '.pssc' extension. Please fix the path specification and try again. Role Capability file path '{0}' is not valid. The path argument must resolve to a single file in the file system with a '.psrc' extension. Please fix the path specification and try again. The 'Roles' entry must be a hashtable, but was a {0}. Could not convert the value of the '{0}' role entry to a hashtable. The 'Roles' entry must be a hashtable with group names for keys, where the value associated with each key is another hashtable of session configuration properties for that role. Could not find the role capability, '{0}'. The role capability must be a file named '{1}' within a 'RoleCapabilities' directory in a module in the current module path. Cannot find module path to import. The value of the ModulesToImport parameter {0} does not exist or is not a module directory. Correct the value and try the command again. The specified configuration file '{0}' was not loaded because no valid configuration file was found. Computer {0} has been successfully disconnected. The reconnection attempt to {0} failed. Attempting to disconnect the session... Attempting to reconnect to {0} ... Network connectivity to {0} has been lost and the attempt to reconnect has failed. Please repair the network connection and reconnect using Connect-PSSession or Receive-PSSession. The network connection to {0} has been interrupted. Attempting to reconnect for up to {1} minutes... The network connection to {0} has been restored. {0} authentication requires an explicit user name and password. Specify the user name and password by using the -Credential parameter and try the command again. Basic authentication is not supported over HTTP on Unix. Cannot find a scheduled job with name {0}. {0} is the job definition name More than one job definition was found with name {0}. Try including the -DefinitionType parameter to Start-Job in order to narrow the search for the job definition to a single job source adapter. The member 'SchemaVersion' is not present in the configuration file. This member must exist and be assigned a version number of the form 'n.n.n.n'. Please add the missing member to the file {0}. The member '{0}' must be a string. Change the member to the correct type in the file {1}. The member '{0}' must be a string array. Change the member to the correct type in the file {1}. The member '{0}' must be a hashtable. Change the member to the correct type in the file {1}. The member '{0}' must be a hashtable array. Change the member to the correct type in the file {1}. The member '{0}' is not a valid key. Please change the member to a valid key in the file {1}. The member '{0}' must be a valid enumeration type "{1}". Valid enumeration values are "{2}". Change the member to the correct type in the file {3}. Error parsing configuration file {0} with the following message: {1} The -WriteJobInResults parameter cannot be used without the -Wait parameter The member '{0}' is not an absolute path {1}. Change the member to an absolute path in the file {2}. The key '{0}' in the member '{1}' is not valid. Change the key in the file {2}. The member '{0}' must contain the required key '{1}'. Add the require key to the file {2}. The key '{0}' contains an extension {1} that is not valid. Specify an extension from the following list: {{{2}}}. The key '{0}' in the member '{1}' must be a script block. Change the key to the correct type in the file {2}. The session configuration file {0} is not valid. Specify a valid session configuration file and try the command again. Network connection interrupted Attempting to reconnect to {0} ... Job {0} has been created for reconnection. Session {0} with instance ID {1} on computer {2} has been successfully disconnected. Session {0} with instance ID {1} has been created for reconnection. The SessionName parameter can only be used with the Disconnected switch parameter. A failure occurred while attempting to connect the PSSession. A failure occurred while attempting to connect to the target virtual machine. A failure occurred while attempting to connect to the target container. The PSSession is in a disconnected state and is not available for connection. The Hyper-V Module for PowerShell is not available on this machine. Failed to launch PowerShell process ({1}) inside container with id {0} with error: {2}. The Containers feature may not be enabled on this machine. Failed to terminate PowerShell process with id {0} inside container with id {1}. The input ContainerId {0} does not exist, or the corresponding container is not running. The input VMId parameter does not resolve to a single virtual machine. The input VMId {0} does not resolve to a single virtual machine. The input VMName parameter does not resolve to any virtual machine. The input VMName parameter resolves to multiple virtual machines. The input VMName {0} does not resolve to a single virtual machine. The virtual machine {0} is not in running state. The credential is invalid. The input username cannot be empty. Cannot enter session {0} because it is not in the disconnected state or is not available for connection. Retrieve the remote session using Get-PSSession -ComputerName {1} -InstanceId {2}. Cannot enter session {0} because it is not in the disconnected state or is not available for connection. Reconnect using Connect-PSSession or Receive-PSSession. Network connectivity to {0} has been lost and the reconnection attempt failed. Please repair the network connection and reconnect using Connect-PSSession or Receive-PSSession. Failed to create an instance of RemoteSessionHyperVSocketClient due to SetSocketOption failure. Failed to create an instance of RemoteSessionHyperVSocketServer. Reconnection attempt canceled. Please repair the network connection and reconnect using Connect-PSSession or Receive-PSSession. One or more jobs could not be suspended because the state was not valid for the operation. The -AutoRemoveJob parameter cannot be used without the -Wait parameter The WS-Management service cannot process the request. Cannot find the {0} session configuration in the WSMan: drive on the {1} computer. For more information, see the about_Remote_Troubleshooting Help topic. A job could not be created from the {0} specification because the provided runspace is not a local runspace. Try again using a local runspace, or specify a RunspaceMode argument. The session {0} cannot be disconnected because the specified idle time-out value {1} (seconds) is either greater than the server maximum allowed {2} (seconds), or less than the minimum allowed {3} (seconds). Specify an idle time-out value that is within the allowed range, and try again. {0} is a placeholder for the session name {1} is a placeholder for the provided idletimeout value {2} is a placeholder for the maximum allowed idletimeout value {3} is a placeholder for the minimum allowed idletimeout value The specified IdleTimeout session option {0} (seconds) is not a valid period. Specify an IdleTimeout value that is greater than or equal to the minimum allowed {1} (seconds). {0} is a placeholder for the provided idletimeout {1} is a placeholder for the minimum allowed idletimeout value The cmdlet "{0}" or the alias "{1}" cannot be present when "{2}","{3}","{4}" or "{5}" keys are specified in the session configuration file. "The transport option is not valid. Parameter "{0}" can be non-zero only if parameter "{1}" is set to true." The member '{0}' must be an array consisting of either string or hashtable elements. The member '{0}' must be an array consisting of either string or hashtable elements. Change the member to the correct type in the file {1}. Cannot retrieve the job definition '{0}' because path '{1}' refers to a '{2}' provider path. Change the path parameter to a file system path. {0} is job definition name {1} is the user provided path {2} is the path provider Cannot retrieve the job definition '{0}' because path '{1}' resolves to multiple file paths. Change the path parameter so that it is a single path. {0} is job definition name {1} is the user provided path Cannot find a scheduled job with type {0} and name {1}. {0} is the job definition type and {1} is the job definition name. Cannot find the WorkingDirectory path {0}. Cannot connect to session {0}. The session no longer exists on computer {1}. {0} is the session name that cannot be found. {1} is the computer name where the session was. The connect operation failed for session {0} with the following error message: {1} The -Force parameter cannot be used without the -Wait parameter. One or more jobs are in a suspended or disconnected state, and cannot continue without additional user input. Specify the -Force parameter to continue to a completed, failed, or stopped state. When RunAs is enabled in a PowerShell session configuration, the Windows security model cannot enforce a security boundary between different user sessions that are created by using this endpoint. Verify that the PowerShell runspace configuration is restricted to only the necessary set of cmdlets and capabilities. The job was suspended successfully by adding the Force parameter. The session configuration file {0} is not valid. Specify a valid session configuration file and try the command again. Error parsing configuration file: {1}. Register-PSSessionConfiguration : The '{0}' key in the {1}. session configuration file contains a value that is not valid. Correct the file and try the command again. Disconnected sessions are supported only when the remote computer is running PowerShell 3.0 or a later version of PowerShell. Memory usage of a cmdlet has exceeded a warning level. To avoid this situation, try one of the following: 1) Lower the rate at which CIM operations produce data (for example, by passing a low value to the ThrottleLimit parameter), 2) Increase the rate at which data is consumed by downstream cmdlets, or 3) Use the Invoke-Command cmdlet to run the whole pipeline on the server. The cmdlet that exceeded a warning level of memory usage was started by the following command line: {0} PSSession {0} was created using the EnableNetworkAccess parameter and can only be reconnected from the local computer. Cannot start job. The language mode for this session is incompatible with the system-wide language mode. Cannot create runspace. The language mode for this configuration is incompatible with the system-wide language mode. Cannot exit a nested pipeline because the pipeline is not in the nested state. The PowerShell server session is not in a valid state for running nested commands. No nested commands can be run in this session. Cannot invoke a nested command on the remote session because a nested command is already running. The remote session was unable to invoke command {0} with error: {1}. The remote session command is currently stopped in the debugger. Use the Enter-PSSession cmdlet to connect interactively to the remote session and automatically enter into the console debugger. The remote session to which you are connected does not support remote debugging. You must connect to a remote computer that is running PowerShell 4.0 or greater. Because the session state for session {0}, {1}, {2} is not equal to Open, you cannot run a command in the session. The session state is {3}. No valid sessions were specified. Ensure you provide valid sessions that are in the Opened state and are available to run commands. The session {0}, {1}, {2} is not available to run commands. The session availability is {3}. The command cannot run because the ChildJobs property is empty. The job cannot be debugged because there is no PowerShell host debugger available. Make sure you are running this command in a host that supports debugging. Cannot find job with id {0}. Cannot find job with Instance Id {0}. Cannot find job with name {0}. The job cannot be debugged because there is no host UI available. Make sure you are running this command in a PowerShell host that implements PSHostUserInterface. The job cannot be debugged because the host debugger mode is set to None or Default. The host debugger mode must be LocalScript and/or RemoteScript. Multiple jobs were found with Id {0}. Debug-Job can debug only one job at a time. Multiple jobs were found with the name {0}. Debug-Job can debug only one job at a time. The Named Pipe server listener used for process attach is already running. Enter-PSHostProcess does not support entering the same PowerShell session it is running in. Multiple processes were found with this name {0}. Use the process Id to specify a single process to enter. Cannot enter process with Id '{0}' because it has not loaded the PowerShell engine or the named-pipe listener was disabled. No process was found with Id: {0}. No process was found with Name: {0}. No named pipe was found with CustomPipeName: {0}. Cannot process the command because the pipeName specified is too long. Pipe names on this platform can be up to {0} characters long. Your pipe name '{1}' is {2} characters. The current host does not support the Enter-PSHostProcess cmdlet. "The named pipe target process has ended." "The Hyper-V socket target process has ended." {0}[Process:{1}]: {2} {0}[{1}]: {2} Unable to connect to application domain name {0} of process {1}. Error: {2}. Unable to connect to pipe with name {0}. Error: {1}. PowerShell plugin cannot process the Connect operation as required negotiation information is either missing or not complete. PowerShell plugin failed to process to connect operation. The supplied plugin context is not valid. Powershell plugin encountered a fatal error while processing {0} arguments. The supplied command context is not valid. The supplied input data is not valid. Only input data of type {0} is supported. The supplied input stream is not valid. Only {0} is supported as input stream. The supplied output stream set is not valid. Only {0} is supported as output stream. The supplied WSMAN_SENDER_DETAILS is not valid. Cannot process null WSMAN_SENDER_DETAILS. The supplied shell context is not valid. {0} NULL value is not allowed for {0} with the plugin method {1}. NULL value is not allowed for input stream and output stream sets. {0} and {1} are the supported input and output streams. NULL value is not allowed for {0} with the plugin method {1}. NULL value is not allowed for {0} with the plugin method {1}. PowerShell plugin operation is shutting down. This may happen if the hosting service or application is shutting down. PowerShell plugin does not understand the option {0}. Make sure the client is compatible with the build {1} and the protocol version {2} of PowerShell. An option with name {0} is expected from the client. Make sure the client is compatible with the build {1} and the protocol version {2} of PowerShell. <PSProtocolVersionError ServerProtocolVersion="{0}" ServerBuildVersion="{1}">Powershell plugin does not support the protocol version {2} requested by client.</PSProtocolVersionError> Powershell plugin encountered a fatal error while reporting context to WSMan service. Unable to create managed server session. Powershell plugin encountered a fatal error registering a wait handle for shutdown notification. Cannot enter Runspace because a Runspace is already pushed in this session. Cannot enter Runspace because there is no server remote debugger available. Cannot enter Runspace because it is not a remote Runspace. Remote transport error: {0} Unable to open pipe connection for PowerShell in container. Error code: {0}. Unable to create PowerShell IPC named pipe. Error code: {0}. Timeout expired before connection could be made to named pipe. WSMan Initialization failed with error code: {0}. Unable to start named pipe server while in server mode. Could not grant remote access to '{0}': '{1}'. The session configuration has been registered, but this group does not have access. To resolve this error, provide a valid group name and register the session configuration again. Could not get the session capabilities for the session configuration '{0}': this configuration was not registered with a session configuration file (.pssc), such as one created by the New-PSSessionConfigurationFile cmdlet. Could not resolve username '{0}'. Verify the username and try again. Groups associated with machine's (virtual) administrator account Cannot create or open the configuration session {0}. Enforces script input parameter validation. This is automatically enabled when MountUserDrive is specified. Creates a 'User' PSDrive in the session for use with Copy-Item when File System provider is not visible. The member '{0}' must be a boolean. Change the member to the correct type in the file {1}. The member '{0}' must be an integer. Change the member to the correct type in the file {1}. Processing the User drive threw an error {0}. Optional maximum size in bytes of user drive created with MountUserDrive parameter. Default maximum size for User drive is 50MB. Cannot find the file system provider. Group managed service account name under which the configuration will run Invalid Group Managed Service account name. Account name must be of the form 'DomainName\UserName'. Group accounts for which membership is required to use the session. Cannot parse sddl string because it contains mismatched parentheses: {0}. RequiredGroups property hashtable must contain only a single key. The RequiredGroups property is not in a name/value pair hashtable format. This must be a hashtable of the form (using PowerShell syntax): RequiredGroups = @{ Or = 'Administrators' }. Unknown key in Required Groups configuration. Required Groups hashtable can only contain 'And' and 'Or' hash keys for logical membership groupings. Unknown value in Required Groups configuration. Required Groups hashtable can only contain values that are either group names or another logical hashtable. Malformed ACE {0}. Regular ACEs must have exactly 6 sections. Cannot create a session User Drive because the current user name contains invalid file path characters. Invalid role capability key: {0}. Make sure the role capability name is spelled correctly and is a valid session configuration property. Invalid role capability key type: {0}. Role capability keys must be strings that identify a valid session configuration property. Invalid role key type: {0}. Role keys must be strings that identify a security group. Other Possible Cause: -The domain or computer name was not included with the specified credential, for example: DOMAIN\UserName or COMPUTER\UserName. Failed to start the SSH client process needed for the remoting connection with error: {0}. The specified key file {0} was not found. The SSH client session has ended with error message: {0} SSH connection attempt failed after time out: {0} seconds. SSH client process terminated before connection could be established. The provided SSHConnection hashtable is missing the required ComputerName or HostName parameter. The provided SSHConnection hashtable parameter name or element is null or empty. The provided SSHConnection hashtable parameter {0} is not supported. The provided SSHConnection hashtable contains both a ComputerName and HostName parameter. Only one can be specified. The provided SSHConnection hashtable contains both a KeyFilePath and IdentityFilePath parameter. Only one can be specified. Could not find the provided role capability file {0}. The provided role capability file {0} does not have the required .psrc extension. The SSH transport process has abruptly terminated causing this remote session to break. PowerShell 6+ does not support WOW64. The binary must match the architecture of the processor. The "{0}" executable file was not found. Verify that the WOW64 feature is installed. Unable to install plugin {0} to directory {1}. The WinRM plugin DLL {0} is missing for PowerShell. Please run Enable-PSRemoting and then retry this command. This parameter set requires WSMan, and no supported WSMan client library was found. WSMan is either not installed or unavailable for this system. Exit code: {0} Stdout: '{1}' Stderr: '{2}' Information about the process could not be read: '{0}'. Host system does not have the correct version of Hyper-V schema. HTTPS on Unix does not currently support CA or CN checks. Use the PSSessionOption -SkipCACheck and -SkipCNCheck if you are certain you trust the server you are connecting to and the network in between. PowerShell remoting has been disabled only for PowerShell 6+ configurations and does not affect Windows PowerShell remoting configurations. Run this cmdlet in Windows PowerShell to affect all PowerShell remoting configurations. PowerShell remoting has been enabled only for PowerShell 6+ configurations and does not affect Windows PowerShell remoting configurations. Run this cmdlet in Windows PowerShell to affect all PowerShell remoting configurations. Enter-PSHostProcess cmdlet is disabled because an application control policy such as 'AppLocker' or 'Windows Defender Application Control' is in enforcement. Remote debugger exception: {0}, error message: {1} Unable to create Windows PowerShell process because Windows PowerShell could not be found on this machine. The Runspace argument to Create must be a non-null RemoteRunspace object. The session configuration hash table contains an invalid key type. Keys should be string types. The session configuration file contains an unsupported configuration option: {0}. This is a remoting endpoint configuration option, that does not apply to PowerShell session state. The session configuration file contains an unknown configuration option: {0}. Expression Evaluation May Fail Creating a PowerShell object from a script block may require evaluating some expressions within the script block. The expression evaluation will silently fail and return 'null' in Constrained Language mode, unless the expression represents a constant value. Failed to get Hyper-V VM State. The value was of the type {0} but was expected to be Microsoft.HyperV.PowerShell.VMState or System.String. Hyper-V {0} sent an invalid {1} response during the connection negotiation. Negotiating a secure connection to Hyper-V failed. Make sure the Host and Guest are updated with all relevant Microsoft Updates.