The term 'Repair-WinGetPackageManager' is not recognized as the name of a cmdlet, function, script file or operable program

[Umeaboy]

I wanted to install

Queueing Audacity.Audacity for Winget
Queueing BleachBit.BleachBit for Winget
Queueing BlenderFoundation.Blender for Winget
Queueing Kitware.CMake for Winget
Queueing Discord.Discord for Winget
Queueing Gyan.FFmpeg for Winget
Queueing FreeCAD.FreeCAD for Winget
Queueing GIMP.GIMP.3 for Winget
Queueing GitHub.GitHubDesktop for Winget
Queueing GoLang.Go for Winget
Queueing HexChat.HexChat for Winget
Queueing XBMCFoundation.Kodi for Winget
Queueing Insecure.Nmap for Winget
Queueing OpenJS.NodeJS.LTS for Winget
Queueing Notepad++.Notepad++ for Winget
Queueing OBSProject.OBSStudio for Winget
Queueing PuTTY.PuTTY for Winget
Queueing Python.Python.3.12 for Winget
Queueing Oxen.Session for Winget
Queueing OpenWhisperSystems.Signal for Winget
Queueing Telegram.TelegramDesktop for Winget
Queueing eloston.ungoogled-chromium for Winget
Queueing Ventoy.Ventoy for Winget
Queueing VSCodium.VSCodium for Winget
Queueing RARLab.WinRAR for Winget
Queueing WiresharkFoundation.Wireshark for Winget
Queueing Yarn.Yarn for Winget
Queueing yt-dlp.yt-dlp for Winget

and that ends up with:

Attempting to repair WinGet using Repair-WinGetPackageManager...

Error: The term 'Repair-WinGetPackageManager' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

[Umeaboy]

Is this meant to be happening?

[ChrisTitusTech]

This requires Windows 11/10 to be on 24H2 and above.

[savety6]

Steel happening even in 24H2

[stevem-crm]

Same thing happening here. It might be that a component was not installed. "VCRUNTIME140_1.dll was not found..."

winver = 24H2. Just running Winver causes the error above.

FIX:

• Go to https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170
• Follow directions and install for both x64 and x86
• Reboot

Winget is up to date and is working.

[Umeaboy]

Is this solution also fixed in winutil for the future or do we need to use the workaround for now?

[stevem-crm]

I am sure it will be corrected, but for now we have to use this workaround. Probably just an oversight.

[Euro377]

I'm getting the same error message for Winget before and after following the above steps to install VCRUNTIME140. I didn't get a winget.exe system error.
I also tried the WinGet Reinstall Fix Button and that failed after four attempts.


Today I had downloaded latest Win 11 ISO & used the paid for exe version of Winutil to successfully install on new PC. Installed drivers & latest Win updates, then came back to WinUtil to install programs & ran into this problem.
I also tried WinUtil directly from Powershell but ran into both the same issues.
Hope this can be fixed soon, thanks.

[ChrisTitusTech]

This is queued for testing and should be fixed in ff0ca40

[Umeaboy]

Problem is now solved on my fresh installation on the 1st time running to apply the tweaks.

Thank you all so much for fixing this. Closing as solved.

Should anyone here see a different result please add a comment and I'll reopen it again.