MegaBites-AI/Windows-powershell

1#Copyright (c) Microsoft Corporation.2 3Vendor=Microsoft4Description=This PowerShell snap-in contains Windows Eventing and Performance Counter cmdlets.5 6NoMatchingEventsFound=No events were found that match the specified selection criteria.7NoMatchingLogsFound=There is not an event log on the {0} computer that matches "{1}".8NoMatchingProvidersFound=There is not an event provider on the {0} computer that matches "{1}".9NotALogFile=The {0} file does not appear to be a valid log file. Specify only .evtx, .etl, or .evt files as values of the Path parameter.10NotAFileSystemPath=The {0} path does not appear to be a valid log file path. Specify a valid file system path.11NoProviderFound=No provider found with name {0}.12NoEventMessage=Cannot retrieve event message text.13 14QueryTrace=Constructed structured query:\n{0}.15LogProviderOrPathNeeded=You must specify at least one Log, Provider or Path key-value pair.16KeywordLongExpected=Invalid value '{0}' specified for keyword.17DateTimeExpected=The following value is not in a valid DateTime format: {0}.18InvalidSIDFormat=The following value is not in a valid security identifier (SID) format: {0}. Enter a valid SID, such as S-1-5-32-544.19InvalidContext=The {0} Context key-value is not a valid SID or NT account name.20ProviderLogLink=The {0} provider writes events to the {1} log.21SpecifiedProvidersDontWriteToLog=The specified providers do not write events to the {0} log. This log will be ignored.22LogsAndProvidersDontOverlap=The specified providers do not write events to any of the specified logs.23ProviderMetadataUnavailable=Could not retrieve information about the {0} provider. Error: {1}.24LogInfoUnavailable=Could not retrieve information about the {0} log. Error: {1}.25SpecifyOldestForLog=The {0} event log can be read only in the forward chronological order because it is an analytical or a debug log. To see events from the {0} event log, use the Oldest parameter in the command.26SpecifyOldestForEtlEvt=The {0} event log file can be read only in the forward chronological order because it is an .etl or an .evt file. To see events from the {0} event log, use the Oldest parameter in the command.27NullNotAllowedInHashtable=A null value was encountered in the {0} hash table key. Null values are not permitted.28IncorrectEventId=Event cannot be written because there are no events defined with id {0} for the provider {1}.  Please correct the event id and try again.29IncorrectEventVersion=Event cannot be written because the specified version {0} for event {1} is not defined for the provider {2}.  Please correct the version and try again.30VersionNotSpecified=Event cannot be written because multiple events with id {0} have been defined for provider {1}.  Please provide a version for the event and try again.31ProviderNotSpecified=Provider name must be specified.32EventIdNotSpecified=A valid Event Id must be specified.33PayloadMismatch=Provided payload does not match with the template that was defined for event id {0}.  \r\nThe defined template is following: \r\n{1}34 35Timestamp=Timestamp36CookedValues=Cooked Values37CounterApiError=Internal performance counter API call failed. Error: {0:x8}.38CounterPathIsInvalid=The {0} performance counter path  is not valid.39CounterPathInvalidOrNotInFile=The {0} performance counter path is either not valid or it is not present in the following files: {1}.40CounterPathsInFilesInvalid=No valid counter paths were found in the files.41CounterSetEnumAccessDenied=Cannot retrieve information about the {0} performance counter set because access was denied.42CounterInvalidDateRange=The value of the StartTime parameter must be less than the value of the EndTime parameter.43Counter32FileLimit=You cannot import more than 32 .blg counter log files in each command.44Counter1FileLimit=You cannot import more than one comma-separated (.csv) or tab-separated (.tsv) performance counter file  in each command.45CounterNotALogFile=The {0} file does not have the expected file name extension. Specify only .blg, .csv, or .tsv files when you use the Path parameter.46CounterNoMixedLogTypes=You cannot import different types of performance log files in the same command.  Specify only one type of file in the Path parameter.47NoMatchingCounterSetsFound=Cannot find any performance counter sets on the {0} computer that match the following: {1}.48NoMatchingCounterSetsInFile=Cannot find any performance counter sets in the {0} files that match the following: {1}.49NoCounterSetsOnComputer=Could not find any performance counter sets on the {0} computer: error {1:x8}. Verify that the {0} computer exists, that it is discoverable, and that you have sufficient privileges to view performance counter data on that computer.50CounterFileExists=The {0} file already exists. To overwrite this file, use the Force parameter in the Export-Counter command.51CounterExportSampleNotInInitialSet=The {0} performance counter cannot be exported to the {1} file because it was not part of the first sample set.52CounterPathTranslationFailed=The default values for this command failed. Error: {0:x8}.53CounterContinuousOrMaxSamples=The Continuous parameter and the MaxSamples parameter cannot be used in the same command.54CounterSampleDataInvalid=The data in one of the performance counter samples is not valid. View the Status property for each PerformanceCounterSample object to make sure it contains valid data.55CounterCircularNoMaxSize=The Circular parameter will be ignored unless the MaxSize parameter is also specified.56ExportCtrWin7Required=This cmdlet can be run only on Microsoft Windows 7 and above.57FileOpenFailed=Unable to open the {0} file for writing.58FileCreateFailed=Unable to create the {0} file. Verify that the path is valid.59ExportDestPathAmbiguous=The following export destination path is ambiguous: {0}.60