{"id":1190,"date":"2016-07-28T13:52:48","date_gmt":"2016-07-28T13:52:48","guid":{"rendered":"http:\/\/avastar.online\/?page_id=1190"},"modified":"2016-07-28T13:52:48","modified_gmt":"2016-07-28T13:52:48","slug":"installation-issues","status":"publish","type":"page","link":"https:\/\/avalab.org\/avastar\/293\/reference\/troubleshooting\/installation-issues\/","title":{"rendered":"Install & Update"},"content":{"rendered":"

<\/image>Installation & Update Issues<\/h2>\n
\n
Installing an Add-on should be a straight forward and easy task. But despite our attempt to make things easy, sometimes things go wrong. This Guide is a collection of Issues which have been reported by others. Ok, we have only one issue by now, but we add them as they get reported.<\/div>\n
Don’t Panic. Your problem can be fixed.<\/div><\/div>\n<\/div>\n

When the update fails<\/h3>
\n

When you update an Add-on in Blender, then normally the following steps are performed:<\/p>\n

    \n
  1. The installer disables the current version of the Add-on.<\/li>\n
  2. The disabled Add-on is removed from the system (deleted from disk).<\/li>\n
  3. The new Add-on version is installed.<\/li>\n
  4. You now can enable the new version manually<\/li>\n<\/ol>\n

    However sometimes you can not enable the addon after a new version is installed. this can happen because the first step (disabling the Add-on) does not disable all of the software. So it may happen that the old Add-on leaves some traces in the running Blender, which may result in subsequent errors when you try to enable the new Addon Version.<\/p>\n

    When the above situation happens to you, then please go ahead as follows:<\/p>\n

    Step 1: Remove traces<\/h4>\n
    \n
    \n