Forum Thread: Unstable Googlechrome 5.x

You are currently viewing a forum thread in the Secunia Community Forum. Please note that opinions expressed here are not of Secunia but solely reflect those of the user who wrote it.

This thread was submitted in the following forum:
PSI

This thread has been marked as locked.
Todd-Ao Unstable Googlechrome 5.x
Member 20th Jun, 2010 09:48
Ranking: 0
Posts: 1
User Since: 11th Jun, 2009
System Score: N/A
Location: N/A
You constantly tell me my "Googlechrome 5.x" is unstable, despite I have updated it several times through your link and have re-scanned afterwards.

What´s wrong?

TiMow RE: Unstable Googlechrome 5.x
Dedicated Contributor 20th Jun, 2010 10:29
Score: 737
Posts: 728
User Since: 26th Jun 2009
System Score: N/A
Location: CH
Last edited on 20th Jun, 2010 10:32
This is my bog-standard reply for this (recurring) problem - every time Chrome updates.

Quote:
"A common problem when updating Chrome, is that the new version creates a new file and still leaves the old insecure file, which PSI reports. This old file needs to be manually removed.

You need to use PSI on the Advanced mode interface - click "Advanced" on top right of PSI window, then "OK". Along the top is a series of tabs.

Firstly, to check if Chrome is correctly updated/patched, go to the tab "Patched" and click - here is a list of all your patched programs.

Scroll down to Google Chrome 5.x, and for the version number, you should see 5.0.375.70 - if you have already updated to the latest up to date version.

Now click the tab "Insecure" (red lettering, when there's a problem). The old Chrome file should be listed here. On its left is "[+]" - click on this to reveal toolbox icons, then find "Open Folder" and click this.

This takes you to the location of the old Chrome file. You should see both the up to date version no. (5.0.375.70) and the old version no. (5.0.375.55). Make sure the old version no. is highlighted, right click, then delete.

This now goes to recycle bin, where you probably need to further delete it (as PSI also reports its contents). Reboot your PC and full re-scan PSI - this should now resolve this problem.

If your require further assistance, then post back here."
Unquote.

TiMow

EDIT: Interesting user name - when I lived and worked in La-La land Todd-AO were a sound PP company - as I'm sure you know.


--
Computing is not yet a perfect science - it still requires humans.
Was this reply relevant?
+1
-0

This thread has been marked as locked.