Not able to Visual Studio in Debug mode for a web page

Giovine, John 0 Reputation points
2025-11-21T19:41:00.5+00:00

Just installed Visual Studio Community 2026.

Tried to run a simple "Hello World" web page and get the following:

Access is denied.

__Description:__An error occurred while accessing the resources required to serve this request. You might not have permission to view the requested resources. __Error message 401.3:__You do not have permission to view this directory or page using the credentials you supplied (access denied due to Access Control Lists). Ask the Web server's administrator to give you access to 'Z:\Code\WebApplication1\WebApplication1\WebForm1.aspx'.


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.8.9316.0

I did see a comment saying that the updated framework 4.8 was preventing debugging.

How can I get back to debugging my code?

Developer technologies | Visual Studio | Debugging
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Varsha Dundigalla(INFOSYS LIMITED) 3,725 Reputation points Microsoft External Staff
    2025-11-24T10:39:08.1+00:00

    Thank you for reaching out.
    The error 401.3 – Access denied due to ACLs usually means the web server (IIS or IIS Express) doesn’t have permission to read your project files. It’s not caused by the .NET Framework version. Most often this occurs when the project is on a network or external drive (like Z:\) or when folder permissions block the account running the web server.

    Workarounds:

    1. Move the project to a local drive (e.g., C:\Projects). IIS Express often blocks network paths during debugging.
    2. Check folder permissions – Make sure your user account (or IIS_IUSRS if using full IIS) has Read & Execute rights on the project folder.
    3. Run Visual Studio as Administrator – This can bypass permission issues during debug.
    4. Verify authentication settings – In Web.config, set authentication mode="None" or ensure the account is allowed if using Windows Authentication.

    Quick fix: Moving the project to C:\ and running Visual Studio as Administrator solves most cases.

    Please let us know if you require any further assistance, we’re happy to help.

    If you found this information useful, kindly mark this as "Accept Answer".

    1 person found this answer helpful.

  2. Bruce (SqlWork.com) 81,971 Reputation points Volunteer Moderator
    2025-11-22T19:26:36.9433333+00:00

    You probably need to run vs as admin. Right click and select run as admin. I just make copy of the short cut and set run as admin in the shortcut. You can even drag the shortcut to the menu bar.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.