"Windows" asset type is a mess.

[JonU]

I've been trying to clean up our new installations (we had Lansweeper years ago and have just come back to using it), but when I go in and try to update systems labeled with the asset type "windows", it's disallowed. Meanwhile, we have plenty of these systems that are not labeled "windows" for their asset type but instead show the more accurate laptop/desktop designation of what they are. This really is a mess and makes no sense in setting the typing of those systems. Yes, we can (and have) made dynamic groups to show those devices more accurately, but that means any graphs/metrics/ect on the dashboard are useless to us as they show the hodge podge mess of asset types. Are there any plans to fix that? I have seen other threads somewhat similar in question, and the repeated answers seems to have been "sorry, that's how it is" instead of an actual response about resolving the situation. 

[DavidPK]

In Lansweeper, anything discovered on the network is treated as an asset, and assets are grouped into broad technical categories (servers, desktops, networking equipment, OT, users, software, etc.).

For IT devices, “Windows” is one of those core, system‑managed categories.

For assets that were discovered as Windows machines:

The Asset type = Windows is set automatically by the discovery logic.
That field is locked because Lansweeper uses it internally for:
Discovery/scanning behavior (which protocols/queries to run)
Normalization and reporting logic.

If you are linked to the cloud, it is possible to change it there however it is not possible to change it in the on-prem classic console. 

[JonU]

I did notice I can change it in the cloud site linked to our on prem, but that fact it doesn't then sync back to the on prem pretty much makes doing that useless. Is there any plans to fix that?