There is no problem with your web.config. Your web site runs under a process. In iis you can define the identity of that process. The identity that your web site's application pool runs as (Network Services, Local System, etc.), should have permission to access and read web.config file.
Update:
This updated answer is same as above, but a little longer and simpler and improved.
First of all: you don't have to change anything in your config file. It's OK. The problem is with windows file permissions.
This problems occurs because your application can not access and read web.config file.
Make the file accessible to IIS_IUSRS group. Just right click web.config and click properties, under security tab, add IIS_IUSRS.
So what is this IIS_IUSRS thing?
Your web site is like an exe file. Just like any exe file, it should be started by a user and it runs according to permissions assigned to that user.
When your site is started in IIS, Application Pool of your web site is associated with a user (Network Services, Local System, Etc. ...) (and can be changed in IIS)
So when you say IIS_IUSRS, it means any user (Network Services, Local System, Etc. ...) that your site is running as.
And as @Seph mentioned in comment below: If your computer is on a domain, remember that IIS_IUSRS group is a local group.
Also make sure that when you're trying to find this user check the location it should be set to local computer and not a corporate domain.
This is a very intermittent behavior. I usually get this issue once or twice a month. Following steps would resolve the problem easily.
Before trying anything else, try iisreset
Step 1: >> Open Run (Ctrl +R) >> type iisreset
If this doesn't work, then try step 2.
Step 2: Open task manager >> Processes >> select Process and right click >> end task. This should kill IIS worker process.
If step 2 doesn't work for you then go to step 3.
Step 3: Task manager >> Services and restart the IISADMIN.
Some of you might not have IISADMIN service so If you can see IISADMIN, right click and restart.
Best Answer
Instead of using the "Use Local IIS Web Server" setting in visual studio I always check "Use Custom Web Server" and point it at my local url. for your example localtest.me with the start url above set to localtest.me
If you still run into problems you can always get into debug mode but doing attach to process instead of F5 and selecting the IIS process.