I am running the newest Fences version (4.1.0.2) on Windows 10 and 11. Object Desktop shows that Fences is up to date.

However, "winget update" in PowerShell insists that the version is not current. But take a look:

PS C:\temp> winget update

Name                      Id                       Version   Available    Source

-----------------------------------------------------------------------

Stardock Fences 4   Stardock.Fences 4.1.0.6    4.07.02       winget

The formatting is a bit jacked, but you will note that the version I am on is 4.1.0.6. Winget is stating that a new version is available, 4.07.02. This is actually a downgrade - if I use winget to update Fences, Object Desktop states an update is available.

It would appear that the winget repo sees two different version standards: one with 4 numbers separated by periods, and another with 3 numbers separated by periods. This appears to confuse winget.

I am unsure what the fix is, but figured you all would want to know.