Any advantage using mklink instead of changing location?

Hi all.

I moved some of my libraries using the following.

from an administrative command prompt
robocopy /MIR %SYSTEMDRIVE%\Users\Joe\Documents D:\Documents

Then booted into safe mode

Then from an administrative command prompt
rmdir /s /q %SYSTEMDRIVE%\Users\Joe\Documents
mklink /D %SYSTEMDRIVE%\Users\Joe\Documents D:\Documents

I did this for most of my libraries and "Public Documents"

Is there any advantage/drawback to doing it the way I did it as opposed to right clicking the library in explorer, selecting "Properties" selecting "Location" tab and moving it that way?

Many thanks

reason I ask is I use a piece of music software (Cubase)

When I create a new project and save it to documents, the window tells me its saving to C:\Users\Joe\Documents

But if I close and reopen it, it opens it from D:\Documents.

While its the same file, Cubase gets confused and asks me the following

The Project file has been moved

Please confirm the project working directory

Document path is D:\Documents\Cubase Projects\.......

New (1)D:\Documents\Cubase Projects\.......
Old (2) C:\Users\Joe\Documents\Cubase Projects\.....

And when I asked about this on Cubase forum, someone responded that to move the libraries, the correct way is to right click on it in explorer, select properties, select the Location tab and do it that way.

I would have thought that using mklink cant be any worse than using the location tab?

Thanks

I used to do it using the location tab, but a few bits of software still managed to put stuff into my C drive.

I would have two Documents in c:\Users\Joe

One pointing to Documents on my D drive, and another that appeared to have the same name, but was an actual directory on my C drive. (Some of the software I use is quite old)

Since using mklink, I haven't had this problem

I could always back up the directory contents, remove the links, then move with location, but I wondered if anyone knows why I should need to do this?