Microsoft Lists not installing — fixes that actually work

Microsoft Lists can fail to install for three common reasons: a client-side Store/installer error, an integration issue with Teams/Office, or an account/tenant policy or licensing block. Start by reproducing and capturing the exact symptom, then apply reversible client fixes (sign out/in, try the web app, check license) before moving to Store or Office repair and, only as a last resort, reinstalling. If those steps fail, gather logs and escalate with the error text and timestamps.

What exactly is happening when Microsoft Lists won't install

Describe the symptom precisely and capture any error text or codes before you change anything.

The exact message varies; copy it or, if none appears, describe the behavior (for example: "installer window closes after 5 seconds" or "Microsoft Store shows 'This app can't open. Try reinstalling it' when I click Install for Microsoft Lists").

When it appears: record the exact step that triggers it — clicking Install in the Store, running Office Setup, enabling Lists in Teams, or opening Lists inside SharePoint. Note whether the problem is per-user or machine-wide by testing another user account on the same PC if possible.

Before you start

Product and versions this applies to:

• Windows 10 and Windows 11 clients installing the Microsoft Store app.
• Microsoft 365 clients where Lists appears as part of Office/Teams or as a SharePoint-based app.

Privileges needed:

• Local Administrator for repairs, Store resets, and reinstall steps; regular user access for license checks and basic troubleshooting.

Restart/backup:

• Some steps (Windows Update, Office repair, reinstall) require a restart. Back up any local configuration you need before reinstalling applications.

Safe checks to run first:

1. Open Lists in a browser to confirm the service is available for your account.
2. Sign out of the Microsoft Store, Teams, and Office apps, then sign back in to refresh credentials.
3. Check that the device has network access to Microsoft services and is not blocked by a proxy or firewall.

If these checks show the web app works and signing out/in fixes things, stop and use the web client while you plan the next steps.

Could my account, license, or tenant policy be blocking the install

Before changing the client, verify account and tenant-side blocks that commonly stop installations.

• Privileges and context:
• Local Administrator is required for some diagnostics and fixes; an admin is required to change tenant or policy settings.

Steps you can run as a user:

1. Check your license assignment in the Microsoft 365 account area (open your web portal account and view assigned licenses).
2. If possible, try a different user on the same machine who has a confirmed license; if that user can install Lists, the issue is account or license-related.
3. Ask an admin to verify tenant settings:

• Ensure the Lists app isn't blocked in the Microsoft Teams admin center under Teams apps > Manage apps.
• Verify app deployment and permission policies in the Microsoft 365 admin center.
• Confirm Intune or Group Policy isn't preventing Store installs or app sideloading.

If a tenant policy or missing license is the cause, an administrator must change the setting or deploy the app centrally. Meanwhile, use the browser version as a fallback.

Try these safe fixes first: Store, cache, permissions, and Office repair

Do these steps from least to most intrusive. Stop when the app installs or the symptom changes.

1. Sign out and sign back in to the Microsoft Store, Teams, and Office apps (user-level).
2. Use the browser version to confirm service availability (user-level).
3. Reset the Microsoft Store cache (non-destructive).

wsreset.exe

Expected result: the Store opens and app listings refresh. If the Store still fails to install, continue.

4. Run the Windows Store Apps troubleshooter.

Settings > System > Troubleshoot > Other troubleshooters > Windows Store Apps > Run

Expected result: the troubleshooter reports found issues and actions taken. If it reports fixes applied, retry the install. If it cannot fix the issue, record its message.

5. Check for and install Windows updates.

Settings > Windows Update > Check for updates

Expected result: system is up to date. If updates install, reboot and try again.

6. Repair Office when Lists is delivered via Microsoft 365 Apps.

Settings > Apps > Installed apps (or Apps & features) > locate Microsoft 365 Apps (or Microsoft Office) > Modify > Quick Repair

Expected result: Office repair completes and Lists availability may be restored. If Quick Repair doesn't help, repeat and choose Online Repair.

Online Repair re-downloads Office files and requires time and an internet connection.

7. Run installers or the Store app as Administrator when appropriate.

• Right-click a downloaded installer and choose "Run as administrator".

Expected result: the installer proceeds past the previous failure point or shows a clearer error. If it still fails, capture the installer message.

8. If you suspect a corrupted user profile, create a new local user account and attempt the install there to distinguish profile vs. system issues.

If you're using Teams or the web, try these integration-specific fixes

Lists often appears inside Teams or SharePoint rather than as a separate local app. If the failure looks integration-related, follow these steps.

1. Confirm the Lists app is enabled in Teams (admin action).

• Admins: check Teams admin center under Teams apps > Manage apps and verify Microsoft Lists is allowed.

2. Update the Teams client and clear its cache (user-level).

Teams > Click your profile > Check for updates

To clear Teams cache (close Teams first):

del /q %appdata%\Microsoft\Teams\Application Cache\*\*
del /q %appdata%\Microsoft\Teams\Cache\*\*

Expected result: Teams updates and cache clearing remove stale state; reopen Teams and check Lists availability. If the Lists tab still fails to add, test the Teams web client.

3. Use the browser version as a diagnostic step to isolate client vs. service problems.
4. If Lists is used inside SharePoint, verify the site collection feature or modern experience is enabled; an admin may need to enable or update those settings.

Expected result: if the web client works and the desktop client fails, the problem is local to the desktop app and you should collect desktop logs before reinstalling.

How to confirm the app is installed and working and what to test next

After a fix, verify functionality in multiple places.

• Open the Lists desktop app (if installed) and confirm it launches without errors and shows your lists.
• Open Teams and add or open a Lists tab to confirm integration works.
• Open the Lists web app in a browser and create a simple test list.

1. Create a test list in the app or web:

1. Click New list
2. Choose Blank list
3. Name it "Test Install"
4. Add a column and save

Expected result: the list creates and accepts items. If creation fails, capture the exact error text.

2. Check Windows Event Viewer for related errors.

Event Viewer > Windows Logs > Application

Expected result: no persistent installer errors; if there are entries, note timestamps and error text.

3. Quick PowerShell check for Store package presence (run as the user who installed the app):

Get-AppxPackage *Lists*

Expected output: a package entry for the Lists app. If the command returns nothing, the Store package isn't installed.

Rollback guidance:

• If a step makes things worse, undo only that step: restore a backed-up configuration, sign back into the previous account, or use System Restore if you created one. Record which step caused regression so you can report it.

When to escalate and what information to collect before contacting support

Escalate to Microsoft support or your internal IT after you’ve collected concise evidence so they can reproduce the failure and avoid repeating steps.

Collect this information first:

• Exact error text and any numeric codes (copy/paste or screenshot). Use the copied text rather than a paraphrase.
• Time and date when the error occurred and the short sequence of actions: e.g., "I clicked Install in Microsoft Store → error shown".
• Windows build and edition (Settings > System > About) and whether you installed via Microsoft Store, Office installer, or Teams.
• User and tenant details you can provide: user UPN, tenant ID (if available), and license type.

Logs and locations to gather:

• Event Viewer logs: Application and Setup logs covering the failure time.
• Windows Store Apps troubleshooter output and any Store diagnostic logs.
• Installer log files from Office or an MSI/MSIX installer (check %temp% for logs the installer reports).
• Teams desktop logs (Ctrl+Alt+Shift+1 in Teams saves logs) and screenshots of Teams admin settings if relevant.

When you contact support, include the exact steps you tried and note any unexpected regressions so they don't repeat diagnostics you've already run.

Conclusion

If reversible fixes (sign out/in, browser fallback, Store cache reset, Office repair, Teams cache clear) don't work, collect the logs and escalate with exact error text, timestamps, and the steps you tried. If the root cause is a tenant policy or missing license, an admin must change the setting or assign a license.

Frequently Asked Questions

Can I use Lists without installing anything?

Yes. Open Microsoft Lists in a browser via the Microsoft 365 or SharePoint web interfaces. Use the web app while you troubleshoot the client install.

Will uninstalling and reinstalling Office remove my data?

Uninstalling Office removes local program files but not your cloud data. Lists stored in SharePoint or Microsoft 365 remain intact. Avoid drastic steps until you’ve collected logs and understood the failure cause.

What if the Microsoft Store itself won't open or install any apps?

Try `wsreset.exe`, run the Windows Store Apps troubleshooter, and check Windows Update. If the Store is blocked by policy, an admin must allow it or deploy apps centrally.