LegacyUpdate/LegacyUpdate

Add the ability to use e.g. Firefox instead of Internet Explorer.

RemixPL1994 opened this issue · 6 comments

Hello.

Add the ability to use e.g. Firefox instead of Internet Explorer. Please.

Today I was instaling Windows 7 to my old laptop and using LegacyUpdate to avoid errors in searching and downloading Windows Updates.

Before I used LegacyUpdate, I disabled Internet Explorer in Windows features. I always do this immediately after installing another browser (Chome, Firefox).

My favorite is always Firefox.

I always completely remove and disable Internet Explorer and Edge from the system so that they are not visible.

Can you make it possible to open the search, download and install updates on the currently installed default browser in the system?

That is, instead of Internet Explorer, e.g. Firefox, which is the default installed browser.

Currently, at this point I get an error and it is not possible and I have to re-enable Internet Explorer in the system functions.

If we were to use Firefox, it would be more convenient, more modern and better.

You expect Firefox to run ActiveX?

You expect Firefox to run ActiveX?

Sorry. I don't expect anything. I also don't know why ActiveX is required for LegacyUpdate to work properly.

And is it possible to do it in a different way than through ActiveX and Internet Explorer so that LegacyUpdate is launched on, for example, an additionally installed default browser in the Firefox system?

If for some reason it is difficult to do but possible and takes time - I understand.

If it's completely impossible - okay, I understand too. I didn't know this before.

You can use Windows Update Mini Tool (WUMT) instead Internet Explorer
https://sccm.ie/kit/wumt.zip

after you install LegacyUpdate, run the tool and make sure that "Update service" box is set to "Windows Server Update Service"

kirb commented

It’s not a silly question at all - support for other browsers very much could be added. Earlier versions of Firefox can be supported by writing an NPAPI (Netscape plugin API) plugin. Probably can also be done using WebExtensions for Chrome and modern Firefox, as some extensions are able to talk to a native server binary (1Password does this as an example). Just hasn’t been done at this point because the initial goal of Legacy Update was to replace the Microsoft WUWeb ActiveX control for one that works on legacyupdate.net - that, and the Windows Update website is heavily dependent on IE proprietary APIs that I’d need to make more cross-browser compatible.

But you know, in my working place we use windows 10/11, we turn that active x as run in allowed sites settings and allowed sites and that work mean concrete sites work especially on new Microsoft Edge or Firefox. So active x are like bundled in windows some components. So i think if is it all, update legacy should work normally. I was told more (that to autor) because your project has big potential. You can add automatic update him with updates. And if tell more, Windows 10 loose support in 2025. Will be next esu in history. So if legacy update make replace original windows update and we by security windows update put on him in system, then your project did can normally download esu. That's my suggestions how can make more

@kirb

Using Firefox to launch LegacyUpdate to check for and install future updates would be great.

I hope you can do this in an update someday.