Windows 7
- Failed to secure the machine account %1. Have an administrator remove the builtin\account operators full control Access Control ...
- Failed to secure the machine account %1. This operation will be retried. Have an administrator verify the builtin\account ...
- Failed to send data to remote server because list of proxy servers was exhausted without receiving a response. The error ...
- Failed to send data to remote server using the following proxy configuration: Access Type (%2); Proxy Server (%3); Proxy ...
- Failed to set dedicated IP address '{0}' because it is not one of the dedicated IP addresses on node '{1}'. Please specify ...
- Failed to set dedicated IP address '{0}' because more than one dedicated IP addresses will be changed. Please specify only ...
- Failed to set extended affinity timeout on port rule. One or more cluster nodes do not support extended affinity feature. ...
- Failed to set handling priority for port rule '{0}' because the port rule mode is not 'Multiple'. Please change the port ...
- Failed to set handling priority for port rule '{0}' because the port rule mode is not 'Single'. Please change the port rule ...
- Failed to set handling priority for port rule '{2}' to node '{1}' to '{0}' because this priority is already in use by another ...
- Failed to set handling priority for port rule with IP address '{2}' and port '{1}' on node '{3}' to '{0}'. Please enable ...
- Failed to set NLB cluster on interface '{0}' on node '{1}'. Please make sure NLB is already bound and configured on this ...
- Failed to set port rule because the port range (specified by the start and end ports) overlaps with and the range in one ...
- Failed to set port rule because the start port is larger than the end port. Please specify the correct start and end ports. ...
- Failed to set port rule load weight because the neither 'Equal' nor 'LoadWeight' were specified. Please specify the correct ...
- Failed to set port rule timeout. Extended affinity timeout is only applicable to port rules that have a filtering mode of ...
- Failed to set the correct security settings for the selected account(s) to administer this Read-only domain controller. {0} ...
- Failed to set the IP address for the port rule. The new IP address '{0}' is not one of the virtual IP addresses on cluster ...
- Failed to set timeout on port rule with IP address '{0}' and port '{1}'. Extended affinity timeout is only applicable to ...
- Failed to set virtual IP address '{0}' because it is not one of the virtual IP addresses on the NLB cluster '{1}'. Please ...
- Failed to set virtual IP address '{0}' because more than one virtual IP addresses on different clusters will be changed. ...
- Failed to set virtual IP address '{0}' because more than one virtual IP addresses will be changed. Please specify only one ...
- Failed to start language pack setup wizard because the system is pending reboot. Please restart the system and try running ...
- Failed to start session monitoring. Automatic VM hibernation based on SaveDelay parameter is disabled. Verify permissions ...
- Failed to start the Group Policy snapin. The gpedit.msc file may be missing, files with the .msc extension may not be associated ...
- Failed to start the Group Policy snapin. The gpme.msc file may be missing, files with the .msc extension may not be associated ...
- Failed to start the Scanner and Camera Installation Wizard. Please use the Add Hardware Control Panel applet to install your ...
- Failed to turn off virtual machine '%1' in order to delete it. The current instance of the virtual machine must be deleted ...
- failed to uninstall drivers when migrating dual-mode devices from mass storage class to Media Transfer Protocol (MTP). Error ...
- Failed to unlink the Group Policy Object with the Active Directory site, domain, or organizational unit. You may not have ...
- Failed to update cluster setting on cluster '{0}' because the primary IP address '{1}' is not one of the cluster virtual ...
- Failed to update Identity Management for UNIX schema entity: '%1' with the following attributes: %2 This will be retried ...
- Failed to update setting on cluster node '{0}' for cluster '{1}'. Please confirm that the node specified is part of the cluster. ...
- Failed to update the backup exclusion key with err = %d (%ws). You should have local built in administrator privilege to ...
- Failed to update the configuration with the new location of the saved state and memory files for virtual machine '%1': %3 ...
- Failed to update the configuration with the new location of virtual hard disk '%3' for snapshot '%1': %4 (%5). If you apply ...
- Failed to update the configuration with the new location of virtual hard disk '%3' for virtual machine '%1': %4 (%5). Remove ...
- Failed to update the path of the parent disk for virtual hard disk '%3' for snapshot '%1': %4 (%5). The disk may not work ...
- Failed to update the path of the parent disk for virtual hard disk '%3' for virtual machine '%1': %4 (%5). The disk may not ...
- Failed to update the snapshot configuration with the new location of the saved state and memory files for snapshot '%1': ...
- Failed to update the storage location of the snasphot files to '%5' for virtual machine '%1': %3 (%4). (Virtual machine ID ...
- Failed to upgrade printer settings for printer %1 driver %2. Error: %3. The device settings for the printer are set to those ...
- Failed to validate the new AD RMS Web application pool identity, which must be a domain user account. Open IIS manager and ...
- Failed to write to the virtual hard disk failed because the system failed to allocate a new block in the virtual hard disk. ...
- Failed transfer of zone %1 from DNS server at %2. The DNS server at %2 aborted or failed to complete transfer of the zone. ...
- Failed while deleting Data Exchange integration service item '%3' from the registry of the guest operating system: %4 (%5). ...
- Failed while deleting Data Exchange integration service item '%3' from the registry of the guest operating system: %4 (%5). ...
- Failed while setting the Data Exchange integration service item '%3' in the registry of the guest operation system: %4 (%5). ...
- failed with error (%2) because the collection already contains an object of with identifier, %3, and publisher, %4, with ...
- Failed writing the file screen audit log on volume '%1' due to a disk-full error: If the disk is full, please clean it up ...
- FailedRequestTracing module detected invalid configuration on path '%4'. Attribute "guid" in section contains invalid value ...
- FailedRequestTracing module detected invalid configuration on path '%4'. Attribute "statusCode" contains invalid value '%3'. ...
- FailedRequestTracing module detected invalid configuration on path '%4'. Trace provider or tracing area name '%3' is not ...
- FailedRequestTracing module encountered problem while reading configuration. Configuration system returned exception '%3' ...
- FailedRequestTracing module encountered problem while reading configuration. No logs will be generated until this condition ...
- FailedRequestTracing module encountered runtime error. The problem happened at least %1 times in the last %2 minutes. The ...
- FailedRequestTracing module failed to create directory '%3'. No logs will be generated until this condition is corrected. ...
- FailedRequestTracing module failed to create XSL file '%3. Friendly rendering of log files will not be available. The problem ...
- FailedRequestTracing Module failed to delete at least one log file from the directory '%3'. The problem happened at least ...
- FailedRequestTracing module failed to write buffered events to log file for the request that matched failure definition. ...
- Failover Cluster Manager could not bring the group '%1' online. The error was '%2'. For more information see the Failover ...
- Failover Cluster Manager could not change the auto start settings for group '%1'. The error was '%2'. For more information ...
- Failover Cluster Manager could not complete disk defragmentation for volume '%1'. The error was '%2'. For more information ...
- Failover Cluster Manager could not complete disk error checking for volume '%1'. The error was '%2'. For more information ...
- Failover Cluster Manager could not contact the DNS servers to resolve name '%1'. For more information see the Failover Cluster ...
- Failover Cluster Manager could not delete the group '%1'. The error was '%2'. For more information see the Failover Cluster ...
- Failover Cluster Manager could not display the dependency report. This might happen if the dependency relationship between ...
- Failover Cluster Manager could not enable the tools property page for '%1' because some information about the volumes could ...
- Failover Cluster Manager could not find function '%1' in clusapi.dll. Please make sure that the installation of the Failover ...
- Failover Cluster Manager could not find the appropriate admin extensions property page for CLSID '{%1}'. For more information ...
- Failover Cluster Manager could not find the appropriate admin extensions property page. For more information see the Failover ...
- Failover Cluster Manager could not generate a report after performing one of the tasks requested by the user. The user request ...
- Failover Cluster Manager could not get virtual machines on cluster node '%1'. The error was '%2'. For more information see ...
- Failover Cluster Manager could not impersonate user '%1' because it did not get the token required. For more information ...
- Failover Cluster Manager could not impersonate user '%1'. For more information see the Failover Cluster Manager Diagnostic ...