StephenWise wrote:
When a file or folder is downloading, a .download extension is put on the file to show that it's in the process of downloading, but until this update, that extension would go away upon completion.
What it's doing is called an "atomic save". It is creating a ".download" folder and saving the actual download file inside that folder. This is how standard Mac apps have saved documents for many years. It's also what has made Macs virtually unusable on any kind of network. The process of moving the download file out of the ".download" folder and then deleting the folder is something that hasn't worked reliably on a network in over a decade.
Certain 3rd party apps might not use Apple's "atomic save" procedure so they might be more reliable on networks.
It seems there's either a bug that is preventing it from converting into the actual file, or Safari has changed to force us to open the package in that cumbersome manner, perhaps for security reasons? I have found nothing online to indicate that it is a feature and not a bug.
It's definitely a bug, but not really a Safari bug. It's deeper into the operating system's filesystem layer. Considering how old and deeply embedded it is, I can't imagine it ever being fixed.
Just change your download location to the Downloads folder on the startup drive. That's the default and it will work fine at that location.
