Install State Unknown for all Applications installed during UDI Task Sequence


  • When the UDI Task Sequence finishes, a final "Deployment Complete" window is shown with three tabs (Welcome, Deployment Summary and Applications Installed) and a Start Windows button at the bottom. When I click on the "Applications Installed" tab, all applications have a yellow warning indicating "Install State Unknown" even though every application installs successfully without any errors in the logs. Also there is no SuccessOrFailureCode shown when expanding each application. These same applications install fine via normal deployments (post imaging) and using standard Task Sequences (Install Application step).  

    • Edited by scarneol Wednesday, June 06, 2012 9:50 PM
    Wednesday, June 06, 2012 11:41 AM

All replies

  • Yep, I have that same "error"

    Are you using SCCM 2012 and installing actual Applications or still using Packages?


    Friday, June 15, 2012 7:48 AM
  • Using SCCM 2012 and Applications. The only Packages I have in my SCCM 2012 environment are the Client Installation and the 3 MDT Packages that are required for MDT Task Sequence Integration.    
    Friday, June 15, 2012 11:25 AM
  • I'm having the exact same issue.  I'm using SCCM 2007 SP2, MDT 2012 (6.0.2223.0).  Would really like someone to shed some light on this.  This has become my worst nightmare.  Any help would be appreciated.

    Thursday, July 05, 2012 12:18 AM
  • Anyone find an answer to this?  Still happening with 2012 update1
    Monday, August 27, 2012 4:47 AM
  • I saw the same issue with applications that didn't have MSI product code detection rules. Looks like UDI relies on this detection logic. I have not seen an answer for App-V application types.


    Friday, May 10, 2013 2:12 PM
  • Is there any workaround for non msi installations yet ?

    Thursday, July 11, 2013 8:18 AM
  • I'm seeing this on application model only, packages seem fine.

    Any workaround has been found by any chance? (sccm 2012 r2, mdt 2013)


    Tuesday, July 14, 2015 8:11 PM
  • Exact same issue here. Using MDT 2013 Update 2 and SCCM 2012 R2 SP1 CU3. Rebuilt the UDI wizard in case there have been changes since 2013 Update 1 but still getting the same problem. Although for some reason my powershell script to install Java 7 does report successful (it is an Application not a package). The worst part is that some apps aren't installing successfully, so my technicians have to check each deployed workstation to make sure the apps they expected to have installed made it.

    Has there been any workarounds discovered in the last 3.5 years?

    Thursday, January 21, 2016 3:18 PM
  • Hi there,

    We also have the same issue still on MDT 2012 Update 2...


    Friday, September 16, 2016 11:29 AM
  • We have also got the same problem in  the new SCCM 2016 edition, the issue was not in the SCCM 2012 R2 (1511) realese, but after we migrated to the 2016 finished version, we have got this issue, but only for the packages not for the applications.

    Some of you say that you have Toolkit update 1, there is an update 2 out there:

    Wednesday, November 02, 2016 2:32 PM
  • I think I found the solution - or this worked for me, on the 2016 edition on the SCCM, with Toolkit 2013 Update 2.

    I first tried this link out:

    That got me to get the Name being displayed.

    For the Warning sign to go-away I found out that under my UDI Wizard Designer- Application point in the "" file which is placed here: %Point_of_where_you_have_placed_your_Toolkit_package%\MDT ToolKit Files 2013 Update 2\Scripts\UDIWizard_Config.xml

    -> Application Page -> "mark the application not packages" and then under the "Mappings"

    I found out that they were missing the MSI mappings, which is the "Detection Method" that is being use to confirm that the giving program ahs been installed or not. anyway that MSI value was missing. when that was inserted and alle the DP's  was updated with the new content from the Toolkit packages we did not have the unknown or the warning sign anymore.

    Just remember that if the applications dont have a MSI detection methods, you have to create them as packages also because else the warnings signs for that application program will not go away.

    Thursday, November 03, 2016 12:34 PM