Depending upon options checked when installing things, HALion installers will sometimes use a combination of ‘shortcuts’ which point to actual vstsound archives. So…if library manager points to a ‘short cut’ that then points to a vstsound archive, and you delete the actual archive while leaving the shortcut…well…trouble.
If you delete an actual archive and leave a shortcut to it in place…trouble…
Personally I like to get rid of the ‘short cuts’ that sometimes get scattered in various ‘user directories’ and move all HALion and GrooveAgent content somwhere in “%SYSTEMDRIVE%/ProgramData/Steinberg/” hierarchy of directories. All of the Stienberg apps with media bays know to look in this location for new or revised content on a regular basis. This helps insure that my Stienberg stuff will work no matter the user account one logs in with.
If I’m short on drive space for the partition/device…I still like to keep things HALion in “%SYSTEMDRIVE%/ProgramData/Steinberg/”, but I’ll simply use ntfs junctions to point from there to the secondary device/partition.
If for some reason you do NOT want other accounts on the system to have access to your Stienberg apps…then of course you could take opposite approach and lock things down in protected ‘user directories’.
If you use the library manager to move things it should go smoothy and everything be found. If something gets missed, one can force an instance of HALion to refresh its content in the HALion media browser. I.E. Open an instance of any variant of HALion (Sonic SE, Sonic, or HALion 5/6, Groove Agent 4, etc.), go to the media-bay, and click the ‘refresh’ button. You could do that in stand alone mode, or from a plug in variant. My understanding is that the core HALion engine is same for the whole family of plugins (different UIs and features enabled)…so you’d only have to refresh it in ONE for them all to pick on the content in future sessions.
If you also happen to have Cubase, Nuendo, HALion 5/6, or GrooveAgent 4 on the system, you can also customize your rig by adding or deleting directories (or entire hierarchies of them) that the HALion engine will ‘keep scanned pretty much at all times’ for potential content.