Generally, you don't.How to move programs from ssd "a" (leaving op sys) to ssd "b" and keep associations in ssd "a".
I have one ssd "a" that is full and I want to move those programs to ssd "b" but still have those programs associated in ssd "a". In other words: be able to access those programs in ssd "b" from ssd "a". I want those programs on another ssd, but I don't want to reinstall (buy) those programs on the second ssd.Generally, you don't.
Please give us a more detailed description of what you're wanting to do.
Applications can't be moved like that.I have one ssd "a" that is full and I want to move those programs to ssd "b" but still have those programs associated in ssd "a". In other words: be able to access those programs in ssd "b" from ssd "a". I want those programs on another ssd, but I don't want to reinstall (buy) those programs on the second ssd.
as the user above said, it's better not to tinker with moving apps around, you could mess things up. this should be done while installing the app so it's configured from start to be on the place you want it.Yep. ssd is 50 gb from being full. The second ssd only has Win 10. I also have a 2 tb hdd that is barely used. So I'd like to use the full ssd as an op sys only and programs and data on one of the other two. But I don't want to reinstall all the other programs on the mt ssd or hdd. I'd have to buy all those prgs again to install on the mt drives.
Again, details.Yep. ssd is 50 gb from being full. The second ssd only has Win 10. I also have a 2 tb hdd that is barely used. So I'd like to use the full ssd as an op sys only and programs and data on one of the other two. But I don't want to reinstall all the other programs on the mt ssd or hdd. I'd have to buy all those prgs again to install on the mt drives.
And this is why I favor portable apps whenever possible.When a program is installed, it makes dozens/hundreds of entries in the Registry and elsewhere.