[lensman6]

After installing 1703, and reloading the update that installs remote server admin tools, I am unable to start any of AD tools using my admin account via Run As Different User (Shift - right click). It keeps re-prompting for username and password as though it was entered wrong. It wasn't.

If I remove 1703 and drop back, it works fine.

Any known work-around to this or should I just nuke 1703?

[queensoft]

Try this:
Enable a registry value to show Run as different user in the right-click menu (in Windows 10 Start screen).
Copy the following lines to Notepad, and save the file with .REG extension -- for example: showrunas.reg

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Windows\Explorer]
"ShowRunAsDifferentUserInStart"=dword:00000001

Save then double-click showrunas.reg to apply the setting to the registry.
Logoff and login back or restart computer.

Right-click on a Pinned item (pointing to a desktop app) in the Start screen, click More and click Run as different user.

[GrahnD]

We have the same problem after deployment 1703 and it was caused by UEV, if I disabled UEV and rebooted I could run programs as a different user. You can disable UEV with Powershell and the command Disable-UEV.

It is only a workaround since we want to use UEV but our users that needs to use this function are mostly developers and can handle this them self.