How do I resolve the following Exception...?

Question

How do I resolve the following Exception...?

CDev-8220 425

Exception thrown at 0x00007FFA4A457F9A (KernelBase.dll) in App.exe: WinRT originate error - 0x8000FFFF : 'WindowsXamlManager and DesktopWindowXamlSource are supported for apps targeting Windows version 10.0.18226.0 and later. Please check either the application manifest or package manifest and ensure the MaxTestedVersion property is updated.'. 'App.exe' (Win32): Loaded 'C:\Windows\System32\bcrypt.dll'. Symbol loading disabled by Include/Exclude setting. App.exe!00007FF613E051EB: LogHr(1) tid(1104) 8000FFFF Catastrophic failure Exception thrown at 0x00007FFA4A457F9A in App.exe: Microsoft C++ exception: winrt::hresult_error at memory location 0x000000847FD1D678. The program '[4332] App.exe' has exited with code 0 (0x0).

The project uses the latest installed version, which was 10.0.26100.4188

targetVersion

However, I tried using an earlier version, and so, installed 10.0.20348.0, and retargeted to that.

targetsAvailable

When I do, this results in other errors, since header files windows.ui.interop.h and presentation.h are no longer available.

I created an app.manifest.xml file in the project.

<?xml version="1.0" encoding="utf-8"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
	<compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
		<application>
			<!-- Windows 10, version 1903 or greater -->
			<maxversiontested Id="10.0.26100.4188"/>
			<supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}" />
		</application>
	</compatibility>
</assembly>

I set the properties.

properties

However, I am getting the same errors.

What do I do to resolve these?

3 answers

Your answer

Answer 1

Darran Rowe 2,171

I just use:

  <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
    <application>
      <!-- Windows 10-->
      <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}" />
      <maxversiontested Id="10.0.22621.0" />
    </application>
  </compatibility>

It turns out that the version in maxversiontested isn't that important, the presence of the element is.

One other thing to try is see if the application manifest contains the maxversiontested element. The manifest can be extracted from the executable using mt, which is part of the Windows SDK.

enter image description here

This must contain the compatibility information that you entered, and it is an xml file.

CDev-8220 425 Reputation points

2025-08-06T20:29:28.8833333+00:00

One other thing to try is see if the application manifest contains the maxversiontested element.

Apparently it doesn't.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"><dependency><dependentAssembly><assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" ... <application xmlns="urn:schemas-microsoft-com:asm.v3"><windowsSettings><dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">True/PM</dpiAware></windowsSettings></application></assembly>

I placed the manifest file in the same directory as the application's exe, but nothing changes.

Should the extension be .xml, or .manifest?

Do I need to add the file in Additional Manifest Files?
Darran Rowe 2,171 Reputation points

2025-08-07T13:17:00.7066667+00:00

The extension doesn't matter, but try adding it to the additional manifest files.
Darran Rowe 2,171 Reputation points

2025-08-08T20:38:05.6533333+00:00

As a little follow up to this, while the extension doesn't matter, I think Visual Studio looks for the .manifest extension.

In Visual Studio, a file with the .manifest extension is seen as a manifest tool file:

so this could enable automatic processing.

But passing the file explicitly will guarantee its inclusion.

Answer 2

Varsha Dundigalla(INFOSYS LIMITED) 795 Microsoft External Staff

Thanks for sharing details. Please find the steps below.

1. Fix the manifest file

Replace your app.manifest.xml with this

`<?xml version="1.0" encoding="utf-8"?>

<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">

<compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">

<application>

<supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>

<maxversiontested Id="10.0.26100.4188"/>

</application>

</compatibility>

<application xmlns="urn:schemas-microsoft-com:asm.v3">

<windowsSettings>

</windowsSettings>

</application>

</assembly>

Make sure this manifest file is:

Added to your project
Set to "Content" and "Copy Always" in its properties

2. Use the latest Windows SDK

Steps:

Open Visual Studio
Right-click your project > Properties
Under General > Windows SDK Version, select 10.0.26100.4188
Apply the same SDK across all projects in the solution
Uninstall older SDKs to avoid confusion

3. Set correct manifest tool settings

In Project Properties > Manifest Tool:

Additional Manifest Files: app.manifest.xml
Embed Manifest: Yes
Generate Manifest: No
DPI Awareness: Per Monitor High DPI Aware

4. Initialize XAML safely in code

Use this C++/WinRT code to check API availability before initializing:
#include <winrt/Windows.Foundation.h>

#include <winrt/Windows.Foundation.Metadata.h> #include <winrt/Windows.UI.Xaml.Hosting.h

#
#
#
int main() {
    winrt::init_apartment(winrt::apartment_type::single_threaded);

    if (winrt::Windows::Foundation::Metadata::ApiInformation::IsApiContractPresent(
        L"Windows.Foundation.UniversalApiContract", 8))
    {
        auto manager = winrt::Windows::UI::Xaml::Hosting::WindowsXamlManager::InitializeForCurrentThread();
        // Safe to use DesktopWindowXamlSource
    }

    return 0;
}

5. Verify runtime environment

Ensure the system is Windows 10 version 1903 (build 18362) or newer
Install the VC++ runtime from Microsoft’s website
Let me know if you need any help with this.
Let us know if the issue persists after following these steps. We’ll be happy to assist further if needed.

CDev-8220 425 Reputation points

2025-08-07T10:56:03.57+00:00

I followed each of these steps, thanks, but the error persists.

Exception thrown at 0x00007FFA4A457F9A (KernelBase.dll) in App.exe: WinRT originate error - 0x8000FFFF : 'WindowsXamlManager and DesktopWindowXamlSource are supported for apps targeting Windows version 10.0.18226.0 and later. Please check either the application manifest or package manifest and ensure the MaxTestedVersion property is updated.'. 'App.exe' (Win32): Loaded 'C:\Windows\System32\bcrypt.dll'. Symbol loading disabled by Include/Exclude setting. App.exe!00007FF613E051EB: LogHr(1) tid(1104) 8000FFFF Catastrophic failure Exception thrown at 0x00007FFA4A457F9A in App.exe: Microsoft C++ exception: winrt::hresult_error at memory location 0x000000847FD1D678. The program '[4332] App.exe' has exited with code 0 (0x0).

Varsha Dundigalla(INFOSYS LIMITED) 795 Microsoft External Staff

Thank you for reaching out. Please find the steps below.

Fix for XAML Islands Crash (0x8000FFFF)

Manifest File (app.manifest)

<?xml version="1.0" encoding="utf-8"?>
<assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1">
  <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
    <application>
      <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>
      <maxversiontested Id="10.0.26100.4188"/>
    </application>
  </compatibility>

  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <requestedExecutionLevel level="asInvoker" uiAccess="false"/>
      </requestedPrivileges>
    </security>
  </trustInfo>

  <application xmlns="urn:schemas-microsoft-com:asm.v3">
    <windowsSettings/>
  </application>
</assembly>

Project Setup Checklist

Add the manifest file to your project.
- Set Content = Yes
- Set Copy to Output Directory = Copy Always
In .vcxproj, add: <PropertyGroup> <WindowsTargetPlatformVersion>10.0.26100.4188</WindowsTargetPlatformVersion> </PropertyGroup>
Project Properties → Linker → Manifest File:
Generate Manifest = No Project Properties → Manifest Tool:
- Additional Manifest Files = app.manifest
  - Embed Manifest = Yes
  - Generate Catalog = No Project Properties → C/C++ → Preprocessor → Definitions:
    Add:_WIN32_WINNT=0x0A00

Initialization Code (C++/WinRT)
#include <winrt/Windows.Foundation.Metadata.h>

#include <winrt/Windows.UI.Xaml.Hosting.h> #include <windows.h>

#
#
#

int main() {
    winrt::init_apartment(winrt::apartment_type::single_threaded);

    if (winrt::Windows::Foundation::Metadata::ApiInformation::IsApiContractPresent(
        L"Windows.Foundation.UniversalApiContract", 8)) 
    {
        auto xamlManager = winrt::Windows::UI::Xaml::Hosting::WindowsXamlManager::InitializeForCurrentThread();
        // Safe to use DesktopWindowXamlSource
    }
    else 
    {
        MessageBox(nullptr, L"This feature requires Windows 10 v1903 (18362) or later", L"Unsupported OS", MB_ICONERROR | MB_OK);
    }

    return 0;
}

Verification Steps

Build your project.

Open the .exe with Resource Hacker.
- Go to RT_MANIFEST section.
  - Confirm that <maxversiontested> appears correctly.
  Run the app on Windows 10 v1903 (build 18362) or newer.

Optional debug check:

  if (!IsWindows10OrGreater()) {
      MessageBox(nullptr, L"OS version check failed", L"Error", MB_OK);
  }

If Still Failing

Check for duplicate manifest declarations.
Ensure no conflicting SDK versions across your solution.
Update to Visual Studio 2022 (17.9.6 or newer).
Install the latest VC++ Redistributable on target machines. Let us know if the issue persists after following these steps. We’ll be happy to assist further if needed.

CDev-8220 425 Reputation points

2025-08-07T18:23:08.8033333+00:00
I followed the steps provided, and got these errors:

PCH warning: an unknown error occurred. An IntelliSense PCH file was not generated. command-line error: invalid macro definition: Add:_WIN32_WINNT=0x0A00 'IsWindows10OrGreater': identifier not found

I believe the first error is due to not generating a manifest.

I had to clean the solution after getting PCH warning: header stop needs to be at global scope. An IntelliSense PCH file was not generated, and IntelliSense is misbehaving.

If Still Failing

Check for duplicate manifest declarations.

I removed the manifests from the exe directory.

There are no other manifests anywhere I can think of.

Ensure no conflicting SDK versions across your solution.

Only one SDK is currently installed - the latest.

Update to Visual Studio 2022 (17.9.6 or newer).

The latest update was recently applied to Visual Studio.

Install the latest VC++ Redistributable on target machines.

The VC++ Redistributable were installed.

Let us know if the issue persists after following these steps. We’ll be happy to assist further if needed.

Thanks.

I appreciate anything that might get me past this block.

What I will do is start from scratch, and see if the problem persists.

If any other suggestions, please go ahead and post them.

Answer 3

Varsha Dundigalla(INFOSYS LIMITED) 795 Microsoft External Staff

Thank you for sharing details. Please find the steps below.

Fix Manifest Not Embedding in Win32/XAML Islands

This resolves the 0x8000FFFF error caused by WindowsXamlManager and DesktopWindowXamlSource failing due to missing or improperly embedded manifest data.

Correct Project Settings

app.manifest file:

Item Type: Manifest
Content: False
Copy to Output Directory: Do not copy

Project Properties → Linker:

Generate Manifest: No
Ignore Import Library: Yes
Additional Dependencies: app.res (if using .rc method below)

Project Properties → Manifest Tool:

Additional Manifest Files: app.manifest
Embed Manifest: Yes
Generate Manifest: No
DPI Awareness: Per Monitor High DPI Aware
Use FAT32 Workaround: Yes

Add to your source file (e.g., main.cpp) or .vcxproj:

#pragma comment(linker, "/manifestdependency:\"type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='*' publicKeyToken='6595b64144ccf1df' language='*'\"")

Nuclear Clean Rebuild

# Close Visual Studio
# Delete these folders from your project root:
Remove-Item -Recurse -Force .\bin, .\obj, .\.vs, .\ipch
Remove-Item *.sdf, *.cache

# Clear MSBuild cache
Remove-Item -Recurse -Force "$env:LocalAppData\Microsoft\MSBuild\"

# Restart Visual Studio as Administrator

Runtime Manifest Verification

Add this to the top of your main source file:

#include <Windows.h>
#include <fstream>

void VerifyManifestEmbedding() {
    HRSRC hRes = FindResource(nullptr, MAKEINTRESOURCE(1), RT_MANIFEST);
    if (!hRes) {
        MessageBox(nullptr, L"Manifest resource not found!", L"Fatal Error", MB_ICONERROR);
        ExitProcess(1);
    }

    HGLOBAL hData = LoadResource(nullptr, hRes);
    LPVOID pData = LockResource(hData);
    DWORD size = SizeofResource(nullptr, hRes);

    std::string manifest(static_cast(pData), size);
    if (manifest.find("10.0.26100.4188") == std::string::npos) {
        std::ofstream("manifest_dump.xml") << manifest;
        MessageBox(nullptr,
            L"Wrong manifest embedded! Saved as manifest_dump.xml",
            L"Configuration Error", MB_ICONERROR);
        ExitProcess(1);
    }
}

// Call this FIRST in wWinMain:
VerifyManifestEmbedding();

Post-Build Verification

Add this PowerShell script as a Post-Build Event:

$mt = "${env:ProgramFiles(x86)}\Windows Kits\10\bin\10.0.26100.4188\x64\mt.exe"
& $mt -inputresource:"$(TargetPath);#1" -out:"$(TargetDir)embedded.manifest"
findstr /C:"10.0.26100.4188" "$(TargetDir)embedded.manifest" || (
    echo ERROR: Manifest not embedded correctly!
    exit 1
)

The Nuclear Option (If Still Failing)

Create app.rc with:

1 RT_MANIFEST "app.manifest"

Add to project:

Item Type: Resource Compiler

Project Properties → Linker → Input:

Additional Dependencies: app.res

Add to code:

#pragma comment(linker, "/manifest:no")

Why This Works

Project Settings Fix – Stops Visual Studio from overwriting your manifest.
Clean Rebuild – Removes all cached/broken builds.
Runtime Check – Immediately stops if the wrong manifest is embedded.
Post-Build Script – Verifies the manifest before you even run the app.
Direct Resource Embedding – Forces the manifest into the .exe without relying on Visual Studio’s manifest tool.
Manifest Dependency Declaration – Ensures OS compatibility is declared at link time.

Let us know if the issue persists after following these steps. We’ll be happy to assist further if needed.

CDev-8220 425

I started over, and when I opened the app's exe in Visual Studio, the RT_MANIFEST contains the maxversiontested.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1"><dependency><dependentAssembly><assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="*" publicKeyToken="6595b64144ccf1df" language="*"></assemblyIdentity></dependentAssembly></dependency><trustInfo xmlns="urn:schemas-microsoft-com:asm.v3"><security><requestedPrivileges><requestedExecutionLevel level="asInvoker" uiAccess="false"></requestedExecutionLevel></requestedPrivileges></security></trustInfo><application xmlns="urn:schemas-microsoft-com:asm.v3"><windowsSettings></windowsSettings></application><compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1"><application><supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"></supportedOS><maxversiontested Id="10.0.26100.4188"></maxversiontested></application></compatibility></assembly>chemas-microsoft-com:compatibility.v1"><application><supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"></supportedOS><maxversiontested Id="10.0.26100.4188"></maxversiontested></application></compatibility></assembly>

Yet when I try to execute the code, the error remains.

Exception thrown at 0x00007FFA4A457F9A (KernelBase.dll) in App.exe: WinRT originate error - 0x8000FFFF : 'WindowsXamlManager and DesktopWindowXamlSource are supported for apps targeting Windows version 10.0.18226.0 and later. Please check either the application manifest or package manifest and ensure the MaxTestedVersion property is updated.'. 'App.exe' (Win32): Loaded 'C:\Windows\System32\bcrypt.dll'. Symbol loading disabled by Include/Exclude setting. App.exe!00007FF613E051EB: LogHr(1) tid(1104) 8000FFFF Catastrophic failure Exception thrown at 0x00007FFA4A457F9A in App.exe: Microsoft C++ exception: winrt::hresult_error at memory location 0x000000847FD1D678. The program '[4332] App.exe' has exited with code 0 (0x0).

I did try the Nuclear Clean Rebuild. However, I got errors.

Remove-Item -Recurse -Force .\bin, .\obj, ..vs, .\ipch Remove-Item : Cannot find path '...\bin' because it does not exist. At line:1 char:1
Remove-Item -Recurse -Force .\bin, .\obj, ..vs, .\ipch
    + CategoryInfo          : ObjectNotFound: (...\bin:String) [Remove-Item], ItemNotFoundEx
   ception
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.RemoveItemCommand
Remove-Item : Cannot find path '...\obj' because it does not exist. At line:1 char:1
Remove-Item -Recurse -Force .\bin, .\obj, ..vs, .\ipch
    + CategoryInfo          : ObjectNotFound: (...\obj:String) [Remove-Item], ItemNotFoundEx
   ception
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.RemoveItemCommand
Remove-Item : Cannot find path '...\ipch' because it does not exist. At line:1 char:1
Remove-Item -Recurse -Force .\bin, .\obj, ..vs, .\ipch
    + CategoryInfo          : ObjectNotFound: (...\ipch:String) [Remove-Item], ItemNotFoundEx
   ception
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.RemoveItemCommand
Remove-Item -Recurse -Force "$env:LocalAppData\Microsoft\MSBuild" Remove-Item : Cannot find path '...\AppData\Local\Microsoft\MSBuild' because it does not exist. At line:1 char:1
Remove-Item -Recurse -Force "$env:LocalAppData\Microsoft\MSBuild"
    + CategoryInfo          : ObjectNotFound: (C:\Users\...\MSBuild\:String) [Remove-Item], ItemNotFoundEx
   ception
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.RemoveItemCommand

The only thing I haven't done is #5 The Nuclear Option.

I tried creating the app.rc file, but I am not sure I am going about adding the RT_MANIFEST correctly.

Perhaps you can step me through that, thanks.

Darran Rowe 2,171 Reputation points

2025-08-09T14:21:38.3433333+00:00

That doesn't matter, as long as the manifest file is showing that max version tested is in the application manifest, then nothing else will change. So embeding the manifest using an external resource file will not change a thing.

Although, did you notice, the manifest that is in your post is invalid?

I will also outright state that I have never done anything more than just put the information into a manifest file ever, even when working with Xaml Islands. The only time I have used a separate .rc file to add the manifest is when I have done a non MSBuild command line build.

One pretty old sample that I have of this even just shows that I don't try too hard with the manifest and it just works. But pay very close attention to the version number. Windows HATES unexpected version numbers here. The safest version numbers to use are the initial release of a version of Windows with a 0 at the end, also, keeping this number as low as possible also helps if you intend to run this on older versions of Windows. So as a serious suggestion, try 10.0.18362.0 and this exact version alone.
CDev-8220 425 Reputation points

2025-08-09T18:39:55.3+00:00
Although, did you notice, the manifest that is in your post is invalid?

Yes, I did two different projects - one where I used projectname.exe.manifest, to see if that made a difference, and one with app.manifest, and I extracted the first, using Visual Studio.

That's the xml I pasted, since it's a lot tidier than the one extracted with mt.exe.

Both are about the same though.

So as a serious suggestion, try 10.0.18362.0 and this exact version alone.

That does not seem possible, for two reasons.

Earlier SDKs are being removed from Visual Studio.

windows.ui.composition.interop.h is not available in earlier versions... although I don't know if I need that.

So, there is nothing more I can do then, to use Xaml Islands in c++. I really don't want to do C#.
Darran Rowe 2,171 Reputation points

2025-08-09T19:04:16.16+00:00

No, I am not stating to use the Windows 10 10.0.18362.0 SDK, but just setting maxversiontested to 10.0.18362.0.

The version in maxversiontested doesn't have to match the Windows SDK version used to build the application. It seems like Windows itself doesn't do much with the number besides check that it matches a certain set of numbers.

To show what I mean,

These screenshots show everything that I mean. The first screenshot shows a Xaml Island application working with maxversiontested in the manifest file set to 10.0.18362.0. It is also showing that this project has the Windows SDK set to the latest version.

The second screenshot shows that the list of SDKs that Visual Studio sees, and it is only able to see 10.0.22621.0 and 10.0.26100.0, what's more, these are the latest versions of those, so they are really 10.0.22621.3235 and 10.0.26100.4654.
Darran Rowe 2,171 Reputation points

2025-08-09T19:06:11.1866667+00:00

Just in case these forums have completely messed up my previous post. I'm not saying to change the version of the Windows SDK that you are using, I am just saying that you should just change the value in the application manifest's maxversiontested to 10.0.18362.0. It doesn't have to match the Windows SDK version.
CDev-8220 425 Reputation points

2025-08-09T23:13:11.8933333+00:00

I was skeptical about this actually working, but it did.

I guess it should though, since 10.0.18362.0 is the maximum version that has been tested.

Thanks for your help. I was feeling rather downhearted, but now my hopes are back up.
Varsha Dundigalla(INFOSYS LIMITED) 795 Reputation points Microsoft External Staff

2025-08-11T08:58:15.97+00:00

Hope you're doing well! Please let us know if the issue is resolved.

Share via

How do I resolve the following Exception...?

3 answers

Your answer