“Attach to process” doesn't show IIS worker thread running under my own account

Multi tool use
“Attach to process” doesn't show IIS worker thread running under my own account
Background
I want to run my ASP.NET site under full IIS on my local machine so I can be debugging more quickly after a rebuild. My team's policy is that developers don't have admin privileges on their machines. Even without admin rights, it should be possible to debug under IIS by configuring the IIS worker thread to run under my own account, but it's not working like that for me.
The worker process is running under my own account:
And when I am running Visual Studio as admin, the thread is shown as running under my own account:
But when running Studio as a non-admin user, the process list doesn't include the IIS worker thread unless I tick "all users", and then the User Name is blank:
Question
Is there anything I can do to get the thread to show up and be attachable when running Visual Studio under my own user?
Thanks Lex, that's interesting. Apparently session 0 isolation came in around 2007. This KB article from around 2015 suggests though that I should nevertheless be able to debug.
– OutstandingBill
Jul 4 at 2:30
You can read your linked threads where I left my comments. ASP.NET development should run VS as administrator, and IIS running a true service account (not your account). If a team ask its members to do ASP.NET without that, I will laugh and quit to save my life. Of course, you have your own judgement.
– Lex Li
Jul 4 at 2:52
By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.
Please use Google to learn session isolation. IIS worker processes, even if running under your account, are in session 0, not your logon user session.
– Lex Li
Jul 3 at 12:26