DOWNLOAD LOCATION CHANGER · FEATURE GUIDE
Download folder not changing in Chrome? Check the destination
Start by identifying which setting you changed: the Chrome default download location, the folder in a Save As dialog, or the destination inside Download Location Changer. These controls affect different parts of the download workflow.
Confirm the browser and setting you actually changed
Open Downloads settings in the same Chrome profile that starts the download. Check the displayed Location and whether the browser asks where to save each file. A choice in a save dialog can differ from the default directory. Changing a setting in one browser does not configure another browser, and existing files stay where they were saved. Test a fresh download rather than reopening an old download-history entry.
Wait for the download to finish before checking routing
Download Location Changer uses a completed-file transfer for absolute Windows destinations. It is expected for the in-progress download to appear in the initial browser directory. Wait until the browser finishes and the helper completes its transfer. The destination field is not proof that a transfer succeeded: open the target folder and check the actual file.
Check the Windows companion connection
For an absolute path outside the browser download directory, the companion must be installed and connected to the extension in the profile you are using. Signing in to notoow only connects your account; it does not install the helper. Check the extension connection status and the setup guide. Follow the documented installer repair steps if needed, and do not bypass operating-system security warnings.
Check the full path, storage and routing state
Use a complete local path such as D:\Projects\Assets rather than a folder nickname. Check that the drive is mounted, the destination is writable, and both the original and destination locations have sufficient space. Verify that routing is not paused and that any enabled file-type sorting rule points to the intended subfolder. Test with conversion disabled to distinguish a folder-routing problem from a format-conversion problem.
Preserve the original and report a reproducible failure
If the transfer fails, keep the original and record the error, browser version, extension version and companion version. Try a small non-sensitive file in a simple local NTFS folder and note the result. Remove private paths and filenames from screenshots before contacting support. Changing a filename extension does not fix routing or convert a file, and repeated downloads can create confusing duplicate files.