Hyper-V in environments throwing error about devhome HOT 4 OPEN

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:

• No access to DevBoxes despite being in Hyper-v group (#2989), similarity score: 0.76

Closed similar issues:

• Hyper-V extension crashing in Dev Home Canary (#2835), similarity score: 0.81
• Hyper-V is confusing (#2745), similarity score: 0.78
• Can't select the image of a Hyper-V virtual machine. The field is not displayed (#3000), similarity score: 0.76
• HyperVManager.cs crashes with a powershell error. (#2771), similarity score: 0.76

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

from devhome.

Hey @crutkas, Which error are you talking about exactly? If you mean the request to add the user to the Hyper-v group: I explain why its needed here: #2995 (comment)

from devhome.

Sorry looks like the screenshot didn’t paste in.

This is adding user to hyper-v group

If hyperv manager lets me create / launch / delete without this, dev home should too

from devhome.

We can talk offline about it but we actually can't as the Hyper-V extension would need to run elevated in order to do that. The comment I linked above explains it. But under the hood Hyper-V manager is elevating (without a UAC prompt), by means we can't use in Dev Home. The only other way to allow users to interact with Hyper-V is if they are in the Hyper-V admin group. Once added to this group the users would need to log off/on again or reboot. It's a local users and groups account which is a bit of a special case, as even after being added/removed from the group the users access token that was given to them at logon, does not get updated. The Hyper-v apis are checking the users access token to confirm if they're in the group, which is why we can't just add them and have it all just work as they still won't be able to see/interact with their VMs until they've logged off/rebooted unfortunately:

Heres an excerp from a MS learn doc: How Access Tokens Work | Microsoft Learn which states

If you add a user to a group after the user’s access token has been issued, or modify privileges assigned to the user account, the user must log off and then log on again before the access token will be updated.

from devhome.