Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Environments reliability] Hyper-V Operations: Can't add standard user account to Hyper-V Administrator group if elevating using a separate administrator account #3112

Closed
hollowdrutt opened this issue Jun 4, 2024 · 1 comment · Fixed by #3532 or #3589
Assignees
Labels
Area-Environments Issue-Bug Something isn't working or needs investigation Priority-2 Resolution-Fix-Available Available in a release Type-Reliability Related to stability and reliability

Comments

@hollowdrutt
Copy link

Dev Home version

0.1401.505.0

Windows build number

10.0.22635.0

Other software

No response

Steps to reproduce the bug

  • On my computer I have one standard user account and one administrator user account.
  • When I run Dev Home as standard user and try to create an environment I get the message "The current user is not in the Hyper-V administrators group."
  • I click the "Add user to group"-button, get a UAC prompt asking for an administrator account, I authenticate with my administrator account, the error message about "The current user is not in the Hyper-V administrators group." disappears.

Expected result

My user is added to Hyper-V administrators group and I am able to create an environment.

Actual result

When I once again try to create an environment I get the same message "The current user is not in the Hyper-V administrators group.".
When I start lusrmgr.msc and look in the Hyper-V Administrators group only my administrator account is added to it, probably because the PowerShell script adds my administrator account instead of my user account to Hyper-V Administrator group.

Included System Information

No response

Included Extensions Information

No response

@hollowdrutt hollowdrutt added the Issue-Bug Something isn't working or needs investigation label Jun 4, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage New issue that the core contributors need to triage label Jun 4, 2024
@kanismohammed kanismohammed added Priority-2 and removed Needs-Triage New issue that the core contributors need to triage labels Jun 5, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the In-PR This issue has a related PR label Aug 6, 2024
@krschau krschau added Resolution-Fix-Committed Fix is checked in, but may take 3-4 weeks before it's in a release and removed In-PR This issue has a related PR labels Aug 14, 2024
@krschau krschau added this to the Dev Home v0.17 milestone Aug 14, 2024
@huzaifa-d huzaifa-d reopened this Aug 16, 2024
@huzaifa-d
Copy link
Contributor

Fix not working in latest canary. Will need to investigate.

@huzaifa-d huzaifa-d removed the Resolution-Fix-Committed Fix is checked in, but may take 3-4 weeks before it's in a release label Aug 16, 2024
@bbonaby bbonaby added the Type-Reliability Related to stability and reliability label Aug 21, 2024
@bbonaby bbonaby changed the title Can't add standard user account to Hyper-V Administrator group if elevating using a separate administrator account [Environments reliability] Can't add standard user account to Hyper-V Administrator group if elevating using a separate administrator account Aug 21, 2024
@bbonaby bbonaby changed the title [Environments reliability] Can't add standard user account to Hyper-V Administrator group if elevating using a separate administrator account [Environments reliability] Hyper-V Operations: Can't add standard user account to Hyper-V Administrator group if elevating using a separate administrator account Aug 21, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the In-PR This issue has a related PR label Aug 21, 2024
@krschau krschau added Resolution-Fix-Committed Fix is checked in, but may take 3-4 weeks before it's in a release and removed In-PR This issue has a related PR labels Sep 3, 2024
@krschau krschau added Resolution-Fix-Available Available in a release and removed Resolution-Fix-Committed Fix is checked in, but may take 3-4 weeks before it's in a release labels Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Environments Issue-Bug Something isn't working or needs investigation Priority-2 Resolution-Fix-Available Available in a release Type-Reliability Related to stability and reliability
Projects
None yet
5 participants