This issue has been reported by several users following the rollout of Windows 11 24H2. One key change in this update is the enforcement of SMB signing, which can block access to certain NAS devices—especially consumer-grade models that don’t support or have SMB signing disabled. Even though your NAS is visible on the network, attempts to map it may fail with a “file not found” error due to this protocol mismatch.
To resolve this, I recommend checking your NAS settings and enabling SMB signing if supported. Alternatively, you can adjust your Windows security policies to allow unsigned SMB connections, though this may reduce security and should be done with caution.
You can find more details and step-by-step guidance in this support article.
If this helps, feel free to hit “Accept Answer” so others can benefit too 😊. Let me know if you’d like help walking through the configuration!