Windows Server

Workaround and Permanent fix for this snap-in performed a non-valid operation and has been unloaded: To continue using this snap-in restart MMC or try loading the snap-in again

windows-pe-screenshot1-rcm1200x0

The Windows Assessment and Deployment Kit (Windows ADK) and Windows PE add-on have the tools you need to customize Windows images for large-scale deployment, and to test the quality and performance of your system, its added components, and the applications running on it. Here are some interesting guides on how to set up and install the WDS role, how to configure Windows Deployment Services on Windows Server 2019, and how to configure DHCP Server option 60, 66, and 67 for Windows Deployment Services. and how to configure Windows Deployment Services on Windows Server 2019.

Windows 11 WinPE does not include the 32-bit Windows PE version any longer. Here is a guide on how to correctly upgrade Windows Assessment and Deployment Kit, Windows Preparation Environment, and Microsoft Deployment Toolkit.

The 32-bit versions of Windows PE are no longer included in the Windows PE add-ons starting with the ADK for Windows 11, version 22H2. The last supported version of 32-bit Windows PE is available in the Windows PE add-on for Windows 10, version 2004. Also, for the complete installation steps of WinPE, please see the following guide: Install ADK, MDT, and WDS: How to deploy Windows images via Microsoft Deployment Toolkit and Windows Deployment Services,

The following error message was displayed when I had to update a deployment share for Win11. “This snap-in performed a non-valid operation and has been unloaded: To continue using this snap-in restart MMC or try loading the snap-in again“.

If you look at the images above, one of them gave a hint of why this error was prompted. Upon clicking on OK, the following Window will be displayed, making the MDT console useable, and you have to restart it.

mdtcrashing

Reason for the error

The installation of Windows WinPE was completed with a missing directory for x86 as you can see below. As you continue to read further, I will show you how this issue was temporarily, and permanently resolved.

MisssigWinPEpath

Workaround: Copy the x86 folder from an existing MDT Server

In order to temporarily resolve this issue, I had to copy the x86 folder from a different deployment server. Afterward, I was able to update my deployment shares without issues.

workaroundforerror

Permanent Fix

Re-initiated the whole process of installing WinPE and Windows ADK again. Following the following order. I uninstalled ADK and WinPE and had the server restarted. This fixed the issue.

After uninstalling WinPE and Windows ADK, it is always recommended to have your server restarted. This is because restarting your device puts it in its default state and runs everything from scratch. This way, your PC gets rid of the trash and delivers better performance after the restart. This restart process resolves issues like RAM leakage, overheating, and incomplete updates/installations.

As you can see below, this is the installation of the Windows Preparation Environment (WinPE) again after the uninstallation.

As you can see below, I am currently re-installation the Windows Assessment and Deployment Toolkit (Windows ADK).

As you can see from the image below, the missing part was included by default after the installation of WinPE.

Noerrors

Note: Also ensure you use the latest Microsoft Deployment Toolkit (MDT). Deploying Windows 11 with MDT is relatively easy. This can be downloaded from the following link.

As you can see, the Microsoft Deployment Toolkit is running as desired. I was now able to update the Deployment share without issues.

UpdateDeploymentsharewithoutissues

I hope you found this blog post helpful. Please let me know in the comment session if you have any questions.

Subscribe
Notify of
guest

0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x