I'm having trouble accessing a shared folder on file explorer from a new device, but can access it on my old device. Why is this?

Question

"I am trying to support someone with a data migration from one device to another device. On the old laptop there is a shared folder on file explorer that we can access. It allows us to view the files and edit them etc. However, when we use the new laptop to access the same exact link on file explorer to the same shared folder, the folder force closes. What could be causing this?"

When we try to access the shared folder from the new laptop, it force closes the file explorer application. It only closes when we open on sub folder within the shared folder. All of the other sub folders work just fine. We've tried just about everything to figure out why it is force closing but have yet to find what is triggering this.

Answer 1

Hello Alexnader,

Experiencing force closure of File Explorer when accessing a specific subfolder from a new laptop, while it works fine on another device, suggests a few potential issues that could be causing this behavior. Here are some steps and considerations to help diagnose and potentially resolve the issue:

1. Check for File System Errors:

It's possible that the subfolder in question has file system errors or corruption that only manifests when accessed from the new device. Run a file system check from the old laptop (or the server hosting the folder if applicable). You can do this by right-clicking on the drive in File Explorer, selecting 'Properties', then 'Tools', and finally 'Check'.

2. Permissions Issue:

Ensure that the new laptop has appropriate permissions to access the subfolder. Permissions might not be set universally across the entire shared folder. Compare the security settings of the subfolder that is causing File Explorer to crash with other subfolders that are accessible without issues.

• Right-click on the folder, select 'Properties', go to the 'Security' tab, and check the permissions. Ensure that the user account or group used on the new laptop has the necessary access.

3. Compatibility Issues:

If the shared folder uses any software or services that integrate with File Explorer (like certain file preview or indexing services), there might be compatibility issues with the new laptop. Check for any necessary software updates or configurations that need to be mirrored from the old laptop to the new one.

4. Network Issues:

Ensure that the network settings on the new laptop are configured correctly and similarly to the old laptop. Differences in network configurations (like different network profiles or firewall settings) could affect how network resources are accessed.

---

5. File Formats or Encodings:

Sometimes, specific file types or encoding within a folder can cause issues depending on the system accessing them. Check if the problematic subfolder contains any unusual file types or large files that could be causing the crash.

6. Graphics Drivers or File Explorer Extensions:

Outdated graphics drivers or problematic File Explorer extensions could cause crashes when rendering file previews or thumbnails. Update the graphics drivers on the new laptop and consider disabling shell extensions using a tool like ShellExView to isolate the issue.

---

7. Application Logs:

Check the Event Viewer on the new laptop for any application logs that occur at the time of the crash. This might provide more insight into what is causing File Explorer to close abruptly.

• Press Win + R, type eventvwr.msc, and press Enter. Look under 'Windows Logs' > 'Application' for error messages related to Explorer.exe.

8**. Clear File Explorer History:**

Sometimes, clearing File Explorer's history can resolve issues caused by stale or corrupt data:

• Go to File Explorer Options (search in the Start Menu), under the 'General' tab, click on 'Clear' next to 'Clear File Explorer history'.

By following these steps, you should be able to narrow down the cause of the problem. If the issue persists, you may need to temporarily move the contents of the problematic subfolder to another location to see if the issue is related to the specific content within the folder.

Best regards

Rosy