Merge pull request #8686 from MicrosoftDocs/main

Auto push to live 2025-04-10 02:00:02

Author: Deland-Han

support/mem/configmgr/os-deployment/os-deployment-task-sequence-not-continue.md

@@ -1,9 +1,9 @@
 ---
 title: An OS deployment task sequence doesn't continue
 description: Describes an issue in which a task sequence doesn't continue after Windows Setup or the in-place upgrade finishes if an OEM product key is used during Windows deployment.
-ms.date: 02/11/2025
+ms.date: 04/10/2025
 ms.custom: sap:Operating Systems Deployment (OSD)\Operating System In-place Upgrade Deployments
-ms.reviewer: kaushika, frankroj, Jowiswel
+ms.reviewer: kaushika, frankroj, Jowiswel, frankroj
 ---
 # An OSD task sequence doesn't continue after Windows Setup or an in-place upgrade finishes
 
@@ -36,7 +36,7 @@ These issues usually occur when you deploy a nonenterprise edition of Windows, s
 
 ## Cause
 
-These issues occur because an OEM product key is used during Windows deployment. When an OEM product key is used, **Setupcomplete.cmd** is disabled. This behavior occurs in both Windows 8.1 and Windows 10. See the following information from [Windows Deployment Issues](/previous-versions/windows/it-pro/windows-8.1-and-8/hh825613(v=win.10)#windows-deployment-issues):
+These issues occur because an OEM product key is used during Windows deployment. When an OEM product key is used, **Setupcomplete.cmd** is disabled. This behavior occurs in both Windows 10 and Windows 11. See the following information from [Windows Deployment Issues](/previous-versions/windows/it-pro/windows-8.1-and-8/hh825613(v=win.10)#windows-deployment-issues):
 
 - [September 2012] Changes in Out-Of-Box (OOBE) Experience
 

support/power-platform/dataverse/working-with-solutions/media/missing-dependency-on-solution-import/application-update.png

@@ -1,24 +1,26 @@
 ---
 title: Missing dependencies during solution import in Power Apps
 description: Works around an issue about missing dependencies that occurs when you import a solution in the target environment in Microsoft Power Apps.
-ms.reviewer: jdaly
-ms.date: 09/25/2023
+ms.reviewer: matp
+ms.date: 04/10/2025
 author: swatimadhukargit
 ms.author: swatim
 ms.custom: sap:Working with Solutions\Dependencies prevent a solution import
 ---
 # Missing dependencies error during solution import
 
-This article provides a workaround for an issue about missing dependencies that occurs when you [import a solution](/powerapps/maker/data-platform/import-update-export-solutions) in Microsoft Power Apps. You can't proceed with the solution import until the missing dependencies are resolved.
+This article provides a workaround for an issue about missing dependencies that occurs when you [import a solution](/powerapps/maker/data-platform/import-update-export-solutions) in Microsoft Power Apps.
 
 _Applies to:_   Power Platform, Solutions
 
 ## Symptoms
 
-When you try to import a solution in [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc), you receive an error message like the following one:
+When you try to import a solution in Power Apps, you receive an error message like the following one:
 
 > Import failed due to missing dependencies.
 
+You can't proceed with the solution import until the missing dependencies are resolved.
+
 ## Cause
 
 The solution has dependencies on a component that exists in the source environment where the solution is deployed. However, the component doesn't exist in the target environment where the solution is imported.
@@ -27,36 +29,54 @@ This issue might occur when applications are upgraded to the latest version thro
 
 ## Workaround
 
+> [!IMPORTANT]
+> The experience described here might not be available to the environments of all the regions yet.
+
 To work around this issue, follow these steps:
 
 1. Select the **Show dependencies** button to navigate to the **Missing dependencies** page.
 
-    The **Missing dependencies** page lists all the components that are missing from the target environment. It also shows the solution or application from which the component dependencies are obtained.
+    This page lists all missing components and categorizes them into **Applications**, **Managed Solutions**, and **Unmanaged Components**.
 
-2. Resolve this issue based on the different types of dependencies described in the following sections:
+    > [!TIP]
+    > Another method to find dependencies of components is to open the solution file, unzip it, and then open the *solution.xml* file. In the file, look for the `<MissingDependencies>` element that lists all missing dependencies.
+
+2. Expand each section of dependencies and resolve the issue based on the type of dependencies described in the following sections. Once the missing dependencies are fixed, retry the import.
 
 ### Missing dependencies coming from a Dynamics 365 application
 
-You can find these dependencies in the **Managed Solution** tab of the **Missing dependencies** page. To resolve this issue:
+This issue occurs when the solution relies on components from Dynamics 365 applications that are missing or outdated in the target environment. You can find these dependencies in the **Applications** section of the **Missing dependencies** page. Each entry provides details about the missing application in the following format:
+
+_<solution_name> (<solution_version>) from <application_name>_
 
-- If the application isn't installed in the target environment, [install the application](/power-platform/admin/manage-apps#install-an-app) from the Power Platform admin center.
-- If the application is installed but has an outdated version, a link is provided next to the solution. This link will redirect you to the Power Platform admin center update page for the environment where you can update the application to resolve the issue.
+Next to the application name, you'll find an **Install** or **Update** button that redirects you to the Power Platform admin center.
 
-  The following screenshot shows the link provided on the **Missing dependencies** page.  
+:::image type="content" source="media/missing-dependency-on-solution-import/missing-dependencies-applications-section.png" alt-text="Screenshot that shows the Applications section of the Missing dependencies page." lightbox="media/missing-dependency-on-solution-import/missing-dependencies-applications-section.png":::
 
-  :::image type="content" source="media/missing-dependency-on-solution-import/missing-dependency.png" alt-text="Example of the application upgrade link for a component with missing dependencies." lightbox="media/missing-dependency-on-solution-import/missing-dependency.png":::
+ To resolve this issue:
 
-  Select the link to open the upgrade application page in the Power Platform admin center.
+- If the application isn't installed in the target environment:
 
-  :::image type="content" source="media/missing-dependency-on-solution-import/application-update.png" alt-text="Example of the upgrade application page in the Power Platform admin center." lightbox="media/missing-dependency-on-solution-import/application-update.png":::
+  - System administrators can use the **Install** button, which redirects to the [application installation](/power-platform/admin/manage-apps#install-an-app) page in the Power Platform admin center. Choose and install the application.
+  - Non-system administrators can use the **Copy Install Link** button to copy the application installation link and request their system administrator to install the application. Alternatively, a system administrator can directly go to the [application installation](/power-platform/admin/manage-apps#install-an-app) page to install the application in the Power Platform admin center.
 
+- If the application is installed but outdated in the target environment:
+
+  - System administrators can use the **Update** button to open the application update page in the Power Platform admin center.
+  - Non-system administrators can use the **Copy Update Link** button to copy the application update link and request their system administrator to update the application.
+  
 ### Missing dependencies coming from another managed solution
 
-You can find these dependencies in the **Managed Solution** tab of the **Missing dependencies** page. To resolve this issue, import the same version of the solution that's installed in the source environment into the target environment.
+This issue occurs when the solution relies on components from another managed solution that's missing in the target environment. You can find these dependencies in the **Managed Solutions** section of the **Missing dependencies** page. Expanding the section provides additional details.
+
+:::image type="content" source="media/missing-dependency-on-solution-import/missing-dependencies-managed-solutions-section.png" alt-text="Screenshot that shows the Managed Solutions section of the Missing dependencies page." lightbox="media/missing-dependency-on-solution-import/missing-dependencies-managed-solutions-section.png":::
+
+To resolve this issue, import the same version of the solution that's installed in the source environment into the target environment.
 
 ### Missing dependencies on the "Active" solutions
 
-You can find these dependencies in the **Objects** tab. This indicates that the dependency is from unmanaged customization in the source environment. To resolve this issue, return to the source environment, include the missing components, export the solution again, and then import it into the target environment.
+This issue occurs when the solution relies on unmanaged customizations from the source environment that are missing in the target environment. You can find these dependencies in the **Unmanaged Components** section of the **Missing dependencies** page. Expanding the section provides additional details.
+
+:::image type="content" source="media/missing-dependency-on-solution-import/missing-dependencies-unmanaged-components.png" alt-text="Screenshot that shows the Unmanaged Components section of the Missing dependencies page." lightbox="media/missing-dependency-on-solution-import/missing-dependencies-unmanaged-components.png":::
 
-> [!TIP]
-> Another method to find dependencies of components is to open the solution file, unzip it, and then open the *solution.xml* file. In the *solution.xml* file, look for a `<MissingDependencies>` element. All the missing dependencies are listed within this node.
+To resolve this issue, return to the source environment, include the missing components, export the solution again, and then import it into the target environment.