For those of us who have a million external runtimes, it is always wise to backup your library.xml file before updating. Make a copy of that file and move it to a holding folder (directory). Use it after updating and if the updating has changed your library.

(If your update has gone smoothly and your library looks okay, you don't need to do anything else.)

The reason why the library disappears is most likely because of this scenario:

During update installation, the screen asks if you want to retain existing preferences, make a backup, or do a fresh installation. Your choice at this point determines your updated library's destiny.

Also, during update installation, the screen asks where you want to install the Poser Content runtime. Your answer here will also determine the destiny of your updated library.

Old hands like me, who have used Poser since the Stone Ages, will know what to do. More recent converts or newer users may - depending on their update actions - face some bizarre situations post-updating.

There are some of us old-timers (in Poser time-reckoning) who have institutional memory of Poser usage experience. We'll try to share our old-geezer tips, if needed.

Sound advice. As a matter of fact, one should also save all of our pref spec data in a separate backup folder along with our Python scripts.

All sound advice ... I hope all our users read this thread!!

Can it be made a sticky here? We had several queries on other fora that dealt with library prefs.

Infinity10- you describe a problem, but not the solution. Many of us don't know how to back these files up, how to restore them, or which choice in the installer creates which fate. It would also be helpful to post a solution for those of us who did not realize we had to back up the xml.file. It is now somewhat too late for me to do that- how can I make things work right again?

This may be old-hat for some of us old timers .... But what I do is NEVER download new stuff into the primary runtime (unless it is an update to what is already there) OR the provided "download" file that accompanies each full version of Poser since Poser 5. I make a separate runtime and name it Poser X runtime ... or I make specific runtimes ... Architecture, clothing ... OR I label runtimes for stores Renderosity, DAZ, Poser World ... or again for figures ... La Femme, Project E, Apollo ... There are several ways you can do this. Mine is a mish-mash of all of these, but hea, it works for me.

I got 99% of my runtimes on an external drive. The content that comes with the install of the program is installed to the main runtime in my Public Documents folder on my hard drive, Python scripts to Program Files/whatever Poser iteration is the latest/Python/poserscripts...everything else is manually placed into the external runtimes via Windows Explorer. That way, I am completely in control and although during a brand new install I have to manually re-add my runtimes via the little + sign in the Library window, I know exactly what I add. (and I've learned this by reading the manual and readmes of products I purchase. My money, my responsibility not to break it).

If Poser isn't acting up, Like in the case of installing an update it usually safe to use the "Keep Existing Preferences" option during install. If you do that it's important to also remember where you have the base content installed. If you choose a different folder Poser will be in a confused state. The core program will think the content is in one place and the library, using the old preferences will be looking in the wrong place.

nerd posted at 5:11PM Thu, 03 October 2019 - #4365694

If Poser isn't acting up, Like in the case of installing an update it usually safe to use the "Keep Existing Preferences" option during install. If you do that it's important to also remember where you have the base content installed. If you choose a different folder Poser will be in a confused state. The core program will think the content is in one place and the library, using the old preferences will be looking in the wrong place.

I may have such a conflict going....

My library seems to be pointing at the old Poser 11 Content folder in Public Documents, not the one on my secondary drive...

try this

I didn’t get the option to save prefs when I installed on my Mac. Ended up replacing the “Applications support/Poser/11” folder in my Library with a backup. Did the same with the “Python” folder in the main application folder to get ALL my prefs and add-ons working.