Windows 10 Explorer doesn't refresh after copying file off network share

Hi Glenn,

There are several reasons why File Explorer's doesn't refresh. It could be caused by a corrupted hard drive, outdated drivers, and applications. We encourage you posting this as a feedback using the Feedback Hub. We'll gather additional details and information about your concern that will help determine the cause and address it. The feedback items regularly receive Microsoft responses to see what we're doing about your submission. Revisit frequently for status updates.

For more information on Feedback Hub, see our support article and YouTube video

1. Type Feedback Hub in the Cortana search and press Enter.
2. Navigate to Feedback in the left menu, click + Add new feedback tab.
3. Select the Problem, and share the details you want to us to know, and choose the appropriate category and subcategory.

Note: Reproduce your concern if possible while is monitoring is enabled. To do this, click Begin monitoring or Start Capture to start recording and Stop monitoring when you’re done.

1. Once you've completed the form and monitoring, click Submit.  
2. Click My feedback at the top, then find the item you submitted.
3. Open the item you submitted, then click Share.
4. Click Copy link, then paste the link here in your response(It will look like https://aka.ms/<unique link>).

You can perform a clean boot to rule out the drivers and applications. For now, you can apply one of these workarounds to address the File Explorer's refresh issue:

1. Reset Windows Explorer. Open the Task Manager and look for Windows processes under the Processes tab. Right-click Windows Explorer and select End task. Click the File tab and click Run new task. Type explorer.exe inside the box and press Enter.
   
   
2. Restore defaults on your Desktop icons. Right click on the desktop, then click Personalize. Select Themes and click Change desktop icons, then press Restore to default. Press OK.

Feel free to post back if you need further help.

Hi there, thanks for the response.

It's a fresh install and a brand-new PC. So it's very unlikely to be things like malware or corrupt HDD, etc. 

Since writing, I was able at least isolate the problem to happening only when I map a drive to an old SMB server. Taking the computer to a different location and connecting to a newer SMB server, the problem doesn't occur.

My guess is that this has to do with compatibility between the SMB protocol implementation that Windows 10 uses, vs. the old 4 year old SMB server. 

My solution is to replace or upgrade the old SMB server to new.

Any one else who is having this problem should comment on:

1) What kind of server they are connecting to. IE: Microsoft Windows, Linux running Samba, Mac OSX with it's SMB.

2) What version is the OS of the server.