I have made sure that the widget id, version and even display/title names are different than our test network. isEnabled keeps reverting back to 0 on that private configuration file.
Thinking back to when I saw the same issue on my site, I concluded that it was because I didn't write the 'drag and drop' embed bit that would let me add it as a 'feature' on my site.
I think when you add another feature, it resets the 'is enabled' flags for all widgets but those dragged on as a feature.
I had not added the "feature" into the site from the manage area. We had created a feature for our widget but did not think it was necessary for it to maintain the tab at top. I placed it lets see if the tab stays.