logo logo

The next-generation blog, news, and magazine theme for you to start sharing your stories today!

The Blogzine

Save on Premium Membership

Get the insights report trusted by experts around the globe. Become a Member Today!

View pricing plans

New York, USA (HQ)

750 Sing Sing Rd, Horseheads, NY, 14845

Call: 469-537-2410 (Toll-free)

hello@blogzine.com

Fix Deployment Workbench Crashing Issue When Accessing WinPE Tab Properties

avatar
Louis Ferguson

An editor at Blogzine


  • 🕑 4 minutes read
  • 3 Views
Fix Deployment Workbench Crashing Issue When Accessing WinPE Tab Properties

The Microsoft Deployment Toolkit (MDT) Workbench features a user-friendly graphical interface designed for managing various deployment tasks. Through this interface, users can configure deployment shares, create task sequences, and add essential drivers and updates, as well as tailor the deployment process to their needs. Yet, at times users encounter an issue where the Deployment Workbench freezes when attempting to access the WinPE tab properties. In this article, we will explore effective methods to fix this problem.

Microsoft Deployment Workbench

MMC has identified an error in one of its snap-ins and will proceed to unload it.

Please report this error to Microsoft, and then terminate the MMC.

Unload the snap-in and continue operating.

Deployment Workbench crashing when opening WinPE tab Properties

How to Fix the Crash of Deployment Workbench When Accessing WinPE Tab Properties

If you’re facing crashes of Deployment Workbench while trying to access the WinPE tab properties, implement the following solutions:

  1. Create an x86 directory
  2. Download and install a previous version of Windows PE
  3. Remove Profile files
  4. Repair MDT Deployment Workbench

Let’s break down each solution in detail.

1] Create an x86 Directory

When faced with an error alert, it’s prudent to select the “Unload the snap-in and continue running”option and confirm by clicking OK. This step will provide insight into the error, revealing that a required file cannot be located. Hence, it’s necessary to capture the file path specified in the error.

Usually, the system will be searching for an x86 (32-bit) directory, which is typically missing in newer releases of the MDT Workbench. To remedy this, one can replicate the 64-bit directory and rename it to x86, tricking the Workbench into believing it can access the correct location.

To execute this, launch File Explorer and navigate to the copied location. You likely won’t spot an x86 directory, so create a duplicate of the 64-bit folder (often labeled as amd64) and rename it to ‘x86′.

Once complete, the WinPE tab properties should open without issues. However, since these are 64-bit files, head over to MDT Deployment Share Properties, access the General tab, uncheck the x84 option from the Supported Platforms section, and save your modifications. Finally, verify whether this resolves the issue.

2] Download and Install an Older Version of Windows PE

Although you might access WinPE properties using the preliminary workaround mentioned, bear in mind that it won’t function effectively on a 32-bit system, as this capability has been phased out in the latest MDT deployments. Fortunately, there is an add-on available for download to fix this issue. Follow these steps:

  1. Visit learn.microsoft.com.
  2. Search for the Windows PE add-on for the ADK, version 2004, and click the provided link to access the download.
  3. Next, go to Settings > Apps > Installed apps, and uninstall the current version of Windows Assessment and Deployment Kit Windows Preinstallation Environment Add-ons.
  4. Then install the add-on you just downloaded.

Finally, accessing the WinPE tab in the Deployment toolkit should work seamlessly, including compatibility with 32-bit systems.

3] Remove Profile Files

Changes made to the Deployment Workbench might not take effect due to the presence of outdated profile files. Deleting these files is recommended to ensure your changes are implemented. Here’s how to do it:

  1. Launch Deployment Workbench by searching for it via the Start Menu.
  2. Select File > Options.
  3. Click on Delete files.
  4. A confirmation prompt will appear; select Yes to proceed.

Wait briefly while the files are deleted. Afterward, restart your PC and check if the problem persists.

4] Repair MDT Deployment Workbench

In addition to removing profile files, consider running the repair function for Deployment Workbench after the aforementioned changes (or execute the repair before implementing any changes) to see if this alleviates the issue. Follow these guidelines:

For Windows 11

  1. Open Settings.
  2. Navigate to Apps > Installed apps.
  3. Search for “Deployment Workbench” , click on the three dots, and choose Modify.

For Windows 10

  1. Access Settings.
  2. Go to Apps > Apps & features.
  3. Select “Deployment Workbench” , click the tool, and then choose Change/Modify.

Click on Repair and follow the prompts displayed on-screen to finish the procedure. Once completed, close the Deployment Workbench via Task Manager and check if the issue is resolved.

With the solutions outlined above, you should be able to troubleshoot and resolve the crashing issue.

Why Does MySQL Workbench Keep Crashing?

MySQL Workbench can be resource-intensive; if it crashes, you should examine if other background processes are consuming excessive system resources. To check this, open Task Manager and review the Processes tab. If another application is using a significant amount of CPU or memory, terminate that process before re-launching MySQL Workbench.

How to Speed Up MySQL Workbench?

To enhance the performance of MySQL Workbench, ensure you are using the latest version of the application. Additionally, consider modifying the my.cnf file to allocate more memory to MySQL and prioritize effective indexing and query optimization.

Source



Leave a Reply

Your email address will not be published. Required fields are marked *