- Dec 11, 2012
- 4
- 0
- 0
Not sure if that was spotted on, but it is reproducible, as I ran into it each and every time when trying it on my 1520
The outcome of the bug render all appx/appxbundle-packaged (8.1) apps pretty much useless. This includes system apps that were separated from the OS, like Calendar, Podcasts and even Battery Saver. Yes, it's a serious bug, which results in inability to manage battery-saving options, whether or not an app is allowed to run in the background or if it I allowed to override battery saver mode.
All you need to do, is install all Additional language support resources onto the phone, i.e.:
So that's it: all apps that are based on appx packaging are now crashing on startup.
* - applies mostly to Nokia/Microsoft devices, other OEMs like HTC often love to include only several pre-selected languages for a phone that is to be sold in a specific region.
-------------------------
Update: Hell it is basically the exact same bug I spotted on Windows desktop some years ago (during Windows 8 Developer Preview) and it got NEVER fixed despite the fact that I constantly reported it to various channels. And now with the inclusion of WinRT to Windows Phone 8.1 the bug got carried over.
If you add too many languages to the list, appx apps, i.e. all Windows Store apps will start to behave slowly, even to the point of crashing on splash screen if loading for too long. Even though Windows allows slightly more time tolerance when opening an app, than Windows Phone 8.1 allows. Windows Store itself will still open, but won't be able to connect, so it will show a connection error page instead of Store home page.
On both systems any associated bugs are simply getting fixed by removing any extra languages from the language list.
Slightly related: if you install all Language Packs (MUIs) and all the smaller Language Interface Packs (LIPs) to a Windows desktop up to the point of exceeding the length of the connection string, you will be unable to use Windows Update, Microsoft Update or any other service, that uses it directly or indirectly. You will not be able to (until you remove some language packages) to check for updates, get definitions for Windows Defender/Security Essentials/System Center Endpoint Protection, install or update any apps from the Windows Store, etc. Windows Update in Control Panel will give connection errors.
While it may not be needed for a typical user on Windows client to have such a setup, that issue is definitely a problem on Windows Server as language resources are treated on a system level: imagine a Remote Desktop Services host with dozen of users, each needing their own user interface language in their profile session.
---------------------------------------
Perhaps there aren't too much exposure of these bugs yet, and that's why Microsoft never fixed them... How about making a news article about all this, so Microsoft will notice, that yes there is a problem? Since as we can see, they are migrating all platforms to appx apps when implementing app universality, and that comes bundled with the described language bugs. The first doesn't let you to use the apps at all, the second doesn't let you to install and update apps at all.
The outcome of the bug render all appx/appxbundle-packaged (8.1) apps pretty much useless. This includes system apps that were separated from the OS, like Calendar, Podcasts and even Battery Saver. Yes, it's a serious bug, which results in inability to manage battery-saving options, whether or not an app is allowed to run in the background or if it I allowed to override battery saver mode.
All you need to do, is install all Additional language support resources onto the phone, i.e.:
- In Settings - Language add all available* languages to the list, though keep English on top of the list to not cause interface locale change on restart to a language that you may not understand. Tip: instead of constantly selecting "move up" in the context menu, you can remove it and re-add - new languages are always added to top of the list. The language list works the same way as on Windows 8/8.1 desktop in determining the language order.
- Add all keyboards in Settings - Keyboard.
- Add all speech TTS engines in Settings - Speech. Though it will require you to reboot for each pack installation.
So that's it: all apps that are based on appx packaging are now crashing on startup.
* - applies mostly to Nokia/Microsoft devices, other OEMs like HTC often love to include only several pre-selected languages for a phone that is to be sold in a specific region.
-------------------------
Update: Hell it is basically the exact same bug I spotted on Windows desktop some years ago (during Windows 8 Developer Preview) and it got NEVER fixed despite the fact that I constantly reported it to various channels. And now with the inclusion of WinRT to Windows Phone 8.1 the bug got carried over.
If you add too many languages to the list, appx apps, i.e. all Windows Store apps will start to behave slowly, even to the point of crashing on splash screen if loading for too long. Even though Windows allows slightly more time tolerance when opening an app, than Windows Phone 8.1 allows. Windows Store itself will still open, but won't be able to connect, so it will show a connection error page instead of Store home page.
On both systems any associated bugs are simply getting fixed by removing any extra languages from the language list.
Slightly related: if you install all Language Packs (MUIs) and all the smaller Language Interface Packs (LIPs) to a Windows desktop up to the point of exceeding the length of the connection string, you will be unable to use Windows Update, Microsoft Update or any other service, that uses it directly or indirectly. You will not be able to (until you remove some language packages) to check for updates, get definitions for Windows Defender/Security Essentials/System Center Endpoint Protection, install or update any apps from the Windows Store, etc. Windows Update in Control Panel will give connection errors.
While it may not be needed for a typical user on Windows client to have such a setup, that issue is definitely a problem on Windows Server as language resources are treated on a system level: imagine a Remote Desktop Services host with dozen of users, each needing their own user interface language in their profile session.
---------------------------------------
Perhaps there aren't too much exposure of these bugs yet, and that's why Microsoft never fixed them... How about making a news article about all this, so Microsoft will notice, that yes there is a problem? Since as we can see, they are migrating all platforms to appx apps when implementing app universality, and that comes bundled with the described language bugs. The first doesn't let you to use the apps at all, the second doesn't let you to install and update apps at all.
Facebook
Twitter
Instagram