devhome icon indicating copy to clipboard operation
devhome copied to clipboard

Widgets not shown on dashboard

Open pete1854 opened this issue 1 year ago • 1 comments

Dev Home version

0.1901.687.0

Windows build number

10.0.22635.4515

Other software

OS Build Version: 10.0.22635.4515.amd64fre.ni_release.220506-1250 .NET Version: .NET 8.0.10

Steps to reproduce the bug

  1. Install DevHome
  2. Launch DevHome
  3. Show Dashboard

Expected result

Dashboard with widgets (if any are installed)

Actual result

A text: "We're having trouble displaying widgets. Restarting Dev Home may help."

Included System Information

CPU: 13th Gen Intel(R) Core(TM) i9-13900K Physical Memory: 63.71GB (48.03GB free) Processor Architecture: x64

Included Extensions Information

Extensions: Microsoft.Windows.DevHomeGitHubExtension_0.1800.625.0_x64__8wekyb3d8bbwe (Dev Home GitHub Extension (Preview)) Microsoft.Windows.DevHomeAzureExtension_0.1300.624.0_x64__8wekyb3d8bbwe (Dev Home Azure Extension (Preview)) Microsoft.Windows.DevHome_0.1901.687.0_x64__8wekyb3d8bbwe (Core Widget Extension) Microsoft.Windows.DevHome_0.1901.687.0_x64__8wekyb3d8bbwe (Hyper-V Extension) Microsoft.Windows.DevHome_0.1901.687.0_x64__8wekyb3d8bbwe (Windows Subsystem for Linux Extension) Microsoft.Windows.DevHome_0.1901.687.0_x64__8wekyb3d8bbwe (Git)

Widget Service: MicrosoftWindows.Client.WebExperience_524.30502.0.0_x64__cw5n1h2txyewy

pete1854 avatar Dec 02 '24 14:12 pete1854

We've found some similar issues:

  • #3802 , similarity score: 93%
  • #3843 , similarity score: 91%
  • #2945 , similarity score: 90%
  • #3801 , similarity score: 90%
  • #3842 , similarity score: 89%
  • #3259 , similarity score: 85%
  • #914 , similarity score: 82%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

similar-issues-ai[bot] avatar Dec 02 '24 14:12 similar-issues-ai[bot]

Duplicate of #3995

krschau avatar Apr 29 '25 17:04 krschau

We've identified this as a duplicate of another one that already exists. This specific instance is being closed in favor of tracking the concern over on the the linked issue. Please add your 👍 to the other issue to raise its priority. Thanks for your report!