Repository navigation
fix: clarify Windows AI API unavailable messaging - #630
Merged
Merged
Conversation
Use neutral messaging for NotSupportedOnCurrentSystem while preserving readiness checks, model preparation, hardware requirements, and existing diagnostics. Add focused regression tests and document the availability behavior. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The messaging changes are consistent with the stated scope and adequately covered by focused tests.
0 open findings
What changed in this PR
Clarifies Windows AI API availability messaging without changing compatibility checks or hardware requirements.
Changes:
- Adds neutral unavailable-state titles and descriptions.
- Prevents stale messaging after exceptions.
- Adds regression tests and documentation.
| File | Description |
|---|---|
docs/AddingSamples.md |
Documents availability messaging behavior. |
AIDevGallery/Samples/Definitions/WcrApis/WcrApiHelpers.cs |
Adds neutral unavailable descriptions. |
AIDevGallery/Models/ModelCompatibility.cs |
Selects state-specific titles and descriptions. |
AIDevGallery/Controls/WcrModelUnavailable.xaml.cs |
Shares the default issue title. |
AIDevGallery/Controls/SampleContainer.xaml.cs |
Applies and resets availability messaging. |
AIDevGallery.Tests/UnitTests/WcrApiConfigurationTests.cs |
Adds regression coverage for compatibility states. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Milly Way (weiyuanyue)
approved these changes
Oct 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR addresses misleading Windows AI API availability messaging reported on RTX Spark devices.
The existing unavailable screen showed "This device isn't supported" followed by a hardware requirement such as "A Copilot+ PC is required." This can make the unavailability of a particular API or model look like a problem with the device's Copilot+ PC status.
The updated messaging improves the experience on RTX Spark and other devices by describing API availability rather than device branding. It does not enable additional APIs or models, or bypass readiness checks.
What changed
NotSupportedOnCurrentSystem, show "Windows AI API unavailable" with the default message "This Windows AI API is currently unavailable on this device.", without the hardware-requirement prefix.Ready/NotReadyhandling, other state descriptions, Limited Access Feature diagnostics, and Windows Insider guidance.Tests