# Bug Report: Persistent Update Notification for Already-Installed Version

Q&A
,
1

Title: Amazon Quick Desktop keeps prompting for update v0.1000.20027 despite being on the latest version

Environment:

  • OS: Windows

  • Current version: Latest (already installed)

  • Update being offered: v0.1000.20027

Description: The Amazon Quick desktop app persistently shows an update notification stating “v0.1000.20027 is ready to install,” even though the latest version is already installed. The notification does not go away after:

  • Fully quitting and restarting the app

  • Multiple restarts

  • Waiting for the update to apply

Expected Behaviour: The update notification should not appear when the latest version is already installed.

Actual Behaviour: The app continuously prompts to install v0.1000.20027, which appears to be an older version than what is currently running.

Suspected Root Cause: Based on a similar community thread, this may be related to an installation path mismatch — older versions installed under %LOCALAPPDATA%\quickwork\agent\ while newer versions install to %LOCALAPPDATA%\Programs\quickwork\, preventing the in-place upgrade mechanism from recognising the current installation.

Steps to Reproduce:

  1. Have the latest version of Amazon Quick installed

  2. Observe the update notification for v0.1000.20027

  3. Restart the app — notification persists

Workaround Attempted: Restarting the app multiple times — issue persists.

Request: Please advise on how to permanently dismiss this notification, or provide a fix in a future release to handle the path mismatch gracefully.

2

Hi @bhsuhail and welcome to the community!

This is interesting behavior you’ve found. I tried to recreate this bug on my end but unfortunately could not. I did see the v0.1000.20027 update in the top left of the app, but when I went to update it, the notification was resolved after the restart.

image
image443×364 12 KB

Since this is a public facing community, there is isn’t much we can do for resolving this since we do not have access to anyone’s account nor do we have back end authority. Since you marked your post with the correct ‘error’ tag, I’ll leave this post open for the time being, in case any new developments occurs, and if nothing changes, I’ll archive it to promote visibility to the AWS team.

3

Hi @bhsuhail,

I wanted to check in with you and see if there has been any updates on this issue? Do you still see the Update notification? Anything you can share within the next 3 business days would be greatly appreciated!

4

Hi @bhsuhail,

Since we haven’t received an update from you, I am archiving this post to promote visibility to the AWS team.