Roku Remote Tool app update

I’d been running into WinGet reporting that the current version of the desktop Roku RemoteTool app as being 4.1.2 and showing an update to version 4.1.2.1385, yet after WinGet downloads and installs the update, the next time WinGet is run, it again reports the app as being version 4.1.2 with the 4.1.2.1385 version available as an update and again downloads the app and installs it, only to still show the installed version as 4.1.2 with 4.1.2.1385 available.
WinGet apparently gets it’s version info from the registry value of Display Version (in my case on a Windows 11 Pro version at

HKEY_USERS\S-1-5-21-3877097282-1900542303-776228544-1001\Software\Microsoft\Windows\CurrentVersion\Uninstall\roku_remote_tool\DisplayVersion)

Of course it will likely be at a different USER folder for you, but otherwise basically the same.
Edit the value there for roku_remote_tool\DisplayVersion to change from 4.1.2 to 4.1.2.1385.
As the software ages and does get an upgrade the version numbers may change, but at least this is where the number reported to WinGet is saved.
I was having trouble with WinGet constantly finding the upgrade available for Roku RemoteTool available and taking the time to download and install the program each time I ran Winget.
Changing the value in that registry key seems to have resolved that glitch.

Thanks for sharing this detailed fix! I’ve noticed the same issue with WinGet repeatedly showing the Roku Remote Tool update. Editing the DisplayVersion in the registry makes a lot of sense since that’s where WinGet pulls its info.

I’ll give this a try and see if it stops the constant update prompts. Appreciate you posting the exact registry path and steps — super useful!

Hopefully, Roku or WinGet addresses this in a future update to avoid manual edits.

Thanks for sharing this — super helpful! I was stuck in the same WinGet loop with Roku RemoteTool showing 4.1.2 even after updates. Editing the DisplayVersion in the registry to 4.1.2.1385 fixed it right away. Hopefully Roku or WinGet will eventually address this officially.