Windows Server

Unable to execute: The application GUID not found in the application list

The Microsoft Deployment Toolkit (MDT) is a free tool for automating Windows and Windows Server operating system deployment, leveraging the Windows Assessment and Deployment Kit (ADK) for Windows 10. It is primarily used to deploy images to a large number of physical machines and can be downloaded from this link. When running a deployment, the following error below can be displayed due to many reasons. I will be discussing the reasons and how to resolve this issue in this guide.

Here are some articles relating to how to determine application GUID. Single App Kiosk Mode Configuration using MDM Bridge WMI Provider, Package Full Name: How to determine Apps UWP and remove pre-provisioned appx in Windows 10 and How to set up a Single App Kiosk Mode Configuration using a Local Account / MDM Bridge WMI Provider.

The "Error, the application GUID {xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx} not found in application list: Unable to execute" was prompted because of dependencies configured for the application.
– Note: The application GUID was not present in the MDT Deployment Share Rule (it was removed) and also in the application list.
– It was not also present in the Deployment Share Application folder.

To fix this issues, kindly follow the steps outlined below.
– Expand your deployment share
– Click on the Application
– Right click on the specific application and select properties
– On the dependency tab, search for the GUID and remove it.

If the steps defined above does not help in resolving your issues, then it is most likely that the issue is as a result of a residual GUID laying around in the application.xml file in which the dependency is deleted.

Before proceeding with this step, ensure you backup the Application.xml file.
– Next, on your Click on your Deployment Share folder
– Expand the Control folder and
– Double click on the Applications.xml file to edit it. (I recommend using a text editor for this steps. You could use XML Editor).
– Next, search for the GUID from the error screen using the find dialog box.
– You now click on the Dependency associated with this GUID and delete it. Be sure to search for the GUID multiple times for this.

Other things you could look at for;
1: Remove the application in the MDT deployment share rule if it is there. This rule can be found by right clicking on your task sequence. On the rule tab, locate the application with the GUID and remove it.

– Alternatively, you can right click on the application in MDT, disable it and hide it as shown below if you do not want to remove it completely.


2: Most times, you may have to generate a new Lite Touch Boot image by updating your deployment share. In this way, you will be eliminating any potential issues that are present in the old boot file. Therefore, update your deployment share in order to generate a new Lite Touch Image and then replace the boot image on WDS. On how to perform these steps correctly, visit the following link.

I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.

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