Since the implementation of the private keys in the web.config, there are still a lot of new users who do not read the documentation and forget to copy them from their old config upon upgrading.  I realize everyone should read the docs and in a perfect world, that would be great.  The fact is, it is not a perfect world and I see several posts a week, sometimes a day, dealing with this very issue. 

As developers who need to adjust apps for use cases, maybe it would be a good time to add a warning before the upgrade process that tells the user if they have not done that, they need to click cancel to stop the upgrade process, make the changes and go through the process again.  I think it would stop a lot of frustration for newbies and even some of us who forget things from time to time, not to mention, the tons of posts filling up the forums over and over and over.

I have not upped to 4.7 yet, so if this was already implemented, I apologize for the post.  Otherwise, I would love to hear feedback from the community on this suggested enhancement.

Wallew

I realize that change was made, but lets look at an all to often scenario for a newbie.

1. Upload upgrade files to existing site.
2. Rename web.config to webold.config. (Not knowing for forgetting to change the keys)
3. Change connection string in release.config and save as web.config (sometimes skipping step 2 and overwriting the original web.config.)
4. Post in forum because they can't login.
5. Constantly answering the post with, change the keys.....  I have also noticed lately, a lot of older members don't even bother answering.
6. Result - Frustrated DNN user.

Wallew

The point is you shouldn't rename or delete the web.config once it is set up.

My typical process is more like this:

1. Install DNN first time using Install package
2. If not using the Install wizard or starter kit method, edit realease.config to proper settings for installation environment and save as web.config
3. New DNN version released
4. Get Upgrade package
5. copy over existing install
6. check release.config for new nodes and add to my existing web.config.
7. Happy DNN user

I understand what you are saying , but like Mitch, it's going to be pretty hard to stop and I'm not even sure how you could do it.  That's why the approach that is presently used has been taken.