CreateProcessWithLogonW and UAC

CreateProcessWithLogonW and UAC by Martin_Zugec

Closed

as External Help for as External

Type:	Bug
ID:	771531
Opened:	11/18/2012 8:30:44 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

I'm using CreateProcessWithLogonW with LOGON_NETCREDENTIALS_ONLY in one of my projects.
It works just fine, however the problem is if this process will try to start another process that requires elevation.

First of all, it will get crazy and display duplicate accounts (it will ask you for password instead of regular Yes\No options). Even when you specify the password, the process UI is completely corrupted.

Details (expand)

Visual Studio 2012

1.) Open non-elevated command prompt
2.) Run "Runas /NetOnly /User:xxx cmd" (you can literally use xxx, since it's explicit authentication)
3.) From cmd, try to execute MMC
UAC prompt will pop-up - you can already see that it's corrupted, since there are multiple accounts
4.) Select your account, enter password
5.) Corrupted GUI will appear on screen

English

Any

English

Corrupted GUI

UAC should behave the same way as with any other process.
After UAC prompt, elevated process should be created.

0 attachments

Posted by Microsoft on 1/16/2013 at 7:07 PM

Thank you for your bug submission. The issue you reported appears to be on a released Windows Product. If this issue is severe, causing critical business situations or blocking your product development or deployment, please go to <http://support.microsoft.com> or call 1-800-MICROSOFT for assistance. For Microsoft premier customers, please contact your administrator, your Technical Account Manager, or your Microsoft premier account representative. Other Support links - http://support.microsoft.com/ph/14019#tab13 <http://support.microsoft.com/ph/14019>

Posted by Martin_Zugec on 1/7/2013 at 10:16 PM

Dear Microsoft,

Any feedback on this issue? It's been a while since last update.

Thanks,
Martin

Posted by Microsoft on 11/19/2012 at 11:10 PM

Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Posted by Microsoft on 11/19/2012 at 9:51 AM

Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)