Repository navigation
Protect data folders and recover moved drives - #300
Merged
Merged
Conversation
btsouth
marked this pull request as ready for review
October 5, 2026 03:35
btsouth
added a commit
that referenced
this pull request
Oct 5, 2026
Protect data folders and recover moved drives
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.
Mapped network subfolders are now refused by the shared-folder policy, while local SUBST folders remain supported. Sharing also fails safely when the Windows home path is empty or relative.
Failed uninstalls keep their Apps entry, shortcuts, redirect and location pointer until the data folder is gone. A guarded removal receipt and the preserved launcher allow retries after partial deletion, and normal startup and stale Settings refuse to recreate a partly removed installation. Linked profile and data paths remain protected, with the linked component and instructions for using the real path or removing the data folder manually shown in Apps & features.
Successful removal cleans up owned bootstrap diagnostics and an empty host move store. Other installations, portable host state and unknown files remain, and cleanup errors are reported.
Moved installations record their volume identity and relative folder path, so a drive-letter change can repair owned entrypoints and pointers without trusting a replacement drive at the old letter. Reachable older move records gain this identity on an updated launch; if identification fails, startup logs the error and keeps the working redirect. New moves refuse identification failures with instructions to retry or choose another drive. Older records already disconnected still require their original letter to be restored first.
Portable creation rejects FAT32 and filesystem query failures before expensive work. Startup rejects positively identified FAT filesystems and logs query failures while continuing to launch an existing portable installation. exFAT copies budget the full allocation of copied files, while NTFS copies retain sparse allocation estimates.
Changelog:
Shared folders and uninstall retries now protect your data more reliably, and moved installations recover when their drive letter changes. Portable copies detect FAT32 limits before copying and account for exFAT storage needs, while existing installs keep launching when volume identification is unavailable.