@sonal96-ttn  Agree with @ArpitVarshney  . You are not logged in to your explorer.  

I am exactly not sure exactly how you are modifying the configurations, because as per my understanding, if you have a config under your apps config folder, then when you modify it via system console, it shud get saved under the same path or else if no specific path is mentioned, it will get saved u...

So you have a custom config node, but when you update it via felix console , it is not getting saved under your config ?

Always make sure to have a custom config node for your configurations under your apps. For now the existing one , can you package it ? 

I would write a servlet , query the pages with component reference and remove the component via servlet. The steps would be pretty much same as what @gaurav3415  mentioned above. 

Happy to help Tushaar 

Can you give a sample of the code how you are invoking the class and just a skeleton of your class (remove any main business logic ) ?

You can always define a specific schema to a specific folder. Please read through https://helpx.adobe.com/in/experience-manager/6-3/assets/using/metadata-schemas.html#Applyfolderspecificmetadata  https://docs.adobe.com/content/help/en/experience-manager-65/assets/administer/metadata-schemas.html#App...

You can find the ACS commons tool I was mentioning in https://adobe-consulting-services.github.io/acs-aem-tools/features/aem-fiddle/index.html . It is basically a utility provided by Adobe Consulting Services. If you install this in your AEM server , you actually don't need to stop or install bundle...

Try some other browsers and see if you are seeing the same behavior