New package: ElementLabs.Bionic version 1.0.3+3

[AlexanderBartash]

📖 Description

Adds the initial WinGet manifest for Bionic version 1.0.3+3.

✅ 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-407964-20260726-1

[AlexanderBartash]

@microsoft-github-policy-service agree

[AlexanderBartash]

I tested the submitted multi-file manifest locally on Windows x64.

Bionic was also launched manually from %LOCALAPPDATA%\Programs\Bionic\Bionic.exe. The application opened normally and appeared functional; I observed no reason to suspect an installation or runtime problem.

Validation and installation

PS D:\tmp> $manifest = 'D:\tmp\winget-pkgs\manifests\e\ElementLabs\Bionic\1.0.3+3'
PS D:\tmp> winget validate --manifest $manifest
Manifest validation succeeded.

PS D:\tmp> winget install --manifest $manifest
Found Bionic [ElementLabs.Bionic] Version 1.0.3+3
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://bionic-installers.lmstudio.ai/win32/x64/1.0.3-3/Bionic-1.0.3-3-x64.exe
  ██████████████████████████████   608 MB /  608 MB
Successfully verified installer hash
Starting package install...
Successfully installed

Installed application metadata

PS D:\tmp> Get-ItemProperty $uninstallRoots -ErrorAction SilentlyContinue |
>>     Where-Object DisplayName -match '^Bionic' |
>>     Select-Object DisplayName, DisplayVersion, Publisher, UninstallString

DisplayName    DisplayVersion Publisher UninstallString
-----------    -------------- --------- ---------------
Bionic 1.0.3+3 1.0.3+3        LM Studio "C:\Users\alexa\AppData\Local\Programs\Bionic\Uninstall Bionic.exe" /currentuser

The registry also provided the expected quiet uninstall command:

DisplayName          : Bionic 1.0.3+3
DisplayVersion       : 1.0.3+3
Publisher            : LM Studio
InstallLocation      :
QuietUninstallString : "C:\Users\alexa\AppData\Local\Programs\Bionic\Uninstall Bionic.exe" /currentuser /S
UninstallString      : "C:\Users\alexa\AppData\Local\Programs\Bionic\Uninstall Bionic.exe" /currentuser

This metadata matches the submitted AppsAndFeaturesEntries.

Uninstallation

Before the package exists in the public WinGet source, winget list reports the raw ARP identity rather than ElementLabs.Bionic:

PS D:\tmp> winget list --name Bionic
Name           Id                                                Version
------------------------------------------------------------------------
Bionic 1.0.3+3 ARP\User\X64\7c1a7243-201d-510b-a8e1-803c5b933ce8 1.0.3+3

PS D:\tmp> winget list --id ElementLabs.Bionic --exact
No installed package found matching input criteria.

Consequently, uninstalling through the unpublished local multi-file manifest did not correlate the installed entry:

PS D:\tmp> winget uninstall --manifest $manifest --silent
No installed package found matching input criteria.

Uninstallation through the exact registered application name succeeded silently:

PS D:\tmp> winget uninstall `
>>     --name 'Bionic 1.0.3+3' `
>>     --exact `
>>     --silent
Found Bionic 1.0.3+3 [ARP\User\X64\7c1a7243-201d-510b-a8e1-803c5b933ce8]
Starting package uninstall...
Successfully uninstalled

Afterward, the uninstall registry entry was absent and the installation directory contained no files.

I believe the manifest-based uninstall result is caused by the package not yet being available for source correlation. I am calling it out in case reviewers expect different behavior when testing an unpublished local multi-file manifest.

[AlexanderBartash]

Thank you for your contribution @AlexanderBartash! There was an issue validating your pull request. Many common validation questions and issues can be resolved by reading through the Validation Guide. Please review the guide and update your pull request if needed. If you have any questions, feel free to ask for help!

Template: msftbot/validation/validationGuideAdded

The installer metadata shown by the pipeline matches the submitted manifest:

• Architecture: x64
• Installer type: nullsoft
• SHA-256: E6C8173AFDCAC494B7EE9EF22C8A3E3388FA44054D14B55E62804FF73FDD1959
• Installer URL: the official version-specific LM Studio URL

The Installers Scan step passed. The Installation Validation progress changed from Waiting to InProgress and then to Completed, after which the Azure task reported only:

Status: Completed
##[error] Failed

The log contains no Defender threat name, affected file, event details, or error code. I am not sure what I need to do here.

As documented in my earlier comment, this exact manifest installed successfully, Bionic launched and appeared functional, its registered metadata matched AppsAndFeaturesEntries, and silent uninstallation succeeded.

https://dev.azure.com/shine-oss/winget-pkgs/_build/results?buildId=374572&view=logs&j=68997d86-8ece-5ae8-3ac5-ccdbfa458731&t=b79910ce-dca5-5e27-ad7f-bd285eecb5a2&l=96

From my local env:

PS C:\Users\alexa> Update-MpSignature

PS C:\Users\alexa> Get-MpComputerStatus |
>>     Select-Object `
>>       AntivirusSignatureVersion,
>>       AntivirusSignatureLastUpdated

AntivirusSignatureVersion AntivirusSignatureLastUpdated
------------------------- -----------------------------
1.455.359.0               2026-07-26 11:06:06

PS C:\Users\alexa> $installer = 'D:\tmp\Bionic-1.0.3-3-x64.exe'
PS C:\Users\alexa> $installDir = Join-Path $env:LOCALAPPDATA 'Programs\Bionic'

PS C:\Users\alexa> Test-Path -LiteralPath $installer
True

PS C:\Users\alexa> Start-MpScan -ScanType CustomScan -ScanPath $installer

PS C:\Users\alexa> Get-MpThreatDetection |
>>     Sort-Object InitialDetectionTime -Descending |
>>     Select-Object -First 20 `
>>       InitialDetectionTime,
>>       ThreatID,
>>       Resources,
>>       ActionSuccess,
>>       CurrentThreatExecutionStatus |
>>     Format-List

PS C:\Users\alexa> Get-WinEvent `
>>     -LogName 'Microsoft-Windows-Windows Defender/Operational' `
>>     -MaxEvents 200 |
>>     Where-Object Id -in 1116, 1117, 1118, 1119 |
>>     Select-Object TimeCreated, Id, Message |
>>     Format-List

PS C:\Users\alexa> Get-WinEvent `
>>     -LogName 'Microsoft-Windows-Windows Defender/Operational' `
>>     -MaxEvents 100 |
>>     Where-Object Id -in 1000, 1001, 1002 |
>>     Select-Object TimeCreated, Id, Message |
>>     Format-List

TimeCreated : 2026-07-26 16:33:16
Id          : 1001
Message     : Microsoft Defender Antivirus scan has finished.
                Scan ID: {190FC9C1-95A2-4E30-80B9-3320CDF5C4FA}
                Scan Type: Antimalware
                Scan Parameters: Custom Scan
                User: NT AUTHORITY\LOCAL SERVICE
                Scan Time: 0:00:01

TimeCreated : 2026-07-26 16:33:14
Id          : 1000
Message     : Microsoft Defender Antivirus scan has started.
                Scan ID: {190FC9C1-95A2-4E30-80B9-3320CDF5C4FA}
                Scan Type: Antimalware
                Scan Parameters: Custom Scan
                Scan Resources: file:_D:\tmp\Bionic-1.0.3-3-x64.exe
                User: NT AUTHORITY\LOCAL SERVICE
                Scan Trigger: On demand
                Scan Only If Idle: Enabled
                Low CPU Priority for Scans: Disabled
                Thread Priority: 7

PS C:\Users\alexa> Test-Path -LiteralPath $installDir
False

[stephengillie]

Hi AlexanderBartashnnThis manifest uses the same values for DisplayVersion and PackageVersion. This is not recommended, and the DisplayVersion should be removed.

(Deterministic automation - build 1800.)

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-148-407964-20260730-1

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-148-407964-20260730-2

[AlexanderBartash]

Fixed, thank you.

[stephengillie]

Verify:

[wingetbot]

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