Windows 10: UWP application can't launch in offline mode

We faced a problem with one of our UWP application in offline mode.





When offline, after the UWP install finish, click "Launch", it will report error with "12007" error(Also same problem from the Start Menu). Even we removed the "Internet connection" capabilities, it still failed with the same error. Actually when goto the program installed folder, click the program exe file, it can launch successfully. So we assume the installation is correct, but some other issues. And once the network is connected, it will launch successfully, after that, it will always launch successfully even disconnect network again. We do not found much info about this issue , need some info



:)

 

Launch Path for UWPs

Hi,

I suggest you to refer the article on Launch the default app for a file and check if it helps.

https://msdn.microsoft.com/en-us/windows/uwp/launch-resume/launch-the-default-app-for-a-file

Hope this information is helpful. Please get back to us with the information required, if you need further assistance, we’ll be glad to assist you

 

Launch Path for UWPs

I have a MS wireless keyboard 3000 v2. With the MS mouse and keyboard centre, some of the shortcut keys can be used to trigger specific actions or launch specific apps.

I have not trouble setting shortcuts for win32 apps but not for UWP apps. If I create a shortcut for the UWPs on the desktop and reference to open the UWP via that shortcut I get an catastrophic error prompt.





any ides to launch a UWP?

 

[UWP] all UWP application windows are not displayed anymore after a lot of start/kill of any UWP application

Hello,

This issue seems linked to the Windows Anniversary Update (build 10.0.14393,
also reproduced on build 14905.rs_prerelease.160811-1739) and the new UWP lifecycle introduced with it, since this issue was not there before.

The test scenario is simple:

1. start any UWP application (in my example the windows calc.exe, the default Windows 10 calculator application)

2. wait 0.5 second

3. kill the same UWP application

4. repeat the 1-2-3 steps 5000 times

This scenario is basically reproducing an automated test environment.

The expected result is that the tested application will always be displayed correctly.

The actual result is that the tested application is not displayed anymore after a various number of loops (between 200 and 800). It looks like it is running in the background since the process can be seen in the task manager.

When the UWP application window can't be displayed, the scope of the issue is much more important: no UWP content can be displayed anymore (Edge browser or Windows settings, etc).

The way to recover from this is to log out from the user session and log in again.

Here is a python script to reproduce the issue:

Is it a known issue ? Any way to work around this (this is blocking our UWP automated testing environment)?

BR

Jean-Marc