Windows ui xaml dll 0xc000027b

Windows.UI.Xaml.dll gives error 0xc000027b
Little background:

yesterday I had a Skype group video chat and my PC gave me 3/4 times a GSOD (can’t find the dumps, though) VIDEO SCHEDULER INTERNAL ERROR.

Since yesterday I’m having a pretty annoying bug, or shall I say two:

A lot of UWP crash at start (calculator, mail, Unigram etc.).
When searching something with Cortana, the font is weird. It looks like times new roman.
Closer inspection, and every time bug #1 occurs, Windows.UI.Xaml.dll gives an error.

Windows.UI.Xaml.dll, version: 10.0.17763.292
Exception code: 0xc000027b
Directory of the module generating the error: C:\Windows\System32\Windows.UI.Xaml.dll

And along with these errors, some .NET Runtime errors 1026

framework version: v4.0.30319
Exception: System.IO.FileNotFoundException
in MS.Internal.Text.TextInterface.Native.Util.ConvertHresultToException(Int32)
in MS.Internal.Text.TextInterface.FontFamily.GetFirstMatchingFont(MS.Internal.Text.TextInterface.FontWeight, MS.Internal.Text.TextInterface.FontStretch, MS.Internal.Text.TextInterface.FontStyle)
in MS.Internal.Text.TextInterface.FontFamily.get_Metrics()
in MS.Internal.FontFace.PhysicalFontFamily.MS.Internal.FontFace.IFontFamily.LineSpacing(Double, Double, Double, System.Windows.Media.TextFormattingMode)
in MS.Internal.TextFormatting.SimpleTextLine..ctor(MS.Internal.TextFormatting.FormatSettings, Int32, Int32, System.Collections.ArrayList, Int32 ByRef, Int32 ByRef, Double)
in MS.Internal.TextFormatting.SimpleTextLine.Create(MS.Internal.TextFormatting.FormatSettings, Int32, Int32, Double)
in MS.Internal.TextFormatting.TextFormatterImp.FormatLineInternal(System.Windows.Media.TextFormatting.TextSource, Int32, Int32, Double, System.Windows.Media.TextFormatting.TextParagraphProperties, System.Windows.Media.TextFormatting.TextLineBreak, System.Windows.Media.TextFormatting.TextRunCache)
in MS.Internal.TextFormatting.TextFormatterImp.FormatLine(System.Windows.Media.TextFormatting.TextSource, Int32, Double, System.Windows.Media.TextFormatting.TextParagraphProperties, System.Windows.Media.TextFormatting.TextLineBreak, System.Windows.Media.TextFormatting.TextRunCache)
in System.Windows.Controls.TextBlock.MeasureOverride(System.Windows.Size)
in System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)
in System.Windows.UIElement.Measure(System.Windows.Size)
in System.Windows.Controls.Grid.MeasureCell(Int32, Boolean)
in System.Windows.Controls.Grid.MeasureCellsGroup(Int32, System.Windows.Size, Boolean, Boolean, Boolean ByRef)
in System.Windows.Controls.Grid.MeasureOverride(System.Windows.Size)
in System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)
in System.Windows.UIElement.Measure(System.Windows.Size)
in System.Windows.Controls.Grid.MeasureCell(Int32, Boolean)
in System.Windows.Controls.Grid.MeasureCellsGroup(Int32, System.Windows.Size, Boolean, Boolean, Boolean ByRef)
in System.Windows.Controls.Grid.MeasureOverride(System.Windows.Size)
in System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)
in System.Windows.UIElement.Measure(System.Windows.Size)
in MS.Internal.Helper.MeasureElementWithSingleChild(System.Windows.UIElement, System.Windows.Size)
in System.Windows.Controls.ContentPresenter.MeasureOverride(System.Windows.Size)
in System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)
in System.Windows.UIElement.Measure(System.Windows.Size)
in System.Windows.Controls.Border.MeasureOverride(System.Windows.Size)
in System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)
in System.Windows.UIElement.Measure(System.Windows.Size)
in System.Windows.Controls.Control.MeasureOverride(System.Windows.Size)
in System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)
in System.Windows.UIElement.Measure(System.Windows.Size)
in System.Windows.Controls.Grid.MeasureCell(Int32, Boolean)
in System.Windows.Controls.Grid.MeasureCellsGroup(Int32, System.Windows.Size, Boolean, Boolean, Boolean ByRef)
in System.Windows.Controls.Grid.MeasureOverride(System.Windows.Size)
in System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)
in System.Windows.UIElement.Measure(System.Windows.Size)
in MS.Internal.Helper.MeasureElementWithSingleChild(System.Windows.UIElement, System.Windows.Size)
in System.Windows.Controls.ContentPresenter.MeasureOverride(System.Windows.Size)
in System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)
in System.Windows.UIElement.Measure(System.Windows.Size)
in System.Windows.Controls.Border.MeasureOverride(System.Windows.Size)
in System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)
in System.Windows.UIElement.Measure(System.Windows.Size)
in System.Windows.Controls.Control.MeasureOverride(System.Windows.Size)
in System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)
in System.Windows.UIElement.Measure(System.Windows.Size)
in System.Windows.Controls.Grid.MeasureOverride(System.Windows.Size)
in System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)
in System.Windows.UIElement.Measure(System.Windows.Size)
in System.Windows.ContextLayoutManager.UpdateLayout()
in System.Windows.ContextLayoutManager.UpdateLayoutCallback(System.Object)
in System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()
in System.Windows.Media.MediaContext.RenderMessageHandlerCore(System.Object)
in System.Windows.Media.MediaContext.RenderMessageHandler(System.Object)
in System.Windows.Interop.HwndTarget.OnResize()
in System.Windows.Interop.HwndTarget.HandleMessage(MS.Internal.Interop.WindowMessage, IntPtr, IntPtr)
in System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
in MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
in MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
in System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
in System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
in System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
in MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
in MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
in MS.Win32.HwndSubclass.DefWndProcWrapper(IntPtr, Int32, IntPtr, IntPtr)
in MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
in MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

Here’s the things I’ve tried so far:

Reset each and every app I’ve found affected by this
Windows Apps Troubleshooter (absolutely no effort from it)
sfc scannow
Dism repair
Reset of Windows Apps through Powershell
In-place re-installation
None of the above worked. Can someone help me figure out how to solve these issues?

Windows 10: Windows.UI.Xaml.dll gives error 0xc000027b

Discus and support Windows.UI.Xaml.dll gives error 0xc000027b in Windows 10 BSOD Crashes and Debugging to solve the problem; Little background:

yesterday I had a Skype group video chat and my PC gave me 3/4 times a GSOD (can’t find the dumps, though) VIDEO SCHEDULER…
Discussion in ‘Windows 10 BSOD Crashes and Debugging’ started by gabrielerizzo, Feb 1, 2019.

  1. Windows.UI.Xaml.dll gives error 0xc000027b

    Little background:

    yesterday I had a Skype group video chat and my PC gave me 3/4 times a GSOD (can’t find the dumps, though) VIDEO SCHEDULER INTERNAL ERROR.

    Since yesterday I’m having a pretty annoying bug, or shall I say two:

    1. A lot of UWP crash at start (calculator, mail, Unigram etc.).
    2. When searching something with Cortana, the font is weird. It looks like times new roman.

    Closer inspection, and every time bug #1 occurs, Windows.UI.Xaml.dll gives an error.

    Windows.UI.Xaml.dll, version: 10.0.17763.292

    Exception code: 0xc000027b

    Directory of the module generating the error: C:\Windows\System32\Windows.UI.Xaml.dll

    And along with these errors, some .NET Runtime errors 1026

    framework version: v4.0.30319

    Exception: System.IO.FileNotFoundException

    in MS.Internal.Text.TextInterface.Native.Util.ConvertHresultToException(Int32)

    in MS.Internal.Text.TextInterface.FontFamily.GetFirstMatchingFont(MS.Internal.Text.TextInterface.FontWeight, MS.Internal.Text.TextInterface.FontStretch, MS.Internal.Text.TextInterface.FontStyle)

    in MS.Internal.Text.TextInterface.FontFamily.get_Metrics()

    in MS.Internal.FontFace.PhysicalFontFamily.MS.Internal.FontFace.IFontFamily.LineSpacing(Double, Double, Double, System.Windows.Media.TextFormattingMode)

    in MS.Internal.TextFormatting.SimpleTextLine..ctor(MS.Internal.TextFormatting.FormatSettings, Int32, Int32, System.Collections.ArrayList, Int32 ByRef, Int32 ByRef, Double)

    in MS.Internal.TextFormatting.SimpleTextLine.Create(MS.Internal.TextFormatting.FormatSettings, Int32, Int32, Double)

    in MS.Internal.TextFormatting.TextFormatterImp.FormatLineInternal(System.Windows.Media.TextFormatting.TextSource, Int32, Int32, Double, System.Windows.Media.TextFormatting.TextParagraphProperties, System.Windows.Media.TextFormatting.TextLineBreak, System.Windows.Media.TextFormatting.TextRunCache)

    in MS.Internal.TextFormatting.TextFormatterImp.FormatLine(System.Windows.Media.TextFormatting.TextSource, Int32, Double, System.Windows.Media.TextFormatting.TextParagraphProperties, System.Windows.Media.TextFormatting.TextLineBreak, System.Windows.Media.TextFormatting.TextRunCache)

    in System.Windows.Controls.TextBlock.MeasureOverride(System.Windows.Size)

    in System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)

    in System.Windows.UIElement.Measure(System.Windows.Size)

    in System.Windows.Controls.Grid.MeasureCell(Int32, Boolean)

    in System.Windows.Controls.Grid.MeasureCellsGroup(Int32, System.Windows.Size, Boolean, Boolean, Boolean ByRef)

    in System.Windows.Controls.Grid.MeasureOverride(System.Windows.Size)

    in System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)

    in System.Windows.UIElement.Measure(System.Windows.Size)

    in System.Windows.Controls.Grid.MeasureCell(Int32, Boolean)

    in System.Windows.Controls.Grid.MeasureCellsGroup(Int32, System.Windows.Size, Boolean, Boolean, Boolean ByRef)

    in System.Windows.Controls.Grid.MeasureOverride(System.Windows.Size)

    in System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)

    in System.Windows.UIElement.Measure(System.Windows.Size)

    in MS.Internal.Helper.MeasureElementWithSingleChild(System.Windows.UIElement, System.Windows.Size)

    in System.Windows.Controls.ContentPresenter.MeasureOverride(System.Windows.Size)

    in System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)

    in System.Windows.UIElement.Measure(System.Windows.Size)

    in System.Windows.Controls.Border.MeasureOverride(System.Windows.Size)

    in System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)

    in System.Windows.UIElement.Measure(System.Windows.Size)

    in System.Windows.Controls.Control.MeasureOverride(System.Windows.Size)

    in System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)

    in System.Windows.UIElement.Measure(System.Windows.Size)

    in System.Windows.Controls.Grid.MeasureCell(Int32, Boolean)

    in System.Windows.Controls.Grid.MeasureCellsGroup(Int32, System.Windows.Size, Boolean, Boolean, Boolean ByRef)

    in System.Windows.Controls.Grid.MeasureOverride(System.Windows.Size)

    in System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)

    in System.Windows.UIElement.Measure(System.Windows.Size)

    in MS.Internal.Helper.MeasureElementWithSingleChild(System.Windows.UIElement, System.Windows.Size)

    in System.Windows.Controls.ContentPresenter.MeasureOverride(System.Windows.Size)

    in System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)

    in System.Windows.UIElement.Measure(System.Windows.Size)

    in System.Windows.Controls.Border.MeasureOverride(System.Windows.Size)

    in System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)

    in System.Windows.UIElement.Measure(System.Windows.Size)

    in System.Windows.Controls.Control.MeasureOverride(System.Windows.Size)

    in System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)

    in System.Windows.UIElement.Measure(System.Windows.Size)

    in System.Windows.Controls.Grid.MeasureOverride(System.Windows.Size)

    in System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)

    in System.Windows.UIElement.Measure(System.Windows.Size)

    in System.Windows.ContextLayoutManager.UpdateLayout()

    in System.Windows.ContextLayoutManager.UpdateLayoutCallback(System.Object)

    in System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()

    in System.Windows.Media.MediaContext.RenderMessageHandlerCore(System.Object)

    in System.Windows.Media.MediaContext.RenderMessageHandler(System.Object)

    in System.Windows.Interop.HwndTarget.OnResize()

    in System.Windows.Interop.HwndTarget.HandleMessage(MS.Internal.Interop.WindowMessage, IntPtr, IntPtr)

    in System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

    in MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

    in MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)

    in System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)

    in System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)

    in System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)

    in MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

    in MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)

    in MS.Win32.HwndSubclass.DefWndProcWrapper(IntPtr, Int32, IntPtr, IntPtr)

    in MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)

    in MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

    Here’s the things I’ve tried so far:

    1. Reset each and every app I’ve found affected by this
    2. Windows Apps Troubleshooter (absolutely no effort from it)
    3. sfc scannow
    4. Dism repair
    5. Reset of Windows Apps through Powershell
    6. In-place re-installation

    None of the above worked. Can someone help me figure out how to solve these issues?

    :)

  2. D3dx9_30.dll Not Found error in Ashes Cricket 2009

    Important Note: Do not, under any circumstances, download the d3dx9_30.dll DLL file individually from any «DLL download site.» There are a number of different reasons that downloading DLLs from these sites are never a good idea.

  3. Windows.UI.Xaml.dll gives error 0xc000027b

    Windows 8 FREE Developer Build

    Can someone please give me a step by step showing of how to take control of a .dll file in Windows 8? It looks totally different from 7, where the «Owner» tab is not there.

Thema:

Windows.UI.Xaml.dll gives error 0xc000027b

  1. Windows.UI.Xaml.dll gives error 0xc000027b — Similar Threads — Xaml dll error

  2. Desktop windows xaml source onedrive application error

    in Windows 10 Software and Apps

    Desktop windows xaml source onedrive application error: Recently after an update in windows 11 i get this message from Desktop windows xaml source onedrive application error, usual error message of reference memory not found click ok to terminate the program, just before shutting down my laptop. It’s not causing any trouble right…
  3. Desktop windows xaml source onedrive application error

    in Windows 10 Gaming

    Desktop windows xaml source onedrive application error: Recently after an update in windows 11 i get this message from Desktop windows xaml source onedrive application error, usual error message of reference memory not found click ok to terminate the program, just before shutting down my laptop. It’s not causing any trouble right…
  4. 0xc000027b

    in Windows 10 Gaming

    0xc000027b: gui

    https://answers.microsoft.com/en-us/windows/forum/all/0xc000027b/296ec0d4-b24c-4c78-a448-3fef7ae4a7a6

  5. 0xc000027b

    in Windows 10 Software and Apps

    0xc000027b: gui

    https://answers.microsoft.com/en-us/windows/forum/all/0xc000027b/296ec0d4-b24c-4c78-a448-3fef7ae4a7a6

  6. Wondershare gives error messages_ .dll files missing

    in Windows 10 BSOD Crashes and Debugging

    Wondershare gives error messages_ .dll files missing: on login to Windows 10

    Wondershare sent me error messages

    that four of its .dll files were missing

    I tried all measures

    to correct this

    none worked

    and

    uninstalling did not seem to be an option

    I then happened to DEFRAGMENT MY DISC

    the error messages…

  7. Clibpoard history doesn’t work and gives Exception code: 0xc000027b

    in Windows 10 Ask Insider

    Clibpoard history doesn’t work and gives Exception code: 0xc000027b: [ATTACH] submitted by /u/wuarx
    [link] [comments]

    https://www.reddit.com/r/Windows10/comments/i784mp/clibpoard_history_doesnt_work_and_gives_exception/

  8. Settings Crashes in Windows 10 0xc000027b

    in Windows 10 BSOD Crashes and Debugging

    Settings Crashes in Windows 10 0xc000027b: I have found that the SETTINGS APP on my windows 10 system kept on crashing.

    I followed ALL the suggestions (apart from re-installing Windows 10).

    The Solution was to uninstall KB 4462919 — WindowsUpdate. Then it worked.

    Faulting application name: SystemSettings.exe,…

  9. Skype broken with Exception code: 0xc000027b

    in Windows 10 Software and Apps

    Skype broken with Exception code: 0xc000027b: For a good month now, every attempt to open skype ends with Skype vanishing, and the event viewer entry of:

    Faulting application name: SkypeApp.exe, version: 8.30.76.26, time stamp: 0x5b887cec
    Faulting module name: twinapi.appcore.dll, version: 10.0.17134.137, time stamp:…

  10. Windows Bridge for iOS: UIKit, meet XAML. XAML, meet UIKit

    in Windows 10 News

    Windows Bridge for iOS: UIKit, meet XAML. XAML, meet UIKit: One year ago this August, we released the Windows Bridge for iOS (“Project Islandwood”) as an open-source project on GitHub. For those of you just joining us, the goal of the iOS bridge is to make it easy for iOS developers to make great Windows apps while reusing much of…

Users found this page by searching for:

  1. windows.ui.xaml.dll exception 0xc000027b launch

    ,

  2. 0xc000027b exception code windows.ui.xaml

    ,

  3. faulting module Windows.UI.Xaml.dll how to fix

    ,

  4. windows.ui.xaml.dll 0xc000027b,
  5. xamarin windows.ui.xaml.dll,
  6. windows.ui.xaml.dll exception code: 0xc000027b,
  7. windows.ui.xaml.dll exception XAMARIN,
  8. faulting application name calculator.exe,
  9. twinapi.appcore.dll 0xc000027b,
  10. windows ui xaml dll 0xc000027b win10,
  11. windows ui xaml dll 例外0xc000027b,
  12. 0xc000027b windows.ui.xaml.dll,
  13. windows.ui.xaml.dll crash 0xc000027b,
  14. 0xc000027b SystemSettings Windows.UI.Xaml.dll,
  15. Windows.UI.Xaml 0xc000027b


Readers help support Windows Report. We may get a commission if you buy through our links.

Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more

Several users have reported facing Microsoft Store crash exception error code 0xc000027b. Notably, the Microsoft Store apps crash without displaying any error window. This makes it more difficult to investigate the issue since the error doesn’t show any error message.

However, we have researched and found some reasons that could trigger the Microsoft Store crash exception error code 0xc000027b. This guide will also help you with solutions to fix the problem at your end. Let us get right into it.

What is 0xc000027b, and how does it trigger?

The simple meaning of the error 0xc000027b is that Microsoft Store abruptly closes during an operation or opening of an app. Some of the common 0xc000027b app errors that you will come across are 0xc000027b start menu, 0xc000027b explorer, 0xc000027b calculator, etc.

Although there isn’t any error message displayed, most of the time, when users come across the 0xc000027b, after reading several user reports we found many reasons that could trigger the problem.

  • Time and date are incorrect: Simple it may sound, but several users reported that because the time and date aren’t correct on their PCs, they are getting this issue.
  • Windows Store is problematic: There are chances that there are some underlying issues that are causing the Microsoft Store crash error 0xc000027b.
  • Microsoft Store cache is corrupt: Because of corrupt cache files for Microsoft Store, you will come across various issues including the one at hand.
  • Corrupt Store registry key: Chances are some important registry keys related to the Windows Store are corrupt and causing problems.
  • System files are missing or corrupt: Also, because of some missing or corrupt system files, you may get several issues associated with the Windows program.

Let us check out the different solutions that will hopefully help you resolve the Microsoft Store crash exception code 0xc000027b.

How can I easily get rid of this Microsoft Store error 0xc000027b?

1. Set the correct time and date

  1. Press the Win + I keys to open the Windows Settings.
  2. Click on Time & language on the left.

  3. Select the Date and time option.

  4. Toggle on the Set time automatically option.

  5. From the Time zone drop-down, select the correct time zone.

  6. Scroll down and under Additional settings, hit the Sync now button to sync the time.

Notably, this solution was suggested by one user and has helped several users to fix the Microsoft Store error 0xc000027b.

You can try fixing the time and date for your PC and hopefully resolve the 0xc000027b error and other associated errors such as 0xc000027b start menu, 0xc000027b explorer, and 0xc000027b calculator,

2. Run the Windows Store app troubleshooter

  1. Press the Win + I keys to open the Windows Settings.
  2. Click on Troubleshoot.

  3. Select Other troubleshooters.

  4. Hit the Run button next to the Windows Store.

  5. The troubleshooter will start detecting the issues.
  6. Apply the prompted fixes.
  7. Restart your PC.

If there is an underlying issue with the Windows Store, it can be easily resolved by running the Windows Store troubleshooter.

It will detect the issue and prompt you to apply the fixes to resolve errors, including the Microsoft Store error 0xc000027b.

Read more about this topic

  • Microsoft finally issued fix recommendations for an ancient Microsoft Store bug
  • Fix: An Error Occurred While Loading a Higher Quality Version of This Video
  • iTunesMobileDevice.dll is Missing From Your Computer [Solved]
  • SYNSOACC.DLL Could Not Be Located: How to Fix in Cubase
  • Fix: Omen Gaming Hub Undervolting Not Working

3. Reset Microsoft Store

  1. Press the Win + I keys to open the Windows Settings.
  2. Click on Apps on the left.

  3. Select Installed Apps.

  4. Click the 3-dot icon for Microsoft Store and select Advanced options.

  5. Scroll down and click on Reset.

  6. Hit Reset again in the prompt to reset the Microsoft Store.

Resetting the Microsoft Store helps reset all the files that might be corrupt or causing the problem. When you launch the Store after resetting, all files will be loaded from scratch.

4. Delete Windows Store cache

  1. Press the Win + R keys to open the Run dialogue.
  2. Type regedit and hit Enter.
  3. Navigate to the below path and press Enter. Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\CloudStore\Store

  4. Delete the Cache folder for Store.

  5. Close Registry Editor.
  6. Restart your PC for the changes to take effect.

This issue of Microsoft Store error 0xc000027b could also be triggered if several registry files are missing or corrupt.

You can easily clear the Windows Store cache registry files by following the above steps and see if this helps in 0xc000027b start menu, 0xc000027b explorer, 0xc000027b calculator, or other 0xc000027b associated errors.

5. Run SFC and DISM commands

  1. Press the Win key to open the Start menu.
  2. Run Command Prompt as an admin.

  3. Type the below command and press Enter. sfc /scannow
    SFCSCANNOW CMD

  4. Wait for the SFC Scan process to complete.
  5. Type the below commands and press Enter after each one.Dism /Online /Cleanup-Image /CheckHealth Dism /Online /Cleanup-Image /ScanHealth Dism /Online /Cleanup-Image /RestoreHealth

  6. Restart your PC.

Several users have also asked in forums whether the shellexperiencehost.exe 0xc000027b and kernelbase dll exception code: 0xc000027b errors are similar to 0xc000027b.

In short, yes. If you are facing the shellexperiencehost.exe 0xc000027b and kernelbase dll exception code: 0xc000027b errors, you can apply the fixes mentioned above. Moreover, you will also face these 0xc000027b errors with an app downloaded from the Microsoft Store, such as a calculator.

So, basically, some underlying problems with the Store are causing apps to misbehave. You can also apply the same solutions mentioned above to resolve these issues.

That is it from us in this guide. We have prepared a guide that lists down all the most common Microsoft Store error codes along with the solutions that will help you resolve them.

Feel free to let us know in the comments below which one of the above solutions fixed the Microsoft Store error 0xc000027b on your PC.


Sagar Naresh

Sagar is a web developer and technology journalist. Currently associated with WindowsReport and SamMobile. When not writing, he is either at the gym sweating it out or playing country music on his guitar.

He is an avid traveler and has been to 15 countries, going to more places soon. TRAVEL and WORK is his mantra for a peaceful life.


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.

Windows Store Error 0xc000027b

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:

  1. 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.

    Opening the Date and time window
  2. 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.

    Setting the correct date & time
  3. 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.

    Modifying Time & date

    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.

  4. 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:

  1. 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.

    Typing in “Powershell” and pressing “Shift” + “Alt” + “Enter”
  2. 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
  3. 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

  1. 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.
  2. Once you manage to get inside the Apps & Features screen, go ahead and scroll through the installed (UWP) applications and locate Microsoft Store.
  3. When you see the correct listing, look for the Advanced options menu associated with it and click on it (under Microsoft Corporation).
  4. 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.
  5. After the process is finished, restart your computer and see if the problem is resolved at the next system startup.

Resetting the Microsoft Store

Reset Windows Store via CMD window

  1. 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.
    Running the Command Prompt
  2. 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:
    wsreset.exe

    Resetting Windows Store
  3. 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:

  1. 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.

    Regedit Command
  2. Once you’re inside the Registry Editor, use the left-hand section to navigate to the following location:
    Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\CloudStore\Store

    Note: You can also get there instantly by pasting the location directly into the navigation bar and pressing Enter.

  3. 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.

    Deleting the Cache registry sub-folder of the Microsoft Store
  4. 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.

Kevin Arrows

Kevin Arrows is a highly experienced and knowledgeable technology specialist with over a decade of industry experience. He holds a Microsoft Certified Technology Specialist (MCTS) certification and has a deep passion for staying up-to-date on the latest tech developments. Kevin has written extensively on a wide range of tech-related topics, showcasing his expertise and knowledge in areas such as software development, cybersecurity, and cloud computing. His contributions to the tech field have been widely recognized and respected by his peers, and he is highly regarded for his ability to explain complex technical concepts in a clear and concise manner.

Ошибку с кодом 0xc000027b можно наблюдать в системном компоненте «Просмотр событий» после внезапного закрытия приложения Магазина Майкрософт на Windows 10. Как правило, пользователи пытаются понять, что произошло, почему Магазин так резко прекратил свою работу, после чего и натыкаются на данную ошибку.

Почему возникает ошибка 0xc000027b?

  • Некорректное время и дата. Приложение Магазина может начать работать некорректно из-за неправильно выставленных настроек даты и времени на компьютере пользователя. Исправите настройки — избавитесь от ошибки.
  • Глюк в работе приложения Магазина. Баги во время работы приложения Магазина — это вполне привычное явление. Кстати, привычное и для других UWP-приложений. К счастью, все запросто можно исправить, сбросив каждый компонент приложения Магазина Майкрософт через Powershell.
  • Поврежденные компоненты Магазина. Некоторые компоненты приложения Магазина повреждаются по тем или иным причинам. В таком случае вам потребуется заняться восстановлением поврежденных компонентов с помощью wreset.exe.
  • Поврежденные записи Магазина в реестре системы. Данные Магазина Майкрософт, хранимые в реестре Windows 10, могли быть повреждены, вследствие чего вы и наблюдаете за резким закрытием приложения Магазина и появлением ошибки 0xc000027b.
  • Повреждение системных файлов, важных для работы Магазина. Вы могли столкнуться с повреждением каких-то системных файлов Windows 10, которые активно используются в работе Магазина. Подобную проблему можно исправить, задействовав SFC или восстановление системы.

Методы решения ошибки 0xc000027b

0xc000027b

Метод №1 Выставление подходящих времени и даты

Чтобы полноценно использовать весь функционал Windows 10, на вашем компьютере всегда должны быть выставлены время и дата, совпадающие с регионом вашего проживания. Если вы этого не сделаете, то будете постоянно натыкаться на всевозможные проблемы — к этим проблемам и относится ошибка 0xc000027b.

Чтобы выполнить настройку даты и времени, вам нужно сделать следующее:

  • нажмите ПКМ на Пуск и выберите пункт «Параметры»;
  • в параметрах системы выберите раздел «Время и язык»;
  • нажмите на кнопку «Изменить» и задайте необходимые настройки даты и времени;
  • также вы можете просто активировать опции «Установить время автоматически» и «Автоматически устанавливать часовой пояс», чтобы система самостоятельно выставила все необходимые настройки согласно вашему местоположению.

Как только закончите с настройкой даты и времени, перезапустите свой компьютер и проверьте наличие ошибки 0xc000027b.

Метод №2 «Чистка» приложения Магазина через Powershell

Подобная проблема может возникать из-за одного или нескольких временных файлов, вызывающих ошибки во время процесса валидации, вследствие чего Магазин и закрывается. Многим пользователям удалось побороть ошибку 0xc000027b, избавившись от этих временных файлов.

Делается это следующим образом:

  • нажмите комбинацию Windows+R;
  • пропишите в пустой строчке значение powershell и нажмите Ctrl+Shift+Enter;
  • открыв Powershell, выполните следующую команду:
    • $manifest = (Get-AppxPackage Microsoft.WindowsStore).InstallLocation + ‘\AppxManifest.xml’ ; Add-AppxPackage -DisableDevelopmentMode -Register $manifest
  • перезагрузите компьютер и проверьте наличие ошибки 0xc000027b.

Метод №3 Сброс Магазина Майкрософт

Некоторые компоненты приложения Магазина Майкрософт могут начать работать неправильно или и вовсе быть поврежденными. Благо, вы можете сбросить данное приложение. Выполнить сброс Магазина Майкрософт можно двумя способами — и сейчас мы посмотрим на них оба.

Сброс Магазина через Параметры

  • нажмите Windows+R;
  • пропишите ms-settings:appsfeatures и нажмите Enter;
  • найдите в списке приложение «Microsoft Store» и кликните на него ЛКМ;
  • теперь нажмите на строку «Дополнительные параметры», которая появится ниже;
  • опуститесь ниже в окне и нажмите на кнопку «Сбросить» в соответствующем разделе;
  • нажмите на кнопку «Сбросить» еще раз, чтобы подтвердить свои намерения;
  • подождите появления галочки рядом с кнопкой «Сбросить» — это будет означать завершение процесса;
  • перезагрузите компьютер.

Сброс Магазина через Powershell

  • нажмите Windows+R;
  • пропишите cmd и нажмите Ctrl+Shift+Enter;
  • напишите wsreset.exe и нажмите Enter;
  • подождите появление окошка Магазина — это будет значит успешный сброс приложения;
  • перезагрузите свой ПК.

Откройте приложение Магазина Майкрософт и проверьте наличие ошибки 0xc000027b.

Метод №4 Удаление записей Магазина из реестра

Причиной появления ошибки 0xc000027b могут служить определенные записи Магазина в реестре ОС Windows 10. Вам нужно избавиться от этих записей, а затем посмотреть, разрешит ли это ситуацию или нет.

  • Нажмите Windows+R;
  • пропишите regedit и нажмите Enter;
  • перейдите в следующую директорию реестра:
    • Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\CloudStore\Store
  • выберите папку Cache и удалите ее из выбранного раздела реестра;
  • перезагрузите компьютер.

Метод №5 Восстановление системных файлов

Возможно, в вашей Windows 10 были повреждены системные файлы, применяемые в работе приложения Магазина Майкрософт. Если это действительно так, то вы можете воспользоваться утилитой System File Checker либо вернуть свой ПК в исходное состояние.

Чтобы запустить SFC, сделайте следующее:

  • нажмите Windows+R;
  • пропишите cmd и нажмите Ctrl+Shift+Enter;
  • напишите sfc /scannow и нажмите Enter;
  • подождите окончания работы утилиты;
  • перезагрузите компьютер.

Чтобы вернуть свой ПК в исходное состояние, вам нужно сделать следующее:

  • нажмите ПКМ на Пуск и выберите пункт «Параметры»;
  • перейдите следующим путем:
    • ↓Обновление и безопасность;
    • ↓Восстановление;
  • нажмите на кнопку «Начать» в разделе по возвращению ПК в исходное состояние;
  • теперь выберите опцию «Сохранить мои файлы» и нажмите на кнопку «Сброс»;
  • дождитесь окончания процесса.

Хочется верить, что наша статья была хоть как-то полезна для вас в решении ошибки 0xc000027b.

Понравилась статья? Поделить с друзьями:
0 0 голоса
Рейтинг статьи
Подписаться
Уведомить о
guest

0 комментариев
Старые
Новые Популярные
Межтекстовые Отзывы
Посмотреть все комментарии
  • Как убрать синий экран на компьютере windows 10 при включении компьютера
  • Программа эмулятор дисков для windows 10
  • Windows 10 критическая ошибка при загрузке
  • City guide windows ce
  • Как посмотреть приложения с автозапуском на windows 10