Welcome to Microsoft Q&A!
Thank you for taking the time to document this behavior and the troubleshooting you have already performed.
Based on the behavior you described, this does not appear to be a general remote-management, permissions, or ISO-access issue. Hyper-V Manager supports managing remote Hyper-V hosts, and Hyper-V provides supported methods for attaching ISO images to virtual machines.
The key detail from your testing is that the issue occurs specifically when the remote Hyper-V Manager file browser enumerates a parent directory containing a numeric-only subfolder, while:
- Browsing the same location from Hyper-V Manager on the local host works.
- Numeric file names do not reproduce the issue.
- PowerShell and Windows Admin Center can still perform the ISO operation successfully.
- Renaming the numeric-only folder allows remote browsing through Hyper-V Manager to work again.
These results suggest that the issue is isolated to the remote file-browsing path used by Hyper-V Manager rather than the ISO file itself, folder permissions, or general connectivity to the Hyper-V host.
However, I could not find Microsoft documentation stating that numeric-only folder names are unsupported or are a known limitation of Hyper-V Manager. Therefore, I would avoid treating numeric folder names themselves as an officially confirmed root cause.
Based on the available evidence, this is better described as a reproducible behavior that appears to trigger a failure in the remote Hyper-V Manager file browser.
For now, the practical workaround is the one you have already identified: rename numeric-only folders so they contain nonnumeric characters. For example:
- 2012 → Win2012
- 2016 → Win2016
- 2019 → Win2019
- 2022 → Win2022
After renaming the folders, reconnect to the remote Hyper-V host and browse the same parent directory again. If the directory opens normally and mmc.exe no longer crashes in COMDLG32.dll, this provides additional validation that the folder structure is what triggers the issue in this particular remote browsing workflow.
Moreover, you did the right thing by reporting the behavior through Feedback Hub. And I would like to clarify the support boundary here as well.
Microsoft Q&A is a community-based technical support platform. From the forum, I can help review the observed behavior, compare it with documented product functionality, suggest supported troubleshooting, and provide a practical workaround. However, I do not have access through the forum to the product source code, internal crash analysis, or the engineering investigation required to determine exactly why COMDLG32.dll reaches the 0xc00000fd exception in this scenario.
Because of that limitation, I cannot reliably investigate this particular crash further from Microsoft Q&A, confirm that it is a product defect, identify the affected code path, or provide an engineering fix or timeline. Doing so would require product-level investigation beyond what can be performed through the forum.
Currently, keeping the Feedback Hub report and using nonnumeric folder names is the most practical approach while retaining the evidence you collected in case the issue is investigated further.
References: Remotely Manage Hyper-V Hosts | Microsoft Learn
Set-VMDvdDrive (Hyper-V) | Microsoft Learn
Add-VMDvdDrive (Hyper-V) | Microsoft Learn
Hyper-V Virtual Machine Connection | Microsoft Learn
If you find it useful, please click Accept Answer.
Thank you for choosing Microsoft Q&A.