Winget import exits early with no error (No packages installed)

Brief description of your issue

winget import winget_buggy_import.json does not install most packages listed.
(i.e. Visual Studio installer, or Todoist, the first 2 in the list)

The output shows 6 'not found' packages, and one admin priveleges error.
Trying as admin did not help.

Trying a smaller export list (winget_small_import_works.json, containing only the first two packages)
Installs them OK.

I've had issues before with import exiting early - #1377, but removing only the VCRedist packages did not help, so this may be something else.

winget_buggy_import.json
winget_small_import_works.json

Steps to reproduce

winget import winget_buggy_import.json

Expected behavior

All valid packages should be installed, individual issues should be output as errors to the console

Actual behavior

Most packages are not installed. No descriptive error is output.

> winget import winget_buggy_import.json
No applicable update found.
Package is already installed: Microsoft.EdgeWebView2Runtime
This command requires administrator privileges to execute.
https://github.com/microsoft/winget-cli/issues/2368
Package not found for import: Rufus.Rufus
No applicable update found.
Package is already installed: Google.Chrome
No applicable update found.
Package is already installed: Atlassian.Sourcetree
No applicable update found.
Package is already installed: Microsoft.WindowsPCHealthCheck
No applicable update found.
Package is already installed: Microsoft.VisualStudioCode
> 

Environment

Windows Package Manager v1.3.2091
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19044.2006
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.18.2091.0

Start by running winget import winget_buggy_import.json and compare it with the smaller import list linked in the issue. Inspect the import command's handling of the reported not-found and administrator-privilege results. Done means all valid packages are processed and individual failures produce descriptive console errors rather than ending the import silently.