How to fix Microsoft Store error 0x80070483?

Error 0x80070483 means Windows looked for the app that should open something, often Microsoft Store itself, and found none registered. It usually comes with a Store that will not open, or apps that will not start. Restart the PC first, then reset the Store.

Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What error 0x80070483 means

Codes that start with 0x8007 carry a normal Windows system error inside them. The last four digits, 0483, are hexadecimal for 1155. Microsoft's list of system error codes names 1155 ERROR_NO_ASSOCIATION and gives it one line: "No application is associated with the specified file for this operation."

In plain words, Windows was asked to open something with "its" app and no app was registered for it. Microsoft Store opens through its own link type, and every Store app is registered to your user account. When that registration breaks, Windows has nothing to hand the request to, and this code comes back.

What users see

A Store that does not open or closes at once, Store apps (Photos, Snipping Tool, clipboard, video player) that do not start, and the code in the troubleshooter's result. Users on Microsoft Q&A describe exactly this pattern.

Why the troubleshooter shows it

The troubleshooter tries to reach the Store and its apps and reports the error it hits. The code is its finding, not a fault of the troubleshooter.

What it is not

Not a download or network error and not a licence problem. On its own it says nothing about your hardware.

Why 0x80070483 appears: the causes, ranked

Most often an update changed the Store or its apps and the change is not finished until a restart. Less often the Store's cache or its registration for your account is damaged. Rarely the whole set of app registrations or Windows system files is broken.

How to fix error 0x80070483 in Microsoft Store and Store apps

Fix 1 costs two minutes and, in the Microsoft Q&A thread on this code, was the fix that worked. Fixes 2 to 4 repair the Store and the app registrations. Fix 5 updates the apps. Fixes 6 and 7 repair Windows itself.

Fix 1. Restart the PC with Restart, not Shut down

2 minutesNo riskEveryone, first. Most of all when the error started after Windows or Store updates.

App updates replace the registration of the Store and its apps, and part of that work runs at the next start. With fast startup on, Shut down does not start Windows fresh, while Restart does. The reader who asked about this code on Microsoft Q&A wrote that just restarting was enough.

1. Save your work and close open apps.
2. Select Start, then the Power button.
3. Choose Update and restart if it is offered, otherwise Restart. Do not use Shut down or Sleep for this test.
4. Wait until Windows has started again and you are signed in.
5. Open Microsoft Store from the Start menu, then one app that failed before.

Fix 2. Clear the Store cache with wsreset, then repair or reset Microsoft Store

5 minutesLow riskThe Store opens but stays blank, closes at once or will not download, or Fix 1 did not help.

wsreset clears the Store's cache without touching your apps. Repair rebuilds the Store app's files, and Reset also clears its settings, which can restore the parts Windows needs to open it. Your purchases stay in your Microsoft account.

1. Clear the Store cache. Press Windows + R, type wsreset.exe and select OK. A blank Command Prompt window opens; after a short while it closes and Microsoft Store opens by itself.

   

2. Open System components. If the problem stays, select Start > Settings > System > System components. Next to Microsoft Store, select the three dots and Advanced options. If Microsoft Store is not listed there, look for it in Settings > Apps > Installed apps.

   

3. Repair first. Scroll to Reset and select Repair. Repair keeps the app's data. Open the Store and check whether it works.

   

4. Reset if Repair did not help. Select Reset and confirm. This deletes the Store app's data on this PC; your purchases stay in your Microsoft account. Open the Store and sign in again.

These steps were written for Windows 11 26H2 (build 26300). The full page with the other versions and what each result means: Reset the Microsoft Store

On Windows 11 the Store is under Settings > System > System components. On Windows 10 it is under Settings > Apps > Apps & features > Microsoft Store > Advanced options.

Fix 3. Re-register Microsoft Store for your account with PowerShell

5 minutesLow riskThe Store does not open at all, or wsreset and Repair did not help.

Error 1155 means no app is registered for the request. Re-registering reads the Store's manifest from its install folder and links it to your account again, without downloading anything.

1. Close Microsoft Store and any Store apps.
2. Select Start, type PowerShell and select Windows PowerShell. Open it the normal way, not as administrator, so the Store is registered to your own account.
3. Paste the first command below and press Enter. If PowerShell prints details with Name Microsoft.WindowsStore and an InstallLocation, the Store is on the PC.
4. Paste the three lines of the second command and press Enter. If no red text appears, it worked.
5. Close PowerShell, restart the PC and open the Store.

PowerShell: check that the Store package is there

Get-AppxPackage -Name '*WindowsStore*'

PowerShell: register the Store again for your account

$InstallLocation = Get-AppxPackage -Name '*WindowsStore*' | Select-Object -ExpandProperty InstallLocation
$ManifestPath = $InstallLocation + '\Appxmanifest.xml'
Add-AppxPackage -Path $ManifestPath -Register -DisableDevelopmentMode

The same steps for any one app, with pictures: How to re-register Microsoft Store apps with PowerShell

Fix 4. Re-register all apps of your account when many apps fail

5 to 10 minutesLow riskPhotos, Snipping Tool, Calculator, clipboard and other Store apps do not open, as in the reader's question.

When many apps fail with the same code, their registrations broke together. One command registers every app package of your account again from the files already on the disk.

1. Close all apps you can.
2. Open Windows PowerShell from Start the normal way, not as administrator.
3. Paste the command below and press Enter.
4. Wait until the prompt returns. Some red text is normal; see the note below.
5. Restart the PC and open the apps that failed.

PowerShell: register every app of your account again

Get-AppxPackage | ForEach-Object { Add-AppxPackage -Path "$($_.InstallLocation)\AppxManifest.xml" -Register -DisableDevelopmentMode }

Fix 5. Update the Store apps from Library

5 to 15 minutesNo riskThe Store opens again, but some apps still crash or show the code.

An app that was half updated when its registration broke can stay broken. Get updates installs the current version over it, which also registers it again.

1. Open Microsoft Store.
2. Select Library in the lower left corner (Windows 10: See more > My Library).
3. Select Get updates and wait until all downloads finish.
4. Restart the PC so the updated apps are registered.
5. Open the app that failed.

If one app still fails, repair or reset only that app in Settings > Apps > Installed apps > Advanced options. Step by step: How to repair or reset an app in Windows

Fix 6. Repair Windows system files with DISM and SFC

15 to 30 minutesLow riskSettings, Start or other parts of Windows fail too, or Fixes 3 and 4 print errors such as 0x80073CF6.

The Store and the app registration service are parts of Windows. If their system files are damaged, no app can be registered. DISM fetches good copies and SFC puts them back.

1. Open an elevated command window. Right-click Start and select Terminal (Admin), or type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.

   

2. Run DISM first. Type the command below and press Enter. DISM downloads clean copies of damaged components from Windows Update, so it can take several minutes. Wait until it says The operation completed successfully.

   DISM.exe /Online /Cleanup-Image /RestoreHealth

   

3. Run System File Checker. In the same window, type the command below and press Enter. Do not close the window until the verification reaches 100%.

   sfc /scannow

   

4. Read the result and restart. Compare the last message with the table below this guide, then restart the PC so that repaired files are loaded.

   

These steps were written for Windows 11 24H2 and 25H2. The full page with the other versions and what each result means: Run DISM and SFC to repair Windows system files

Fix 7. Reinstall Windows over itself and keep your files

45 minutes or moreRead the warningLast, when PowerShell finds no Store package, or every fix above failed.

A repair install puts a fresh copy of Windows, including Microsoft Store and the built-in apps, under your existing files and programs. It replaces what the other fixes cannot.

1. Open Recovery in Settings. Open Settings > System > Recovery. Next to Fix problems using Windows Update, select Reinstall now. This keeps your apps, files and settings.

   

2. Start the reinstall. Choose whether the PC may restart on its own 15 minutes after the installation, then select OK.
3. Wait and restart. Windows Update downloads and installs a repair copy of your current Windows version. Keep the PC plugged in and online, and restart it when asked.
4. If that did not help: Reset PC. Back in Settings > System > Recovery, next to Reset this PC, select Reset PC. This keeps your personal files but removes installed apps and settings.
5. Choose Keep my files. Select Keep my files. Do not select Remove everything.

   

6. Choose where Windows comes from. Select Cloud download to download a fresh copy of Windows, or Local reinstall to use the files already on the PC (faster, but may not include the latest updates).
7. Reset. Review the summary and select Reset. The PC restarts several times.

These steps were written for Windows 11 22H2 and later. The full page with the other versions and what each result means: Reinstall Windows without losing files

If 0x80070483 is still there

The code only says that no app was registered. The reason an app could not be registered is written in the Windows event log for app installs and registrations.

1. Right-click Start and select Event Viewer.
2. Open Applications and Services Logs > Microsoft > Windows > AppXDeployment-Server > Microsoft-Windows-AppXDeploymentServer/Operational.
3. Select Filter Current Log, tick Error and select OK.
4. Open the newest errors and look for the package name Microsoft.WindowsStore or the name of the app that fails. Write down the error code and text.

• What to send to Microsoft Support: the error lines from that log, your Windows version from Settings > System > About, and the fixes you tried, with any red text from PowerShell.
• It did not work ("não deu certo"): if Fixes 1 to 6 fail and PowerShell finds no Store package, Fix 7 is the step that brings the Store back.
• A work or school PC: the organization may block or remove the Store by policy. Ask the administrator before you change anything.
• When it is not software: this code does not point to hardware. If Windows also crashes or files get damaged, check the disk with Check a disk for errors (chkdsk).

How to keep 0x80070483 from coming back

The error follows broken app registrations, and most of them come from unfinished updates or from removing built-in apps. These habits avoid both.

Frequently asked questions

What does error code 0x80070483 mean?

It is Windows system error 1155, ERROR_NO_ASSOCIATION, which Microsoft describes as "No application is associated with the specified file for this operation." Windows was asked to open something with an app and found no app registered for it. With Microsoft Store it usually means the Store or one of its apps is not registered right for your account. Restart first (Fix 1), then reset the Store (Fix 2).

Why did the troubleshooter give me 0x80070483?

The Windows Store Apps troubleshooter tries to reach the Store and its apps, and it reports the error it hits. So the code tells you what is wrong, not that the troubleshooter failed. Running it again rarely changes the result. Go on with the fixes on this page: a restart, a Store reset, then re-registering the Store and its apps.

Can I fix 0x80070483 without resetting Windows or using a USB drive?

Yes, in most cases. Fixes 1 to 6 need no USB drive and keep everything on the PC. The reader on Microsoft Q&A who asked exactly this reported that a restart was enough. A repair install (Fix 7) is the last step and also keeps your files and apps; you can start it from Windows without a USB drive.

Microsoft Store and all my apps stopped opening. Will I lose my apps?

No. The apps are still on the disk; only their registration for your account is broken. Re-registering them (Fixes 3 and 4) links them again without downloading anything. A Store Reset signs you out of the Store, but your purchases stay in your Microsoft account. Only a single app's Reset clears that app's own data, so use Repair first.

Should I run the re-register command as administrator?

Not for your own apps. Microsoft's guidance for app registration problems is to register from a normal, non elevated PowerShell window, so the app is registered to the signed-in account. Many older guides use an administrator window with -AllUsers. If your account is not an administrator, sign in with your own account and still use a normal window.

Does this guide fix код ошибки 0x80070483 on Windows 10?

Yes. код ошибки 0x80070483 is the same error code, and the fixes are the same on Windows 10 22H2 and Windows 11. Where menus differ, each fix gives both paths. Windows 10 left Microsoft support on 14 October 2025, so it gets no more security updates; plan a move to Windows 11 if your PC can run it.

Is 0x8007048F the same error as 0x80070483?

No. 0x8007048F is Windows error 1167, "The device is not connected." It usually concerns a drive, a phone or another device that is missing, not app registration. The two codes look alike because both carry a Windows error number inside 0x8007. The fixes on this page are for 0x80070483 only.

My Canon printer shows an error. Is it 0x80070483?

This page is about Microsoft Store and its apps, not about printers. A printer error has its own code from the printer or its driver. If a printer app from the Store will not open and shows 0x80070483, the app's registration is broken: repair or reset that app (Fix 5), then re-register it (Fix 3 with the app's name).

Is 0x80070483 caused by a virus?

Not as a rule. Broken app registrations most often follow unfinished updates or removed built-in apps. If you also see unknown programs, pop-ups or changed browser settings, run a full scan with Microsoft Defender: How to scan for malware with Microsoft Defender. Then come back to the fixes on this page. A scan alone does not register the Store again, so you still need the restart and the Store fixes above.