13 reasons why App installation doesn’t work in Windows 10 (and how to fix it)

If installers or the Microsoft Store fail on your PC, the most common reason is a system or configuration issue blocking the installation process. The problem described as App installation doesn’t work in Windows 10 can be caused by limited disk space, corrupted system files, disabled services, antivirus blocking, certificate errors, missing dependencies, and more. In this guide you’ll learn 13 likely causes and step-by-step fixes so you can get apps installing again.

Key Takeaway

If installs fail, start with the basics: free disk space, run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth, reset the Microsoft Store or installer cache, and ensure the Windows Installer and related services are running; many installation problems are resolved by these steps.

Quick Fix Guide

Quick Fix Guide

Reason for the Problem	Quick Solution
1. Not enough disk space	Free space on the target drive (delete temp files, use Disk Cleanup, or move files).
2. Corrupt Microsoft Store or installer cache	Reset the Store or installer caches (run wsreset.exe and reset Store app).
3. Windows Installer or related services stopped	Start and set Windows Installer, Background Intelligent Transfer Service, and Windows Update to automatic.
4. Third‑party antivirus or firewall blocking installs	Temporarily disable third‑party AV/firewall and try again.
5. Corrupted system files	Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth.
6. Pending or broken Windows updates	Run Windows Update and the Windows Update Troubleshooter.
7. Insufficient permissions / not admin	Right‑click installer and choose Run as administrator or use an admin account.
8. Architecture or compatibility mismatch	Download correct 32‑bit/64‑bit installer or use compatibility mode.
9. Bad or incomplete installer download	Re-download the installer from the official source and verify file integrity.
10. AppX/UWP deployment errors (Store apps)	Re-register Store packages via PowerShell and clear the Store cache.
11. Group Policy or AppLocker blocking	Check gpedit.msc / AppLocker rules and allow the app or installer publisher.
12. Missing dependencies (.NET, VC++ runtimes)	Install required .NET Framework or Visual C++ Redistributables first.
13. Certificate or time/date issues	Correct system time and install the required certificate into Trusted Root.

Detailed Fixes for “App installation doesn’t work in Windows 10”

H3: 1. Not enough disk space
Why it causes the problem

• Installers need temporary space for unpacking and the installation itself; insufficient free space causes failures or incomplete installs.

Step-by-step fix

1. Open Settings > System > Storage to see drive usage.
2. Run Disk Cleanup: press Windows + R, type cleanmgr, press Enter, select the drive, check Temporary files, Windows Update Cleanup, and click OK.
3. Remove large files: open File Explorer > This PC, sort by size, and remove or move large media files to an external drive.
4. Clear temp folder: press Windows + R, type %temp%, delete files inside (skip in-use files).
5. Consider enabling Storage Sense in Settings > System > Storage to auto-clean temporary files.

Notes: Aim to keep several GB free on the system drive (C:), especially if the installer is large.

H3: 2. Corrupt Microsoft Store or installer cache
Why it causes the problem

• The Store or installer caches can become corrupted, preventing UWP apps and some installers from proceeding.

Step-by-step fix

1. Run the Store cache reset: press Windows + R, type wsreset.exe, press Enter and wait (no confirmation pop-up is normal).
2. Reset Microsoft Store via Settings: Settings > Apps > Apps & features > Microsoft Store > Advanced options > Reset.
3. For other installers, clear the temporary package caches: open %localappdata%\Packages and search for relevant app package folders to remove (be careful; back up first).

Tip: After resetting the Store, sign out and sign back into your Microsoft account in the Store app.

H3: 3. Windows Installer or related services stopped
Why it causes the problem

• MSI-based installers and package operations require the Windows Installer service and supporting services (BITS, Windows Update).

Step-by-step fix

1. Open Services: press Windows + R, type services.msc, press Enter.
2. Find Windows Installer, right-click > Properties, set Startup type to Manual or Automatic, then click Start.
3. Ensure these services are running: Background Intelligent Transfer Service (BITS), Windows Update (wuauserv), and Cryptographic Services — set to Automatic and start them.
4. If Windows Installer is misconfigured, re-register it: open elevated Command Prompt and run:
   • msiexec /unregister
   • msiexec /regserver

Note: You may need to reboot after restarting services.

H3: 4. Third‑party antivirus or firewall blocking installs
Why it causes the problem

• Security software can block installers they falsely identify as threats or block network downloads required for installation.

Step-by-step fix

1. Temporarily disable the third‑party antivirus from the system tray icon or its Settings interface.
2. If there’s a firewall, open Control Panel > System and Security > Windows Defender Firewall > Allow an app or feature through Windows Defender Firewall and add the installer if needed.
3. Re-run the installer; if it succeeds, add the installer or app to antivirus exclusions.
4. Re-enable antivirus and firewall afterward.

Tip: If unsure how to disable, consult the vendor’s support site; do not leave protection disabled longer than necessary.

H3: 5. Corrupted system files
Why it causes the problem

• Corrupt or missing system files can break installation components and dependency resolution.

Step-by-step fix

1. Open Command Prompt (Admin): press Windows, type cmd, right‑click, Run as administrator.
2. Run System File Checker: sfc /scannow and wait for completion.
3. If issues persist, run DISM to repair the component store:
   • DISM /Online /Cleanup-Image /RestoreHealth
4. Reboot and try the installer again.

Note: DISM may require network access to download replacement files.

H3: 6. Pending or broken Windows updates
Why it causes the problem

• Pending updates, corrupted update components, or interrupted updates can block installers or cause dependency mismatches.

Step-by-step fix

1. Run Windows Update: Settings > Update & Security > Windows Update > Check for updates and install all pending updates.
2. Run the Windows Update Troubleshooter: Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update > Run the troubleshooter.
3. If the update service is stuck, reset update components via elevated Command Prompt:
   • net stop wuauserv
   • net stop cryptSvc
   • net stop bits
   • net stop msiserver
   • rename C:\Windows\SoftwareDistribution SoftwareDistribution.old
   • rename C:\Windows\System32\catroot2 catroot2.old
   • net start wuauserv
   • net start cryptSvc
   • net start bits
   • net start msiserver

Warning: Renaming SoftwareDistribution forces Windows to rebuild update cache; this is safe but will remove update history.

H3: 7. Insufficient permissions / not running as admin
Why it causes the problem

• Installers often need elevated privileges to write to Program Files, registry, or system folders.

Step-by-step fix

1. Right‑click the installer and choose Run as administrator.
2. If that fails, sign into an administrator account: Settings > Accounts > Family & other users > Add someone else to this PC, then assign administrator role.
3. For MSI packages, use elevated Command Prompt and run msiexec /i “C:\path\to\installer.msi”.

Tip: Avoid using the built-in Administrator account unless necessary; use a standard admin user.

H3: 8. Architecture or compatibility mismatch
Why it causes the problem

• A 32‑bit installer won’t install properly on a 64‑bit targeted location if it’s the wrong build or the app is incompatible.

Step-by-step fix

1. Verify Windows architecture: Settings > System > About > check System type.
2. Download the correct installer (x86 for 32‑bit, x64 for 64‑bit).
3. If older app, right‑click installer > Properties > Compatibility > set Run this program in compatibility mode for: and choose Windows 7/8.

H3: 9. Bad or incomplete installer download
Why it causes the problem

• Partial downloads or corrupted installers will fail during execution or produce errors.

Step-by-step fix

1. Delete the downloaded installer.
2. Redownload from the official vendor’s website; avoid third‑party mirrors.
3. Verify checksum if the vendor provides it (MD5/SHA256) using PowerShell: Get-FileHash C:\path\to\file -Algorithm SHA256.
4. Run the installer as admin.

H3: 10. AppX/UWP deployment errors (Microsoft Store apps)
Why it causes the problem

• UWP apps rely on AppX deployment and package signing that can fail if package registration or services are corrupted.

Step-by-step fix

1. Re-register Store packages: open PowerShell (Admin) and run:
   • Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}
   • Or specifically re-register Store: Get-AppxPackage -allusers Microsoft.WindowsStore | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}
2. Reset Store cache: run wsreset.exe (see earlier).
3. Check for errors in Event Viewer > Applications for further clues.

Note: Re-registering can be slow and may require a reboot.

H3: 11. Group Policy or AppLocker blocking installation
Why it causes the problem

• Administrators or organizational policies can prevent installation of unsigned or unauthorized apps.

Step-by-step fix

1. If you have Pro/Enterprise, open gpedit.msc and check policies under Computer Configuration > Administrative Templates > Windows Components (and AppLocker under Security Settings).
2. For AppLocker: gpedit.msc > Computer Configuration > Windows Settings > Security Settings > Application Control Policies > AppLocker; review rules and exceptions.
3. If the PC is domain-joined, contact your administrator to allow the app.

Note: Windows 10 Home does not include gpedit.msc by default.

H3: 12. Missing dependencies (.NET Framework, Visual C++)
Why it causes the problem

• Many apps require specific .NET versions, VC++ Redistributables, or runtime components.

Step-by-step fix

1. Review the app’s system requirements on the vendor site.
2. To enable .NET 3.5: Control Panel > Programs > Turn Windows features on or off > check .NET Framework 3.5 (includes .NET 2.0 and 3.0), or run:
   • DISM /Online /Enable-Feature /FeatureName:NetFx3 /All
3. Install required Visual C++ Redistributables from Microsoft (x86/x64) matching the app.
4. Reboot and try installing the app again.

H3: 13. Certificate or system time/date issues
Why it causes the problem

• Signed installers require valid certificate chains and accurate system time; certificates can fail validation if the clock is wrong or certs are missing.

Step-by-step fix

1. Check system time: Settings > Time & Language and enable Set time automatically.
2. If the installer has a certificate error, open the installer’s properties > Digital Signatures > view details. Export and install the certificate: open certmgr.msc, right‑click Trusted Root Certification Authorities > Import, and follow the wizard (only for trusted sources).
3. If encountering “certificate not valid” errors for Store apps, ensure Windows Update is current (updates include root certificate updates).

Warning: Only import certificates from trusted vendors.

Additional Tools and Resources

• Use the Microsoft Install/Uninstall Troubleshooter (a downloadable tool) to fix broken MSI packages and installation registry keys.
• For deep logs, check Event Viewer > Windows Logs > Application and Setup, or use *msiexec /i installer.msi /LV “C:\msilog.txt”** to generate a verbose MSI log.
• If everything fails, consider installing in Safe Mode with Networking to rule out third‑party interference (press Shift while selecting Restart > Troubleshoot > Advanced options > Startup Settings > Restart > select Safe Mode with Networking).
• Backup your system or create a System Restore point before making major registry or policy changes.

FAQ

H4: Why does an app say “you don’t have permission to install this app”?
If the app needs elevated privileges, right‑click the installer and choose Run as administrator; if policies block it, check AppLocker or Group Policy or use an admin account.

H4: Can I install an app without admin rights?
Some apps support per‑user installations that don’t require admin. Check the installer options (often “Install for me only”). Otherwise an admin account or temporary elevation is required.

H4: How do I get logs to diagnose an installer error?
For MSI installers, run: *msiexec /i “C:\path\to\installer.msi” /LV “C:\msilog.txt” and review the log for error codes; for Store apps, check Event Viewer under Applications and Microsoft > Windows > AppXDeployment-Server**.

H4: Is reinstalling Windows necessary if installs always fail?
Not usually. Most installation issues are fixable with the steps above; only consider reinstalling Windows after exhaustive troubleshooting and backups.

H4: How can I prevent app installation problems in the future?
Keep Windows updated, maintain free disk space, avoid overzealous security software defaults, and create periodic system restore points before major installs.

Conclusion

Installation failures usually stem from simple issues like low disk space, blocked services, corrupted caches, or missing dependencies — and most are fixable with the steps above. If you work methodically through these 13 checks you’ll resolve the vast majority of cases where App installation doesn’t work in Windows 10.