This is an issue I have seen frequently in vista, cannot seem to circumvent, and makes me want to pull my hair out.
Everytime CS4 or any CS updater runs, and completes updates, a duplicate documents folder is created in the original root directory where the documents folder used to be located at: C:\\Users\User Name. Despite differences bwteen the properties and directory locations of the two documents folders, the folders are somehow linked and the second cannot be eliminated without obstructing the functionality of the first.
I have noticed the same issue with other updates and new software installations, as well, when a user's shell folder - in this case documents - has been relocated to another drive, volume, or partition. My documents folder is currently located on another volume/hard drive. Since, the amount of data I work with regularly cannot be housed on the OS drive, relocating the first of the two documents folder back to the orginal root directory on C:\\ is not an option.
Please advise if this sounds familiar - or if anyone has discovered a workaround for this nuisance of a problem in vista.
thanks
Everytime CS4 or any CS updater runs, and completes updates, a duplicate documents folder is created in the original root directory where the documents folder used to be located at: C:\\Users\User Name. Despite differences bwteen the properties and directory locations of the two documents folders, the folders are somehow linked and the second cannot be eliminated without obstructing the functionality of the first.
I have noticed the same issue with other updates and new software installations, as well, when a user's shell folder - in this case documents - has been relocated to another drive, volume, or partition. My documents folder is currently located on another volume/hard drive. Since, the amount of data I work with regularly cannot be housed on the OS drive, relocating the first of the two documents folder back to the orginal root directory on C:\\ is not an option.
Please advise if this sounds familiar - or if anyone has discovered a workaround for this nuisance of a problem in vista.
thanks