Hyperv driver privilege checks fail

#### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

When filing a bug, please include the following headings if possible. Any
example text in this template can be deleted.

#### Overview of the Issue

"Failed creating Hyper-V driver: Current user is not a member of 'Hyper-V Administrators' or 'Administrators' group"

#### Reproduction Steps

Run Hyperv-iso driver on Windows

### Packer version

v1.14.2

### Simplified Packer Template

any

### Operating system and Environment details

Windows 11 Pro

### Log Fragments and crash.log files

==> Some builds didn't complete successfully and had errors:
Build 'hyperv-iso.amd64_builder' errored after 887 milliseconds 268 microseconds: Failed creating Hyper-V driver: Current user is not a member of 'Hyper-V Administrators' or 'Administrators' group
2025/11/02 09:27:00 machine readable: hyperv-iso.amd64_builder,error []string{"Failed creating Hyper-V driver: Current user is not a member of 'Hyper-V Administrators' or 'Administrators' group"}
==> Builds finished but no artifacts were created.

No source file, test, or entry point is named. Reproduce the Hyper-V ISO driver failure on Windows 11 with the provided Packer version, then locate the privilege check and add focused coverage for the reported group-membership case. Done means valid users can create the Hyper-V driver without the reported false failure.

Written by the indexing model from the issue text.