Why does Safari not download files after Sequoia update?

Solution: It is bull that I need to do this but it works. Copy the download link from safari and open it on google or chrome and then down load it there. If you don't have the google app just download it from the app store for no charge.

I confirm the same problem is STILL in effect on November 27, 2024! Is Apple even attempting to fix this!! I want to keep using Safari but the workflow issues are too severe now. I'm afraid I'm fast becoming a Chrome user. Apple...where are you on this?!?

Version 18.1.1 (20619.2.8.11.12) also does not fix the issue. This is outrageous!

I recently decided to switch to Safari for all my web work, thinking it is the best browser for use with my new M4 Mac Mini. Totally the wrong move since I store all my files on my Synology NAS. Now I have to revert to Firefox or Chrome.

This problem has been here for months and still no fix from Apple???

The problem goes furter then only downloading. When you download multiple times there is sometimes a good download between the errors. so its not abstract at all times. cannot find the trigger when is succeeds, but it is only 5% of all clicks.

The problem also occurs when you upload files to a google drive for instance. The upload fails. when you do the same with another browser it succeeds.

It occured after the latest update which was pushed , thats why i hate updates

It happens to me on any drive, internal, external, Lucid, etc. I learned on another post

that you can right click select "show package contents" and the full file is in there.

Copy and paste to pull it out.

But the work around is becoming a P.I.T.A.

Safari 18.0.1 has not fixed the issue, still have the same problem. "Cannot move file" error when saving to a NAS.

Safari 18.5 and the download issue persist, only downloading when you choose desktop.

very disappointing...

If privacy is a concern for you, use Firefox instead Chrome ;-) . Saving files to network shares works right in Firefox. I'm pretty sure this is a Safari issue and not macOS one, as Safari is the only application showing this problem.

Yes, getting the same issue as well. Spent hours trying to fix this issue that has been created. I have been downloading pdf files to my NAS Synology server for years - direct from Safari. Now I cannot do it. I must change the download location to a local drive and then copy across to the right folder in the server. So, now I have a few more steps to complete, which I didn't have beforehand. Not happy.

To clarify - I can now only get a xxxx.pdf.download filename to my server, but if I switch it and save it on my desktop for example - it will be xxxx.pdf.

This is very annoying.

Just ran into this tonight downloading to NTFS (Paragon) external drive. On Ventura 13.7.1 (22H221), Safari 18.1.1 (18619.2.8.111.7, 18619). What I found is that Safari left a bunch of ".download" files. If you open a Terminal (CLI) and navigate to the appropriate directory, you should notice that those *.download files are actually directories, not files. Within the directories you should see the files you're looking for. I had downloaded some large DMG and ZIP, and used 7zip to verify those... so everything seems to be OK, even though Safari can't move the files after download.

1.) Open finder, navigate to the parent of the relevant download folder

2.) Right-click on the folder, select "New Terminal At Folder"

3.) type: ls *.download => you should see the files listed along with the directory names

4.) type: mv *.download/* . => this moves the contents of each *.download directory into the current directory

5.) Verify your files, as necessary for sanity (e.g., you can install 7zip via MacPorts or whatever)

6.) type: rmdir *.download => this will remove the empty directories... if not empty, this will fail

I have this problem on "Version 13.7.1 (22H221)" - Ventura.

Fine saving to local storage on the iMac, but receive the error "Cannot move file" in Safari when saving to NAS (Synology). Just leaves a 'filename.download' in the target directory/folder that's not useable.

Adam

I have downloaded files using Safari for years without any problem. Now, I cannot download any PDFs to my NAS, which is wholly unacceptable. This makes no sense - how could Apple's QA testing not have caught this? Until I am made aware of this being corrected by Apple, I am ditching Safari. Buh bye....

You are absolutely right. I have been using a NAS and store everything in the NAS from 2018. I download all the files directly to the NAS and I haven't had issues until this week that I installed macOS Sequoia in a new hard drive. I mean downloading from Safari. Firefox and Librewolf have no issues.

As you are saying, Safari downloads the file in a folder of the same name of the file it's downloading and I think I may have some clues and why is happening. Finder in macOS Ventura and also Monterey had quite a bug when renaming files in a network shared folder. Once moved or renamed, Finder was not able to find the file in a while (the time it took no-one knows). If you open the file from a Third party application chances were that you could open the file, even QuickLook would work but Finder was unable to open it, rename it or move it. So I think it's happening again, when in Safari you configure downloads to ask you or even if you set it up to download directly without asking to network because of Safari using Finder internally it creates a Folder with the actual file name, then it renames to .download so it can move the original downloaded file to the parent folder and delete the temp file, and because it's slow once renamed it does not find the renamed folder, so it cannot get inside and move the download original file.

I am going to paste my nsmb.conf I created manually after lot of research because I had a lot off issues when this bugs were happening with a Qnap NAS but not with a TrueNAS server.

Keep in mind that this is for trusted local area network environment where I am just myself.

Probably you should not disable packet signing nor session signing.

One of the biggest issue is Finder's Caching. (Path Finder and other third party managers work way better).

[default]

# Disable NetBIOS
port445=no_netbios

# Disable packet signing
signing_required=no

# Disable SMB session signing
#validate_neg_off=yes

# Enable SMB session signing
validate_neg_off=no

# Disable directory caching
dir_cache_max_cnt=0
dir_cache_max=0
dir_cache_off=yes

# Disable SMB notifications
notify_off=yes

# Lock negotiation to SMB2/3 only
# 7 == 0111  SMB 1/2/3 should be enabled
# 6 == 0110  SMB 2/3 should be enabled
# 4 == 0100  SMB 3 should be enabled
protocol_vers_map=6

# SMB Negotiation (normal, smb1_only, smb2_only, smb3_only)
smb_neg=smb3_only

# Use NTFS streams if supported
streams=yes

# Set hard or soft mount of shares
# Hard mount: a request is issued repeatedly until the request is satisfied.
# Soft mount: tried until completed, the retry limit is met or the timeout limit is met.
soft=yes

# Apple SMB extensions
# ReadDirAttr: This feature changes how macOS handles reads of file metadata stored in
# alternate data stream when listing the contents of large directories. Finder info,
# access rights, and resource fork size are returned more efficiently for the files
# in the directory.

# OsxCopyFile: With the SMB2 protocol, Microsoft implemented server-side optimizations
# when copying files between directories on the file share. The extension introduced by
# Apple ensures that all Apple-specific file metadata is properly copied along with the file
# itself. The copy process is also simplified as it is executed in just one request as
# opposed to splitting the requests into logical chunks which was the case in
# the original feature.
aapl_off=false

# File IDs are legacy compatibility elements for AFP and are not supported by SMB.
file_ids_off=yes

# Disable multi-channel connections and prioritize the wired ethernet connection
mc_prefer_wired=yes
mc_on=no

# Enable multi-channel
#mc_on=yes

But I still have not found a solution to the Safari download issue.

OT168 wrote: "does apple know about this?"

OT168 ~ Apple will if you tell them:

Feedback - Safari - Apple

Contact Apple for support and service

õ¿õ¬

ManifestingMagic wrote: "...Apple...where are you on this?!?"

ManifestingMagic ~ They're not in these user-to-user communities. Use these:

Feedback - Safari - Apple

Contact Apple for support and service

õ¿õ¬