Jump to content
Posted 07 October 2010 - 05:38 AM
Posted 07 October 2010 - 06:29 AM
Edited by MaxoxaM, 07 October 2010 - 06:29 AM.
Posted 07 October 2010 - 07:45 AM
Posted 07 October 2010 - 08:43 AM
When a Java program is invoked using a batch file, executable jar, or Java Web Start/JNLP), the operating system runs a Java launcher from the JRE. The Windows version of the JRE has separate launchers for command-line and GUI applications called java.exe and javaw.exe respectively. Java.exe is the main executable for Sun Java Runtime Environment. Javaw.exe does the same thing except that it does not open the Java controls. Why is that important? Because, using the Java controls can effect how Java runs, and with many programs that use Java, changing how Java runs can crash the program, Java or even Windows itself. As such, Java offers the alternative of using either of those two executables to use Java within a program and the programmer needs to decide whether it is desirable and/or safe to allow the user to change how Java will execute within that program. For more specific information, please refer to Custom Java Launchers And Wrappers (scroll down).
Well I got rid of it. I had to uninstall Java.
What is Java Quick Starter (JQS)?
The Java Quick Starter (JQS.exe) improves the initial startup time of Java applets and applications by periodically prefetching some of the most heavily used Java Runtime Environment files into memory (occupying no more than 20Mb of RAM). Later, when Java is launched, much less disk I/O is required and as a result, startup is much faster.
Determining whether a file is malware or a legitimate process usually depends on the location (path) it is running from. One of the ways that malware tries to hide is to give itself the same name as a common file like java.exe. However, it then places itself in a different location (folder) than where the legitimate file resides and runs from there. Another techinique is for the process to alter the registry and add itself as a Startup program (java.exe). In your case, you determined the legitimate java file to be responsible for your particular issue. Since it was the legitimate file, that explains why it was not detected as malware.
I can't believe none of the programs detected it... Scary
0 members, 0 guests, 0 anonymous users