The scanning error indicates that there was an issue obtaining the printer information for this asset. When the print spooler service is not running on an asset, the WMI classes Win32_printers and Win32_PrinterDriver do not exist. Lansweeper queries these WMI classes when scanning printer data. This has a functional impact in that a scanning error is thrown, as you are seeing now.
If it is crucial for you to scan printer data, you would need to ensure that the print spooler service is running on the asset. Do keep in mind that this scanning error does not prevent Lansweeper from completing the Windows scan though. It is just missing printer data.
If printer data is not essential, you could even disable the PRINTERS and PRINTERDRIVERS scan items in the Scanning\Scanned Item Interval tab. This will disable the scanning of these WMI classes altogether and should also ensure that you no longer see the scanning error on your assets.
