Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

Upgrading Burp doesn't keep extensions

Danny | Last updated: Mar 17, 2015 11:37AM UTC

Everytime I upgrade Burp, I have to set the environment paths, and re-download the BAPPs. Is there a config file somewhere that can be configured to avoid this?

PortSwigger Agent | Last updated: Mar 17, 2015 01:06PM UTC

Burp stores BApp files in a folder called "bapps" in the same location as the Burp executable. If you run Burp from the same location as previously after you upgrade it, then it should automatically reload the BApps that you previously installed.

Burp User | Last updated: Dec 07, 2015 12:50AM UTC

I have just upgraded to 1.6.31 from 1.6.30. However my extensions are not loading. - Everything is in the same directory. My start script just calls a different jar, also in the same directory. - bapps directory has all the content. - Extender->Extensions->Burp Extensions lists all my extensions. They are just not loaded. - Extender->Options has "Automatically reload extensions on startup" selected. - Manual loading of extensions works.

PortSwigger Agent | Last updated: Dec 07, 2015 08:55AM UTC

We're not able to reproduce this problem. Using Burp 1.6.30 to install an extension from the BApp Store, shutting down, and launching 1.6.31 causes the extension to be reloaded as expected. Is there something unusual about the way you are launching Burp?

You must be an existing, logged-in customer to reply to a thread. Please email us for additional support.