microsoft / microsoft/winget-pkgs

[Package Issue]: Microsoft.DevHome = End Of Life (about time)

Open
#218,976 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Bug
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
376

Description

Please confirm these before moving forward
  • I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
  • 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

Please mark Microsoft.DevHome for removal (or freeze) in the manifests repo

because according to the commit
https://github.com/microsoft/devhome/commit/d6d014737e24083c5514852831eff037bd1897b0

  <data name="ShellInfoBar.Message" xml:space="preserve">
    <value>Dev Home will be going away in May 2025 and a subset of its features will be moved to new places. Stay tuned for more information in the following months.</value>
  </data>

and
https://www.theregister.com/2025/01/29/microsoft_dev_home_discontinued/

DevHome is going to be discontinued soon. (yay!.. )

Steps to reproduce
  • DevHome is installed as a random "suprise!!!!" install from Microsoft
  • it then shows up as needing updates when you later do a winget upgrade check and you end up asking yourself "how the f*ck did that got installed YET AGAIN?!"
Actual behavior

DevHome gets randomly reinstalled back even if i keep uninstalling it, and then WinGet picks it up when an update for it becomes available.

Expected behavior

GTFO and stay out!

Environment
environment: Microsoft Windows 10 / 11 + Microsoft Update

(yup... i know that's like saying water is wet but i have no idea why this app thing is getting re-re-re-installed a few times per year and then WinGet starts showing updates for it)
Screenshots and Logs

see https://github.com/microsoft/devhome/issues/1615

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Search the winget-pkgs manifests repository for Microsoft.DevHome and review the referenced Dev Home commit and issue for its end-of-life status. Compare the available removal or freeze conventions, then consider the issue complete when the manifest is handled consistently with that status and no longer produces the reported update entry.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.