![]() ![]() ![]() Appendix B: running the Flash Player updater manually That's over a month since the last update, with a new one clearly available on the website but with no indication that the hourly check running on my machine has noticed it or has any intention of downloading it. I made this observation on Thu, - 4/25/13, 7:00:00pm, and upon checking Adobe's website found that the current version of Flash Player was 11.7.700.169. And yet, when I checked the version of my installed Flash Player, I found it was 11.6.602.180, which, based on looking at the timestamps of the files in C:\Windows\System32\Macromed\Flash was last updated (or installed) on Tue, - 3/12/13, 5:00:08pm. Google's software updater is configured in a similar fashion, and that works just fine. So far, so good - this set-up avoids having a constantly-running service, but makes sure that the checks are run often enough to catch any updates quickly. Upon installation, FPUS is configured to run as a Windows Service, with Start Type set to Manual.Ī Scheduled Task (Adobe Flash Player Updater.job) is added to start this service every hour. OK, way back in Flash Player 11.2 (or so?) Adobe added the Flash Player Update Service (FlashPlayerUpdateService.exe), it was supposed to keep the Flash Player updated. What follows are the details of my efforts to solve this problem on my own. Given the importance of having an up-to-date version of Flash Player installed (for those of us who don't use Chrome with its built-in player), I would like to find a way to ensure that new updates are promptly detected and installed. Flash Player Update Service doesn't run on a reliable schedule, and doesn't automatically download and apply updates when it does run. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |