Windows – Flash Player Automatic Updater on Windows Startup

bootflash-playerpopupsupdateswindows

Adobe Flash Player is set to automatically check for updates on Windows startup. I've always wondered where exactly it is set to do this. Checking the running services, as well as msconfig does not yield its location. The message in question looks like this: http://www.technipages.com/disable-an-update-to-your-adobe-flash-player-is-available-message-forever.html

I know how to disable it via Adobe's web site (instructions are included in link above), but I'm interested in knowing where exactly in Windows is this set to perform this action? I have done some research on this, and people keep saying to check the following registry locations:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce or the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run

However, I have checked those locations, and I still cannot locate where this updater is stored.

I'm pretty sure that malware also uses this technique to automatically load upon startup, and since it's not in the typical location(s) that a user would look, it's well hidden.

Best Answer

Exact answer is here. http://forums.adobe.com/thread/750559

This one was an entertaining puzzle, it's probably been answered elsewhere but I thought I'd let curious people know. As someone mentioned, it is the plugin module (NPSWF32.DLL in case of Netscape/Mozilla/Opera plugin) that does the check; thing is, it does not prompt the user to update immediately (it would not be able to do so with the browser open and the DLL in use anyway), but rather it defers the update until the next restart -- by adding a registry entry in HKLM (or HKCU, not positive)\Software\Microsoft\Windows\CurrentVersion\RunOnce key.

The entry is named FlashPlayerUpdate and contains <system root>\System32\Macromed\Flash\FlashUtil<version>_Plugin.exe -update plugin -- presumably the same command line you would run if you wanted to update the player manually (without the hassle with opening and closing your web browsers). The reason you don't see it in registry or with system tools like msconfig.exe is that RunOnce autostart entries are deleted from registry immediately once they are executed. Normally such entries are used by driver and Windows installations to perform one-time initialization after a reboot (once the required services are started and drivers loaded). So you would have seen that entry with msconfig, had you looked at it after the update check (which the plugin does silently), but before the reboot!

Related Question