Winget installing unknown program... Softway Korea FirmwareUpgrade 9NB29FG67GPQ

[JVKeller]

I have several PC's that are scripted to update apps with winget on a weekly basis.
Basic command. winget update --all

For some reason, several of them tried to install this program?!

Name            Id           Version Source
---------------------------------------------
FirmwareUpgrade 9NB29FG67GPQ Unknown msstore

[denelon]

I'm not familiar with that application. I'd have to make the assumption that something/someone must have used WinGet to install that package on those devices.

You should be able to take a look at the WinGet logs to see if it was triggered via the CLI or via a COM call.

[JVKeller]

No, you don't understand.

I do not and have never heard of this program, so for it to be trying to install on 2 dozen different PCs is not normal.

I have a script updating apps on once a week, but this app is not on my catalog!

@denelon How can an app that I don't have installed, never heard of, try to "install" when my script is to "update" on several computers?

[denelon]

The only way I can think of is if it is listed as a dependency for one of the packages (that shouldn't be the case as it appears it's coming from the Microsoft Store unless it's a dependency for one of the packages in the Microsoft Store), or if as I said above "something else" is calling WinGet and asking WinGet to install it.

You could build a WinGet Configuration file to install all the things you want installed and uninstall anything you don't want installed. That's another approach.

[JVKeller]

I have a script that basically does nothing but 'winget update --all' so it something has it's wires crossed in the database somewhere.

…

On Thu, Aug 7, 2025, 4:05 PM Demitrius Nelon ***@***.***> wrote: The only way I can think of is if it is listed as a dependency for one of the packages (that shouldn't be the case as it appears it's coming from the Microsoft Store unless it's a dependency for one of the packages in the Microsoft Store), or if as I said above "something else" is calling WinGet and asking WinGet to install it. You could build a WinGet Configuration file to install all the things you want installed and uninstall anything you don't want installed. That's another approach. — Reply to this email directly, view it on GitHub <#5640 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AG6GTYVYDDR76SSAXHVS4PD3MOWSLAVCNFSM6AAAAACDL5DGSKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMBTHA3TMMA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[denelon]

It's possible something else is running on those systems and it is also leveraging WinGet to install that package. WinGet doesn't install packages on its own without being invoked by something. WinGet also doesn't support "cross-source" dependency installation. Each device would hold about the last 100 logs for every time WinGet is invoked. I'd suspect there to be a logged event of WinGet installing that other package and the command & arguments used. It would also provide the timestamp when it happened so you could check against when the scripted upgrade --all is running.

[Trenly]

@JVKeller - Can you run winget list --verbose --logs and then upload the log file to this discussion? The logs directory should open after the command runs. It would also be helpful to have the logs from winget update --all --verbose --logs

[JVKeller]

I figured out what was happening. I had a typo in the script arguments that boiled down to: winget install upgrade

If you search for it winget search upgrade it finds that Software Firmware Installer.