LegacyUpdate icon indicating copy to clipboard operation
LegacyUpdate copied to clipboard

Issues accessing the site in China

Open wyf180 opened this issue 2 years ago • 5 comments

Would the LegacyUpdate planning to working for win9x to me?And the web page https://legacyupdate.net/ can't working on my xp vm perhaps due to the GFW could you fix it?

wyf180 avatar Nov 28 '22 09:11 wyf180

Win9x isn't supported yet, there's some more info about it on the FAQ, but since you can't load it I'll copy it over here:

What about Windows 95, 98, Me, and NT 4?

To explain this, here is a quick history of Windows Update:

  • Version 3: Windows Update started life as a program called Critical Update Notification Tool (a very unfortunate acronym), which would nag you to open the Windows Update v3 website to download applicable updates for your system. Not all that intelligent - it was just a website that downloaded a massive (for the time) file listing every update ever released by Microsoft, filtering out the updates irrelevant to your system within the Windows Update website itself.
  • Version 4: A total overhaul of how Windows Update works. Windows Update evolved from just a standalone file to a protocol, where the PC and the Microsoft server compare notes and figure out which updates are applicable to the current system. Included with Windows 2000 and XP, and installable as an update to Windows 98, Me, and NT 4. Also introduced Automatic Updates on 2000 and XP.
  • Version 5 and 6: Windows Update v5 provided some major refinements to v4. Windows Update v6 added support for updating other Microsoft products along with Windows itself (confusingly named Microsoft Update), and is the most current version to this day. Included with Windows Vista right up to Windows 11, and installable as an update to Windows 2000 SP3 and XP RTM.

Legacy Update works because we’re lucky enough that the Windows Update v6 protocol is pretty much the same today as it was when the v6 protocol was first released around 2005. It seems unlikely that Microsoft will completely discontinue Windows Update for 2000/XP, though as I discussed in the introduction paragraph, Microsoft has taken a very destructive approach to discontinuing services for old versions of Windows, right down to deleting legacy downloads and knowledge base articles from their servers, so that’s still an issue to be concerned about.

Given Windows Update is a protocol, and not a website Wayback Machine can easily scrape and archive, I’m concerned that this means the legacy Windows Update servers and the updates/drivers they provide are lost to time. Some, but not all, of Windows Update v3 has been preserved by the Wayback Machine, so I’m looking into what I can do there.

So the answer, pretty much, is that I’d love to support as far back as Windows Update itself has existed, but it may be quite a bit more significant undertaking than Legacy Update has been so far due to Microsoft’s intent to move on from its past. I’m still positive it can be done though!

Sorry you're having problems accessing the site. Just to make sure, you're accessing it with http://, not https://? It won't be able to load with https:// on XP currently, due to limitations of XP's SSL support, and what my host (Cloudflare) supports for free websites. Do you know if you usually have issues loading sites hosted through Cloudflare? I run another site that has a lot of users with Chinese IPs, the only difference I can think of is that Legacy Update can be used without https.

kirb avatar Nov 28 '22 09:11 kirb

Win9x isn't supported yet, there's some more info about it on the FAQ, but since you can't load it I'll copy it over here:

What about Windows 95, 98, Me, and NT 4?

To explain this, here is a quick history of Windows Update:

  • Version 3: Windows Update started life as a program called Critical Update Notification Tool (a very unfortunate acronym), which would nag you to open the Windows Update v3 website to download applicable updates for your system. Not all that intelligent - it was just a website that downloaded a massive (for the time) file listing every update ever released by Microsoft, filtering out the updates irrelevant to your system within the Windows Update website itself.
  • Version 4: A total overhaul of how Windows Update works. Windows Update evolved from just a standalone file to a protocol, where the PC and the Microsoft server compare notes and figure out which updates are applicable to the current system. Included with Windows 2000 and XP, and installable as an update to Windows 98, Me, and NT 4. Also introduced Automatic Updates on 2000 and XP.
  • Version 5 and 6: Windows Update v5 provided some major refinements to v4. Windows Update v6 added support for updating other Microsoft products along with Windows itself (confusingly named Microsoft Update), and is the most current version to this day. Included with Windows Vista right up to Windows 11, and installable as an update to Windows 2000 SP3 and XP RTM.

Legacy Update works because we’re lucky enough that the Windows Update v6 protocol is pretty much the same today as it was when the v6 protocol was first released around 2005. It seems unlikely that Microsoft will completely discontinue Windows Update for 2000/XP, though as I discussed in the introduction paragraph, Microsoft has taken a very destructive approach to discontinuing services for old versions of Windows, right down to deleting legacy downloads and knowledge base articles from their servers, so that’s still an issue to be concerned about. Given Windows Update is a protocol, and not a website Wayback Machine can easily scrape and archive, I’m concerned that this means the legacy Windows Update servers and the updates/drivers they provide are lost to time. Some, but not all, of Windows Update v3 has been preserved by the Wayback Machine, so I’m looking into what I can do there. So the answer, pretty much, is that I’d love to support as far back as Windows Update itself has existed, but it may be quite a bit more significant undertaking than Legacy Update has been so far due to Microsoft’s intent to move on from its past. I’m still positive it can be done though!

Sorry you're having problems accessing the site. Just to make sure, you're accessing it with http://, not https://? It won't be able to load with https:// on XP currently, due to limitations of XP's SSL support, and what my host (Cloudflare) supports for free websites. Do you know if you usually have issues loading sites hosted through Cloudflare? I run another site that has a lot of users with Chinese IPs, the only difference I can think of is that Legacy Update can be used without https.

I tried the ip address was blocked in China in many space.So could you change a new server to fix it. Screenshot_20221129_092443

wyf180 avatar Nov 29 '22 01:11 wyf180

Yikes, sorry about that. Could you see if you can access my other site, https://chariz.com/? This site is on a Cloudflare Pro plan, while legacyupdate.net is on a free plan. I know that Cloudflare limits some of their datacentre network for sites on their free plan. If that works, I'll see if it makes financial sense to upgrade Legacy Update to Cloudflare Pro.

Interestingly, I tried a handful of Chinese firewall checking websites and all confirmed legacyupdate.net is accessible. One showed that the site took an extremely long time to load (60 seconds), though. Is that normal when you visit sites hosted outside the country? If not, I'll try and see what I can do about it, because 60+ second load times is bordering on unusable, and might cause timeouts that make Windows fail to check for updates.

kirb avatar Nov 29 '22 01:11 kirb

Yikes, sorry about that. Could you see if you can access my other site, https://chariz.com/? This site is on a Cloudflare Pro plan, while legacyupdate.net is on a free plan. I know that Cloudflare limits some of their datacentre network for sites on their free plan. If that works, I'll see if it makes financial sense to upgrade Legacy Update to Cloudflare Pro.

Interestingly, I tried a handful of Chinese firewall checking websites and all confirmed legacyupdate.net is accessible. One showed that the site took an extremely long time to load (60 seconds), though. Is that normal when you visit sites hosted outside the country? If not, I'll try and see what I can do about it, because 60+ second load times is bordering on unusable, and might cause timeouts that make Windows fail to check for updates.

Yes,I can access the website .

wyf180 avatar Nov 29 '22 03:11 wyf180

Modify hosts to www.cloudflare.com and FBI.GOV IP

jonm58 avatar Aug 21 '23 04:08 jonm58