A set of technologies in the .NET Framework for building web applications and XML web services.
Hi JoelS ,
I see you've already exhausted the common fixes (registry keys, Edge flags, certificates, VS settings). This issue appears to be specific to the Windows 11 24H2 + VS 2022 v17.14 combination. Here are some advanced solutions that might help:
Solution 1: Windows 11 24H2 Compatibility Fix The build 26100.65.84 has known issues with localhost SSL handling. Try this Windows-specific fix:
- Open PowerShell as Administrator
- Run:
Get-NetFirewallRule -DisplayName "*IIS*" | Disable-NetFirewallRule - Run:
New-NetFirewallRule -DisplayName "IIS Express Allow" -Direction Inbound -Protocol TCP -LocalPort 1024-65535 -Action Allow - Restart and test
Solution 2: Force HTTP in Project Configuration Since HTTPS redirection is the root cause, override it at the project level:
- In your project's
.csprojfile, add:
<PropertyGroup>
<UseSSL>false</UseSSL>
<SSLPort></SSLPort>
</PropertyGroup>
- In
Properties\launchSettings.json, ensure all profiles use HTTP only:
"applicationUrl": "http://localhost:5000"
Solution 3: IIS Express Advanced Reset Your "redirection.config" error suggests deeper IIS Express corruption:
- Stop all IIS processes:
taskkill /f /im iisexpress.exe - Delete entire folder:
%USERPROFILE%\Documents\IISExpress - Run:
"%ProgramFiles%\IIS Express\iisexpress.exe" /config:"%ProgramFiles%\IIS Express\config\templates\PersonalWebServer\applicationhost.config" - Let it recreate the user config
Solution 4: .NET Runtime Profiling Fix The Event Viewer error (HRESULT: 0x80004005) indicates profiling infrastructure failure. This is a Windows 11 24H2 specific issue:
- Run Command Prompt as Administrator
- Execute:
sfc /scannow - Then:
DISM /Online /Cleanup-Image /RestoreHealth - Registry fix: Add
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSStandardCollectorService150→ DWORDStart= 4 (disabled)
Solution 5: VS 2022 Workspace Reset Since you can't downgrade VS:
- Close VS completely
- Delete:
%LOCALAPPDATA%\Microsoft\VisualStudio\17.0_*\ComponentModelCache - Delete:
%TEMP%\VSLogs - Run VS as Administrator once to regenerate
Solution 6: Windows 11 24H2 Workaround If all else fails, this forces HTTP debugging:
- Install Fiddler Classic or similar proxy
- Configure VS to use proxy for localhost
- Set proxy to intercept and prevent HTTPS redirects
The profiling API error suggests Windows Defender or another security tool might be interfering. Try adding VS and your project folders to Windows Defender exclusions.
Hope this helps!