Describe the bug
The Image Description capability is excellent and a key part of how we’re demonstrating Copilot+ PC value.
However, there is a critical servicing issue.
Issue
A pending Windows Update can prevent a Windows AI model from loading, even though:
- The model is installed
- The app has not changed
- The app was previously working
From the app perspective, calls fail or stall with no clear reason. This appears to be related to the model update being delivered via MSIX and not being fully deployed, leaving the model in a blocked state.
Impact
Working apps can stop functioning with no changes. In enterprise, users cannot trigger updates, so apps remain blocked and there's no clear signal or recovery path provided.
This breaks a core expectation: platform capabilities should remain usable until an update is actually applied.
This behavior also appears unique to Windows AI components.
Gaps
AIFeatureReadyState.NotReady is not actionable
- No distinction between install, download, or update-blocked states
- No guidance on how apps should handle this
- No way to reliably test the condition
- Expected Behavior
Pending updates should not block the currently installed model
Blocking should only occur for critical (Pri 0) security issues
Suggestions
Allow existing model versions to run until update is applied
Surface model updates in Windows Update
Provide explicit “blocked due to update” state
Document handling guidance and testing approach
Steps to reproduce the bug
Start with a GA Copilot+ PC with Windows AI Image Description available
Run an app using the model and confirm it works
Allow a Windows Update for the model to become pending (but not installed)
Re-run the same app with no changes
Result:
Model fails to load or stalls with no clear error or guidance
Expected behavior
The currently installed model should continue to load and function even if an update is pending
A pending update should not block runtime functionality
If blocking is required (e.g. critical security issue), it should be explicitly surfaced and detectable
Screenshots
No response
NuGet package version
1.8 and 2.0
Packaging type
Packaged (MSIX)
Windows version
Windows 11 version 24H2 (26100, June 2025 Update)
IDE
No response
Additional context
No response
Describe the bug
The Image Description capability is excellent and a key part of how we’re demonstrating Copilot+ PC value.
However, there is a critical servicing issue.
Issue
A pending Windows Update can prevent a Windows AI model from loading, even though:
From the app perspective, calls fail or stall with no clear reason. This appears to be related to the model update being delivered via MSIX and not being fully deployed, leaving the model in a blocked state.
Impact
Working apps can stop functioning with no changes. In enterprise, users cannot trigger updates, so apps remain blocked and there's no clear signal or recovery path provided.
This breaks a core expectation: platform capabilities should remain usable until an update is actually applied.
This behavior also appears unique to Windows AI components.
Gaps
AIFeatureReadyState.NotReady is not actionable
Pending updates should not block the currently installed model
Blocking should only occur for critical (Pri 0) security issues
Suggestions
Allow existing model versions to run until update is applied
Surface model updates in Windows Update
Provide explicit “blocked due to update” state
Document handling guidance and testing approach
Steps to reproduce the bug
Start with a GA Copilot+ PC with Windows AI Image Description available
Run an app using the model and confirm it works
Allow a Windows Update for the model to become pending (but not installed)
Re-run the same app with no changes
Result:
Model fails to load or stalls with no clear error or guidance
Expected behavior
The currently installed model should continue to load and function even if an update is pending
A pending update should not block runtime functionality
If blocking is required (e.g. critical security issue), it should be explicitly surfaced and detectable
Screenshots
No response
NuGet package version
1.8 and 2.0
Packaging type
Packaged (MSIX)
Windows version
Windows 11 version 24H2 (26100, June 2025 Update)
IDE
No response
Additional context
No response