Hyper-V Manager ISO file browser on remote host crashes when selected directory contains numeric-only subfolder (0xc00000fd COMDLG32.dll)

Simon Bradley 0 Reputation points
2026-11-15T22:09:24.1666667+00:00

I think the title says it all, this is an answer to my own question really. Apologies if this is bad etiquette, I just wanted to call this one out in case others have seen the same problem. I couldn't find any similar reported problems, or at least nothing with this cause. It's a bit of an edge case but hopefully it may help someone.

Summary: don't use numeric folder names in the directory structure of the ISO files you want to mount to VMs.

I've been using Hyper-V for a home lab for years without issues. After doing some housekeeping I started getting problems mounting ISOs via the Hyper-V Manager GUI: when browsing the ISO folder (just a basic folder structure for my ISO files, mostly operating systems) on the remote Hyper-V host it would throw the error "Application failed to open remote file browser", often resulting in a full crash of mmc.exe (example below). A quick Google and ChatGPT did some basic troubleshooting (NTFS/DCOM permissions, firewall, NTLM settings) but couldn't fix it. I scripted my way round it at first but it bugged me as something so basic should just work and had done for years.

Everything else in Hyper-V manager appeared to work ok, I could connect to the Hyper-V host over PowerShell, SMB, and Computer Manager. I knew it used to work so I thought I'd recreate my ISO folder. It was good until I put my first Windows OS images back. I'd put them in folders named 2012, 2016, 2019, etc. and I thought maybe there was a dodgy ISO file in them. Long story short, even creating an empty folder with a purely numeric name would throw the error when remotely browsing its parent folder via Hyper-V Manager. Numeric filenames, with or without extensions, were fine. The numeric folder could be deep in the folder structure and it would work until you hit the parent folder containing the numeric one. Mounting remotely via script or the Windows Admin Center worked fine with numeric folder names. Browsing from Hyper-V Manager on the local host was also fine.

My main pair of systems is a Win11 25H2 machine with Hyper-V installed, with a remote Win2022 Core Hyper-V host, both fully patched and connected to the same domain. I recreated the problem connecting from the same Win11 to my old Win2019 host, and from a Win2022 GUI server to the Win11, Win2019, and Win2022 hosts so I suspect this is a bug somewhere in Hyper-V Manager, clearly not one many people experience as it appears to have been around for a few years.

Summary fix: I renamed my folders to Win2012, Win2016, etc.

I have reported this via the Feedback Hub but forgot to make it public.

Example corresponding Application Error below.

Faulting application name: mmc.exe, version: 10.0.26100.9818, time stamp: 0xfcb031a7 Faulting module name: COMDLG32.dll, version: 10.0.26100.9974, time stamp: 0x82db8ac5 Exception code: 0xc00000fd Fault offset: 0x000000000009e187 Faulting process id: 0x2EC4 Faulting application start time: 0x1DD75425DB8B79A Faulting application path: C:\WINDOWS\System32\mmc.exe Faulting module path: C:\WINDOWS\System32\COMDLG32.dll Report Id: cb2b71a5-b3fa-4023-91fc-5cd25fa89bd1 Faulting package full name: Faulting package-relative application ID:

Windows for business | Windows Server | Storage high availability | Virtualization and Hyper-V
0 comments No comments

1 answer

Sort by: Oldest
  1. Daphne Huynh (WICLOUD CORPORATION) 2,620 Reputation points Microsoft External Staff Moderator
    2026-11-16T04:52:45.34+00:00

    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.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.