New package: yummyzzzz.CoreInstaller version 2.2

[yummyzzzz]

📖 Description

✅ Checklist

• Signed the Contributor License Agreement
• Linked to an issue (if applicable)
  • Resolves #[Issue Number]

📦 Manifest Checklist

• Checked that there aren't other open pull requests for the same manifest update/change
• This PR only modifies one (1) manifest
• Validated manifest locally with winget validate --manifest <path> (validation guide)
• Tested manifest locally with winget install --manifest <path>
• Manifest conforms to the 1.12 schema

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

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-148-403740-20260717-1

[yummyzzzz]

@microsoft-github-policy-service agree

[yummyzzzz]

@stephengillie Hello,
The unattended validation failed, but the bot didn't post the error logs here. Could you please let me know what went wrong or what I need to adjust in the installer/manifest?
Thank you!

[stephengillie]

Automatic Validation ended with:

2026-07-17 05:35:09.143 [FAIL] C:__w\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(500)\WindowsPackageManager.dll!00007FFD8AAF4883: (caller: 00007FFD8AAEFF09) Exception(1) tid(2048) 80070003 The system cannot find the path specified.
2026-07-17 05:35:09.148 [CORE] RemoveMotwIfApplicable failed before IAttachmentExecute::Save(). Result: -2147024893. Proceeding with Save()

(Deterministic automation - build 1786.)

[yummyzzzz]

/check

[yummyzzzz]

/azure-pipelines run

[yummyzzzz]

@stephengillie

Hello,

I verified the installer URL manually, and it downloads perfectly without a 404 error.

It looks like the automated sandbox hit a temporary network or infrastructure issue downloading the file.

Could you please take a look when you have a moment?

Thank you!

[yummyzzzz]

@stephengillie
Friendly ping on this!
Is there anything else needed on my end to get this passed, or can this be manually verified/approved?
Thanks!

[yummyzzzz]

Dear Staff / Review Team,

I deeply apologize, that i am very unpatient and constantly waiting for an Response.

It's just the first Time, that i'm doing this, please forgive me.

Could you please let me know, if everything's okay, and you don't require any further assistance from me for now?

I would be very thankful for an replay,
Regards, Alex / yummyzzzz.

[Trenly]

@yummyzzzz - Logs can be found in the Artifacts section of the validation pipeline run that the bot linked.

In this case, it seems there are two errors. First, the package seems to have a dependency on Microsoft.VCRedist.2015+.x64 that needs to be added to the manifest

Second, it seems the installer hash has changed since the PR was submitted - I'd recommend having versioned releases at GitHub to avoid the hash verification breaking on each version

[Trenly]

See above

[stephengillie]

Manual Validation ended with:

2026-07-30 16:45:57.117 [CLI ] Package hash verification failed. SHA256 in manifest [7d8ff233b98fdafb389709ca3d23553b449851af942607ce956bc4a4d80108ac] does not match download [9019f7e902544bb969d55af5771538b1f382e3946d300dea1ac187c5d96a04da] with file size [314368] and content type [application/octet-stream]

(Deterministic automation - build 1799.)

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-148-403740-20260731-1

[stephengillie]

Automatic Validation ended with:

Installation didn't complete within the timeout
MSI (s) (04:20) [04:49:34:527]: PROPERTY CHANGE: Adding OutOfDiskSpace property. Its value is '0'.
MSI (s) (04:20) [04:49:34:527]: PROPERTY CHANGE: Adding OutOfNoRbDiskSpace property. Its value is '0'.
MSI (s) (04:20) [04:49:34:527]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceAvailable property. Its value is '0'.
MSI (s) (04:20) [04:49:34:527]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRequired property. Its value is '0'.
MSI (s) (04:20) [04:49:34:527]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRemaining property. Its value is '0'.
MSI (s) (04:04) [04:49:35:188]: PROPERTY CHANGE: Adding OutOfDiskSpace property. Its value is '0'.
MSI (s) (04:04) [04:49:35:188]: PROPERTY CHANGE: Adding OutOfNoRbDiskSpace property. Its value is '0'.
MSI (s) (04:04) [04:49:35:188]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceAvailable property. Its value is '0'.
MSI (s) (04:04) [04:49:35:188]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRequired property. Its value is '0'.
MSI (s) (04:04) [04:49:35:188]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRemaining property. Its value is '0'.
2026-07-31 04:49:46.489 [FAIL] C:__w\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(500)\WindowsPackageManager.dll!00007FFC03BE4883: (caller: 00007FFC03BDFF09) Exception(1) tid(2b78) 80070003 The system cannot find the path specified.
2026-07-31 04:49:46.500 [CORE] RemoveMotwIfApplicable failed before IAttachmentExecute::Save(). Result: -2147024893. Proceeding with Save()

(Deterministic automation - build 1802.)

[yummyzzzz]

Hello Trenly & Stephengillie,

I just noticed, that the "microsoft-github-policy-service" bot said, that the "--silent" flag does not work.

I have verified that the "--silent" flag actually works on the newest CoreInstaller version.

The Bot may ran into a problem, because Windows Defender actually flags CoreInstaller as an ScriptDownloader / ScriptInstaller, but this is something an Installer does.

I think Windows Defender flags it as an Virus (Trojan:Script/Wacatac.C!ml), because it asks for Admin Privileges and then downloads the neccessery files automatically.

Another thing that i noticed, that may also be the issue is, that Windows SmartScreen also blocks CoreInstaller because it doesn't have an Digital Signature. CoreInstaller is also getting blocked by PowerShell when running it through PowerShell, e.g. using this Command:

INPUT: PS C:\CoreInstaller.exe --silent

OUTPUT: (It says something like this: PowerShell blocked the Process because it contains a Virus.)

I have attached multiple (original) German & English (Auto-translated) Image of the SmartScreen & Windows Defender Problem.

Thanks in advanced,
Best Regards,
Alex / yummyzzzz

[DuckDuckStudio]

According to the screenshot from the verification log, I guess Validation-Unattended-Failed During installation testing the installer was blocked on user input and no switches were provided. is caused by this pop-up window requiring user interactivity.

Edit: This pop-up window:

[yummyzzzz]

Hello Everybody,

I see, that the Error is caused by the MessageBox, which states that CoreView was successfully installed.

Please let me know, if i should remove the MessageBox, keep it or Replace it. (E.g. The Bottom Right Corner Information Message Box).

Please also let me know if anything else is required from my End.

Thanks,
Regards,
Alex / yummyzzzz

[DandelionSprout]

My vote is on "Remove the messagebox".

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-149-403740-20260802-1

[yummyzzzz]

Hello,

I Updated the Installer to not show any Messagebox when using the --silent flag, aswell as the manifest file, to include the correct SHA and the direct Installation link contains the actual file.

Quick Question: Which type of "System" can i use, to let the user know, that the Installation Process failed when using the --silent flag?

Regards,
Alex / yummyzzzz

[yummyzzzz]

Hello Trenly,

I think i'm on the edge to getting my Software / Application Approved, and it seems like you're the one who needs to approve it.

Please review my Software for any Bugs!

Thanks in advance,
Best Regards
Impatient Alex / yummyzzzz ❤️

[stephengillie]

Verify:

Edit The installer didn't seem to write any Registry data.

[wingetbot]

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.