The logic outlined in the wiki is currently under web review. Additionally, a similar call to the logic is made BEFORE the
FilesInUse dialog. However, when calling before FIU, the Kernel finalization is averted.
With this additional call, we also safeguard against killing any kernel download that is in progress via FilesInUse.
By implementing the fix in this way, we have also added a valuable feature to the PIP installer: if the user has not run java since the previous kernel installation OR encountered an error during a prior finalization, the PIP will function to finalize OR re-finalize and/or clean up prior finalization attempts.
For example, if windows explorer happens to have %PROGFILES%\Java\jre6\lib\bundles locked, and java is run to finalize the kernel, an error will be thrown, and %PROGFILES%\Java\jre6\lib\bundles will not be cleaned off the system. When the PIP installer is run after this scenario, the kernel finalization will be "re-kicked" and the runtime image cleaned up...all 'under the hood'.