Interesting problem. Google Chrome a while ago announced that they will not support NPAPI plugins after 9/1/15 which includes Adobe Flash (and shockwave). Meaning they support only their built in flash code. Fine. But, my Chrome began having Shockwave Crashes almost daily, yet the only shockwave code present after looking at plugins (about://plugins) was Chrome's code. So, the standard fixes to eliminate duplicate plugins) didn't resolve the problem.
When I tried to update Chrome via its update facility, it failed with error=4. I recall trying this several times over the last 3 months and received the error every time. Thus, I believe the right Chrome code for the right Shockwave never got updated correctly and its automatic updating failed every time too. Today I reinstalled Chrome from scratch and it updated Chrome all the way to Version 46.0.2490.71 m (was 42....), plus its Shockwave-like code went to Shockwave Flash 19.0 r0 (was 18...). So, I am hoping this resolves the Shaockwave crashes. I'll post otherwise if it doesn't.
Update 11/20/2015: The above solution did work UNTIL the MSFT November Cumulative update to get you to version 1511. The next day, another update installed to fix the Flashplayer Shockwave for IE and Edge (Security fix) which seems to have fixed the Chrome problem too.
Featured Post
1210. Presidential Debate - Trump and Harris Ridiculous
So was there a winner of the Presidential debate or just another setup with ABC? I'll agree that Kamala was more composed and the strat...
Subscribe to:
Post Comments (Atom)
-
9/29/16 Windows 10 Anniversary Update 1607: The solution for Windows 10 Anniversary Update is to go to : https://forums.mydigitallife.info/t...
-
Previous posts re the GE Refrigerator noise are: 911. GE Refrigerator/Freezer Noise Part I 920. GE Refrigerator/Freezer Noise Part...
-
Dear Jack (not the real name of my visually impair client) once again got bitten by technology. If you followed previous posts re me instal...
No comments:
Post a Comment