Check out the Chrome version by typing into the address bar "chrome://version/". Take a look at the "Profile Path", I have seen that the new update to chrome has a new profile automatically added in the "...AppData\Local\Google\Chrome\<new folder>\Default" and all chrome instances are using the same even when you specify it in the selenium chrome options.
From what I can tell, if you have a Chrome browser opened while running your automation script, the new Chrome browser started by the chrome driver will try to use the same user data folder as the one that is already opened. The chrome driver will not be able to access/update the user data files if it is already being in use.
I do not know what the fix is for this new issue, but you can work around it by switching to a different browser if you need to have a browser open and by not having another instance of Chrome running while you are running your automation scripts.