This behavior is consistent & persistent when using macOS 10.13 & 10.13.1b2, with a standard mapping of smb://server/share from a fully updated Windows 2016 server. Only unmapping & remapping the drive, or logging back into the macOS user account or rebooting, will Finder expose the copied files or new folder. Is there a known fix to force a catalog refresh & wipe the catalog cache?ĭetails: When creating either a folder, or copying a file, to a mapped SMB network drive, the folder or file immediately disappears from view in Finder.
MacOS High Sierra 10.13 exhibits an issue when creating new files or folders across a mapped SMB Network Drive which prevents access and visibility.