WACK generates errors

Heiko 1,211 Reputation points
2022-08-25T12:45:29.073+00:00

I completely reinstalled Windows 11 Pro into a new VM, installed all updates, and then installed VS 2022 Community 17.3.2.

Then I created an empty UWP project, with a 'Hello World!' TextBlock. I associated the app with a store app and was able to create the package bundle (file TestApp1_1.0.1.0_x86_x64_arm_arm64_bundle.msixupload).

After that I started the test with the WACK tool. I have the WACK version 10.0.19041.685. Unfortunately the WACK test does not pass. Normally the app is started 3 times during this process. At the first time it is started only briefly and during the display of the splash screen it is already closed again. On the 2nd and 3rd start of the app, 'Hello World!' becomes visible and the app stays open for a few seconds.

The following outputs can be seen in the WACK log (translated from german):

**Deployment and launch tests**  
  
FAILED  
Platform version startup  
Error: The following errors were detected while checking the high operating system version:  
App cannot be launched.  
App cannot be launched.  
The app "Aaaaaaaaaaa.MyApp_1.0.1.0_x64__xxxxxxxxxxx" failed the platform version startup test.  
Impact if not fixed: The app should not use version information to provide functionality specific to the operating system.  
Remediation method: Check the available operating system functionality using the recommended methods. For more information, see the following link.  
  
PASSED  
App launch  
  
FAILED  
Crashes and hangs  
Error: The following errors were detected while testing crashes and hangs:  
C:\Program Files\WindowsApps\Aaaaaaaaaaa.MyApp_1.0.1.0_x64__xxxxxxxxxxx\TestApp1.exe executable was detected by Windows error reporting. A crash or blockage has occurred.  
Application Aaaaaaaaaaa.MyApp_1.0.1.0_x64__xxxxxxxxxxx has been detected by Windows error reporting. A crash or blockage has occurred.  
The memory dump file "C:\Users\Egon\AppData\Local\Microsoft\AppCertKit\TestApp1.exe.5540.dmp" was created by Windows error reporting. It contains additional information.  
Impact if not fixed: An app that hangs or crashes may cause data loss and is not user-friendly.  
Remediation method: Examine and debug the app to identify and fix the error.  

I have replaced the app identifier here with 'Aaaaaaaaaaaaa.MyApp_1.0.1.0_x64__xxxxxxxxxxx'. The app can of course be started error-free in VS.

What to do? Should I just ignore the two errors?

Universal Windows Platform (UWP)
Visual Studio
Visual Studio
A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.
4,595 questions
{count} votes

Accepted answer
  1. Roy Li - MSFT 31,681 Reputation points Microsoft Vendor
    2022-08-30T08:18:23.673+00:00

    Hello,

    Welcome to Microsoft Q&A!

    The local WACK tool will be affected by many reasons of the local device. And it's hard to say what is the reason. That's why the local WACK test is optional. There is an online WACK test when you upload your app to the Store. The Store only take the result of the online WACK test as result. The local WACK test failed might not be a problem, but if the online WACK test failed, that will be a problem

    Thank you.


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

0 additional answers

Sort by: Most helpful