Symptoms
Windows can browse the NAS share, but a backup application does not offer it.
The useful clue here is what still works: Windows can browse the NAS share, but a backup application does not offer it. That narrows the test to the point where the two paths diverge.
- The failing path: Windows can browse the NAS share, but a backup application does not offer it.
- Control test: Open the share in File Explorer, then compare the backup app’s network-path input and permissions.
- A successful outcome: A disposable file is written and restored through the backup application.
Why It Happens
Keep the source, the backup set and the restore location separate. A test restore to an empty location provides stronger evidence than a green dashboard.
There are three genuinely different layers worth checking; use the observation in the table to decide which one is implicated. None of these is proven merely by the symptoms.
- Backup service runs as different user. This explanation predicts a different result in the comparison test or the more advanced inspection.
- Share browse discovery blocked. This explanation predicts a different result in the comparison test or the more advanced inspection.
- Account lacks write permission. This explanation predicts a different result in the comparison test or the more advanced inspection.
Before Making Changes
Never grant guest write access to protect the backup job.
Save the current configuration or capture screenshots of the exact option values; where a file or recording is involved, work on a disposable duplicate. If this is shared equipment, ask the owner or administrator before changing it. Prefer a safe test item over real customers, medical decisions, paid transactions or irreplaceable data.
Write down the device model, platform, observed time of failure, and which action still works. These details will distinguish an unsupported feature from a malfunction and will be useful if escalation is required.
Problem-Specific Diagnosis
Use the following route rather than guessing based on a product name. The expected differences are designed for this particular failure.
| Action or observation | Meaning of the result | Decision |
|---|---|---|
| Open the share in File Explorer, then compare the backup app's network-path input and permissions. | Does the failure follow the affected file, profile, connection or location? | Keep this result as the baseline; do not alter two systems at once. |
| Use a supported UNC/network path and the correct dedicated backup account. | Does the low-impact correction restore the exact failure without altering the control case? | Re-test; reverse the change if the original symptom is unchanged. |
| Check service-account credentials, app execution context and SMB protocol requirements. | Does this separate share browse discovery blocked from account lacks write permission? | Use documented diagnostic views rather than blind replacement. |
| A disposable file is written and restored through the backup application. | Is the same original symptom gone after a normal repeat? | Record the pass condition and preserve the working settings. |
If the control case fails as well, the fault may be broader than this guide. Stop at that point and check the shared power, account, access or media path before applying the narrow fix.
Beginner and Advanced Paths
Start with the reversible Beginner path. The Advanced path examines a different layer when the first route fails; it is not a repetition of the same restart or setting.
Step-by-Step Troubleshooting
Choose the simple reversible checks first, then investigate the deeper system layer only if necessary.
Record the exact failure
Confirm the behavior without guessing: Windows can browse the NAS share, but a backup application does not offer it. Note the affected account, file, connection or physical control and record the current settings. Never grant guest write access to protect the backup job.
Run the passing comparison
Open the share in File Explorer, then compare the backup app's network-path input and permissions. Keep the working and failing cases separate. If both fail, stop and investigate the common path instead of forcing a narrow repair.
Apply the least disruptive correction
Use a supported UNC/network path and the correct dedicated backup account. Change only this setting or route; do not reset unrelated profiles, storage or pairing records. Save the previous value so it can be restored.
Retest and keep the result
A disposable file is written and restored through the backup application. Repeat after a normal reopening or reconnect. If the control case gets worse, undo the last change and write down the difference.
Separate the three underlying layers
Test the hypotheses independently: backup service runs as different user; share browse discovery blocked; account lacks write permission. A green status indicator does not distinguish them. Use the recorded control case as evidence.
Inspect the deeper component
Check service-account credentials, app execution context and SMB protocol requirements. Use only read-only diagnostics or documented configuration screens first. Capture logs and timestamps rather than removing the component or reinstalling software blindly.
Cross-check with an independent path
Where possible, repeat “Open the share in File Explorer, then compare the backup app's network-path input and permissions.” using a second supported account, safe sample file, physical input, known-good cable or alternate compatible application. Change only one variable and note which outcome follows it.
Choose a reversible targeted escalation
If the deeper check isolates a fault, use a vendor-supported fix or authorized service for that layer; otherwise restore original values. Finish only when: A disposable file is written and restored through the backup application. Never grant guest write access to protect the backup job.
Solution Checklist
Solution Checklist
Common Mistakes to Avoid
- Treating backup service runs as different user as certain just because the behavior looks familiar.
- Changing several independent settings together, which makes the result impossible to interpret.
- Skipping the safety boundary: Never grant guest write access to protect the backup job.
- Calling the issue fixed after one status indicator changes but before repeating the original operation.
- Discarding the working configuration or the only original file before a replacement has been verified.
How to Verify the Fix
A disposable file is written and restored through the backup application.
Use the same baseline case: Open the share in File Explorer, then compare the backup app’s network-path input and permissions. Then repeat the previously failing operation after a normal close-and-open, reconnect or next scheduled cycle, whichever matches the scenario. Confirm the part of the system that was already working is still unaffected.
Where a result can be measured, retain the test timestamp, file name, screenshot or device state. A temporary success that cannot be repeated is not yet a confirmed repair.
If the Problem Continues
Escalate from the surface symptom to the narrower mechanism: Check service-account credentials, app execution context and SMB protocol requirements. If this identifies a hardware, account-policy or service limitation, use the manufacturer’s authorized support route rather than bypassing controls.
When opening a support case, supply the model, software/firmware version actually installed, the failing operation, the successful comparison, the three possible explanations checked, and the final observed result. Redact account identifiers, access codes, serial-number photos and personal information from public posts.
Prevent Recurrence
Keep a short note of the confirmed working configuration, particularly the setting implicated by backup service runs as different user. Repeat the disposable comparison after an app update, device replacement, major account change or new connection only when that change plausibly affects this issue.
Retain a recovery path: spare test material, a saved profile, a restore point, a backup copy or official service information, as appropriate for the device. Do not schedule risky resets as routine maintenance.
FAQ
Is backup service runs as different user definitely the reason this happens?
No. The same symptom can come from share browse discovery blocked or account lacks write permission. First compare the affected and unaffected paths: Open the share in File Explorer, then compare the backup app’s network-path input and permissions. Do not assume any cause without a different outcome.
How can I safely rule out share browse discovery blocked?
Try the reversible correction only after documenting the control: Use a supported UNC/network path and the correct dedicated backup account. If the behavior does not change, restore the old value and use the deeper observation: Check service-account credentials, app execution context and SMB protocol requirements.
What if account lacks write permission turns out to be responsible?
Do not force an unsupported setting or a factory reset. Keep the evidence and ask the manufacturer or responsible administrator to investigate the isolated layer. The measurable pass condition remains: A disposable file is written and restored through the backup application.