Why is Native Access 2 sometimes ignoring the "Download Location" setting?

B.Minor

During the last few weeks I noticed a very strange behavior of Native Access 2 not seen before. Even if there are different folder settings specified in NA2's "File->Settings" menu, namely one dedicated folder definition for the "download" location and another one for the actual library "content", NA2 seems to ignore the "download" folder definition in most cases. Here's an example showing my personal setup:

In contrast to what has been specified there, the new download and installation method seems to work differently. The new approach doesn't necessarily apply to all existing NI & partner downloads (yet), but it seems to be more and more common by NI to write directly to the pre-defined "content" folder instead of downloading the related archive (either an ISO-file or a zipped installer package) to the pre-defined "download" location first and then install the content from there. I don't hope that this new approach is becoming a new NI standard, as from my perspective it introduces two very negative aspects:

- Unnecessary disk wear is applied to the content SSD:

Usually SDDs - especially if library contents are permanently stored there for occasional loading and playback reasons only - shouldn't be exposed to unnecessary file writing and erasing procedures. However, with the new NA2 approach, huge temporary files are already downloaded to the final "content" location before actually re-shaping themselves and forming the actual library structure at the same spot. In fact, a bunch of ".aria2" files may be downloaded in parallel to the destination path right from scratch, even if these file junks will need to be re-organized first before unnecessary temp files are then being deleted again. Over time that new download approach directly at the content location will create a scuttered file structure across your SSD, just increasing loading times and most of all causing unnecessary SSD wear. Not that I've experienced such negative side effects by now, but that's really not the way the "content" folder should be abused as a "working" folder for temporary file manipulation.

- Personal backups of library installation sources are not possible anymore:

This new approach now also prevents users from fetching up related ISO source files or related original installer packages for personal backup purposes. Before it was at least possible to grab downloaded source files from the associated "download" path during their actual installation time towards the "content" target, just before getting "automatically" deleted by NI again. This enabled users to make personal backups of the original executables. However, that new download method directly "streaming" to the "content" target doesn't include any installers or ISO files anymore; instead, a download process just messes around inside the actual content folder. Unfortunately, NI is still not offering any official file repository where users could access all of their purchased products, including earlier versions which are sometimes appreciated to be available for compatibility reasons. In case any currently installed library should ever become messed up for whatever reason, that manual backup of original installers mentioned before is an important precaution requirement, allowing anyone to initiate quick re-installations whenever needed. In case a real disaster should ever happen someday and NI doesn't even provide any official online download possibility anymore for all your purchased products (e.g. just because some of these might have become "a little bit older" in the meantime etc.), you are really screwed if you haven't collected your own backup sources already.

Therefore, the only clean and appreciated approach would be to stick to the initial download and installation concept where the "download" path is always used and treated separately from the defined "content" location. In other words, downloads should only be performed exactly there where they are supposed to happen as specified; and of course the actual installation should be executed from there only.

@Hayo_NI:

What was the reason to deviate from the original NA download and installation approach? Or will there eventually be a dedicated repository/database available soon from where registered useres can safely obtain all versions of their purchased products? THX.

LostInFoundation

If things are going as you mention (and I have no reason to doubt it), I strongly suspect your second observation is the main reason. All the steps NI is taking lately are focused toward keeping users tied to them and dependent from them, so that their decisions can’t have any kind of workaround

Therefore finding a way allowing them to impede you to keep your installation iso is something I see as very close to the direction they are taking

I could be wrong, as I could be wrong on the reasons why they want to remove NA1, hide products in NA2 or remove the database accessible by users…but so many clues all leading to the same conclusion are frankly at least suspect…