Not new, but this seemed like a good place to post this.

I have had trouble lately with the Morphs++ not working, even after reinstalling the morphs and the base figures. I've done it manually, however, and I'm wondering if it must be done with the installer. M4/V4 are all I use from DAZ, so I've been able to avoid the DSON mess for a while.

No, DSON is not needed for Generation 4 characters.

You need to initialize V4 and M4 before the ++ morphs will work correctly.

The files will be in the filepath:

...Smith MicroPoser 10RuntimeLibraries!DAZ

Double click on DzCreateExPFiles-V4.bat

A window will pop up, you will not need to do anything just let it run, when it is done it will close

For M4 the file you need to double click is:

DzCreateExPFiles-M4.bat

Once those are both done re-open poser load your figure, inject the morphs++ from the pose folder and they should now work properly.

Yeah, I've tried that too. There seems to be a bigger problem.

When V4/M4 are first initialized numerous absolute references are written in the morph channels which are valid as long as the original directory structure is maintained. If the install directory changes the morphs will no longer work. The references are absolute and not relative so any change to the original install location will "break" the figure. If this is a reinstall simply put them in a directory structure which matches the original. Use notepad++ (or notepad) to open the file in your RuntimeLibraries!DAZVictoria 4V4BODYChnnls.pz2 to verify the original installation directory structure; do not try and edit this file to correct the directory structures unless you want to spend a long and frustrating time editing because this is not the only place this method of referencing is used by DAZ. After you know where the files need to go simply place them there; that's why I still have an old Smith Micro Poser runtime on my "C" drive after numerous computer rebuilds, It was easier to do this then a reinstall of V4/M4 since the version which I have uses the old installer which throws errors after every install and doesn't even recognize Poser Pro.exe as a valid Poser executable.