United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
JDK-6208676 : Error 1722 coming during jre1.5.0 installation by Windows user with limited (+elevated) priviledges

Details
Type:
Bug
Submit Date:
2004-12-15
Status:
Closed
Updated Date:
2014-02-27
Project Name:
JDK
Resolved Date:
2005-01-19
Component:
install
OS:
windows_xp
Sub-Component:
install
CPU:
x86
Priority:
P2
Resolution:
Fixed
Affected Versions:
6
Fixed Versions:
5.0u3 (b02)

Related Reports
Backport:

Sub Tasks

Description
Error 1722 coming during jre1.5.0 installation by Windows user with limited (+elevated) priviledges

Steps to reproduce:
1. create a user account with limited priviledges
2. give that user elevated priviledges by following these instructions:

From an Administrator-level login, run the Microsoft Management Console --
1. Start, Run, MMC.EXE
2. Click File, Add/Remove Snap-in
3. Click Add...
4. Select: Local Users and Groups, Click Add
5. Click Finish
 
Run Group Policy Edit --
1. Start, Run, GPEDIT.MSC
2. Expand the tree on the left to see
Computer Configuration\Administrative Templates\Windows Components\Windows Installer
3. Double-click "Always install with Elevated Privileges";  choose Enable, OK
4. Double-click "Enable user to use media source while elevated";  choose Enable, OK
5. Expand the tree to see
User Configuration\Administrative Templates\Windows Components\Windows Installer
6. Double-click "Always install with Elevated Privileges";  choose Enable, OK.
7. File, Exit. 

Now try to install the jre1.5.0 as a non administrator. 
Installer will finish with Error 1722 "...did not finished as expected..." with registry update

###@###.### 2004-12-15 01:29:50 GMT

                                    

Comments
EVALUATION

We have never supported installation with elevated priviledges as a non-admin before j2se 6.0.  There are 2 ways we can deal with this.

1. Document that users should not try and install 142 and 15 as a non-admin in elevated mode.
2. Change the LaunchCondition.idt property to be use AdminUser instead of Priviledged.  This could be fixed in a 142 or 5.0 update release.


###@###.### 2004-12-15 16:33:14 GMT
                                     
2004-12-15



Hardware and Software, Engineered to Work Together