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 Unable to find type [{0}]. Unable to find type [{0}]. Details: {1} Incomplete string token. The Unicode escape sequence is not valid. A valid sequence is `u{ followed by one to six hex digits and a closing '}'. The Unicode escape sequence value is out of range. The maximum value is 0x10FFFF. The Unicode escape sequence is missing the closing '}'. The Unicode escape sequence contains more than the maximum of six hex digits between braces. Cannot use [ref] with other types in a type constraint. [ref] can only be the final type in type conversion sequence. Cannot have two occurrences of [ref] in a type sequence. The numeric constant {0} is not valid. The regular expression pattern {0} is not valid. An empty ${} variable reference was found. A name is required inside the braces. Variable reference is not valid. '$' was not followed by a valid variable name character. Consider using ${} to delimit the name. You cannot call a method on a null-valued expression. Method invocation failed because [{0}] does not contain a method named '{1}'. Assignment failed because [{0}] does not contain a property '{1}()' that can be set. Unexpected token '{0}' in expression or statement. The splatting operator '@' cannot be used to reference variables in an expression. '@{0}' can be used only as an argument to a command. To reference variables in an expression use '${0}'. Parameter '{0}' is not valid Missing expression after '{0}' in pipeline element. The expression after '{0}' in a pipeline element produced an object that was not valid. It must result in a command name, a script block, or a CommandInfo object. Parameter {0} requires an argument. Parameter {0} cannot have an argument. Duplicate parameter ${0} in parameter list. Missing argument in parameter list. Splatted variables like '@{0}' cannot be part of a comma-separated list of arguments. Missing file specification after redirection operator. The '{0}' operator is reserved for future use. Redirection to '{0}' failed: {1} Expressions are only allowed as the first element of a pipeline. An empty pipe element is not allowed. The assignment expression is not valid. The input to an assignment operator must be an object that is able to accept assignments, such as a variable or a property. A hash table can only be added to another hash table. The right operand of '-is' must be a type. The right operand of '-as' must be a type. Error formatting a string: {0}. The argument to operator '{0}' is not valid: {1}. The '{0}' operator failed: {1}. The {0} operator allows only two elements to follow it, not {1}. You must provide a value expression following the '{0}' operator. The '{0}' operator works only on variables or on properties. The {0} attribute can be specified only on a hash literal node. Array index expression is missing or not valid. Missing property name after reference operator. The property '{0}' cannot be found on this object. Verify that the property exists and can be set. The property '{0}' cannot be found on this object. Verify that the property exists. Index operation failed; the array index evaluated to null. Cannot index into a null array. Unable to index into an object of type "{0}". Unable to index into an object of type "{0}" with the ByRef-like return type "{1}". ByRef-like types are not supported in PowerShell. The array has too many dimensions: {0}. The number of dimensions for an array must be less than or equal to 32. Array assignment to [{0}] failed because assignment to slices is not supported. You cannot index into a {0} dimensional array with index [{1}]. Array assignment failed because index '{0}' was out of range. Missing expression after '{0}'. ${{variable}} reference starting is missing the closing '}}'. $(subexpression) is missing the closing ')'. Internal error - unexpected unary operator {0}. [ref] cannot be applied to a variable that does not exist. The variable '${0}' cannot be retrieved because it has not been set. Duplicate keys '{0}' are not allowed in hash literals. Duplicate named arguments '{0}' are not allowed. The '{0}' operator works only on numbers. The operand is a '{1}'. An expression was expected after '('. Missing '=' operator after key in hash literal. Missing statement after '=' in hash literal. Missing statement after '=' in named argument. Missing ';' or end-of-line in property definition. Missing expression after unary operator '{0}'. Missing condition in if statement after '{0} ('. Missing statement block after {0} ( condition ). Missing statement block after 'else' keyword. The file could not be read: {0}. The current provider ({0}) cannot open a file. No files matching '{0}' were found. The path cannot be processed because it resolved to more than one file; only one file at a time can be processed. The {0} '-{1}' parameter is reserved for future use. Cannot process the 'switch' statement because of a missing file name argument to the -file option. The file name argument to -file in the switch statement is not valid. The parameter {0} is not valid for the switch statement. The parameter {0} is not valid for the foreach statement. A switch statement must have one of the following: '-file file_name' or '( expression )'. Missing condition in switch statement clause. A switch statement can have only one default clause. Missing statement block in switch statement clause. Missing expression in foreach loop. The correct form is: foreach ($a in $b) {...} Missing statement body in foreach loop. The correct form is: foreach ($a in $b) {...} The param statement cannot be used if arguments were specified in the function declaration. The operation '[{0}] {1} [{2}]' is not defined. An error occurred while enumerating through a collection: {0}. An unhandled COM interop exception occurred: {0} A COM object was accessed after it was already released: {0} Processing was stopped because the script is too complex. The syntax is not supported by this runspace. This can occur if the runspace is in no-language mode. The combination of options with the -split operator is not valid. Options are not allowed on the -split operator with a predicate. The token '{0}' is not a valid statement separator in this version. The '{0}' keyword is not supported in this version of the language. Missing expression after '{0}' in loop. Missing statement body in {0} loop. The 'trap' statement was incomplete. A trap statement requires a body. Incomplete 'try' statement. A try statement requires a body. Parameter declarations are a comma-separated list of variable names with optional initializer expressions. Missing function body in function declaration. Script command clause '{0}' has already been defined. unexpected token '{0}', expected 'begin', 'process', 'end', 'clean', or 'dynamicparam'. Missing closing '}' in statement block or type definition. Missing ')' in method call. Missing ']' after array index expression. Missing closing ')' in expression. Missing closing ')' in subexpression. Missing '(' after '{0}' in if statement. Missing ')' after expression in switch statement. Missing '{' in switch statement. Missing variable name after foreach. The correct form is: foreach ($a in $b) {...} Missing 'in' after variable in foreach loop. The correct form is: foreach ($a in $b) {...} Missing closing ')' after expression part of foreach loop. The correct form is: foreach ($a in $b) {...} Missing opening '(' after keyword '{0}'. Missing while or until keyword in do loop. Missing closing ')' after expression in '{0}' statement. Missing name after {0} keyword. Missing ')' in function parameter list. An error '{0}' occurred while processing this script. Text describing this error could not be loaded. An error '{0}' occurred while processing this script. Text describing this error could not be loaded due to error '{1}'. There is no Runspace available to run scripts in this thread. You can provide one in the DefaultRunspace property of the System.Management.Automation.Runspaces.Runspace type. The script block you attempted to invoke was: {0} Unrecognized token in source text. Action to take for this exception: &Continue Report the error then continue with the next script statement. S&ilently Continue Do not report this error, just continue with the next script statement. &Break Do not continue processing, throw the exception instead. &Suspend Pause the current pipeline and return to the command prompt. Type exit to resume operation when you are done. Cannot run a document in the middle of a pipeline: {0}. Program '{0}' failed to run: {1}{2}. Cannot use '&' to invoke in the context of binary module '{0}'. Specify a non-binary module after the '&' and try the operation again. Cannot use '&' to invoke in the context of module '{0}' because it is not imported. Import the module '{0}' and try the operation again. Executable script code found in signature block. line At {0}:{1} char:{2} + {3} {0,4}+ {1} ! SET ${0} = '{1}'. ! CALL function '{0}' ! CALL function '{0}' (defined in file '{1}') ! CALL method '{0}' The string is missing the terminator: {0}. White space is not allowed before the string terminator. Missing ] at end of type token. Use `{ instead of { in variable names. The Data section is missing its statement block. The "{0}" parameter of the Data section is not valid. The valid Data section parameter is SupportedCommand. Array references are not allowed in restricted language mode or a Data section. Assignment statements are not allowed in restricted language mode or a Data section. Redirection is not allowed in restricted language mode or a Data section. The Do and While statements are not allowed in restricted language mode or a Data section. Expandable strings are not allowed in restricted language mode or a Data section. The '{0}' operator is not allowed in restricted language mode or a Data section. The Trap statement is not allowed in restricted language mode or a Data section. The Try statement is not allowed in restricted language mode or a Data section. Flow control statements such as Break, Continue, Return, Exit, and Throw are not allowed in restricted language mode or a Data section. Foreach statements are not allowed in restricted language mode or a Data section. For and While statements are not allowed in restricted language mode or a Data section. Function declarations are not allowed in restricted language mode or a Data section. Method calls are not allowed in restricted language mode or a Data section. Parameter declarations are not allowed in restricted language mode or a Data section. Property references are not allowed in restricted language mode or a Data section. Script block literals are not allowed in restricted language mode or a Data section. The switch statement is not allowed in restricted language mode or a Data section. A variable that cannot be referenced in restricted language mode or a Data section is being referenced. Variables that can be referenced include the following: {0}. The command '{0}' is not allowed in restricted language mode or a Data section. The data statement is not allowed in restricted language mode or another Data section. The SupportedCommand parameter of the Data section is missing a value. Supply a cmdlet or function name to the parameter. A Begin statement block, Process statement block, or parameter statement is not allowed in a Data section. String multiplication results with more than "{0}" characters are not allowed in restricted language mode or a Data section. Array multiplication resulting in more than {0} elements is not allowed in restricted language mode or a Data section. Dot sourcing is not allowed in restricted language mode or a Data section. Attribute argument must be a constant or a script block. Cannot find the type for custom attribute '{0}'. Make sure that the assembly that contains this type is loaded. Property '{0}' cannot be found for type '{1}'. Unexpected attribute '{0}'. Missing ] at end of attribute or type literal. The function or command was called as if it were a method. Parameters should be separated by spaces. For information about parameters, see the about_Parameters Help topic. The Try statement is missing its statement block. The Try statement is missing its Catch or Finally block. The Catch block is missing its statement block. The Finally block is missing its statement block. Exception type {0} is already handled by a previous handler. Catch block must be the last catch block. Missing type literal. The terminator '#>' is missing from the multiline comment. No characters are allowed after a here-string header but before the end of the line. Parser errors were detected. Missing statement block after '{0}'. Unexpected type [{0}] was found in the parameter statement. Unexpected type [{0}] was found before statement. A null key is not allowed in a hash literal. Attributes are not allowed in restricted language mode or a Data section. The type {0} is not allowed in restricted language mode or a Data section. '{0}' is a ReadOnly property. The type name is missing the assembly name specification. Flow of control cannot leave a Finally block. Unrecoverable error in PowerShell. An AST cannot be used as the child of more than one AST. To use this AST in another AST, call the Copy() method and use its result. Expression is not allowed in a Using expression. A Using variable cannot be retrieved. A Using variable can be used only with Invoke-Command, Start-Job, or InlineScript in the script workflow. When it is used with Invoke-Command, the Using variable is valid only if the script block is invoked on a remote computer. Variable reference is not valid. The variable name is missing. Variable reference is not valid. ':' was not followed by a valid variable name character. Consider using ${} to delimit the name. Not all parse errors were reported. Correct the reported errors and try again. Missing type name after '['. * stream debug stream error stream output stream The {0} for this command is already redirected. verbose stream warning stream Missing statement body after keyword '{0}'. Parallel and sequence blocks are not allowed in restricted language mode or a Data section. Unexpected keyword '{0}'. [void] cannot be used as a parameter type, or on the left side of an assignment. The method cannot be invoked. Cannot convert hashtable to an object of the following type: {0}. Hashtable-to-Object conversion is not supported in restricted language mode or a Data section. Argument must be constant. The argument for the {0} parameter is not valid. Specify a valid string argument. The argument for the Module parameter is not valid. {0} The argument for the Version parameter is not valid. Specify a valid PowerShell version, in the format major.minor version. The argument for the {0} parameter is not valid. Specify a valid PowerShell edition. The argument for the {0} parameter contains duplicate values. Do not specify duplicate PowerShell edition values. Wildcard characters are not supported for module names. Cannot invoke method. Method invocation is supported only on core types in this language mode. Cannot set property. Property setting is supported only on core types in this language mode. An attribute name for resource '{0}' was found that is not valid. An attribute name must be a simple string, and cannot contain variables or expressions. Replace '{1}' with a simple string. The member '{0}' is not valid. Valid members are '{1}'. Missing '{' in object definition. A required name or expression was missing. The schema file {0} was not found. Verify that any modules specified in a configuration statement contain a schema.mof file, and then try running the script again. Cannot define data section. Definition of additional supported commands is not supported in this language mode. Missing '{' in configuration statement. Exception parsing MOF file '{0}':{1}. The name for the configuration is missing. Provide the missing name as a simple name, string, or string-valued expression. Could not find the module '{0}'. Multiple versions of the module '{0}' were found. You can run 'Get-Module -ListAvailable -FullyQualifiedName {0}' to see available versions on the system, and then use the fully qualified name '@{{ModuleName="{0}"; RequiredVersion="Version"}}'. The ThrottleLimit parameter of the foreach statement is missing a value. Supply a throttle limit to the parameter. 'ThrottleLimit' must not be localized. The ThrottleLimit parameter is only supported on foreach statements that use the Parallel parameter. 'ThrottleLimit' and 'Parallel' must not be localized. The configuration block results were null or empty. Verify that configurations were defined in the block. The '{0}' resource can only be used once per configuration, and therefore cannot have a name. Remove '{1}', and then run the script again. There is an incomplete property assignment block in the instance definition. Missing '=' operator after key in property assignment. Duplicate property assignments are not allowed in an instance definition. A second CIM class definition for '{0}' was found while processing the schema file '{1}'. This class was already defined in the file(s) '{2}'. Remove the redundant definition, and then try again. Resource name '{0}' is already being used by another Resource or Configuration. The class name '{0}' does not match '{1}', the name of the file in which it is defined. Rename either the file name to match the class name or vice versa A duplicate resource identifier '{0}' was found while processing the specification for node '{1}'. Change the name of this resource so that it is unique within the node specification. There is no whitespace between the name and the scriptblock in dynamic keyword '{0}' body statement. The key property for an entry in the dictionary of functions to define cannot be empty because the key property is used as the function name. Specify a non-empty string as the value of the key property, and then try the operation again. The format of the resource reference '{0}' in the Requires list for resource '{1}' is not valid. A required resource name should be in the format '[<typename>]<name>', with alphanumeric characters, spaces, '_', '-', '.' and '\'. The capitalized word Requires should not be localized. The words <typename> and <name> should be localized but the <> characters must be preserved. The format of the resource reference '{0}' in the exclusive list for resource '{1}' is not valid. An exclusive resource name should be in the format '<typename>\<name>', with no spaces. The PartialConfiguration '{0}' is set to pull mode which requires a ConfigurationSource property. A null entry was found in the list of variable entries to create in the script block scope. Remove the entry at index {0}, or replace it with a non-null entry, and then try again. The script block that defines function '{0}' cannot be null or empty. Provide a non-empty script block in the function definition dictionary, and then try the operation again. The syntax of the Import-DscResource dynamic keyword is: Import-DscResource [-Name <ResourceName(s)>] [-ModuleName <ModuleName(s)>] [-ModuleVersion <ModuleVersion>]. Name : Names of one or more resources to import. ModuleName : Module names or ModuleSpecification objects of one or more modules to import. ModuleVersion : Version of module to import. If used, ModuleName must represent only one module by name. Import-DscResource dynamic keyword supports only one module when Name parameter is specified. Positional parameters are not supported for the Import-DscResource dynamic keyword. The syntax of Import-DscResource dynamic keyword is: "Import-DscResource [-Name <ResourceName(s)>] [-ModuleName <ModuleName(s)>] [-ModuleVersion <ModuleVersion>] Unable to load resource '{0}': Resource not found. Configuration keyword is not allowed in constrainedLanguage mode. The configuration name '{0}' is not valid. Standard names may only contain letters (a-z, A-Z), numbers (0-9), period (.), hyphen (-) and underscore (_). The name may not be null or empty, and should start with a letter. Configuration only supports the End block in its body. Begin, Process and DynamicParam blocks are not allowed in a configuration. Cim deserializer threw an error when deserializing file {0}. '{0}' is not a valid value for property '{1}' on class '{2}'. Please change the value to one of the following strings: {3}. At least one of the values '{0}' is not supported or valid for property '{1}' on class '{2}'. Please specify only supported values: {3}. Resource '{0}' requires that a value of type '{1}' be provided for property '{2}'. Property '{0}' of Resource '{1}' has value '{2}' which is not between valid range '{3}' and '{4}'. Failed to load the PowerShell data file '{0}' with the following error: {1} Cannot resolve the path '{0}' to a single .psd1 file. The PowerShell data file '{0}' is invalid since it cannot be evaluated into a Hashtable object. Configuration is not supported on WinPE. If the expression passed to the Where() operator is null then you must specify a non-Default value for the selection mode argument. Please change the value of the mode argument to a value other than Default and try running your script again. The generic collection type [{0}] passed to ForEach() has too many type arguments. Please change the specified type to be a generic collection with only one type argument then try running your script again. Unable to convert input to the target type [{0}] passed to the ForEach() operator. Please check the specified type and try running your script again. Script block with a 'clean' block is not supported by the 'ForEach' method. The 'numberToReturn' value provided to the third argument of the Where() operator must be greater than zero. Please correct the argument's value and try running your script again. Redirection only allows another stream to be merged with the output stream. Please correct the redirection operation to merge into the output stream then try running your script again. The ForEach() operator could not find a member '{0}' on the target object. Please verify that the named member exists and then try running your script again. The '{0}' keyword is not supported in this version of the language. The '{0}' property is not supported in this version of the language. Duplicate '{0}' qualifier Modifier '{0}' cannot be combined with '{1}' Missing using directive Missing namespace alias Missing '=' operator Missing using name Variable is not assigned in the method. Missing a property name or method definition. The member '{0}' is already defined. Only one type may be specified on class members. Error during creation of type "{0}". Error message: {1} Cannot convert the value to type "{0}". Property '{0}' cannot be found for attribute '{1}'. Specify one of the following properties: {2}. Attribute '{0}' is not valid on this declaration. It is valid on '{1}' declarations only. Attribute argument must be a constant. Undefined DSC resource '{0}'. Use Import-DSCResource to import the resource. Exception occurred when pre-parsing dynamic keyword '{0}' with details '{1}'. Exception occurred when post-parsing dynamic keyword '{0}' with details '{1}'. Workflow is not supported in PowerShell 6+. Meta Configuration resource {0} is not allowed in the regular configuration. Use meta configuration resources in a configuration with [DscLocalConfigurationManager()] attribute. Regular DSC resource {0} is not allowed in the meta configuration. There is no Runspace available to get and run the SteppablePipeline in this thread. You can provide one in the DefaultRunspace property of the System.Management.Automation.Runspaces.Runspace type. The script block you attempted to get SteppablePipeline from was: {0} There are valid conversions from {0} to {1}. Cannot perform call. Cannot retrieve type information. Could not get dispatch ID for {0} (error: {1}). Cannot find an overload for "{0}" and the argument count: "{1}" Error while invoking {0}. Could not find member. Error while invoking {0}. Named arguments are not supported. Error while invoking {0}. Overflow detected. Error while invoking {0}. A required parameter was omitted. Exception setting "{0}": Cannot convert the "{1}" value of type "{2}" to type "{3}". IDispatch::GetIDsOfNames behaved unexpectedly for {0}. Marshal.SetComObjectData failed. Unexpected VarEnum {0}. Attempting to pass an event handler of an unsupported type. Configuration keyword is not supported in PowerShell 6+. Not all code path returns value within method. Invalid return statement within void method. Invalid return statement within non-void method. Missing '{0}' body in '{0}' declaration. Cannot define enum because of a cycle in the initialization expressions. Enumerator value is either too large or too small for {0}. Enumerator value must be a constant value. Exception occurred when performing semantic check for dynamic keyword '{0}' with details '{1}'. The '{0}' property with type '{1}' of DSC resource class '{2}' is not supported. Missing '(' in class method parameter list. A named block is not allowed in a class method. A param block is not allowed in a class method. Cannot inherit from sealed class '{0}'. Type name expected. '{0}' is not a valid underlying type for enums. Expected a builtin integral type (one of byte, sbyte, short, ushort, int, uint, long or ulong) '{0}': Interface name expected. Base class '{0}' does not contain a parameterless constructor. Invalid base type '{0}'. Base type cannot be an array. Invalid base type '{0}'. Base type cannot be a generic with unspecified parameters. Missing 'base' after ':' in a base class constructor call. A constructor cannot specify a return type. The DSC resource '{0}' has no default constructor. The DSC resource '{0}' is missing a Get method that returns [{0}] and accepts no parameters. The DSC resource '{0}' must have at least one key property (using the syntax [DscProperty(Key)].) The DSC resource '{0}' is missing a Set method that returns [void] and accepts no parameters. The DSC resource '{0}' is missing a Test method that returns [bool] and accepts no parameters. A static constructor cannot have any parameters. The type '{0}' is not allowed on a property. The type '{0}' is not allowed on a parameter. Cannot access the non-static member '{0}' in a static method or initializer of a static property. Failed to parse module script file '{0}' with error '{1}'. Cannot run a document in PowerShell: {0}. Multiple type constraints are not allowed on a method parameter. This script contains malicious content and has been blocked by your antivirus software. '{0}' cannot be specified in LocalConfigurationManager resource. Please switch to Settings instead or use only following values: {1}. '{0}' is defined in a generic type. Type name '{0}' is ambiguous, it could be '{1}' or '{2}'. A 'using' statement must appear before any other statements in a script. This syntax of the 'using' statement is not supported. The specified namespace in the 'using' statement contains invalid characters. information stream Invalid key property. The key property must be of [string], signed/unsigned integer, or Enum types. Invalid Get method. Get method must return [{0}] and accepts no parameters. Cannot load assembly '{0}'. Cannot use assembly with an UNC path: '{0}'. Cannot use assembly with uri schema '{0}'. Missing a newline or semicolon. Cannot assign property, use '{0}{1}'. '{0}' is not a valid value for using name. Cannot assign property, use '{0}{1}'. DebugMode should only have one value. Label '{0}' not found inside the method. Failed to convert the value of CimProperty {0} to the property value of class {1}. Property {0} of PowerShell class {1} is not declared as array type, but defined in its configuration instance as instance array type. Failed to create an object of PowerShell class {0}. The hashtable supplied to the Desired State Configuration resource {0} is not valid. The key or value cannot be null or empty. The username supplied to the Desired State Configuration resource {0} is not valid. The username cannot be null or empty. The username supplied to the Desired State Configuration resource {0} is not valid. The username cannot be null or empty. Property {0} is not declared in PowerShell class {1}, but defined in its configuration instance. PartialConfiguration '{0}' has a Refresh Mode set to Disabled which is not a valid mode for Partial Configurations. Use Pull or Push refresh mode. Cannot create type. Only core types are supported in this language mode. Import-DscResource cannot be specified inside of Node context $PSCulture, $PSUICulture, $true, $false, $null Cannot assign automatic variable '{0}' with type '{1}' Conflict in using PsDscRunAsCredential for Resource {0} because it already specifies PsDscRunAsCredential value. We can only use one PsDscRunAsCredential for the composite resource. Unable to find DSC schema store at "{0}". Please ensure PSDesiredStateConfiguration v3 module is installed. {0} This script contains content that has been flagged as suspicious through a policy setting and has been blocked with error code {0}. Contact your administrator for more information. Cannot use '&' or '.' operators to invoke a module scope command across language boundaries. Class keyword is not allowed in ConstrainedLanguage mode. Missing ':' in the ternary expression. A pipeline chain operator must be followed by a pipeline. Background operators can only be used at the end of a pipeline chain. Directly invoking the 'clean' block of a script block is not supported. Parser Configuration Keyword The Configuration keyword will not be allowed in Constrained Language mode for untrusted script. Parser Class Keyword The Class keyword will not be allowed in Constrained Language mode for untrusted script. Parser Data Section SupportedCommand The Data Section that includes the SupportedCommand parameter would be disallowed in Constrained Language mode for untrusted script. Module Scope Call Operator The module scope call operator will be denied in Constrained Language mode. ForEach Keyword Method Invocation The ForEach keyword will fail '{0}' iteration item method invocation when run in Constrained Language mode. Expression Evaluation May Fail Creating a steppable pipeline 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. Configuration keyword is not supported on ARM64 processors.