microsoft / microsoft/winget-pkgs

[Package Issue]: Mudlet.Mudlet installer URL returns 404

Open
#344,680 2 comments 0 reactions 0 assignees View on GitHub
Issue-Bug Needs-Triage
Dominant language
No language data
Stars
11.1k
Forks
9.7k
PR merge metrics
PR metrics pending

Description

### Please confirm these before moving forward

- [x] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
- [x] I have not been informed if the issue is resolved in a preview version of the winget client.

### Category of the issue

Installation issue.

### Brief description of your issue

The installer URL for Mudlet.Mudlet version 4.19.1 returns "Invalid File ID or File Name."

The URL appears to use a dynamic ID format (e.g., https://www.mudlet.org/download/53/), which currently returns 404.

Upstream Mudlet version is now 4.20.1.

The package may need updating and/or a more stable installer URL if available.

### Steps to reproduce

1. Run: winget install Mudlet.Mudlet
2. Winget attempts to download version 4.19.1
3. Download fails with error 0x80190194 (404)
4. Manually visiting the installer URL in a browser returns:
"Invalid File ID or File Name."

### Actual behavior

Winget fails to download the installer.

Error:
Download request status is not success.
0x80190194 : Not found (404)

### Expected behavior

Winget should successfully download and install the Mudlet installer.

### Environment

```raw
Windows Package Manager v1.28.190
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.26300.7939
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.28.189.0
```

### Screenshots and Logs

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by locating the Mudlet.Mudlet package manifest used by `winget install Mudlet.Mudlet`. Check its 4.19.1 installer URL against the reported 404 and the upstream 4.20.1 release, then verify that the package installs successfully with winget using the corrected release information.

Written by the indexing model from the issue text.

Assessment

Domain
cli, operating-systems
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.