Hi I have a strange issue with new Win 10 computers and elevating explorer.exe with my administrative account. I created a powershell app that serves as a menu system to launch other powershell apps with my admin id. So for example I set the admin credential with the following:

The Computer Support.exe then runs as my admin account. Everything works except when I try to do an admin share to the c: drive of a remote computer. It starts explorer.exe as my regular id that I'm logged into the computer with not my admin account. Here's the simple code for the admin share:

The idea that it works on some W10 computers tells us that you have network issues. Also a recent patch caused some issues with access to admin shares on W10. Contact MS support for a patch. The latest update rollup should have fixed this but maybe it didn't.

Thanks for the info but it seems we are going in circles here. Absolutely it has to do with inconsistences with the Win 10 configurations and that’s why I reached out to see if anyone else has run into this. UAC does play a role because it comes up. But the good news is I figured it out. It turns out it is the following:
HKCR\AppID\ {CDCBCFCA-3CDC-436f-A4E2-0E02075250C2}
Ownership needs to be changed to administrators and then the runas key located here needs to be deleted or renamed.
We had this since Windows 7 and for whatever it was missed in some of the Win 10 configurations. I hope this helps out other people.