Fix misleading documentation about RoamingSettings persistence through Microsoft Store updates#5671
Draft
Fix misleading documentation about RoamingSettings persistence through Microsoft Store updates#5671
Conversation
Contributor
|
Learn Build status updates of commit b2f36e5:
|
…oft Store updates Co-authored-by: GrantMeStrength <1928855+GrantMeStrength@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] ApplicationData.Current.RoamingSettings does not persist between updates via Microsoft Store
Fix misleading documentation about RoamingSettings persistence through Microsoft Store updates
Sep 24, 2025
Contributor
|
Learn Build status updates of commit 46d8c85: ✅ Validation status: passed
For more details, please refer to the build report. |
Contributor
|
Ipsita - any idea who could confirm this proposed update? Thanks. |
|
this is wrong, localsettings arent persisted either |
Gijsreyn
pushed a commit
to Gijsreyn/windows-dev-docs
that referenced
this pull request
Oct 6, 2025
…9153112110sync_temp For protected branch, push strategy should use PR and merge to target branch method to work around git push error
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.
The current documentation incorrectly states that "The system also preserves the contents of these data stores when the user installs an update to your app" without clarifying that this doesn't apply to RoamingSettings during Microsoft Store updates.
This issue has been reported by developers who relied on this documentation and discovered their RoamingSettings data was wiped during Store updates, causing data loss for their users.
Changes Made
Updated
/hub/apps/design/app-settings/store-and-retrieve-app-data.md:[!IMPORTANT]warning in the roaming data section explicitly stating that RoamingSettings may not persist through Microsoft Store updatesUpdated
/uwp/get-started/settings-learning-track.md:Impact
These changes provide developers with accurate information about data persistence behavior, preventing potential data loss scenarios. The updates maintain consistency with existing deprecation warnings about roaming being unsupported in Windows 11 while clearly directing developers to use LocalSettings for critical data that must survive app updates.
The documentation now correctly reflects the actual behavior of the Windows app data system during Microsoft Store updates.
Fixes issue where ApplicationData.Current.RoamingSettings does not persist between updates via Microsoft Store.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.