The information in this article applies to:
Downgrading the Microsoft virtual machine is not a recommended procedure and should be done only as a last resort. Furthermore, this article should be passed to a customer only when all other options have been exhausted.
Important This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the Restoring the Registry Help topic in Regedit.exe or the Restoring a Registry Key Help topic in Regedt32.exe.
Warning Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.
For information about how to edit the registry, view the Changing Keys and Values Help topic in Registry Editor (Regedit.exe) or the Add and Delete Information in the Registry and Edit Registry Data Help topics in Regedt32.exe.
Note You should back up the registry before you edit it. If you are running Microsoft® Windows NT®, you should also update your Emergency Repair Disk (ERD).
This downgrade procedure works in most cases but is not 100 percent guaranteed. Please use this at your own risk:
Q163637 INFO: Availability of Current Build of Microsoft VM.
cd \%Windir%\system32
regsvr32 /u msjava.dll
The latest Microsoft VM released under Internet Explorer is version [nnnn] and consists of the following files for the X86 platform:
Note Make sure that each DLL being renamed has a version number that is higher than that of the Microsoft VM you will be downgrading to. Also, if you can't rename one or more of the DLLs, you will need to reboot your computer.
Note Please be aware that an error made using RegEdit can render a computer unusable.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Code Store Database\Global Namespace\Java Packages
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Java VM
Important The recent 24xx series of the Microsoft VM checks the version of Msjava.dll on the system to determine if it should install. There is a bug in the setup engine such that when there is no Msjava.dll on the system, setup reports that a newer Microsoft VM is already present. The workaround is to install the Microsoft VM with the following command line:
msjavx86.exe /n:v
Important If you normally install any custom classes on the computer, you will have to install them again.
For the latest Knowledge Base articles and other support information on Microsoft® Visual J++® and the Microsoft® SDK for Java, please see the following pages on the Microsoft Technical Support site:
http://support.microsoft.com/support/visualj/
http://support.microsoft.com/support/java/