Windows 10: Windows UWP apps fail to start except one.

xXSWAGNEMITE420YOLOXx · Jul 18, 2018

- Hi! I'm Running 1803 and i get this weird error whenever i try to do anything with UWP Related app (Except one: State of Decay 2). It roughly opens up an error box stating "File system error -2147219196". I tried to enforce app re-rollout
Get-AppXPackage | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}
But since then the error code changed from -2147219196 to -2147219195 and im stuck. Any1 help? Below cap from Event Viewer.

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-07-18T22:26:49.914538500Z" />
<EventRecordID>3303</EventRecordID>
<Channel>Application</Channel>
<Computer>*Redacted*</Computer>
<Security />
</System>
- <EventData>
<Data>Microsoft.Photos.exe</Data>
<Data>2018.18051.17710.0</Data>
<Data>5b4c53ea</Data>
<Data>Windows.UI.Xaml.dll</Data>
<Data>10.0.17134.81</Data>
<Data>4f4899f8</Data>
<Data>c000027b</Data>
<Data>00000000006a4e02</Data>
<Data>36d4</Data>
<Data>01d41ee66b4d1fa8</Data>
<Data>C:\Program Files\WindowsApps\Microsoft.Windows.Photos_2018.18051.17710.0_x64__8wekyb3d8bbwe\Microsoft.Photos.exe</Data>
<Data>C:\Windows\System32\Windows.UI.Xaml.dll</Data>
<Data>9ca962c9-e5e4-47c2-a9d2-97914b0eb578</Data>
<Data>Microsoft.Windows.Photos_2018.18051.17710.0_x64__8wekyb3d8bbwe</Data>
<Data>App</Data>
</EventData>
</Event>

:)

Gupta Varun · Jul 18, 2018

Certain apps are crashing upon start. App reset, re-installation nothing seems to help. Any fixes?

The app in question are as follows:

Engadget UWP

Windows Central UWP

CNET (Windows 8 App)

These were working fine in AU.

I have tried App reset and re-installation from store. Nothing seems to help.

Any suggestions?

Brink · Jul 18, 2018

The path from a desktop app to a Universal Windows Platform (UWP) app

Last month, we provided an overview of the Desktop Bridge in this blog post. We are excited to announce that since then we’ve released a new version of the desktop app converter, adding support for great new features and fixing several issues to provide a more stable environment. To learn more about the improvements in the Desktop App Converter, please visit http://aka.ms/converter.

Today, we will follow up with a walkthrough of a concrete coding example that takes an existing desktop app and gradually migrates and enhances it with the Desktop Bridge into a full Universal Windows Platform (UWP) app that can run on all Windows 10 devices—such as Xbox One, HoloLens, phones, et cetera—and take full advantage of the platform.
Our starting point is a simple Windows Forms app that keeps track of the user’s status by storing it in the registry. Essentially, we start with this:

1
2
3
4 private void cmbBox_SelectedIndexChanged(object sender, EventArgs e)
{
MyRegKey.SetValue("Status", cmbBox.SelectedItem);
}

The code for this sample app, as well as the code for each of the steps along the journey across the bridge, can be found in our sample repo on GitHub. As we gradually migrate our app, it remains fully functional every step of the way and picks up additional features that will help keep users engaged.

Step 1: Convert

As a first step to get our app on the bridge, we take it through the conversion process. There are a couple of options to do this initial step. For a simple app like this, which gets installed just by copying binaries, we can quickly perform a manual conversion as explained in this article on Dev Center and demonstrated in this sample on GitHub. Apps that are using a .MSI (or similar) installer should use the Desktop App Converter for the conversion process. Finally, there are several third party install tool providers who are in the process of adding support for the Desktop Bridge to UWP in their products, as well, such as Advanced Installer, FireGiant and InstallShield.

Once the conversion is complete, we want to test, adjust, and enhance our application in Visual Studio. For that, we can take advantage of the project type for UWP packaging, which the Visual Studio team recently introduced for Visual Studio 15 Preview 2 (see this post for details and instructions).

Now we can hit F5 and debug our application running within the UWP app model. With the conversion, a number of immediate platform benefits become available automatically, such as Start menu integration, clean install/update/uninstall, and distribution of the .appx package via your choice of distribution.

Step 2: Enhance

Now that we have brought our app into the UWP app model, an app identity (as specified in the appxmanifest.xml file) is added, which enables our app to call UWP APIs that were not available to our desktop application before. Let’s look at an example of how to add a Live Tile to our app. The goal is to update the tile on the Start menu whenever the user’s status changes:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17 private void comboBox1_SelectedIndexChanged(object sender, EventArgs e)
{
MyRegKey.SetValue("Status", comboBox1.SelectedItem);

// Update the apps live tile
XmlDocument tileXml =
TileUpdateManager.GetTemplateContent(TileTemplateType.TileSquare150x150Text03);

XmlNodeList textNodes = tileXml.GetElementsByTagName("text");
textNodes[0].InnerText = "MyDesktopApp";
textNodes[1].InnerText = "Status: ";
textNodes[2].InnerText = comboBox1.SelectedItem.ToString();
textNodes[3].InnerText = DateTime.Now.ToString("HH:mm:ss");

TileNotification tileNotification = new TileNotification(tileXml);
TileUpdateManager.CreateTileUpdaterForApplication().Update(tileNotification);
}

Step 3: Extend

In addition to calling more UWP APIs, we can now also add UWP components to our app package to take advantage of other exciting UWP features. Examples of this include adding App Services, becoming a sharing target or a file picker, or adding background tasks.

With background tasks, an app can respond to triggers to execute code even when the app is not running—even if the device is in connected stand-by mode. This way, you can always keep your app up to date and create an experience of an app that is always alive. To illustrate this in our example, we want to use the TimeTrigger to periodically check the status and notify the user via a toast notification:

Now that your Winforms app has identity and runs in the UWP app model. You can declare background tasks in your manifest and register them from your code the same way a UWP can do today:
1 RegisterBackgroundTask("Timer", new TimeTrigger(15, false));

When the TimeTrigger fires, the system will invoke your registered background task in a UWP app container process and you can run code even if your app is not currently running:
1
2
3
4
5
6
7 public sealed class BgTask : IBackgroundTask
{
public void Run(IBackgroundTaskInstance taskInstance)
{
ShowToast("Status: " + currentStatus);
}
}

Step 4: Migrate

To take advantage of UWP UI features such as a touch-friendly UI and smooth animations, let’s migrate the user experience of our project to a XAML front-end. In practice, the details of the UI migration depend on the Win32 UI framework your app has been using and the complexity of your UI. In this simple example, the changes are straightforward. In most real apps, however, this step will require more developer resources.

At this time, we can delete our now obsolete Windows Forms related UI code. However, we still want to keep around our desktop app process for our existing business logic (i.e. managing the app’s state via registry). To communicate between the two processes, we are using an App Service as communication pipeline.

1
2
3
4
5
6
7
8
9
10 private async void cmbBox_SelectionChanged(object sender, SelectionChangedEventArgs e)
{
ValueSet valueSet = new ValueSet();
valueSet.Add("StatusUpdate", cmbBox.SelectedItem.ToString());

if (App.Connection != null)
{
AppServiceResponse response = await
App.Connection.SendMessageAsync(valueSet);
}

Step 5: Expand

In the final step, we will now expand the reach of our application to all Windows 10 devices that run UWP apps by moving the last remaining pieces of code into the UWP app container process. To do so, we will replace the registry-based state with the UWP-compliant ApplicationData API. Thus, we can now deploy our app to phones, Xbox One, HoloLens and other Windows devices that run UWP apps.

Conclusion

The Desktop Bridge offers an exciting path to migrate your existing desktop apps to UWP. It enables you to gradually move across the bridge at your own pace while keeping your existing code investments running at all times along the way.

As you explore the tools on current preview builds, we’re very keen to hear your experiences and feedback. The best place to make feature suggestions is on the Windows Developer UserVoice site. For questions and bug reports, please head over to the Developing Universal Windows apps forums.
Click to expand...

Source: The path from a desktop app to a Universal Windows Platform (UWP) app | Building Apps for Windows

Jean-Marc T. · Jul 18, 2018

[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:

import psutil
import subprocess
import time

for i in range(0, 5000):
print "Loop iteration: %d" % (i)
# start the calc UWP app
subprocess.call(["calc.exe"])

# Wait for 0.5 seconds
time.sleep(0.5)

PROCNAME = "Calculator.exe"

#search and kill the calc UWP app
for proc in psutil.process_iter():
# check whether the process name matches
if proc.name() == PROCNAME:
proc.kill()
Click to expand...

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

BR

Jean-Marc

Windows 10: Windows UWP apps fail to start except one.

Windows UWP apps fail to start except one.

Windows UWP apps fail to start except one.

Windows UWP apps fail to start except one.

Windows UWP apps fail to start except one. - Similar Threads - UWP apps fail

Printing in UWP apps fails with security patch KB5008212

Printing in UWP apps fails with security patch KB5008212

Printing in UWP apps fails with security patch KB5008212

No UWP app or Powershell Both, inbuilt and open source one won't start

No UWP app or Powershell Both, inbuilt and open source one won't start

Windows UWP apps

UWP Apps Won't Start/Launch

UWP apps failing.

Remove all UWP apps except store for new users.