Apps not opening on Windows 11 — you click the icon, nothing happens, no error message, the app just doesn’t launch — is one of the more frustrating problems because there’s so little information to work with. No crash message, no error code, just silence. We go deeper on the whole subject in our Complete Guide to Fixing Windows, Browser, and Software Errors.
The behaviour varies though, and that variation is the clue:
- App icon shows in taskbar briefly then disappears — App launched then immediately crashed. Event Viewer has the details.
- Nothing at all — App didn’t even start. Could be a permissions issue, corrupted install, or a missing dependency.
- Loading cursor for 2 seconds then nothing — App started initialising and failed silently.
- Works for some users, not others on the same machine — User-specific permissions or profile issue.
In all cases: check Event Viewer first. Windows Logs → Application → look for Error entries near the time you tried to launch the app. The “Faulting module name” tells you what crashed. This takes 3 minutes and gives you better information than anything else.
Restart Explorer. Seriously, try it first.
About 20% of “apps not opening” reports on Windows 11 are fixed by restarting Explorer. Explorer manages the shell — the context menus, the start menu, the taskbar — and when it’s in a bad state, clicks don’t propagate correctly to application launches.
Ctrl+Shift+Esc → Task Manager → Windows Explorer → right-click → Restart. Wait 10 seconds and try launching the app. If it works, Explorer was the problem. If this keeps recurring, something is repeatedly crashing Explorer — ShellExView can identify which shell extension is responsible.
Run as administrator
Right-click the app icon → Run as administrator. If the app opens this way but not normally, it needs permissions it’s not getting in standard user mode. This isn’t ideal as a permanent solution, but it confirms the issue is permissions-related.
If it opens as admin: check the app’s installation folder permissions (right-click the app’s exe → Properties → Security tab) — the current user account should have Read & Execute permission. If missing, add it. Also check whether the app needs to be run as admin by design: right-click shortcut → Properties → Compatibility tab → “Run this program as an administrator” checkbox.
Windows Store apps specifically
Microsoft Store apps (UWP apps) have a different failure mode than traditional Win32 apps. When they stop launching without explanation:
Settings → Apps → Installed apps → find the app → three-dot menu → Advanced options → Repair. If repair doesn’t work → Reset. Repair tries to fix the installation without clearing data; Reset does the same but clears app data too. Try Repair first.
If neither works: uninstall and reinstall from the Store. Store apps reinstall cleanly and the fresh install usually fixes whatever corrupted the previous installation.
The SFC fix for system-level launch failures
When multiple apps stop launching simultaneously — or when system apps like Settings, Notepad, or Calculator stop working — system file corruption is usually the cause. Windows can’t load the dependencies these apps need because the files are damaged.
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannowAdministrator Command Prompt. Run DISM first (needs internet, takes 15–20 minutes), then SFC. Restart after both. If SFC reports “found corrupt files and repaired them,” that was it.
Missing Visual C++ and .NET runtimes
Most Windows applications depend on Visual C++ Redistributable packages and/or .NET runtimes. When these are missing, outdated, or corrupted, the apps that depend on them silently fail to launch — no error message because the error happens before the app’s own error handling initialises.
Settings → Apps → Installed apps → search “Visual C++” → you should see Microsoft Visual C++ 2015–2022 Redistributable (both x64 and x86 versions). If these are missing: download the latest from Microsoft’s Visual C++ Redistributable downloads page. Also check for .NET: Apps → search “.NET” → install any missing .NET runtime versions. Many apps specify which .NET version they need in their documentation or installer.
Antivirus quarantining app components
Security software that detects a false positive in an app’s executable silently quarantines it. The app appears installed — the shortcut exists, it’s in the app list — but the actual executable is gone because the antivirus moved it. Clicking the shortcut points to a file that no longer exists, so nothing happens.
Open the antivirus quarantine → check whether the app’s executable or any DLL files are listed. If they are, restore them and add an exclusion for the app’s folder. Then reinstall the app over the top to ensure all components are intact.
User Account Control and compatibility
Applications designed for earlier Windows versions sometimes fail to launch on Windows 11 due to compatibility layer issues. Right-click the app → Properties → Compatibility tab → “Run this program in compatibility mode for” → try Windows 10 or Windows 8. Also try running the compatibility troubleshooter from the same tab — it tests different compatibility settings automatically.
The compatibility fix is useful for older software. For newer software that should natively support Windows 11, compatibility mode usually isn’t the answer — look at the dependency or permissions angle instead.
For app crashes that leave a crash ID, the Windows reliability guide covers Event Viewer navigation in detail and how to read faulting module information. When the issue is Store apps specifically, Microsoft’s Windows 11 app troubleshooting documentation covers the wsreset.exe Store cache clear and the PowerShell re-registration commands for built-in apps that stop launching.
Re-registering Store apps with PowerShell
Built-in Windows apps (Photos, Calculator, Snipping Tool, Mail) that stop opening can be re-registered through PowerShell, which repairs their integration with the Windows shell without uninstalling and reinstalling:
Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"}Run from an administrator PowerShell. This command goes through every installed Store app and re-registers it with Windows. It takes 1–2 minutes, generates some warnings (normal — some apps can’t be re-registered while running), and usually fixes built-in apps that stopped launching after a Windows update corrupted their shell registration.
Windows Store cache clear
The Microsoft Store maintains a local cache that can get corrupted, causing Store apps to fail to launch and the Store itself to behave strangely. Win + R → type wsreset.exe → Enter. A blank Command Prompt window opens, waits 30–60 seconds, then the Store opens automatically when complete. This is the official Microsoft Store cache clear — safe and fast.
Application-specific dependency issues
Some applications need specific system components beyond the standard Visual C++ and .NET packages. Games often need DirectX redistributable components, audio applications might need specific audio driver SDK files, and some older business software needs components from its own installer that don’t get re-run during normal updates.
Check the app’s documentation for minimum requirements and listed dependencies. Then look for a “Verify files” or “Repair installation” option within the application’s own launcher or installer. Steam games have “Verify integrity of game files” under the game properties. Epic Games launcher has a “Verify” option. Adobe apps have a repair option in Creative Cloud. Using the app’s own repair mechanism is often more effective than trying to repair Windows-side.
Disk errors causing launch failures
A dying drive or a file system error can prevent specific files from being read — including application executables. The file exists in the directory listing, but reading its content fails silently. The app “doesn’t open” because Windows can’t actually load the executable file from the disk.
Run CHKDSK: administrator Command Prompt → chkdsk C: /f /r → confirm to run on next restart → restart. CHKDSK scans the file system and marks bad sectors. If it finds and repairs errors, some previously unlaunchable apps may work again after the bad sector is mapped away. CrystalDiskInfo showing health warnings alongside app launch failures is a strong signal that the drive is the root cause.
Third-party security software blocking execution
Application control features in security software (whitelisting, heuristic execution prevention) can silently block applications from running. Unlike quarantine (which removes files), execution prevention leaves files intact but prevents them from loading into memory. The app files exist, but Windows can’t create a process from them.
Check the security software’s activity log — most products log blocked execution events. If the app appears in the blocked list, add an exception. Some corporate security products (Carbon Black, CrowdStrike, Microsoft Defender for Endpoint) use strict application control policies that only allow approved executables to run — newly installed or updated applications need to be approved by IT before they can launch.
Insufficient disk space
Applications that need to create temporary files at launch — unpackers, installers, apps that cache data on startup — will silently fail if there’s insufficient disk space. The app starts initialising, tries to write a temp file, fails, and exits without showing an error.
Check: Settings → System → Storage → how much free space is on the C: drive. If it’s under 5 GB, that’s critically low and very likely causing launch failures for space-sensitive apps. Run Disk Cleanup → Clean up system files → remove Windows Update Cleanup, Previous Windows installations, and Temp files. Getting above 15–20 GB free is the target.
Profile integrity and per-user app registration
Some apps register themselves per-user rather than system-wide. If the user profile has accumulated corruption — particularly in the registry hive or the AppData folders the app writes to — the app can’t complete its startup process and exits silently.
Create a new Windows user account: Settings → Accounts → Other users → Add account → add a local account → log in with that account → try launching the problem app. If it works in the new account, the issue is specific to the original user’s profile. Migrating data to the new account (documents, settings) is less disruptive than it sounds, especially if OneDrive sync handles most documents automatically.
Windows 11 version compatibility
Some applications have minimum Windows 11 build requirements that go beyond just “Windows 11.” A developer targeting 22H2 or 23H2 features may ship an app that silently fails on 21H2 or 22H2 without an informative error. The app’s system requirements page or store listing should specify the minimum Windows version.
Check the current Windows build: Settings → System → About → Windows specifications → Version and OS Build. Compare this against the app’s requirements. If the build is older than required, updating Windows (Settings → Windows Update → Check for updates) may be all that’s needed to make the app launchable.
Checking the Windows Application Event Log efficiently
Rather than scrolling through all events in Event Viewer, filter for the specific app: Event Viewer → Windows Logs → Application → right-click → Filter Current Log → Event Sources → type the app name or “Application Error” → OK. This shows only errors related to that app or to app crashes generally, making it much faster to find the relevant entries from the time you tried to launch.
The two most useful fields in each crash event: “Faulting application name” (confirms it’s the right app) and “Faulting module name” (tells you which component caused the crash — if it’s a Microsoft DLL, it’s a Windows component issue; if it’s a third-party DLL, it’s the app or one of its dependencies).
For the specific case where apps stopped opening after a Windows feature update (the major annual upgrades), the in-place upgrade repair approach sometimes works when SFC doesn’t: download the Windows 11 ISO, mount it, run setup.exe → choose “Upgrade this PC” → “Keep personal files and apps” → complete the upgrade. This reinstalls Windows over itself, fixing component corruption while keeping everything installed. It’s a bigger commitment than SFC (45–90 minutes) but addresses corruption at a deeper level. Worth knowing as an option before concluding that the only fix is a full reinstall.
A quick summary of what to try and in what order, based on what’s most common: restart Explorer → try running as administrator → check Event Viewer for the crash module → run App Repair from Settings if it’s a Store app → run SFC/DISM → check for missing VC++ runtimes → check antivirus quarantine → check disk space. Most cases resolve somewhere in the first four steps. The rest are for persistent issues where the simple approaches haven’t worked, or for situations where Event Viewer has given you a specific module name that points to a particular dependency or system component. You might also run into Teams Microphone Not Working.
One more worth mentioning: if the problem started immediately after the machine woke from sleep and goes away after a restart, the issue is a sleep/resume problem rather than a launch problem. Some apps don’t handle Windows 11’s Modern Standby resume correctly and their background processes are in a bad state after wake. A full restart clears that state and they launch normally again. If this is the consistent pattern, the permanent fix is either updating the specific apps or configuring the power settings to use traditional S3 sleep rather than Modern Standby — which is a deeper change but solves the wake-state corruption for affected applications. Related: Outlook Calendar Not Syncing.
