CoreWidgetProvider.HelpersSystemData exception

[darioinova]

Dev Home version

0.1501.533.0

Windows build number

10.0.22631.3810

Other software

OS Build Version: 10.0.22631.3810.amd64fre.ni_release.220506-1250
.NET Version: .NET 8.0.5

Steps to reproduce the bug

Just opening the Dashboard with the CPU widget

Expected result

show the GPU widget correctly

Actual result

The type initializer for 'CoreWidgetProvider.HelpersSystemData' threw an exception.

Included System Information

CPU: 12th Gen Intel(R) Core(TM) i7-1265U
Physical Memory: 15.69GB (0.76GB free)
Processor Architecture: x64

Included Extensions Information

Extensions:
Microsoft.Windows.DevHome_0.1501.533.0_x64__8wekyb3d8bbwe (Core Widget Extension)
Microsoft.Windows.DevHome_0.1501.533.0_x64__8wekyb3d8bbwe (Hyper-V Extension)
Microsoft.Windows.DevHomeGitHubExtension_0.1500.533.0_x64__8wekyb3d8bbwe (Dev Home GitHub Extension (Preview))
Microsoft.Windows.DevHomeAzureExtension_0.1000.533.0_x64__8wekyb3d8bbwe (Dev Home Azure Extension (Preview))

Widget Service:
MicrosoftWindows.Client.WebExperience_524.13200.30.0_x64__cw5n1h2txyewy

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• The type initializer for 'CoreWidgetProvider.Helpers.SystemData' threw an exception on Windows 10 and 11. (#3259), similarity score: 0.87
• "We're having trouble displaying widgets. Restarting Dev Home may help." error when launching Dev Home on Windows 10 and 11 (#2945), similarity score: 0.77

Closed similar issues:

• The type initializer for 'CoreWidgetProvider.Helpers.SystemData' threw an exception. (#2673), similarity score: 0.89

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[krschau]

Duplicate of #3259

[microsoft-github-policy-service]

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!