0x8a150004 : Opening manifest failed

[obfuscated-loop]

Relevant area(s)

WinGet CLI

Relevant command(s)

winget install

Brief description of your issue

I am receiving this error inside of my Windows Sandbox when I try to install my Helium manifest I generated with winget download.

PS C:\Users\WDAGUtilityAccount\Desktop\applications\helium> winget install -m .\Helium_0.13.6.1_User_X64_nullsoft_en-US.yaml
An unexpected error occurred while executing the command:
0x8a150004 : Opening manifest failed

All other manifests I have generated work 100% within the sandbox however the Helium Browser manifest always fails to open.

Steps to reproduce

1. Copy this manifest file (Helium_0.13.6.1_User_X64_nullsoft_en-US.yaml):

PackageIdentifier: ImputNet.Helium
PackageVersion: 0.13.6.1
Moniker: helium
Icons:
- IconUrl: https://cdn.winget.microsoft.com/icons/bf092ed48b8eed5656dcd29746a8133542e1eb9a21e0e4754e0b25da366b6743.ico
  IconFileType: ico
  IconResolution: custom
  IconTheme: default
  IconSha256: bf092ed48b8eed5656dcd29746a8133542e1eb9a21e0e4754e0b25da366b6743
Tags:
- chromium
- helium-browser
- heliumbrowser
- manifestv2
- mv2
- web-browser
- webbrowser
PackageLocale: en-US
Copyright: 2026 The Helium Authors. All rights reserved.
Description: The Chromium-based web browser made for people, with love. Best privacy
  by default, unbiased ad-blocking, no bloat and no noise.
ShortDescription: Private, fast, and honest web browser.
License: GPL-3.0
LicenseUrl: https://github.com/imputnet/helium/blob/HEAD/LICENSE
PackageName: Helium
PackageUrl: https://helium.computer/
PrivacyUrl: https://helium.computer/privacy
Publisher: The Helium Authors
PublisherSupportUrl: https://github.com/imputnet/helium/issues
PublisherUrl: https://imput.net/
ReleaseNotes: 'Changes since last build:

  helium-windows

  4f4a64f update: helium 0.13.6.1 (#304)

  helium-chromium

  c6feb7e0 revision: bump to 6 (#2015)

  03a16cfa merge: update to chromium 149.0.7827.200 (#2014)

  d447f889 merge: update ungoogled-chromium to 149.0.7827.200

  8f30897f Update to Chromium 149.0.7827.200

  1772f7ce bump-platform: check if b/s/chrome exists instead of just b/s/ (#2003)


  See this GitHub Actions Run for the Workflow file used as well as the build logs
  and artifacts'
ReleaseNotesUrl: https://github.com/imputnet/helium-windows/releases/tag/0.13.6.1
Installers:
- Architecture: x64
  InstallerType: nullsoft
  InstallerSha256: 1bb1975b48323122391a43644d35ccf65e69de5926493b7f5a9985b68e0c1772
  InstallerUrl: https://github.com/imputnet/helium-windows/releases/download/0.13.6.1/helium_0.13.6.1_x64-installer.exe
  Scope: user
  ReleaseDate: 2026-06-26
  InstallerAbortsTerminal: false
  InstallLocationRequired: false
  RequireExplicitUpgrade: false
  DisplayInstallWarnings: false
  DownloadCommandProhibited: false
  ArchiveBinariesDependOnPath: false
  ProductCode: imput Helium
  UpgradeBehavior: install
  FileExtensions:
  - htm
  - html
  - pdf
  - shtml
  - svg
  - webp
  - xht
  - xhtml
  Protocols:
  - http
  - https
  - mailto
  - tel
  AppsAndFeaturesEntries:
  - {}
  ExpectedReturnCodes:
  - InstallerReturnCode: 3
    ReturnResponse: alreadyInstalled
  - InstallerReturnCode: 4
    ReturnResponse: downgrade
  - InstallerReturnCode: 22
    ReturnResponse: cancelledByUser
  - InstallerReturnCode: 60
    ReturnResponse: installInProgress
  InstallerSwitches:
    Silent: /S
    SilentWithProgress: /S
    Log: /VERBOSE-LOGGING /LOG-FILE="<LOGPATH>"
    InstallLocation: /D=<INSTALLPATH>
  InstallModes:
  - interactive
  - silent
ManifestVersion: 1.12.0
ManifestType: merged

2. winget install -m Helium_0.13.6.1_User_X64_nullsoft_en-US.yaml

Expected behavior

Download/installation starts

Actual behavior

0x8a150004 : Opening manifest failed

Environment

Windows Package Manager v1.29.280
© 2026 Microsoft. All rights reserved.

Windows: Windows.Desktop v10.0.26200.8457
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.29.279.0

WinGet Directories
-------------------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
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                        Enabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled
ProxyCommandLineOptions                   Disabled
ConfigurationProcessorPath                Disabled
DefaultProxy                              Disabled

[Trenly]

This appears to be an issue with the merged manifest. The AppsAndFeaturesEntries is coming through as an empty object in a list even though the original manifest has it defined as:

AppsAndFeaturesEntries:
- DisplayVersion: ""

@obfuscated-loop - As a workaround, you can simply remove or update the AppsAndFeaturesEntries in the downloaded manifest

[Trenly]

Going to tag @denelon since I know he hasn't triaged this, and it seems like a bit more fundamental of an issue with how the merged manifests get created