Exception calling "Parse": Version string portion was too short or too long – Windows 11 24H2, winget 0x8a15000f

[evilwall]

⚙️ Issue Checklist

• I have read the guidelines.
• I checked for duplicate issues.
• I searched for existing discussions.
• I checked for an existing pull request that addresses this issue.

📜 What part of Winutil are you having issues with?

Microwin/streamlined ISO, Windows 11 24H2

📝 Provide a clear and concise description of the issue.

Hi!
When I try to run the Chris Titus Tech WinUtil script (irm "https://christitus.com/win" | iex) on Windows 11, version 24H2 (Microwin/streamlined ISO), I get the following error message:

Exception calling "Parse" with "1" argument(s): "Version string portion was too short or too long."

🔄 Steps to reproduce the issue.

1. Install Windows 11 24H2 (Microwin/streamlined ISO)
2. Open PowerShell (admin or user)
3. Run irm "https://christitus.com/win" | iex
4. Observe the error

❌ Paste the full error output (if available).

Exception calling "Parse" with "1" argument(s): "Version string portion was too short or too long."
0x8a15000f : Data required by the source is missing

🖼️ Additional context.

• Read related issues (About the system version number error after Microwin streamlined win11 25h2 #3500, winget reinstall and other errors.. #3496, Exception when calling "ShowDialog" with 0 argument(s): during executing the command in powershell in admin mode #3536) but those solutions do not work for my version.
• Tried resetting winget sources, clearing App Installer cache, reinstalling App Installer, admin/non-admin PowerShell, etc.
• Manual winget commands also fail on this system

[Cinter94]

Are you sure you have winget installed and working? I selected chocolatey and had same issue, resolved installing winget

[evilwall]

Are you sure you have winget installed and working? I selected chocolatey and had same issue, resolved installing winget

Yes I have winget installed. I tried to install application without Chris's tool and it works fine.

Edit: I tried to use winget by itself to uppgrade all apps and i got

winget upgrade --all
Failed when searching source: winget
An unexpected error occurred while executing the command:
0x8a15000f : Data required by the source is missing

winget --version
v1.11.510

[evilwall]

I solved it

Here are the key commands that repaired mywinget installation and made WinUtil work again.

Winget/Package Source Repair

# Reset all winget sources to default
winget source reset --force

# Update all sources, including msstore and winget CDN
winget source update

App Installer/winget Manifest Registration

# Re-register winget's source package (run with the correct path)
Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\Microsoft.Winget.Source_*\AppXManifest.xml" -Verbose

Optional: PowerShell WinGet Client Repair

# Install the latest WinGet client module and repair all dependencies
Install-Module Microsoft.WinGet.Client -Force
Repair-WinGetPackageManager

Confirm repairs and update all packages — including those missing version info

# Upgrade all packages and show ones with missing version info
winget upgrade --all --include-unknown

These steps reset your winget sources, repaired corrupted package registrations, and made sure your App Installer and package manager are up to date and correctly registered, unblocking WinUtil and any other winget-powered automation.[5][11][12][13]

[github-actions]

This issue was marked as stale due to inactivity.

[GabiNun]

fixed /close