Alber
Jan 13, 2025Iron Contributor
Status:
New
Something is preventing you from using Windows App right now.
After being auto-updated from Windows App version 2.0.327.0 to version 2.0.328.0, some of our users can't launch their Windows App anymore and get an error message says:
"Something is preventing you from using Windows App right now."
Since there is no way to control the update process, we could only let our desk users use MSRDC instead, as a temporary solution.
For the frontline users, I could only pray that this problem will not take place until weekend.
If any Microsoft person sees this post, please let the Windows App team know about this and fix this problem ASAP.
- Wei SUN
Microsoft
Pls try to check this box to mitigate this issue
- AlberIron Contributor
OK I got a positive respond from the MS support team.
This issue is a bug of Windows App version 2.0.328.0, will take place when
- The Windows system language is non-English AND
- The Windows user account name is non-English.
The check box mentioned by Wei SUN is a recommended temporary solution.
Well, hope the next new version will be released soon.
- AlberIron Contributor
I believe that box would help in this issue because I found some Windows App logs saying something like language code page not found error.
But as I know, something could be broken with that box checked.
It's not a 100% safe and positive option, especially in enterprise environment.
Since the older version works fine without that box checked, I think we should wait the next new version to have this issue solved.
Thanks for the information anyway.
- Daniel-M
Microsoft
Thank you for taking those steps. We will look into it promptly
- Daniel-M
Microsoft
Thank you for reporting this issue!
On a machine that can reproduce the issue, would you be able to utilize Feedback Hub to submit the issue under the category "Apps" "Windows App"?
- AlberIron Contributor
I've submitted feedback in Feedback Hub with the same title of this post.
Also, I have an open ticket (TrackingID#2501130030002606) about this issue for several days without a positive progress.
Now the number of the devices impacted by this issue is increasing.
Once a device gets 2.0.328.0 update, it almost gets this issue.
The only exception is:
For what I found, some of our Surface devices are fine with 2.0.328.0 and they are all in kiosk mode with Windows App.
All the devices mentioned above are managed by Intune and Windows App is also deployed by Intune.