search

coolcoolad / pythonxy

Automatically exported from code.google.com/p/pythonxy
0 stars 0 forks source link

Windows 7 user installation problem (UAC) #398

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Plugin updates, even from unstable release 2.7.2.2b4 (i.e. 
http://pythonxy.googlecode.com/files/sphinx-1.1.2_py27.exe), are blocked by 
Windows 7`s UAC. I mean installation package can`t start without Administrator 
credentials. Python installation package starts normally. 
It is a problem when UAC can`t be disabled without administrator account.

Original issue reported on code.google.com by mark.l.k...@gmail.com on 27 Mar 2012 at 1:23

GoogleCodeExporter commented 8 years ago 
Was Python x,y or python installed for all users?

Please fill the bug report - it saves a lot of time!

Original comment by grizzly.nyo on 28 Mar 2012 at 4:37

GoogleCodeExporter commented 8 years ago 
Python was installed for this user only.

This is not an ordinary bug - ok, let me try:
1. Any plugin update
2. I didn`t install Python(x,y) itself
3. I didn`t install Python(x,y) itself
4. I didn`t install Python(x,y) itself
5. I didn`t install Python(x,y) itself
6. I didn`t install Python(x,y) itself
7. Windows 7
8. a regular user 
9. simply by double-clicking on the installer
10. I didn't do anything, you installed directly on your
machine without precaution

What steps will reproduce the problem?
1. Log on as a regular user on Windows 7 (with non-zero UAC level)
2. Try to launch any plugin update
3. It will require adminitstrator credentials which is not right

I think this report won`t save your time as much as this:

I dig around a problem and found that this lines should be included in 
installer`s manifest to avoid UAC problems:
<trustInfo 
 xmlns="urn:schema-microsoft-com:asm.v3">
 <security>
  <requestedPrivileges>
   <requestedExecutionLevel
    Level="asInvoker"
    uiAccess="false"/>
  </requestedPrivileges>
 </security>
</trustInfo>

Put this strings right after </dependency> tag. Plugin updates installer has an 
integrity check - so i can`t check if this manifest change resolves the 
problem, but I`m 99% sure it does. In this case you`ll need to update all 
plugin installers...

Original comment by mark.l.k...@gmail.com on 29 Mar 2012 at 5:42

GoogleCodeExporter commented 8 years ago 
Let's try self signing.

Original comment by grizzly.nyo on 1 Apr 2012 at 2:45

GoogleCodeExporter commented 8 years ago

Original comment by grizzly.nyo on 18 May 2012 at 11:44

GoogleCodeExporter commented 8 years ago

Original comment by grizzly.nyo on 18 Oct 2012 at 2:00

GoogleCodeExporter commented 8 years ago

Original comment by grizzly.nyo on 6 Dec 2012 at 7:22

GoogleCodeExporter commented 8 years ago

Original comment by grizzly.nyo on 1 Jun 2013 at 10:22