Powershell v7.4.3, which installed Microsoft.Winget.CommandNotFound by Powertoys, might failed to start without Internet connection. The module in Powertoys need to update.

[neville-studio]

Microsoft PowerToys version

0.82.0

Installation method

PowerToys auto-update

Running as admin

Yes

Area(s) with issue?

Command not found

Steps to reproduce

If not connected Internet and Installed Microsoft.Winget.CommandNotFound by Powertoys in following steps:

1. Open Microsoft Powertoys Setting Page,
2. Turn to Command Not Found Page.
3. Click 'Install'

The Powershell might failed to start.

In microsoft/winget-command-not-found#10 I have see that this issue has fixed in its latest version, when will the PowerToys use the latest version of the module to install?

✔️ Expected Behavior

The Powershell successed to start

❌ Actual Behavior

The Powershell might failed to start. returned the error

An error has occurred that was not properly handled. Additional information is shown below. The PowerShell process will exit.
Unhandled exception. System.Management.Automation.CmdletInvocationException: An error occurred while connecting to the catalog.
 ---> Microsoft.WinGet.Client.Engine.Exceptions.CatalogConnectException: An error occurred while connecting to the catalog.
   at Microsoft.WinGet.Client.Engine.Commands.Common.FinderCommand.GetPackageCatalog(CompositeSearchBehavior behavior)
   at Microsoft.WinGet.Client.Engine.Commands.Common.FinderCommand.FindPackages(CompositeSearchBehavior behavior, UInt32 limit, PackageFieldMatchOption match)
   at Microsoft.WinGet.Client.Engine.Commands.Common.FinderExtendedCommand.FindPackages(CompositeSearchBehavior behavior, PackageFieldMatchOption match)
   at Microsoft.WinGet.Client.Engine.Commands.FinderPackageCommand.<>c__DisplayClass1_0.<Find>b__0()
   at Microsoft.WinGet.Client.Engine.Commands.Common.ManagementDeploymentCommand.Execute[TResult](Func`1 func)
   at Microsoft.WinGet.Client.Engine.Commands.FinderPackageCommand.Find(String psPackageFieldMatchOption)
   at Microsoft.WinGet.Client.Commands.FindPackageCmdlet.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
   --- End of inner exception stack trace ---
   at System.Management.Automation.Runspaces.AsyncResult.EndInvoke()
   at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
   at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location ---
   at Microsoft.WinGet.CommandNotFound.WinGetCommandNotFoundFeedbackPredictor.WarmUp()
   at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__128_1(Object state)
   at System.Threading.QueueUserWorkItemCallback.Execute()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart()

Other Software

Powershell, v7.4.3

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• Exception on opening Powershell 7.4.2 with (#33304), similarity score: 0.76
• Windows store version of powertools fails to install Command Not Found (#31935), similarity score: 0.75

Closed similar issues:

• [CommandNotFound] - breaks powershell when internet is disconnected (#33065), similarity score: 0.81
• PowerShell Microsoft.WinGet.Client module installation error (#31916), similarity score: 0.75
• PowerShell Microsoft.WinGet.Client module installation error (#31915), similarity score: 0.75

Note: You can give me feedback by thumbs upping or thumbs downing this comment.