<?xml version="1.0"?>
<rss version="2.0">
<channel>
<title>SyMenu - Troubleshooting &amp; Bug Reports - V.4.14-UAC features not work with built-in adminis - Messages</title>
<link>https://ugmfree.it/forum/messages.aspx?TopicID=399</link>
<description>SyMenu - Troubleshooting &amp; Bug Reports - V.4.14-UAC features not work with built-in adminis - Messages</description>
<language>en-us</language>
<docs>http://blogs.law.harvard.edu/tech/rss</docs>
<pubDate>Thu, 03 Dec 2015 08:03:04 GMT</pubDate>
<lastBuildDate>Thu, 03 Dec 2015 08:03:04 GMT</lastBuildDate>
<item>
<link>https://ugmfree.it/forum/messages.aspx?TopicID=399</link>
<title>Message from Gianluca</title>
<description><![CDATA[I will study a solution sooner or later.<br/>Thanks.]]></description>
<pubDate>Thu, 03 Dec 2015 08:03:04 GMT</pubDate>
</item>
<item>
<link>https://ugmfree.it/forum/messages.aspx?TopicID=399</link>
<title>Message from VVV_Easy_Symenu</title>
<description><![CDATA[V.4.14-The UAC SyMenu features does not work with the Windows built-in administrator account.<br/>I describe how to reproduce the bug.<br/>1) Three accounts:<br/><ul><li>"UserSyMenu" -&gt; Normal Users Group</li><li>"Owner" and "Administrator" (Built-in administrator) -&gt; Administrators Group</li></ul>2) Running with "UserSymenu" (NO UAC authorization):<br/><ul><li>Elevating with password "Owner" -&gt;UAC=OK; Shield=OK (appears)</li><li>Elevating with password "Administrator" -&gt; UAC=OK, Shield=NOK (no appears)</li></ul>(Note: To be able to use built-in administrator account: "net user administrator /active:yes" or with "lusrmgr.msc").<br/>------------------------------------------------------------------------------------------<br/>Even it is not important issue, it's a pity to keep without fixing so I want to try to help.<br/>I think it is easy to detect if you work in "Elevate mode" with the Windows CMD "whoami"<br/>For instance the following solution:<br/><ul><li><b>whoami /groups | find "S-1-16-12288" && Echo I am running elevated, so I must be an admin anyway ;-)</b></li></ul>works fine in Elevated CMD windows with the build in Administrator and with "normal" administrator account.<br/>------------------------------------------------------------------------------------------<br/><b><u>Links:</u></b><br/>Windows CMD "whoami"<br/><ul><li> <a href="http://ss64.com/nt/whoami.html" target="_blank" rel="nofollow">http://ss64.com/nt/whoami.html</a></li></ul>Proposed Solution:<br/><ul><li><a href="http://stackoverflow.com/a/17803989" target="_blank" rel="nofollow">http://stackoverflow.com/a/17803989</a></li></ul>Windows Integrity Mechanism Design (Mandatory Levels):<br/><ul><li><a href="https://msdn.microsoft.com/en-us/library/bb625963.aspx" target="_blank" rel="nofollow">https://msdn.microsoft.com/en-us/library/bb625963.aspx</a></li></ul>Security Identifiers Technical Overview:  <br/><ul><li><a href="https://technet.microsoft.com/en-us/library/dn743661.aspx" target="_blank" rel="nofollow">https://technet.microsoft.com/en-us/library/dn743661.aspx</a></li></ul>Windows desktop applications &gt;  Design &gt;  Guidelines &gt;  Windows Environment &gt;  User Account Control <br/><ul><li><a href="https://msdn.microsoft.com/en-us/library/windows/desktop/dn742497(v=vs.85).aspx" target="_blank" rel="nofollow">https://msdn.microsoft.com/en-us/library/windows/desktop/dn742497(v=vs.85).aspx</a><br/><br/></li></ul>]]></description>
<pubDate>Tue, 01 Dec 2015 20:56:13 GMT</pubDate>
</item>
</channel>
</rss>
