Initialization failed because the driver device could not be created. Use the string "%2" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name.
Initial connection to Bluetooth HID device %2 failed. The device has been removed as a personal or paired device. You must ...
Initialization commands may lead to the exposure of sensitive information in the modem log. Consult your modem's instruction ...
Initialization could not complete because the minimum number of connections required to initialize the Ldap connection pool ...
Initialization failed because of a system execution failure on path %1. There is not enough memory to start the process. ...
Initialization failed because the driver device could not be created. Use the string "%2" to identify the interface for which ...
Initialization of the High Precision Event Timer failed due to a BIOS configuration problem. The operating system will use ...
Initialization of the High Precision Event Timer failed due to an interrupt configuration problem. The operating system will ...
Initialization of the High Precision Event Timer failed due to unsupported hardware. The operating system will use another ...
InitializePrintProvider failed for provider %1. This can occur because of system instability or a lack of system resources. ...