The problem was not a Chromium-based issue as a "chrome.exe" file workaround would fix the issue. You can read about the report in full in this article here. Reports and allegations like these ...
Right click Google Chrome's shortcut icon and choose Properties. In the target field, append "-enable-java" at the end of execute path "C:\Documents and Settings\Administrator.XXXXXX\LocalSettings ...
Results that may be inaccessible to you are currently showing.
Hide inaccessible results
Feedback