Inside Poser, logged in the "Renderosity" option, I only see the following options for the items I have:

- Install all;

- Uninstall all;

- Check for new purchases;

- Logout;

- Install/Reinstall (individually);

In case I only want to remove (uninstall) a specific item, do I have to do it manually (outside the app)?

Good question! I would like to know too. Just checked and it seems like my old V4 stuff isn't installed (it is) and uninstalling everything seems a little much. So for now and until someone find a solution, it is manually uninstall for me :D

This is something that the techs should be alerted about and requested.  It is ludicrous that this feature has been overlooked.  It is understood that P12 is still evolving but to not consider an individual uninstall for purchased items is unfathomable.

Agreed, but the implementation would be fragile. Poser is very liberal in the way the user can install files. It even goes to the length that it by default automatically starts to search for files when a file is not found at the specified location.

Unfortunately the default way of arranging content, made mandatory by Renderosity, causes files to be spread over a very wide folder-tree. The structure of that folder tree is shown verbatim in the Poser library, which causes users to endlessly run up and down that tree to combine figures with their materials, supporting props and poses. To make things worse, the structure of the tree is decided by maker rather than by purpose of the content.
No surprise users re-arrange content files to have at least some structure in their runtimes.

The 'purchases' folder is a good thing, be it that I fail to see the difference with the old 'downloads' folder. For me it is a sandbox in which i can examine the new content and rearrange/rename files to my liking, after which I move everything to the runtime folder where i want it to be, leaving 'purchses' empty and ready for the next session. That final Runtime folder ay any time may or may not be connected to the library. . .

Obviously, unless there is a way to update the info Poser has about where files are re-located, Poser will never be able to reliably un-install the product.Therefore better not have he individual un-install.

Un-install all is another way to flush the sandbox.

I like how it works, I never mess with the Poser original installed folders "Downloads", "Included", "Purchases", "Runtime", For my sandbox stuff I use another separate location / runtime.

About implementation, I understand the concerns related to files/folders moved by the user. But it could be as simple as check if all the files can be found in the original place before uninstalling, otherwise pop up a message to the user suggesting the manual way. Windows OS does a similar thing when you are uninstalling an app and it does not find the thing.

The problem that you all making is to assume that Poser keeps track of each and every file.  I have studied the Purchase system and have put in multiple bug reports to make it work mostly correctly.  The purchase system downloads a Manifest file that lists each of the Zip files that make up a purchase.  If you go into your account at Renderosity and look at a item you purchased it could have a single file or several.  Poser downloads each of the files listed in the Manifest and the extracts the content of the file to the Purchase Runtime.  Since a product is suppose to be laid out in a logical manner the files inside the Zip get placed in the correct location.  Once all the Zips for a product have been processed then Poser writes an entry into a file called "PurchasesCache.json" located in the Programs preference file storage location. namely "C:\Users\username\AppData\Roaming\Poser\12".  The entry looks like this: ""120379":{"title":"Maisie Catsuit","installed":true,"size":"231 MB"},".  The Catalog number of the item in the store, The name of the product, if it installed correctly and the size.

As you can see there is nothing to say where the product was installed.  This is conjecture on my part since I don't want to press the uninstall all button.  If you were to press that button then most likely Poser would Zero out the PurchasesCache.json file, and it may even delete all the content in the Purchase Runtime.  However as soon as you run poser again it will recreate the PurchasesCache.json flle with all the items you can reinstall.  Here is an example of a purchase waiting to be installed:

"147548":{"title":"Songbird ReMix Peafowl of the World","size":"168.2 MB"},  The only difference is that is does not say if it installed correctly or not.

Somehow I managed to get the forum to right justify my post.

The issue to uninstall might be possible if you had a list of where all the files were located.  However if you have a product with Template files they get left in the downloads area until you move them manually.  The exception is that a couple of vendors place the templates in a folder inside the Runtime folder so fake out the Poser installer.  But that is non-standard and can not be accounted for.  There is of course the required readme that lists all the files in the product and the tree structure where they are located.  However there is no standard as to where the Readme is placed. or what it is called.

Well, in this case I don't see the single uninstall coming any time soon. One thing vendors could do is to included some kind of uninstall instructions, even (who knows) a batch command, python or something, which of course would only work if files were kept in original place. I would consider including one in case I manage to find a way, It would make everyone's life a lot easier.

Vendors do include a readme file that lists all the files and where they are located within a runtime.  And for the most part each product is self-contained and you can delete the folders of the product and be rid of it.  However you can run into an issue if the vendor does things non standard.  Not to pick on anyone but Dreamland makes a very nice set of city blocks.  And for Poser each block comes with the same textures in a folder just for that block.  So I have a bunch of the same files that are only useful for the one product, without a bunch of work to unify the materials.  I was reading what he did when he released a set of houses for DS.  There he made the first house with all the textures and if you wanted house #4 you also had to buy house #1 to get the textures.  Makes sense if that you don't fill up your storage with a bunch of redundant texture files, but imagine what would happen if you uninstalled house #1.  All the rest of the houses would be left plain white with no color.