How to make Windows App Certification Kit see a new app? RRS feed

  • Question

  • I would like to validate my Metro App on local machine, like described here:


    but I cannot make the validation tool to see it. Steps to repro are very simple: open VS, create new C# application, build a package, install and... nothing. I can see the app on the Metro start screen and it runs fine.

    I verified with PowerShell as described in another post that the package is correctly installed and I even tried to run validation from command line using packagefullname, without success (the command line approach works for sample applications from Microsoft though).



    • Moved by Bobby L. _Microsoft employee Tuesday, January 3, 2012 9:52 PM tools issue - question (From:Windows Store: Publishing Metro Style apps for Windows 8)
    Saturday, December 31, 2011 8:51 AM

All replies

  • Hey Greg,

    Does this article regarding the validation tool help?



    Sunday, January 1, 2012 12:03 AM
  • Nope, and the article is not updated, we no longer have appcert.exe, the name has changed (we have wslk.exe).

    Also there might be an error, this did not work for me at all:

    [package full name] is the fully qualified file name of the package file to test.

    instead one must use the FullName property of the installed package (find it either through PowerShell or in the Program Files\Applications directory).

    The catch is that the tool works fine for packages signed with Microsoft key (included apps and samples), but reports that other packages cannot be found. The UI version does not display my packages at all, so I cannot select them for validation.

    The repro is easy: use non-Microsoft private developer account, build empty C# application, build  package, install and try to validate it.



    Sunday, January 1, 2012 8:16 AM
  • Having the same issue with my app developed using HTML/JS.  
    Tuesday, January 3, 2012 2:37 AM
  • Hey all,

    I will be moving this thread to the Tools for Metro style apps forum, where they will be able to better assist with this question.

    Thanks for the feedback and your continued testing of Windows Developer Preview.



    Tuesday, January 3, 2012 9:50 PM
  • Hi Greg,

    Thanks for the report. This isn't correct behavior, but we've seen some systems get into this state before. Unfortunately there isn't any known way to get a Developer Preview system which has gotten into this state out of it short of reinstalling. 

    Good catch on the documentation. I'll make sure a doc bug is filed to update it. You can also do so yourself with the feedback tool or connect. There is a section for documentation errors under Windows Kits\Software Development Kit\Documentation inaccuracies.

    If you’re an MSDN subscriber, the information on how to join the Connect program is included on the download page where you installed Windows Developer Preview.  There’s a link to the Connect site and an invitation code that you can click on to join using a Windows Live ID account. If you’re not an MSDN subscriber follow this limited use link to join the Connect program and then follow the steps here.


    • Proposed as answer by 3lun Wednesday, January 4, 2012 6:23 AM
    Tuesday, January 3, 2012 10:40 PM
  • Any follow-up to this problem? Cause I'm having the same problem right now. I have deployed several applications from Visual Studio and also installed some applications from Windows Store. the kit only detected 7-8 apps (of which, three were my deployed HTML apps, none of the C# apps were detected).



    Wednesday, April 11, 2012 7:06 AM
  • Same problem here... any solution?



    Jorge Fioranelli

    Sunday, May 6, 2012 3:33 AM
  • Sunday, May 6, 2012 3:42 AM
  • My problem was working from a Standard Account when you really want to run Windows App Certification Kit (WACK) for Windows Store Apps from an Administrator Account.  If when you run WACK it asks you for a password instead of a simple Yes/No then you could be facing this issue.  No, simply entering your password is not enough.

    First create an App Package using Visual Studio

    • Open your solution in Visual Studio
    • Select your project in Solution Explorer, I have a test project, so select your main.
    • Menu/Store/Create App Store Packages
    • No, for now we don't want to upload.  We are running WACK locally first.
    • Make note of the Output location, you can even copy it.
    • Under solution Configuration you can drop down to Release instead of Debug if you like, otherwise WACK will fail that test, but that's not critical for now.
    • Follow the Wizard until the end.
    • Use Windows Explorer to find your package.
    • Copy the latest version of your package folder.
    • Paste your package folder someplace where your Admin user can get it, using an external drive for example.
    • Logout and back on to your admin account.
    • Explore to your package folder.
    • Right click on 'Add-AppDevPackage' Windows Power Shell Script and run in Power Shell, follow the instructions.
    • This will install the application for your admin user, press the Windows button to return to the Start Screen to observe your app has been installed.
    • You will not have any first time user setup, if you have not run this app for this user before.
    • Now run WACK UI or command line and it will find your application just fine.
    • I passed everything but the Debug Package, as explained above, the first time :)
    • Don't forget, you might need to right click and open your XML file into Internet Explorer to read it well, I was so frustrated by this point I almost forgot this part, lol
    • Even if you run WACK on MS apps from a Standard account they bomb bad, don't get frustrated, try running from an Admin account.

    Chris Ward

    Tuesday, April 23, 2013 4:12 AM