The exception code 0xc000027b is typically encountered after the Microsoft App Store closes by itself after appearing to work normally. There is no error window when this issue occurs (the Windows Store just closes automatically), but affected users have discovered this error code via Event Viewer when investigating the issue.
What’s causing the Microsoft Store Error 0xc000027b and How to Fix it?
- Incorrect Time & Date – As it turns out, this particular issue can also occur due the fact that the machine clock is incorrect. In most cases, this problem appears due to a bad timestamp that determines the Microsoft Store’s server to terminate the connection which ends up closing the app. In this case, you can resolve the issue by adjusting the time and date to the correct values.
- Store app glitch – It’s also possible that this particular issue is occurring due to the fact that the local folder of the Microsoft Store contains certain files that are stuck in a limbo state. If this scenario is applicable, you should be able to resolve the issue by refreshing every relevant Store component via Powershell a command.
- Corrupted Store component – One fairly common issue that will trigger this particular error code is a corrupted Windows Store component. In most cases, this happens after a security scanner ends up quarantining some items that are actively being used by the Windows Store component. In this case, you can resolve the issue by resetting the entire Windows store automatically or by using the wreset.exe utility.
- Corrupted Store reg key – Certain registry keys can also be responsible for holding data relevant to the malfunctioning of the Windows Store component. Several affected users have managed to fix the issue by using Registry Editor to clear the relevant registry key.
- System File Corruption – Under certain circumstances, this issue can occur due to an underlying system file corruption issue that ends up affecting the stability of the Microsoft Store. In this situation, you can typically resolve the issue by performing a repair install.
Method 1: Setting the Correct Time & Date
In a lot of documented cases, the 0xc000027b error code is a direct consequence of the fact that the date, time, or timezone has been altered during the process of upgrading the machine’s OS. Several affected users have confirmed that for them, the issue was occurring due to the fact that their machine clock was incorrect.
This might seem insignificant, but chances are certain Store requests will fail due to a bad timestamp and the Store’s server will not allow the connection to be established. If this scenario is applicable, setting the time, date and timezone correctly should allow you to take care of the issue very easily.
Here’s a quick guide on setting the correct time & date in order to resolve the 0xc000027b:
- Open up a Run dialog box by pressing Windows key + R. Next, once you’re inside the Run window, type ‘timedate.cpl’ inside the text box and press Enter to open up the Date and Time window.
- Once you manage to get inside the Date & Time window, go to the Date and time tab and click on Change date and time to open the next menu.
- Once you’re inside the Date & Time menu, use it to access the calendar and select the appropriate date. Next, move over to the Time box and set the appropriate time according to the timezone that you live in.
Note: If you want to be certain that the clock doesn’t become offset again, you should also modify the time zone to the correct one by clicking on Change Timezone.
- Once you are finished with the modifications, restart your computer and see if the issue is resolved at the next system startup.
If you’re still encountering the 0xc000027b error, move down to the next method below.
Method 2: Refreshing the Store app via Powershell command
As it turns out, this particular issue can also occur due to one or more temp files that are actually producing errors during the validation phase that ultimately forces the Microsoft Store to auto-close.
Several affected users that encountered this issue have managed to get the issue resolved by opening an elevated Powershell prompt and running a command capable of clearing all files that are associated with the Microsoft Store component.
Here’s a quick guide on doing this:
- Press Windows key + R to open up a Run dialog box. Next, type ‘powershell’ and press Ctrl + Shift + Enter to open up an elevated Powershell prompt. When you see the UAC (User Account Control), click Yes to grant the necessary admin access.
- Once you are inside the PowerShell prompt, type the following command and press Enter to refresh the Store component along with any associated dependency:
$manifest = (Get-AppxPackage Microsoft.WindowsStore).InstallLocation + '\AppxManifest.xml' ; Add-AppxPackage -DisableDevelopmentMode -Register $manifest
- After the command is successfully processed, restart your computer and see if the issue is resolved at the next computer startup.
If the same 0xc000027b error code is still occurring, move down to the next potential fix below.
Method 3: Resetting Windows Store
As it turns out, one of the most common culprits that will ultimately spawn this error is some type of corrupted inside the Windows Store component. This scenario is fairly common in those situations where Windows Defender or a different 3rd party security scanner ends up quarantining some items that are essential to the Windows Store.
If this happens, the Windows Store will end up closing whenever the utility calls upon the file that has been quarantined. Some users that were also encountering this issue have reported that they finally managed to resolve the issue after they reset the Microsoft Store along with any associated dependencies.
This procedure will end up replacing any quarantined instances with healthy copies that will take its place. Keep in mind that when it comes to doing this, there are two ways forward. Options number one involves using the Windows Store reset utility while the second one is more suitable for non-technical individuals that would prefer to do the entire process from the menus of Windows 10.
Follow whichever guide you feel more comfortable with:
Reset Windows Store via Settings Menu
- Press Windows key + R to open up a Run dialog box. Next, type ”ms-settings:appsfeatures’ and press Enter to open up the Apps & Features menu of the Settings app.
- Once you manage to get inside the Apps & Features screen, go ahead and scroll through the installed (UWP) applications and locate Microsoft Store.
- When you see the correct listing, look for the Advanced options menu associated with it and click on it (under Microsoft Corporation).
- Next, scroll down to the Reset tab, then click on the Reset button to initiate the process. After you start the operation, do not interrupt it until it is finished.
- After the process is finished, restart your computer and see if the problem is resolved at the next system startup.
Reset Windows Store via CMD window
- Open up a Run dialog box by pressing Windows key + R. Next, type ‘cmd’ inside the text box and press Ctrl + Shift + Enter to open up an elevated Command Prompt. Once you are prompted by the UAC (User Account Control), click Yes to grant administrative privileges.
- Once you are inside the elevated Command Prompt, type the following command and press Enter to run the command capable of resetting Windows Store along with all its dependencies:
- After the command is successfully processed, restart your computer and see if the problem is resolved at the next system startup.
If you’re still noticing that the Windows Store app crashes and the Event Viewer log points towards the 0xc000027b error code, move down to the next method below.
Method 4: Deleting Windows Store Cache Registry keys
As it turns out, this particular issue can also be caused due to several registry keys that might end up holding temporary data which ends affecting the stability of the Microsoft Store. If this scenario is applicable, resetting the cache conventionally will not resolve the issue since the same registry keys will still remain firmly in place.
To resolve this issue in this case, you will need to use Registry Editor to locate the problematic key and delete it swiftly. Several affected users that were also struggling with this issue have confirmed that this operation finally allowed them to fix the 0xc000027b error.
Here’s a quick guide on how to get this done on Windows 10:
- Press Windows key + R to open up a Run dialog box, Next, type ‘regedit’ and press Enter to open up the Registry Editor. When you are prompted by the UAC (User Account Control), click Yes to grant administrative privileges.
- Once you’re inside the Registry Editor, use the left-hand section to navigate to the following location:
Note: You can also get there instantly by pasting the location directly into the navigation bar and pressing Enter.
- After you manage to get to this location, right-click on Cache (the sub-folder of Store) and choose Delete from the newly appeared context menu to get rid of it.
- Once the file is deleted, restart your computer and see if the issue is resolved at the next computer startup.
If the 0xc000027b error is still occurring at the next computer startup, move down to the next method below.
Method 5: Performing a repair install
If none of the methods above have allowed you to resolve the issue, it’s probably due to the fact that you’re dealing with a system file corruption that cannot be resolved conventionally. In situations such as this one, the only viable fix that will not produce any noticeable data loss is to perform a repair install procedure (in-place repair).
This operation is a little tedious, but it will allow you to refresh every relevant Windows component without losing any personal data, applications, games and user preferences. But keep in mind that performing a repair install (in-place repair) will require you to have an installation media.