shywolf@ Thanks for the issue.

Tested the issue on Windows 7,10 and Mac OS 10.12.6 on the reported version 65.0.3325.181 and the latest Canary 68.0.3410.0 and unable to reproduce the issue.

1. Launched Chrome and set the Download Location in chrome://settings/Downloads
2. made sure the 'Ask where to save each file before downloading' option is turned off.
3. Downloaded a test doc and can see that if is downloading without showing any prompt to save the file.
Attached is the screen cast for reference.

Request you to update chrome to the latest Stable 66.0.3359.117, retry the issue on a new chrome profile without any flags/extensions and update the thread with the observations.

Thanks..

Deleted: 837225.mp4 2.1 MB

	837225.mp4 2.1 MB View Download

Hi,

Thanks for your reply. I did test this in Chrome 66 already. I just did the reporting with 65. But I'll try with a new profile. First observation in the screencast though, you keep everything local. The issue can be reproduced by setting the download location to a network based location, albeit an UNC path or mapped network drive.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Reproduced in Chrome 66.0.3359.117 with a clean profile, no flags and without extensions (fresh install).

Unable to reproduce the issue on Win-10 using chrome latest stable #66.0.3359.139 and latest canary #68.0.3425.0.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1) Opened chrome browser after fresh installation.
2) Set the download directory to a network location Z:
3) Made sure the setting "Ask where to save each file before downloading." is turned OFF
4) Downloaded a file and observed that chrome did not ask for where to save the file.

shywolf@ - Could you please check the attached screen cast and please let us know if anything missed from our end. Also please check the issue on latest stable #66.0.3359.139 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!

Deleted: 837225.mp4 3.3 MB

	837225.mp4 3.3 MB View Download

I've been playing around a bit with this issue, and it turns out that if the network location is a Windows based fileshare there's no problem, but if the share is on a Netapp filer the described problem occurs. I'm going to try and find a way to use a Samba share too to see if it's some kind of obscure interoperability issue.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Ok, I found a Samba share and it does the same. Also, what I just noticed is 
that the default path the "save as" interface points to is actually the "Downloads" Windows special folder, probably a default choice for Chrome. If that folder is also redirected to a non-Windows based file share then the "save as" default path seems to be the Chrome program directory, but that aside.

Now, I assume Chrome simply uses the underlying OS for file operations so this might actually be a problem with Windows 7 interoperability with non Windows based fileshares (Samba, Netapp). I'll have to investigate that.

Hmm, I lied...it does work with Samba. Turns out I was trying to write to a readonly share. Oops. Netapp Filer doesn't work though. It's probably environmental.

Wow...

I did a file access trace as a last ditch resort (generally doesn't give much useful information) but this time I stumbled across this:
Operation: CreateFile
Path: \\netapp_svm\userhomedir$\<username>
Result: Name Invalid

At first I thought it was a problem with the fact the share was hidden, but I couldn't reproduce it with other hidden shares, on either Netapp or Windows. So I created a new subdirectory under \\netapp_svm\userhomedir$ and tried again. No complaints there, everything works. The problem seems to be limited to certain subdirectories under \\netapp_svm\userhomedir$. At first glance I don't see anything wrong with them, but for some reason either Windows or Chrome doesn't like them. I'll need to do an indepth analysis.

Fun.

For some reason the offending directories (and only the top level directories) have an "R" attribute. Apparently something checks if a directory is writable before downloading a file to it. In and of itself not a bad idea, but in this case it has bit us in the behind. I need to fix this in my environment. At least it's not an issue in Chrome!

@shywolf: From your comment#11 to comment#13 it is understood that the issue is with your environment rather than with chrome. It would be highly helpful if given a confirmation on closing this issue if this isn't getting affected by chrome.

Thanks!

Yeah, it looks not to be an issue in Chrome, so as far as I'm concerned this can be closed.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

As per the confirmation given by the reporter in comment#15 closing this issue and marking it as Won't fix.

Thanks!