The model and serial are pulled from WMI (Windows Management Instrumentation) on the client machine itself. Most likely, they are stored incorrectly in WMI itself, which is not something we can fix. You can manually override the information in Lansweeper by hitting the Edit Asset button on the asset page. The warranty not being scanned may be a result of the model information being incorrect, as we do require the model for some vendors. Warranty scanning pulls information from the vendors' websites and is currently only supported for Dell, Fujitsu, HP, IBM, Lenovo and Toshiba.
As for the widget you're referring to: this pulls data from the tsysOS database table. This table stores a "conversion" of the OS code into a "readable" OS name, as well as a reference to the OS icon. At the moment, there's just one entry in this table for Windows 10, for OS code 10.0.10240. This is why you're having issues with the widget. With each new OS release, we need to add a new entry with the OS code and OS name to tsysOS.
We've asked development to add the more recent OS code to tsysOS, but we're not sure when they'll have time to do this, as they are currently very busy with the Lansweeper 6.0 help desk beta. You can always add your own entries to tsysOS, manually (e.g. through SQL Server Management Studio) or through a script. A sample script that adds an entry for OS code 10.0.10586 can be seen below and executed in the Configuration\Database Scripts section of the Lansweeper console. Running this script should "fix" the widget. We do recommend backing up your database prior to running any scripts, just to be safe. Backup instructions can be found
here.
insert into tsysOS(OScode, OSname, Image, Sortorder) VALUES('10.0.10586', 'Win 10', 'ten10.png', 18)
GO