Norton, for some reason, doesn't think the configure file is safe. Not only that, but it deletes it.
The bug seems to have gone away with the latest patcher build, can you confirm this?
It also didn't reappear in the 2013-07-06 build. I'm closing this bug now since the root issue seems to have been solved on Norton's end; feel free to re-open in case it re-appears in the future.