Support ended

[candrapersada]

is there thorium-legacy support for windows 7?

[ltguillaume]

It should work, but it's completely impossible for me to properly support it.

1. I see that @Alex313031 has renamed the repository yet again, without changing the thor_ver file accordingly, or notifying me
2. Releases aren't predictable: sometimes a release is only for WinXP, or exclusively for a specific instruction set or architecture, so when WinUpdater sees there's a new version, but can't find the appropriate build, there's no real way to tell what it should do.
3. The new filenames for with e.g. WINXP at the end aren't consistent with the rest either, so WinUpdater will most probably get confused.
4. This has been the case ever since I've been following this project, so I don't expect these breaking changes to stop.

As such, in addition to the following reasons, I've made the decision to stop supporting Thorium WinUpdater completely.

[candrapersada]

I've made the decision to stop supporting Thorium WinUpdater completely.

if so will it still continue to support chromium-winupdater?
and is there an option like this in Chromium-WinUpdater.ini?

InstallerFile=thorium_AVX_mini_installer.exe https://github.com/Alex313031/thorium-legacy/releases/download/M122.0.6261.168/thorium_AVX_mini_installer.exe
PortableFile=Thorium_AVX*.zip https://github.com/Alex313031/thorium-legacy/releases/download/M122.0.6261.168/Thorium_AVX_122.0.6261.168.zip

[ltguillaume]

For now, you can just keep using Thorium WinUpdater: it has some hardcoded workarounds for the unconventional naming schemes used in Thorium. Well, at least for the non-legacy builds: release and naming conventions are more consistent in that repo.

You could start using Chromium WinUpdater if it receives an update that is important or if Thorium WinUpdater stops working altogether (for the build you'd like to use).