Hi Todd,
[moving back to the mailing list]
The URL is the one that WinSparkle (the behind the scenes update checker) uses to look for updates. It composes the URL from it’s own parameters and asks the server what the available update is. It also checks with a limited frequency (every 24 hours, if I remember correctly).
I’m not sure what kind of CDN or other web technologies are in between the Wireshark update server and your internet link, but it seems it may take a while for it to propagate to ‘your neck of the woods’ so to speak.
If Gerald goes through all of his multi page release checklist it should pop up in a reasonable amount of time. Or you can be proactive and get it once you receive notice of a new release. But only if you really cannot wait :)
Enjoy,
Jaap
> On 16 Jan 2018, at 21:32, Todd Adamson <tadamson@xxxxxxxxxxx> wrote:
>
> About of hours after posting this, I was able to download it. Not sure what changed or when. I had tried via multiple ISP's and with and without firewall interference. I didn't have the link to the xml file that was mentioned earlier, so I couldn't verify it. I've saved the link now for future reference.
>
> Todd
>
>
> On 1/16/2018 3:15 AM, Jaap Keuter wrote:
>>>
>>> On 15 Jan 2018, at 17:46, Todd Adamson <tadamson@xxxxxxxxxxx <mailto:tadamson@xxxxxxxxxxx>> wrote:
>>>
>>> My installation of 2.4.3 is not recognizing that 2.4.4 is available. Can someone check to see if there is something missing on the host site? This happening recently where one of the files was not updated to indicate a newer file existed.
>>>
>>> Todd
>>>
>>
>> Hi,
>>
>> The update URL (https://www.wireshark.org/update/0/Wireshark/2.4.3/Windows/x86-64/en-US/stable.xml) is nicely pointing to 2.4.4 at this moment.
>> Is that what matches your situation?
>>
>> Thanks,
>> Jaap
>>
>>
>> ______
>
