NanoBoyAdvance.NanoBoyAdvance version 1.7.1

[superusercode]

• Have you signed the Contributor License Agreement?
• Have you checked that there aren't other open pull requests for the same manifest update/change?
• This PR only modifies one (1) manifest
• Have you validated your manifest locally with winget validate --manifest <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
• Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[microsoft-github-policy-service]

superusercode,

The check-in policies require a moderator to approve PRs from the community.

Our moderators are community volunteers, please be patient and allow them sufficient time to review your submission.

Template: msftbot/requiresApproval/moderator

[stephengillie]

This package installed normally, but errored when launched:

Faulting application name: NanoBoyAdvance.exe, version: 1.7.1.0, time stamp: 0x64629636
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process id: 0x0x1720
Faulting application start time: 0x0x1D989AFECE4518D
Faulting application path: C:\Users\User\AppData\Local\Microsoft\WinGet\Packages\NanoBoyAdvance.NanoBoyAdvance__DefaultSource\NanoBoyAdvance.exe
Faulting module path: unknown Report Id: 47cfdecc-e95a-4633-a102-3e29cc1aac06
Faulting package full name:
Faulting package-relative application ID:

[superusercode]

due to the vm?

[superusercode]

installs and launches fine for me locally

[stephengillie]

installs and launches fine for me locally

You've got numerous VCRedist and .NET packages that the validation VMs may not. Since the VM is meant to emulate what a new PC might be like, if the user hasn't installed anything yet. For a more accurate troubleshooting perspective, please consider installing a fresh copy of Windows onto a Hyper-V instance, checkpointing it, and installing these there - then resetting to the checkpoint between each install. (And regular Windows Updates and Defender updates of course.) This is environment I'm using, automated with a few scripts.

[superusercode]

I'll try setting up a virtualbox instance, though I can't use hyperv/windows sandbox since that requires pro last I recall.

[stephengillie]

Oh - sorry - yes, any virtualization solution should work the same here.

[superusercode]

clean win11 image on virtualbox runs it without the error

[ItzLevvie]

[Policy] Hardware

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ItzLevvie]

@wingetbot run

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ItzLevvie]

[Policy] Blocking-Issue

[denelon]

Supporting custom hardware in validation is "Not Planned".

• Support hardware requirements. #199504