Fences beta bug (winget)

from Stardock Forums

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.

fences
4,928 views 2 replies
Reply #1 from Stardock Forums Top

Hello,
Sorry to hear you are having issues. I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Thanks

Basj,
Stardock Community Assistant

Reply #2 from Stardock Forums Top

We do not manage WinGet repos.

What one should look at for version is the installer details \ File version:

Once installed, the exact version is found via details of Fences.exe.

Also, if you are using WinGet for updates, please do not use \ contrast it with ODM as there are issues we need to resolve with that delivery medium.  

Sean Drohan
Stardock Product Lifecycle Manager

 

SoundPackager - Customize the Windows sound scheme