MMC has detected an error in the snap-in and will unload it.

Question

at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileSystemEnumerableIterator1.CommonInit() at System.IO.FileSystemEnumerableIterator1..ctor(String path, String originalUserPath, String searchPattern, SearchOption searchOption, SearchResultHandler`1 resultHandler, Boolean checkHost)
at System.IO.Directory.GetFiles(String path)
at Microsoft.BDD.Core.DeploymentTools.GetFeaturePacks(String platform, String deploymentSharePath)
at Microsoft.BDD.Workbench.DeployWindowsPE.RefreshData()
at Microsoft.ManagementConsole.SnapInBase.ProcessNotification(Notification notification)
at Microsoft.ManagementConsole.NamespaceSnapInBase.ProcessNotification(Notification notif)
at Microsoft.ManagementConsole.Internal.SnapInClient.Microsoft.ManagementConsole.Internal.IMessageClient.ProcessNotification(Notification notification)
at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessNotification(Notification notification)
at Microsoft.ManagementConsole.Executive.SnapInNotificationOperation.ProcessNotification()
at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)

I get an error when trying to look at my PE settings after I just did a new install of our PXE server. I am trying to get Windows 11 up and working, but when I go to setup the PE settings I cannot do anything with Deployment workbench.

Answer 1

Hello

Thank you for posting in Microsoft Community forum.

The error message you’re seeing is related to the Microsoft Management Console (MMC) encountering an issue with a snap-in, which in this case appears to be related to the Deployment Workbench. This could be due to a variety of reasons, such as file corruption or issues with the .NET Framework.

Here are some steps you can try to resolve this issue:

Check for System File Corruption: Use the System File Checker tool to repair missing or corrupted system files. You can do this by opening Command Prompt as an administrator and typing sfc /scannow.

Perform a DISM Scan: The Deployment Image Servicing and Management (DISM) tool can fix Windows corruption errors. Open Command Prompt as an administrator and type DISM /Online /Cleanup-Image /RestoreHealth.

Reinstall MMC Snap-ins: If the issue is specific to the snap-in, reinstalling it might help. This would involve uninstalling and then reinstalling the feature related to the snap-in.

Update the .NET Framework: The MMC relies on the .NET Framework, so ensuring you have the latest version installed could resolve the issue.

Check Permissions: Ensure that you have the necessary permissions to access and modify the files or services related to the snap-in.

If these steps don’t resolve the issue, it might be helpful to look at the specific error messages and codes in the MMC crash details. These could provide more insight into what’s causing the issue.

It may be helpful to refer to the following documents:

Deployment Workbench Crashes when opening the Win PE tab in properties? - Microsoft Q&A

[SOLVED] MDT Deployment Workbench force closes when trying to create ISO - Windows Server (spiceworks.com)