devhome icon indicating copy to clipboard operation
devhome copied to clipboard

dev drive

Open thenetwork01 opened this issue 1 year ago • 1 comments

Dev Home version

0.1901.687.0

Windows build number

10.0.26100.2894

Other software

OS Build Version: 10.0.26100.2894.amd64fre.ge_release.240331-1435 .NET Version: .NET 8.0.10

Steps to reproduce the bug

set up dev drive in dev home

Expected result

initiate dev drive

Actual result

error Failed to generate the initial creation form

Included System Information

CPU: 13th Gen Intel(R) Core(TM) i9-13980HX Physical Memory: 63.64GB (48.88GB free) Processor Architecture: x64

Included Extensions Information

Extensions: 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) Microsoft.Windows.DevHomeAzureExtension_0.1300.624.0_x64__8wekyb3d8bbwe (Dev Home Azure Extension (Preview)) Microsoft.Windows.DevHomeGitHubExtension_0.1800.625.0_x64__8wekyb3d8bbwe (Dev Home GitHub Extension (Preview)) 9932MartCliment.WingetUIWidgets_0.7.0.0_x64__g91dtg5srk15g (Widgets for UniGetUI) Microsoft.DevHomeMicrosoftGameDevExtension_0.500.669.0_x64__8wekyb3d8bbwe (Dev Home Microsoft Game Dev Extension (Preview))

Widget Service: MicrosoftWindows.Client.WebExperience_524.34401.20.0_x64__cw5n1h2txyewy Microsoft.WidgetsPlatformRuntime_1.6.1.0_x64__8wekyb3d8bbwe

thenetwork01 avatar Jan 19 '25 07:01 thenetwork01

We've found some similar issues:

  • #837 , similarity score: 82%
  • #929 , similarity score: 81%

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 Jan 19 '25 07:01 similar-issues-ai[bot]

Duplicate of #4019

krschau avatar Apr 28 '25 15: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!