microsoft / microsoft/WindowsAppSDK
Issue with MakeAvailableAsync() Hanging Without Error
- Dominant language
- C++
- Stars
- 4.7k
- Forks
- 471
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 28
Description
### Describe the bug
Hi,
I have encountered an issue while debugging MakeAvailableAsync(). The function hangs and does not return any error when executed.
System Configuration:
OS: Windows 11 Insider Dev 26120.3291
IDE: Visual Studio 2022
SDK: Windows App SDK 1.7.250127003-experimental3
Project Type: .NET 8.0
CPU: Intel® Core™ Ultra 5 238V
Region: Taiwan
Issue Description:
When executing the following code:
var loadResult = await TextRecognizer.MakeAvailableAsync();
if (loadResult.Status != PackageDeploymentStatus.CompletedSuccess)
{
throw new Exception(loadResult.ExtendedError?.Message ?? "OCR model loading failed");
}
The program stops at MakeAvailableAsync() and does not return any error.
Additional Information:
The same code works correctly on a system with an AMD Ryzen AI 300 series CPU.
No exceptions are thrown, and the application simply hangs at that line.
Could this be related to hardware compatibility, or is there any known issue with Intel Core Ultra 5 processors in this scenario? Any insights would be appreciated.
Thank you!
### Steps to reproduce the bug
var loadResult = await TextRecognizer.MakeAvailableAsync();
if (loadResult.Status != PackageDeploymentStatus.CompletedSuccess)
{
throw new Exception(loadResult.ExtendedError?.Message ?? "OCR model loading failed");
}
### Expected behavior
_No response_
### Screenshots
_No response_
### NuGet package version
Windows App SDK 1.7 Experimental 3: 1.7.250127003-experimental3
### Packaging type
_No response_
### Windows version
_No response_
### IDE
Visual Studio 2022
### Additional context
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the MakeAvailableAsync() call on the reported Intel Core Ultra 5 and AMD Ryzen AI 300 systems, comparing whether the operation completes or hangs. Inspect the returned PackageDeploymentStatus and available diagnostics; done means determining whether this is hardware-specific and documenting a reproducible cause or confirmed resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100