Prompt to update on launch which results in 'No Update available'

[darkred]

Summary

Since yesterday I get A New version of Sublime Text is available, download now? at launch
but then it shows "No update available".

Expected behavior

It should automatically download+update to the new build.

Actual behavior

I just get No Update available when clicking "Download".

Steps to reproduce

• launch ST 3 build 3118 x64 in win10x64:
  you'll get A New version of Sublime Text is available, download now
  in order to update to build 3119.
• cicking "Download" shows "No update available".
• After that, clicking Help|'Check for updates' I get "No update available".
  Since then. the above (the prompt to update) reappears every time I launch ST3, but it always results as "No update available".
• There's no relevant entry in console.
• The new build installer is indeed available in http://www.sublimetext.com/3dev

Duplicate of this: #1149

Environment

• Operating system and version:
  • Windows 10 x64
  • Mac OS ...
  • Linux ...
• Sublime Text:
  • Build 3119 x64 dev

[PixelT]

+1
occurs on Windows, on Mac is OK.

[keith-hall]

It occurred to me on Windows 7, but this was literally one second after Jon posted the forum post about 3119, so the update server probably hadn't been made aware of the new build yet. I ended up downloading the installer manually. On another Windows 7 machine, it updated from 3118 to 3119 automatically without any problem. (both machines and both ST3 instances are the x64 versions)

[darkred]

For testing, I also installed build 3118 x64 in a virtual machine (vmware) of win10 x64,
and clicking "Download" on the update prompt finished updating to 3119 successfully.

So, I guess something in my ST3 installation is blocking the update..
But, there's no error entry in console.
Also, FWIW, I tried disabling all packages that I had installed, but the issue remains.

[darkred]

I noticed using Process Monitor while checking for updates
that every time ST3 accesses/downloads this file:
C:\Users\<username>\AppData\Local\Microsoft\Windows\INetCache\IE\______\updatecheck.htm

There were various existing updatecheck.html files inside the IE's subfolders.
The newest updatecheck.html content was:

{
    "latest_version": 3118,
    "update_url": "https://www.sublimetext.com/3dev",

    "manifest_host": "www.sublimetext.com",
    "update_host": "download.sublimetext.com",

    "manifest_path_osx": "/_pak/sublime_text_osx_3118.manifest.xz",
    "update_path_osx": "/sublime_text_osx_3118.pak.xz",

    "manifest_path_windows_x64": "/_pak/sublime_text_windows_x64_3118.manifest.xz",
    "update_path_windows_x64": "/sublime_text_windows_x64_3118.pak.xz",

    "manifest_path_windows_x32": "/_pak/sublime_text_windows_x32_3118.manifest.xz",
    "update_path_windows_x32": "/sublime_text_windows_x32_3118.pak.xz"
}

That existing updatecheck.html should contain 3119 instead of 3118
but for some reason it didn't, so it should be deleted.
So I solved this by clearing history in IE:
I pressed Tools | Internet Options (General tab) | Delete,
in order to delete temporary files as follows (using the default settings) :
.
After that, the update completed successfully.

[wbond]

As of build 3137 we updated the server config to with HTTP headers to prevent caching and tweaked the client side code that looks for updates. This should hopefully prevent this issue in the future.