New drive/synth content/can I just change new drive name?

Hey all, I'm moving all my synth content from a "normal" internal drive to a soon-to-be installed SSD drive.  It will be an in-place copy/transfer, i.e., both drives will remain in the PC, at least for now.  To avoid having to redirect the software synth's drive path's to the new drives, is it possible to just rename the new drive - after moving all of the content, but before opening the synth to which it is linked - to the same drive letter as the old drive, so that the synth just looks for the drive letter and finds the content as if nothing's changed?
 
For example, a synth is now directed to drive E for it's content.  I install a new drive, move all of the content to that new drive - which windows named G, for example, by default - and rename the new drive (the G drive) to "E."  I then - and only then - open up the synth.  Will it look for its usual/old path to E, find it - and its content - on the (new, formerly G) E drive as if nothing's changed?  Or will the name change alone not be enough?  I hope that question is somewhat clear!
 
Thanks!

Perfect, thank you. Just to be clear, by "synth," I assume you're referring to content, since the synth itself - the VST, I guess - is already installed in the C drive?

Anyhow, thanks again, and you also answered/confirmed the proper way of re-naming a drive letter, so I should be all set.

The main use for most people of a symlink is that some software only installs to the C: drive. If you are using a small C: drive then tricking it into installing to a symlink masquerading as a folder on that drive can move the actual code and data to the link target. Linking is fast and very low demand, but you will only get the performance of the drive that the link points to. So a symlink on a fast SSD will result in things actually running from a slower drive if that is where the link points. That should be obvious, but sometimes is overlooked.