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

gabrielerizzo · Feb 1, 2019

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?

:)

ShiBDiB · Feb 1, 2019

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.

Note: If you've already downloaded d3dx9_30.dll from one of those DLL download sites, remove it from wherever you put it and continue with the following steps.

1. Restart your computer if you haven't yet done so.

The d3dx9_30.dll error might be a fluke or one-time issue and a simple restart could clear it up completely. It's unlikely this will fix the problem, but restarting is always a good first troubleshooting step.

2. Install the latest version of Microsoft DirectX 9. Chances are, upgrading to the latest version of DirectX 9 will fix the d3dx9_30.dll not found error.

Note: Microsoft often releases updates to DirectX 9 without updating the version number or letter so be sure to install the latest release even if your version is technically the same.

Note: Are you a Windows Vista user with DirectX 10? Your game or program may still need DirectX 9 files to run properly so give the installation a try. Don't worry, both versions of DirectX can be run side by side in Windows Vista.

3. Assuming the latest DirectX version from Microsoft doesn't fix the d3dx9_30.dll error you're receiving, look for a DirectX installation program on your game or application CD or DVD. Usually, if a game or other program utilizes DirectX, the software developers will include a copy of DirectX on the installation disc.

Sometimes, though not often, the DirectX version included on the disc is a better fit for the program than the latest version available online.

4. Uninstall the game or software program and then reinstall it again. Something may have happened to the files in the program that work with d3dx9_30.dll and a reinstall could do the trick.

5. Restore the d3dx9_30.dll file from the DirectX 9 software package. If the above troubleshooting steps haven't worked to solve your d3dx9_30.dll error, try extracting the d3dx9_30.dll individually from the DirectX 9 package.

6. Update the drivers for your video card. While it's not the most common solution, in some situations updating the drivers for the video card in your computer could correct this DirectX issue.
Click to expand...

Brink · Feb 1, 2019

Introducing XAML Standard and .NET Standard 2.0

XAML Standard

We are pleased to announce XAML Standard, which is a standards-based effort to unify XAML dialects across XAML based technologies such as UWP and Xamarin.Forms.

XAML Standard is a specification that defines a standard XAML vocabulary. With that vocabulary, frameworks that support XAML Standard can share common XAML-based UI definitions. The goal is for the first version, XAML Standard 1.0, to be available later this year.

Post-specification plans include support of XAML standard in Xamarin.Forms and UWP. You can continue developing your UWP and Xamarin.Forms apps as you do today. When XAML Standard support is enabled, you will be able to reuse and share between the frameworks and expand into more platforms.

To visualize what this support would look like, here’s a side-by-side comparison between today’s XAML in Xamarin.Forms and in UWP:

In the above example – once XAML Standard is supported by Xamarin.Forms, you can use <TextBlock /> and have it supported in a Xamarin.Forms app targeting iOS and Android instead of needing to know and use <Label /> as shown above. In addition to a TextBlock, here are some of the currently proposed items for standardization.

We are at the beginning of a journey that makes it easy for you to reuse your XAML source files between some simple Xamarin.Forms and UWP views. For example – a Settings.xaml page, where you typically have some text, toggle switches and some buttons. You’d only need to design and create one XAML file to describe this UI and that can be used everywhere.

Nothing changes for existing developers – you can continue to use the same APIs you have always used in both frameworks. XAML Standard will help you reuse/share any common UI code that you wish to share between end points.

The XAML Standard v1 draft spec is being defined in the open, we encourage you to start a discussion or give us direct feedback in the GitHub repo here.

.NET Standard 2.0

We are also happy to announce .NET Standard 2.0! .NET Standard is the set of APIs which work in all .NET implementations. A good way to think about it is how HTML5 is today. There are many different browsers which implement HTML parsing and rendering, but the HTML standard is the common glue that holds the web together and allows for interoperability.

.NET Standard was introduced in June of 2016 to bring consistency to the .NET ecosystem. With the .NET Framework, Xamarin & Mono, .NET Core and then UWP, there were many different implementations of .NET and it was very difficult to write code or a library that could work across all of them. Using .NET Standard, and the tooling in Visual Studio, makes it possible to build libraries and NuGet packages that work literally everywhere .NET runs.

The feedback we received on after .NET Standard’s introduction last year was generally phrased as “We like the direction you’re going in, but the set of APIs isn’t large enough to be useful.” The goal with .NET Standard 2.0 is to respond to that feedback and add a large set of .NET’s “greatest hits” into .NET Standard. To do this, we looked at the intersection of APIs between the .NET Framework and Mono. This lead to the 2.0 definition including over 20,000 new APIs and those APIs enable the top 70% of existing NuGet packages to work.

With the addition of .NET Standard 2.0 support for UWP with the Fall Creators Update, .NET developers will be able to share code across all Windows 10 devices, in the cloud and through the rest of the .NET ecosystem. This will also make it easier to reuse existing WinForms and WPF code as many of the most frequently used APIs like DataSet/DataTable, and popularly requested APIs like SqlClient, are now part of .NET Standard 2.0.

You can learn more about .NET Standard here.

Forming the shape of the future

We invite you, the .NET community, to join the discussion and help shape the future of XAML Standard and .NET Standard. You can provide your feedback, both suggestions and issues, at the following locations; .NET Standard on Github and XAML Standard on Github.

Resources:

Github

.NET Standard

XAML Standard

Microsoft Docs

.NET Standard Documentation

Build 2017

Session Video (Presentation Slides)

Ch9 Interview with Tim Heuer, Scott Hunter and Miguel de Icaza

All online Build 2017 Sessions, Presentations and Labs

Click to expand...

Source: Introducing XAML Standard and .NET Standard 2.0 - Building Apps for Windows

gbird · Feb 1, 2019

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.

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

Windows.UI.Xaml.dll gives error 0xc000027b

Windows.UI.Xaml.dll gives error 0xc000027b

Windows.UI.Xaml.dll gives error 0xc000027b

Windows.UI.Xaml.dll gives error 0xc000027b - Similar Threads - Xaml dll error

Desktop windows xaml source onedrive application error

Desktop windows xaml source onedrive application error

0xc000027b

0xc000027b

Wondershare gives error messages_ .dll files missing

Clibpoard history doesn't work and gives Exception code: 0xc000027b

Settings Crashes in Windows 10 0xc000027b

Skype broken with Exception code: 0xc000027b

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

Users found this page by searching for:

windows.ui.xaml.dll exception 0xc000027b launch

0xc000027b exception code windows.ui.xaml

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