My confusing, 10-day journey to getting a UWP game to work on Windows 10

Four games, 15 months, Windows 10, and a zoo of confusing crashes later...

Read the whole story

 

[Bongle]

I was trying to install the desktop facebook and instagram apps on my Windows 10 machine earlier this week, and both of them had crashes within about 10 seconds of starting the app. The FB app didn't even require any user interaction before it disappeared.

I poked around in the windows event logger, and you're right that there's nothing useful in there. I could find no minidumps or other kind of logging that might help me figure out what's bust.

So yeah, that's the entirety of _my_ UWP experience. Apps that are probably just web browsers inside can't even get started.

 

[Bongle]

I was trying to install the desktop facebook and instagram apps on my Windows 10 machine earlier this week, and both of them had crashes within about 10 seconds of starting the app. The FB app didn't even require any user interaction before it disappeared.

I poked around in the windows event logger, and you're right that there's nothing useful in there. I could find no minidumps or other kind of logging that might help me figure out what's bust.

So yeah, that's the entirety of _my_ UWP experience. Apps that are probably just web browsers inside can't even get started.

To be honest windows is probably just protecting you from crappy social media... Think of it as having done you a favour and you can now live your life properly ;-)

Yeah, I wasn't that sad. It was my first time playing with the windows store and figured those were going to be among the simplest and best-supported apps on it, since they're made by a fairly big company.

 

[Bongle]

This all ended with Microsoft throwing its hands in the air and asking that I reinstall that year's Windows Creators Update, which—lo and behold—did the trick

This has been a constant problem with Windows 10 since the very beginning:

-- Clean install.
-- Programs A and B work just fine, but Program C won't install, or, installs but won't run properly.
-- Wipe and clean install again.
-- Program C now installs and runs just fine, but Program D won't install, or, installs but won't run properly.
-- Lather, Rinse, Repeat ..... until finally after 4 or 5 attempts everything is running (sort of) smoothly.

Another reason why I still run Windows 7 on my main computer.

The error code in question . . . . ."0x80070003," failed to narrow down any source for the error

It is beyond absurd that Microsoft still refuses to provide clear error messages that actually explain what is wrong.

0x80070003 - ERROR_PATH_NOT_FOUND

That one might actually be fairly solvable: Grab procmon from Microsoft Sysinternals, and watch for CreateFile calls from your process that fail to find their targeted file. If it's genuinely not finding the path to some resource, you should be able to narrow it down pretty quickly.