Symptoms
Windows Backup Copies Desktop Files but Skips a Folder Linked from Another Drive. This symptom affects a particular operation; a related feature may still behave normally.
To capture the distinction, begin with this observation: Identify the linked folder’s real drive and whether it is a junction, symbolic link or library location. Note whether the failure follows a specific file, account, input, session or device.
Why It Happens
Three different mechanisms can lead to a similar visible symptom. Use a comparison before deciding which applies:
- The source location is excluded, virtual, online-only or not represented as expected in the backup catalog.
- A sync conflict, different account, library scope or file-version mapping points to an older item.
- Destination format, permissions, filename limits or restore tooling cannot reproduce original metadata.
Use the diagnostic comparisons below to distinguish these possibilities before choosing a correction.
Before Making Changes
Never interpret a successful backup banner as proof that linked content was saved. A backup marked successful is not verified until files can be restored; protect the only copy and use a separate restore folder. Use a disposable test item if the operation can send notifications or alter shared data.
Write down each original setting so you can reverse the change; do not risk the sole remaining copy of a file or account record.
Problem-Specific Diagnosis
The useful question is which layer makes the same action behave differently. Check a specific disposable file in its source location, backup catalog and restored destination. These observations guide testing; they are not a diagnosis until verified.
| What you observe | What it suggests | Next comparison |
|---|---|---|
| One path succeeds and the original path fails | File visible in the source but absent from backup points to scope or exclusion. | Compare a normal file in the backed-up folder with one behind the link; use a separate direct backup for excluded targets. |
| The result changes when account, source or device changes | Correct backup content but an incorrect local display points to syncing or account view. | Identify the linked folder's real drive and whether it is a junction, symbolic link or library location. |
| Both the original and control fail consistently | A restore with correct bytes but changed names or permissions points to metadata mapping. | Review junction/reparse-point handling and test a restore into a spare directory, not over the original. |
Step-by-Step Troubleshooting
Start with the Beginner tab for reversible checks. Choose Advanced only when the comparison points to a specific setting or integration.
Capture the symptom without changing data
Identify the linked folder's real drive and whether it is a junction, symbolic link or library location. Note the device or app, affected item, time, and visible state. This baseline will let you tell a genuine fix from a temporary refresh.
Check the safest relevant setting
Open the folder's true location and check which folders the Windows backup feature explicitly covers. Make only that one small change, then repeat the original action once before adjusting anything else.
Compare an independent path
Compare a normal file in the backed-up folder with one behind the link; use a separate direct backup for excluded targets. Keep other variables steady. If the alternate path works, focus on the layer that differs; if both fail, investigate shared dependencies.
Confirm the everyday workflow
A restored test file from the linked target opens from independent backup media. Repeat the check from a fresh session if practical. Restore the original setting if this change did not improve the result.
Identify the failing boundary
Review junction/reparse-point handling and test a restore into a spare directory, not over the original. Record the result and the original configuration so it can be restored; do not infer a cause without a comparison.
Separate client, account and device layers
Check a specific disposable file in its source location, backup catalog and restored destination. Determine whether the mismatch follows the content, account, hardware path or application before choosing a targeted correction.
Apply one narrow correction
Based on the evidence, adjust only the affected rule, profile, input, route or supported feature setting. Open the folder's true location and check which folders the Windows backup feature explicitly covers. If a change is unavailable for this model or account, stop rather than forcing it.
Prove the fix and document rollback
A restored test file from the linked target opens from independent backup media. Test the original failing path and the control path. Reverse the last change if it introduces another fault; preserve screenshots of the working state.
Solution Checklist
Common Mistakes to Avoid
Do not initialize storage, overwrite the newest file, mass-delete old revisions or assume one cloud copy is a tested backup. For this specific scenario: Never interpret a successful backup banner as proof that linked content was saved. Changing more than one setting at once makes it harder to identify the actual cause.
How to Verify the Fix
A restored test file from the linked target opens from independent backup media. Repeat the original action in a fresh session rather than assuming that one successful preview proves the repair. Confirm the control path still works.
- Reproduce the fault with the original input before making a change.
- Rerun the comparison: Compare a normal file in the backed-up folder with one behind the link; use a separate direct backup for excluded targets.
- Verify that the successful result persists after reopening the affected app or reconnecting the device.
- If other functionality regresses, restore the recorded previous settings.
If the Problem Continues
If the test still fails, preserve the baseline and the comparison results. Review junction/reparse-point handling and test a restore into a spare directory, not over the original. Share the exact device model, app version, relevant screenshots without private information, and the smallest reproduction with official product support or the account administrator. If the fault is hardware-related or safety-critical, use authorized service instead of bypassing protection.
Prevent Recurrence
Keep at least one separate tested backup and periodically restore representative files, including paths and permissions. Document the final working setting and the test that demonstrated success. After an app, device, router or account change, check a small example again before relying on the workflow.
FAQ
Does this mean the entire device or service has failed?
Not necessarily. The source location is excluded, virtual, online-only or not represented as expected in the backup catalog. Compare a known-good path before assuming a widespread fault.
What should I test before resetting anything?
Identify the linked folder’s real drive and whether it is a junction, symbolic link or library location. Check a specific disposable file in its source location, backup catalog and restored destination. This is more informative than a full reset.
How can I tell whether the problem is solved?
A restored test file from the linked target opens from independent backup media. Verify the result again after reconnecting or restarting the relevant app or device.
Disqus hosts the discussion. Comments load automatically as you approach this section and may use cookies.