smtp4dev command not available after winget install (alias not created / not on PATH)

[Makeea]

---

Description

After installing smtp4dev via winget, the smtp4dev command is not available in PowerShell, even though installation reports success.

---

Steps to Reproduce

winget install smtp4dev
smtp4dev

---

Expected Behavior

smtp4dev should be available as a command (via winget alias / shim) and launch the application.

---

Actual Behavior

PowerShell returns:

smtp4dev : The term 'smtp4dev' is not recognized as the name of a cmdlet, function, script file, or executable program.

---

Environment

• OS: Windows 11 Pro 25H2

• Shell: PowerShell 7.6.0

• Install method: winget (Rnwood.Smtp4dev)

• Install location:

• OS: Windows 11 Home 25H2

• Shell: PowerShell 5.1.26100.8115

• Install method: winget (Rnwood.Smtp4dev)

• Install location:

  %LOCALAPPDATA%\Microsoft\WinGet\Packages\Rnwood.Smtp4dev_*
  

---

Investigation / Findings

• The executable exists:

  Rnwood.Smtp4dev.exe
  

• Winget reports:

  Command line alias added: "Rnwood.Smtp4dev"
  

• However:

  • No working smtp4dev.exe shim exists in:

    %LOCALAPPDATA%\Microsoft\WinGet\Links
    

  • The alias name does not match expected CLI usage (smtp4dev)

  • The binary name (Rnwood.Smtp4dev.exe) differs from expected command (smtp4dev)

---

Workaround

Manually create a PowerShell function:

make new file if needed

notepad $PROFILE

function smtp4dev {
    & "$env:LOCALAPPDATA\Microsoft\WinGet\Packages\Rnwood.Smtp4dev_*\Rnwood.Smtp4dev.exe"
}

Or how we have it on our system

function smtp4dev {
    & "$env:LOCALAPPDATA\Microsoft\WinGet\Packages\Rnwood.Smtp4dev_Microsoft.Winget.Source_8wekyb3d8bbwe\Rnwood.Smtp4dev.exe"
}

Reload:

. $PROFILE

---

This appears to be either:

• a packaging issue in the winget manifest, or
• a failure in alias/shim creation during install

---

[Rockerby]

I had this today during a fresh installation too.