Windows 11 Apps Won't Open? Nothing Happens When You Click — or It Flashes and Vanishes

You click an app — a browser, a game, the Microsoft Store, a program you use every day — and nothing happens. No window opens, no error appears, the mouse maybe spins for a second and then everything is exactly as it was. Or the app does something almost worse: a window flashes up for a split second and vanishes before you can read it, so the program clearly tried to start and gave up. Either way it looks like the app has died, and the temptation is to reinstall Windows or download something to "fix" it.

Hold off on both. An app that won't launch is almost always one of a short, fixable list: it's already running in the background with no visible window, it's missing a small Microsoft component it needs to start, its files have gotten scrambled, or another program on your PC is quietly shutting it down as it opens. Before we start, one thing to skip: the "PC repair," "app fixer," and "registry cleaner" tools that fill these search results. An app that won't open is a stuck process or a missing part, not something a paid cleaner can find — and every fix below is free and built into Windows.

First: what kind of "won't open" is it — and is it a Store app or a normal program?

Two quick questions save you a lot of poking. First, what exactly happens when you click? If absolutely nothing appears — no window, no flash, no error — the app is probably either already running invisibly or missing something it needs to start. If a window flashes up and instantly closes, the app is launching and then crashing on itself, which points more at scrambled app files, a bad update, or another program interfering. And if you get an actual message — "This app can't open," "This app can't run on your PC," or a specific error code — that's a clue worth reading rather than clicking past.

Second, is it a Microsoft Store app or a normal ("desktop") program? Store apps — things like the Microsoft Store itself, Photos, Calculator, Xbox, and many apps you got from the Store — have their own built-in Repair and Reset buttons, so they get their own fixes below. Classic desktop programs and most games — the ones you downloaded from a website or installed from a disc — don't have those buttons and lean on a different set of fixes. If you're not sure which one an app is, that's fine; just try the quick wins first, then jump to whichever section matches.

One case belongs in different guides. If it's the Start button or the whole taskbar that won't respond — not one app, but the thing you launch everything from — that's the Windows desktop shell, and our guide to a Start menu or taskbar that won't work covers it. If a game opens and runs fine but crashes partway through play, that's usually a graphics-driver issue, not a launch problem. This guide is for the app that won't start in the first place.

The two-minute wins: it's already running, and a proper restart

Start here, because these fix a surprising share of "nothing happens when I click." The single most common trick: the app is already running with no window on screen, and Windows won't open a second copy, so your click seems to do nothing. Press Ctrl + Shift + Esc to open Task Manager and look down the Processes list for the app's name. If it's there, click it and choose "End task" (do this for every copy you see), then try launching it again from a fresh start. This is exactly the case a paid "app fixer" can't help with and the fix costs nothing.

If that didn't do it, restart the PC properly — and on Windows 11 "properly" matters. Choosing Shut down and powering back on is not a clean restart, because a feature called Fast Startup saves part of the system and reloads it, glitch and all; choosing Restart forces a genuine fresh boot. A real restart clears stuck processes and half-loaded components, and quite often an app that refused to open opens fine afterward. It's the least glamorous step and one of the most effective, so don't skip it before moving on to the deeper fixes.

If it's a Microsoft Store app (or the Store itself won't open)

Store apps have repair tools built in, and they're the first thing to reach for. Go to Settings > Apps > Installed apps, find the app in the list, click the three dots next to it, and choose Advanced options. Scroll down to the Reset section and click Repair first — this tries to fix the app without touching your data or settings, so it's safe to run. If Repair doesn't help, click Reset just below it; Reset wipes the app back to a fresh install (you'll lose that app's local settings and sign-in, but not your personal files), which clears up most stubborn Store-app launch failures.

If it's the Microsoft Store itself that won't open — or Store apps generally are misbehaving — clear the Store cache: press Windows key + R, type wsreset.exe, and press Enter. A blank window opens for about ten seconds and then the Store launches on its own; that's it working, not freezing. There's also a built-in troubleshooter at Settings > System > Troubleshoot > Other troubleshooters > "Windows Store Apps" > Run, which checks the common causes for you. One more thing worth a look: Store apps rely on a couple of Windows services being on. Press Windows + R, type services.msc, and make sure "Windows Update" and "Application Identity" are running (right-click > Start if either is stopped) — if they've been disabled by an old "speed up my PC" tweak, Store apps can quietly refuse to launch.

If it's a normal program or a game: permissions and missing Microsoft runtimes

For classic desktop programs and games, start with permissions. Some apps — especially older ones, installers, and anything that touches system files — need administrator rights to start, and they simply do nothing when launched normally. Right-click the app and choose "Run as administrator" to test it. If that fixes it, make it stick: right-click the app > Properties > Compatibility tab > tick "Run this program as an administrator" > Apply. While you're in the Compatibility tab, if it's an old program, you can also try "Run this program in compatibility mode for" an earlier Windows version.

Now the cause the content farms bury: a missing runtime. Many programs and games are built with Microsoft's development tools and need a matching "runtime" installed to start — most commonly the Microsoft Visual C++ Redistributables and the .NET Framework (or the newer .NET Desktop Runtime). If the one an app needs isn't on your PC, the app often just won't start, with no error at all — you click and nothing happens. Two fixes: reinstall the program from scratch (a proper installer usually adds the runtimes it needs), and install the current Microsoft Visual C++ Redistributables and .NET Runtime from Microsoft's own download pages. Games especially bundle these in their installer, so a full reinstall of the game — or "verifying" its files in Steam, Epic, or the Xbox app — pulls the missing pieces back in. Get these only from Microsoft's site, never a third-party "DLL fixer," which is a common way to end up with malware.

If it flashes open and instantly closes (or crashes on launch)

When an app clearly tries to start — a window flashes, or you get a "the app stopped working" style message — the app is launching and then crashing, and Windows keeps a record of exactly why. Open Event Viewer (search the Start menu for it), and under Windows Logs > Application look for a red Error entry stamped at the moment you tried to open the app; it names the program and often a fault module, which turns "it just closes" into a specific thing to search. For a Store app, run the Repair and Reset above; for a normal program, the reliable move is to fully uninstall it (Settings > Apps > Installed apps) and reinstall the latest version from the maker — a great many crash-on-launch problems are just a scrambled or out-of-date install.

If a whole batch of apps started crashing on launch at once, suspect a background program hooking into everything as it opens. Security tools, game overlays, cloud-sync clients (OneDrive, Dropbox), clipboard managers, RGB-lighting and hardware-monitor utilities, and VPN clients can all interfere with apps as they start. Temporarily turn off or exit those, or do a "clean boot" — press Windows + R, type msconfig, press Enter, and on the Services tab tick "Hide all Microsoft services," then Disable the rest and restart. If your apps launch fine after that, re-enable the disabled items a few at a time until the culprit reappears. And if your antivirus is the suspect, don't leave it off — add the app to its exceptions list instead (our guide to scanning for viruses covers doing that safely).

When it's not just you: a recent Windows update

Sometimes the problem isn't your PC at all — a Windows update breaks app launching for a wave of machines at once, and no amount of tweaking on your end fixes it until Microsoft ships a correction. There was a clear example in early 2026: an update left some apps unresponsive or throwing errors when they opened or saved files from cloud storage like OneDrive and Dropbox, until Microsoft pushed an emergency follow-up patch that put it right. So if your app trouble started suddenly, right after an update — and especially if you're hearing other people hit the same thing the same week — that's a strong hint it's Microsoft's bug, not yours.

When that's the case, the fix usually arrives through Windows Update, so check Settings > Windows Update > "Check for updates" and install anything waiting. If the trouble clearly lines up with a specific update you just got, you can go the other way as a stopgap: Settings > Windows Update > Update history > Uninstall updates, remove the most recent one, and pause updates for a week until the corrected version lands. Treat "everyone's suddenly having this" as a reason to wait for the patch, not to tear your machine apart.

The live example right now: the Dolby Digital bug that closes apps by itself

As of early October 2026 there is a live, confirmed example of exactly that, and it is unusually hard to recognise because the thing that broke has nothing obvious to do with the app that dies. On October 2, 2026 Microsoft added an entry to its Windows release health dashboard, marked Confirmed, titled "Applications which require AC-3 audio decoding might close unexpectedly". AC-3 is Dolby Digital — the soundtrack format on DVDs, on Blu-ray discs and the files people rip from them, on a lot of camcorder and recorded-TV footage, and in plenty of older games. In Microsoft's words, following "installation of Windows updates released September 22, 2026 (KB5124010), and later", "some applications which require the decoding of AC-3 (Dolby Digital) audio might close unexpectedly."

The symptom pattern is the reason this one sends people down the wrong path. Microsoft describes it like this: "In some cases the application can fail to launch, or close without warning. In other cases the application will work normally until certain features are used, such as playing music." And: "Affected applications may vary and can include games, media players, and certain productivity applications." Notice what you do not get — an error message, or any sound problem you could actually hear. The program is gone before it plays anything, so nothing about the failure points at audio, and the natural assumption is that the app is corrupt. If you have been reinstalling a program that suddenly started closing itself, rule this out before you reinstall it again.

It does not hit everything, and Microsoft is specific about why: the code involved is "most commonly used in legacy applications that still rely on Windows built-in audio decoding", while modern apps "frequently include their own audio decoding components". In practice that means a current browser or a recently updated media player will probably be fine, while an old DVD-player program, an aging editing suite, or an older game may not be. That gives you a clean test: if the same file plays happily in one program and kills another, you are looking at this bug rather than a damaged file. One more boundary worth knowing — Microsoft lists the affected platforms as Windows 11 versions 24H2, 25H2 and 26H2, with "Server: None". Windows 10 is not on the list.

To check whether the update is even on your machine, press Windows key + R, type winver and press Enter: the affected builds are 26100.9550 on 24H2, 26200.9550 on 25H2 and 26300.9550 on 26H2. You can also look for KB5124010 under Settings > Windows Update > Update history. There is a reason most people will not find it yet. KB5124010 is optional — Microsoft calls it "the final preview update for Windows 11, version 24H2" and a "non-security preview update" — and optional updates do not install themselves, so for now this mostly affects people who deliberately went looking under Optional updates. Because these updates are cumulative, though, the same code is expected to reach everyone else in October's Patch Tuesday on October 13, 2026 unless a correction lands first, and Microsoft has not committed to a date: it says only that it is "working on releasing a resolution for this issue in a future Windows update."

Why the update's own page will not tell you — and what to do about it

If you go looking for confirmation in the obvious place, you will come away thinking it must be your PC. Microsoft's release notes for KB5124010 have their own "Known issues in this update" list, and as of October 3, 2026 this is not on it — that page does not mention AC-3 or Dolby anywhere at all. The entry lives only on the separate Windows release health pages, which are published per Windows version rather than per update. So the update's own page is silent, and the dashboard that knows is one most people have never heard of. Worth remembering generally: "it is not listed in the update notes" is not the same as "it is not a known problem."

For what to actually do, the options are honest but limited. If a program you need has stopped working and KB5124010 is on the machine, you can take it back off: Settings > Windows Update > Update history > Uninstall updates. Removing this one is a milder trade than usual, because it is a non-security preview update rather than a Patch Tuesday security fix — you are not stripping out that month's protection. It is still a stopgap rather than a destination, since Windows will offer it again; pausing updates for a week or two is the tidier way to keep it off while a fix lands. What not to do is reinstall the app over and over, or buy a "repair" tool to chase it. Nothing is wrong with the app.

Two things make this particular update a judgement call rather than a simple rollback. First, some people installed it on purpose: KB5124010 is also the update that fixed the Windows File History bug that stopped backups running over the summer, which our backup guide covers. If that is you, you are weighing a working backup against a program that closes itself — and the backup is usually the more expensive thing to lose, so working around the app while you wait is generally the better call. Second, if you are on Windows 11 version 24H2, the clock matters: Microsoft's own notes say "Windows 11, version 24H2 Home and Pro editions will reach end of updates on October 13, 2026", after which those devices "no longer receive fixes for known issues". So on 24H2 Home or Pro, if the correction is not inside that October 13 update, it will not arrive on that version at all — the way out is moving up to 25H2 or 26H2, which our guide to 24H2's end of support walks through. (24H2 Enterprise and Education "remain supported until October 12, 2027".)

And if the app that is failing is one you only use for music or video, check the simpler thing first: this is a bug about an app shutting down, not about sound going quiet. If your speakers have stopped working but your programs all open fine, that is a different problem with a different fix, and our guide to no sound on Windows 11 is the right place to start.

Still nothing? System files, a test account, and the last resort

If a single app is stubborn, one quick test tells you a lot: create a new Windows user account (Settings > Accounts > Other users > Add account) and try the app there. If it opens fine in the new account, the problem is a corrupted setting in your own profile, not the app or the PC — you can move your files over to the new account and use that. If nothing opens in the new account either, the trouble is system-wide.

For system-wide trouble, repair Windows' own files: open Command Prompt or Terminal as administrator and run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth, and restart — together these fix corrupted system components that can stop apps launching. It's also worth a full malware scan, since some infections deliberately block programs from opening (our guide on scanning for viruses walks through it). And if apps across the whole machine still won't start after all of this, the clean endpoint is Settings > System > Recovery > "Reset this PC" with the "Keep my files" option — it reinstalls Windows fresh while leaving your documents in place, which clears deep software damage without wiping everything.

How we can help

The honest short version: don't buy an "app fixer" or "PC repair" tool for a program that won't open — the real fixes are free and built into Windows. Start with the two-minute wins (End the app in Task Manager in case it's already running, then a proper Restart). For Store apps, use the Repair and Reset buttons and wsreset; for normal programs and games, try Run as administrator and make sure the Microsoft runtimes (.NET and Visual C++) are installed, or just reinstall the app clean. If it flashes and vanishes, let Event Viewer name the crash and suspect a background program; if it started right after an update, check Windows Update for the fix.

If you'd rather not work through all that — or you've tried and your apps still won't launch — that's exactly the kind of everyday Windows headache we sort out for homes and small businesses across Southern California and the Coachella Valley: figuring out whether it's a stuck process, a missing runtime, a scrambled install, an overzealous background app, or a bad update, doing the free fix, and telling you honestly when it's something more. Because we don't sell software subscriptions, the advice you get from us is just the actual fix.