NTFS is not a POSIX-compatible filesystem and does not store POSIX file ownership information or permissions. This means that the ownership and permissions must be emulated by the Linux kernel upon mounting the filesystem into the virtual filesystem layer.
Given that the filesystem is mounted somewhere under the /run hierarchy ─ which only exists in memory while the system is up and running, because /run itself is mounted as a tmpfs ─ you are obviously relying on the automagic from the udisks2 subsystem of systemd.
Better is to put up a static mountpoint for the filesystem and static mount options in /etc/fstab. Here’s how to do it… 
- First, create a directory that this filesystem must be mounted on. Given that you’re most likely using the filesystem to store personal data for your user account ─ as opposed to data that must be shared between all accounts ─ I recommend that you create this directory inside of your own home directory, e.g. as
/home/canelesso/ssd250, in lowercase (because that’s easier to type).
mkdir /home/canelesso/ssd250
- Next, you must set up the mount options for the filesystem in
/etc/fstab. This requires root privileges, and as I don’t know what graphical environment and GUI editor you’d be using, I’ll describe the procedure by way of a terminal-based editor.
lsblk -o UUID /dev/sda1
Write down that UUID or copy it to the clipboard.
sudo nano /etc/fstab
Add a line for the new filesystem…
UUID=THE-UUID-YOU-COPIED /home/canelesso/ssd250 ntfs-3g auto,nofail,uid=1000,gid=1000,utf8,umask=022,defaults 0 0
Make sure there are no commas between the mount options. Save the file with Ctrl+O and Enter, and exit nano with Ctrl+X.
Exit the terminal by pressing Ctrl+D. If you reboot now, then the filesystem will automatically be mounted at /home/canelesso/ssd250 and will be writable to you. 
Note: As @maycne.sonahoz said, Windows Fast Boot must be disabled, because it leaves the Windows filesystems in an open state, which the Linux kernel will interpret as potential filesystem damage, and then it will resort to a read-only mount to prevent further damage to said filesystem.