Relevant area(s)
PowerShell Module
Relevant command(s)
No response
Brief description of your issue
When starting a PowerShell session without an active internet connection, the Microsoft.WinGet.CommandNotFound module fails during its background WarmUp() task. The resulting CatalogConnectException is unhandled and causes the entire PowerShell process to crash with exit code 0xe0434352 (process exited with code 3762504530).
Steps to reproduce
- Disconnect the PC from the internet (turn off Wi-Fi / unplug Ethernet).
- Open a new PowerShell / Windows Terminal session with
Microsoft.WinGet.CommandNotFound enabled.
- Observe the startup error and process crash.
Expected behavior
Background catalog warmup failures due to lack of network connectivity should be handled gracefully (e.g., swallowed or logged silently) without crashing the PowerShell host process.
Actual behavior
An unhandled System.Management.Automation.CmdletInvocationException wrapping a Microsoft.WinGet.Client.Engine.Exceptions.CatalogConnectException is thrown from WinGetCommandNotFoundFeedbackPredictor.WarmUp(), terminating the PowerShell session immediately.
Environment
[winget --info]
Windows Package Manager v1.29.290
© 2026 Microsoft. All rights reserved.
Windows: Windows.Desktop v10.0.26200.8875
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.29.290.0
WinGet Directories
-------------------------------------------------------------------------------------------
Logs %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8…
User Settings %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8…
Portable Links Directory (User) %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User) %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root C:\Program Files\WinGet\Packages
Portable Package Root (x86) C:\Program Files (x86)\WinGet\Packages
Installer Downloads %USERPROFILE%\Downloads
Configuration Modules %LOCALAPPDATA%\Microsoft\WinGet\Configuration\Modules
Links
---------------------------------------------------------------------------
Privacy Statement https://aka.ms/winget-privacy
License Agreement https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale
Admin Setting State
--------------------------------------------------
LocalManifestFiles Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride Disabled
LocalArchiveMalwareScanOverride Disabled
ProxyCommandLineOptions Disabled
ConfigurationProcessorPath Disabled
DefaultProxy Disabled
Relevant area(s)
PowerShell Module
Relevant command(s)
No response
Brief description of your issue
When starting a PowerShell session without an active internet connection, the
Microsoft.WinGet.CommandNotFoundmodule fails during its backgroundWarmUp()task. The resultingCatalogConnectExceptionis unhandled and causes the entire PowerShell process to crash with exit code0xe0434352(process exited with code 3762504530).Steps to reproduce
Microsoft.WinGet.CommandNotFoundenabled.Expected behavior
Background catalog warmup failures due to lack of network connectivity should be handled gracefully (e.g., swallowed or logged silently) without crashing the PowerShell host process.
Actual behavior
An unhandled
System.Management.Automation.CmdletInvocationExceptionwrapping aMicrosoft.WinGet.Client.Engine.Exceptions.CatalogConnectExceptionis thrown fromWinGetCommandNotFoundFeedbackPredictor.WarmUp(), terminating the PowerShell session immediately.Environment