Starting with version 6.11, in toolstar®testWIN an automated check of Windows device statuses is available within the automation system. This allows you to easily check—in the background—whether Windows has detected any issues in Device Manager, without having to open the program and perform a manual check each time. All issues detected by Windows (covering a total of 58 possible error scenarios) are automatically identified and displayed in a list for each device.
The options allow you to choose how the results are displayed: either by device type or by connection. This means the display is organized either by type—similar to the Windows Device Manager—or sorted according to the device's connection type.
List of all possible problems and codes
| Code | Description |
|---|---|
| Code 0 | Ready / Error-free: The device is correctly configured and functioning properly. |
| Code 1 | Not configured: The device is not configured, or no driver is installed. |
| Code 2 | Driver/Devloader failed: The device driver could not be loaded. |
| Code 3 | Insufficient memory: The driver could not be loaded due to insufficient RAM. |
| Code 4 | Invalid entry type: The driver or registry entry is corrupt or incorrect. |
| Code 5 | Resource arbitrator missing: The device is requesting a resource that no allocator can manage. |
| Code 6 | Startup configuration conflict: Required resources conflict with the startup resources. |
| Code 7 | Filter driver error: A filter driver for the device could not be loaded. |
| Code 8 | Devloader not found: The driver system file is missing or corrupt. |
| Code 9 | Invalid data: The hardware ID in the registry is invalid or corrupt. |
| Code 10 | Startup failed: The device cannot be started (often due to outdated or defective drivers). |
| Code 11 | Device not responding: The device reported invalid/conflicting data to the PnP manager. |
| Code 12 | Resource conflict: The device cannot find available I/O resources (IRQ, DMA, ports). |
| Code 13 | Driver not verified: The device has not been verified or approved by the operating system. |
| Code 14 | Restart required: The device will only work again after the computer is restarted. |
| Code 15 | Resource Reallocation: The device is causing a conflict and must be re-enumerated. |
| Code 16 | Incomplete configuration: The device could only be partially identified and configured. |
| Code 17 | Unknown resource type: The device is requesting an invalid resource type. |
| Code 18 | Reinstallation required: The drivers for this device must be reinstalled. |
| Code 19 | Registration error: The configuration information in the registry is corrupted. |
| Code 20 | VxD Error (Obsolete): Legacy error code for VxD loading errors in Windows 95/98. |
| Code 21 | Being removed: Windows is removing this device from the system. |
| Code 22 | Device disabled: The device was manually disabled in Device Manager. |
| Code 23 | Devloader not ready: The driver loader aborted initialization. |
| Code 24 | Device not found: The device is not present, is not responding, or is disconnected. |
| Code 25 | Device moved: Windows is still setting up or re-queuing the device. |
| Code 26 | Too early in the startup process: The device cannot yet be charged at this stage. |
| Code 27 | Invalid configuration: No valid resource configuration found for the device. |
| Code 28 | Drivers not installed: No drivers have been installed for this device. |
| Code 29 | Disabled at the hardware level: The device is disabled in the BIOS/UEFI or has no power. |
| Code 30 | IRQ conflict: The device is using an interrupt that cannot be shared. |
| Code 31 | Device could not be added: Driver addition failed (broken dependency). |
| Code 32 | Driver service disabled: The service start type is set to disabled in the registry. |
| Code 33 | Resource translation failed: The bus driver could not translate resources. |
| Code 34 | No software configuration: settings must be made manually (e.g., via jumpers). |
| Code 35 | Missing from ACPI/BIOS table: The BIOS does not contain valid ACPI information for the device. |
| Code 36 | IRQ translation failed: A required PCI interrupt could not be translated. |
| Code 37 | DriverEntry failed: Initialization in the driver code failed. |
| Code 38 | Unload failed: A previous instance of the driver is still in memory. |
| Code 39 | Driver loading error: The driver file could not be loaded (missing or corrupt). |
| Code 40 | Service key invalid: Driver information in the registry could not be accessed. |
| Code 41 | No devices for legacy service: Loaded legacy driver did not create any PnP devices. |
| Code 42 | Duplicate device: An identical device is already running in the system. |
| Code 43 | Device stopped: The device was stopped because it reported errors. |
| Code 44 | Paused: An application or service has paused the device. |
| Code 45 | Not connected: The device currently exists in the registry only as a stale entry. |
| Code 46 | System is shutting down: Access not possible because Windows is currently shutting down. |
| Code 47 | Waiting for ejection: The device is ready for safe removal. |
| Code 48 | Driver blocked: The driver was blocked for security or compatibility reasons. |
| Code 49 | Registry too large: The system registry file has reached the maximum size. |
| Code 50 | Failed to set properties: Registry properties could not be applied. |
| Code 51 | Waiting for dependency: The device is waiting for another service or device to start. |
| Code 52 | Unsigned driver: The driver could not be loaded due to a missing or invalid signature. |
| Code 53 | Occupied by the debugger: The device is reserved by the kernel debugger. |
| Code 54 | Device is being reset: The device is currently performing a reset. |
| Code 55 | Console locked: The device is blocked while the user session is locked. |
| Code 56 | Class configuration required: The device requires advanced setup by the class installer. |
