# Windows Installation (IFTW) and Java Update FAQ

> ## Questions:

> Q. I have "Check for Updates Automatically" checked in the Java Plug-in Control Panel, but scheduled automatic updates do not seem to happening. Is there something wrong?

> Q: I downloaded the installer and it is only 1MB. Why is it so small?

> Q: Why does Java Update ask me to reboot?

> Q: I had the Java Plug-in Control Panel open for Java Update and the About tab showed version x.x.x. Then I ran Java Update and it still showed version x.x.x. Why is this?

> Q: Netscape/Mozilla is not working correctly with Java Plug-in. Why?

> Q: I try to install on the `D:\` drive and Java Update is still installing files onto the `C:\` drive. Why?

> Q: How can I uninstall the Java Update version I just installed?

> Q. After the JRE bootstrap installer is downloaded and executed, the message below shows up. Why is this?

> > This installer cannot proceed with the current Internet Connection settings of this system. Please check your Control Panel -> Internet Options, and make sure the settings and proxy information are correct, and/or make sure you can view webpages through Internet Explorer

> Q: I found two processes—`jucheck.exe` and `jusched.exe`—running in the background of my system after installing JRE. Is there a way to shut them down?

> Q . After Java Update updates my system, my browser still uses the Microsoft VM, or an older version of the Sun Java VM, to run applets. What's wrong?

> Q: When I click the Update Now button from the Java Control Panel, it complains about the system being "offline." What does that means?

> Q: I followed the instruction to install version x.x.x. After the installation and reboot, a message popped-up from system tray saying an update is available for download. What should I do?

> Q: I want to try out Java Update but I am afraid beta software may cause problems on my computer. What should I do?

> Q: I encountered the following error when running the J2SE installer:

> > Error 1606: Could not access network location file MSI/CAB and still fail after immediate retry.

> Q: I encountered the following error when running the J2SE installer:

> > This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.

> Q: Error 1311: Source File Not Found. Could not find `C:\Downloads\ja555000.cab`.

> Q: Error 1722. There is a problem with this windows installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vender.

> ## Questions and Answers:

> Q. I have "Check for Updates Automatically" checked in the Java Plug-in Control Panel, but scheduled automatic updates do not seem to happening. Is there something wrong?

> A: The automatic update feature works only on Windows 2000 with SP3 and WindowsXP. If you are running on one of the other supported operating system, this feature will not work. If you want to do an update, use the Update Now button for manually updating Java.

> Q: I downloaded the installer and it is only 1MB. Why is it so small?

> A: The Java installer is designed for Install On Demand. It will download more installer files based on user selection and system configuration. The size of installer should be roughly 1MB.

> Q: Why does Java Update ask me to reboot?

> A: Rebooting may be necessary for any of the following reasons:

> 1. If you use Netscape/Mozilla browsers and if they are java-enabled, files of previous jre's may have been locked.
> 2. Installing Windows Installer 2.0 (Microsoft technology used by the Java installer) sometimes requires rebooting.

> Q: I had the Java Plug-in Control Panel open for Java Update and the About tab showed version x.x.x. Then I ran Java Update and it still showed version x.x.x. Why is this?

> A: You need to close and restart the Java Plug-in Control Panel to get the updated Control Panel.

> Q: Netscape/Mozilla is not working correctly with Java Plug-in. Why?

> A: Were you asked to reboot the system ? Please reboot the system and try again.

> Q: I try to install on the `D:\` drive and Java Update is still installing files onto the `C:\` drive. Why?

> A: Regardless of whether an alternate target directory was selected, Java Update needs to install some update files on the Windows system drive . Doing so saves download time on future updates to the latest version of Java.

> Q: How can I uninstall the Java Update version I just installed?

> There are two ways to accomplish this:

> 1. If you want to uninstall the Java 2 JRE, use the "Add/Remove Programs" utility in the Microsoft Windows Control Panel (Start->Settings->Control Panel to get to "Add/Remove Programs").
> 2. Alternatively, if you still have the original installation program that you used to install the Java 2 JRE, you can double-click on it. This will take you to a screen with Modify and Remove options. Select Remove to uninstall the JRE. Note that you must be connected to the Internet for this to work.

> Q. After the JRE bootstrap installer is downloaded and executed, the message below shows up. Why is this?

> > This installer cannot proceed with the current Internet Connection settings of your system. In your Windows Control Panel, please check Internet Options -> Connections to make sure the settings and proxy information are correct.

> A: The JRE bootstrap installer uses the system Internet Connection setttings to connect to the web for downloading extra files. If you are behind a firewall and require proxy settings, make sure the proxy settings in Internet Options/Internet Properties are set up properly (Start->Control Panel->Internet Options/Internet Properties->Connections->LAN Settings ...).

> If you can browser the external web (i.e., outside the firewall) with Internet Explorer, then your proxy settings are properly set up. The installer doesn't understand the proxy settings specified in Netscape/Mozilla.

> Q: I found two processes—`jucheck.exe` and `jusched.exe`—running in the background of my system after installing JRE. Is there a way to shut them down?

> A: `jusched.exe` is the scheduler process of Java Update; `jucheck.exe` is the process for checking/performing updates in Java Update. These processes run automatically and transparently to users. To shutdown these processes, simply uncheck the "Check for Updates Automatically" checkbox in the Update tab of Java Plug-in Control Panel.

> Q . After Java Update updates my system, my browser still uses the Microsoft VM, or an older version of the Sun Java VM, to run applets. What's wrong?

> A: If you installed the JRE through the Custom option but unchecked the browser selections, you may run into this situation. To fix the problem, go to the Browser tab in Java Plug-in Control Panel and check the browsers that you want to run the newly installed version of Java.

> Q: When I click the "Update Now" button from the Java Control Panel, it complains about the system being "offline." What does that means?

> A: Java Update can only be run if the system is connected to the network. A system that is not connected to the network is referred to as being "offline". When the Update Now button is clicked, it will check the online/offline status of your system. If your system is not currently connected to the network or dial-up networking is disconnected, the error message will show up. Check that your system is currently connected to the network and try it again.

> Q: I followed the instruction to install version x.x.x. After the installation and reboot, a message popped-up from system tray saying an update is available for download. What should I do?

> A: The message is part of the Java Auto Update mechanism, which detects at user login time if a newer version of the JRE is available for download . You may simply click on the system tray Java Update icon to download and install the update.

> Q: I want to run Java Update but I am afraid it may cause problems on my computer. What should I do?

> A: You may want to backup your Windows registry before testing out Java Update. The following command will export the necessary registry keys to a file:

> > `regedit -e reg.1 -t HKEY_LOCAL_MACHINE
> > regedit -e reg.2 -t HKEY_CURRENT_USER
> > regedit -e reg.3 -t HKEY_CLASSES_ROOT`

> To fully restore the registry keys, the following command can be used to import the exported registry values:

> > `regedit -i reg.1
> > regedit -i reg.2
> > regedit -i reg.3`

> Q: I encountered the following error when running the J2SE installer:

> > Error 1606: Could not access network location file MSI/CAB and still fail after immediate retry.

> What does it mean?

> A: This problem occurs when the server is too busy or when the network is too congested to serve the file. Please retry by running the installer again.

> Q: I encountered the following error when running the J2SE installer:

> > This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.

> A: There are several possible reasons:

> - Proxy server requires authentication;
> - network connection fails;
> - download manager software interrupts the download process, e.g., GetRight;
> - TSR (Terminate and Stay Resident) programs, like Norton AntiVirus, may distract the installation process.

> To address these problems, please make sure third-party downloader/TSR programs are turned off and the network connection is setup properly. Also, if a proxy is in use, make sure that proxy authentication is turned off.
> Q: Error 1311: Source File Not Found. Could not find `C:\Downloads\ja555000.cab`.

> A: This is a known MSI engine problem. See following:

> - `http://support.microsoft.com/default.aspx?scid=kb;[LN];Q290106`
> - `http://support.microsoft.com/default.aspx?scid=kb;[LN];Q307346`
> - `http://support.microsoft.com/default.aspx?scid=kb;[LN];290896`

> Q: Error 1722. There is a problem with this windows installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vender.
> A: This is caused by previous unsuccessful install/uninstall of software through MSI engine. This problem will usually disappear if the users run the installer again.

Copyright © 2003 Sun Microsystems, Inc. All Rights Reserved.