Skip navigation
This discussion is locked
Currently Being Moderated

11.1.102.62 and Win2K install - SetDllDirectoryW not supported

Feb 20, 2012 10:43 AM

I have been merrily upgrading Flash Player for Firefox over the years on my Windows 2000 SP4 machine, up through and including 11.1.102.55.

 

The installation program for 11.1.102.62 however, relies on the SetDllDirectory call, which sadly is not supported in Win2K kernel.dll.

 

Can you go back to using the LoadLibrary call so that Win2K users can continue to benefit from the latest patches and upgrades?

 

Thank you,

M. Miller

 
Replies 1 2 Previous Next
  • Currently Being Moderated
    Feb 20, 2012 12:04 PM   in reply to M_Miller12345
     
    |
    Mark as:
  • Chris Campbell
    9,456 posts
    May 4, 2010
    Currently Being Moderated
    Mar 7, 2012 1:04 PM   in reply to M_Miller12345

    Hi Mark,

    I'm forwarding this along to our installer team for their review.  I was not aware of any installer changes for the latest update, but I'm a bit surprised you were able to install 11.1.102.55 on Win2k.

     

    Last Official Win2k Build: 10.1.102.64

     

    Thanks,

    Chris

     

    Edit: Removed reference to 10.3 build, as that's also broken with this update.  Added link to the last "official" version that supported Win2k.  Please note that versions previous to 11.1.102.62 were reported to install and work on Win2k but were not tested or guaranteed to work by Adobe.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 21, 2012 6:43 PM   in reply to M_Miller12345

    I have the same problem.  I can run 11.1.102.55 but not 11.1.102.62 because of this same error message.

     

    Currently the version I have that your web site shows I have.

    winflash.jpg

    The error message from the 11.1.102.62 intaller.

    flasherror.jpg

     
    |
    Mark as:
  • Chris Campbell
    9,456 posts
    May 4, 2010
    Currently Being Moderated
    Feb 21, 2012 7:17 PM   in reply to Muffen Me

    Thank you guys.  I've confirmed with our Installation team that there was indeed a security related change to the installer which is now causing this to occur.  Could you open up a new bug on this over at bugbase.adobe.com and post back with the URL?  Given 2k's unsupported status with FP 11, I'm not sure how successful I'll be pushing for a fix, but if enough people vote and comment for the bug, anything is possible.

     

    Thanks,

    Chris

     
    |
    Mark as:
  • Chris Campbell
    9,456 posts
    May 4, 2010
    Currently Being Moderated
    Feb 22, 2012 6:36 PM   in reply to M_Miller12345

    I agree.  I'm going to escalate this internally.

     

    Chris

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 23, 2012 1:14 PM   in reply to M_Miller12345

    Thanks for starting this thread, Mike.

     

    I too have some Windows 2000 SP4 pc's, and I also noticed this installation problem when I tried to update them to the latest, safe-from-critical-vulnerabilities-version (v10.3.183.15) of Adobe Flash Player that should be able to be run by Windows 2000 pc's (at least according to the information at the following URL).

    http://kb2.adobe.com/cps/142/tn_14266.html#main_Archived_versions

     

    This update is all the more important because of the vulnerabilities listed in the following security bulletin:

    http://www.adobe.com/support/security/bulletins/apsb12-03.html

     

    I'm currently running Adobe Flash version 10.3.183.11 and tried to update to the v10.3.183.15 both by:

    1) the pertinent files in the .zip archive available at the following URL:

    http://fpdownload.macromedia.com/get/flashplayer/installers/archive/fp _10.3.183.15_archive.zip

    and

    2) these two direct links:

    http://get.adobe.com/flashplayer/completion/?installer=Flash_Player_10 _for_Internet_Explorer

    http://get.adobe.com/flashplayer/completion/?installer=Flash_Player_10 _for_Other_Browsers

    Unfortunately, both methods produce the installation files which fail with the same error you reported.  I also voted for the bug's fixing at the URL you provided.

     

    Thank you also, Chris, for doing whatever you can to "bump" this issue to an internal area that can get it resolved for us Windows 2000 pc users both now and going forward.  :-)

     

    I'll try to keep checking back here for pertinent updates.  It would be nice if a topical Google search would be able to find this thread as well.  The one below didn't really help me out.

    http://www.google.com/search?q=%2Bflash+The+procedure+entry+point+SetD llDirectoryW+could+not+be+located+in+the+dynamic+link+library+KERNEL32 .dll

     

    Message was edited by: AcroNot with the following: The google URL actually DID help a bit, since THIS forum is listed there.  They are also discussing this issue at:  http://forums.scotsnewsletter.com/index.php?showtopic=52490   (Maybe we can get a post there to have others there check out this forum and the bug report.)  P.S.:  I just assumed the "M" stood for "Mike" because I once knew someone with that name!  :-)

     
    |
    Mark as:
  • Chris Campbell
    9,456 posts
    May 4, 2010
    Currently Being Moderated
    Feb 23, 2012 5:27 PM   in reply to M_Miller12345

    Just for future reference, our internal bug number for this is 3122132.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 26, 2012 6:26 AM   in reply to M_Miller12345

    Last year, Windows Update accidentally offered Win2K systems a C++ runtime update that replaced a DLL with one that contained XP-only calls. I go thit by that and had to replace the bad DLL with the older one.

     

    I wonder if the installer has it's own copy of that DLL and is using it. If it's not completely bound in, I wonder if it could be found in a temp directory if the installer extracts a bunch of files. Could you cancel/terminate the installer, find the DLL, and either replace it with a Win2K compatible version, or just delete it so it uses the main system copy?

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 29, 2012 3:16 AM   in reply to M_Miller12345

    Hi out there,

     

    there's a way to install newest updates anyway. There exists a wrapper which includes used procdure call.

    You may find a howto on my blog

    http://www.ortwinpinke.de/2012/02/29/adobe-flash-player-11110262-unter -windows-2000-installieren/

     

    But i also would prefer a solution for a "normal" installation under win2000.

     

    regards from germany

     

    Ortwin

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 29, 2012 7:46 AM   in reply to Oldperl

    Hi Ortwin, clicked on your link but sadly my German is not that good Have same problem as M_Miller and would like some help. Will go and vote re bug,

    Thanks

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 29, 2012 9:24 AM   in reply to M_Miller12345

    Doh! Of course, thanks.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 29, 2012 9:35 AM   in reply to M_Miller12345

    Ok, translated page but as I said, I'm a bit of a novice so I have no idea what I'm supposed to do? Now need it translated into layman's terms.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 29, 2012 10:20 AM   in reply to M_Miller12345

    Funny: I logged into my computer today, and Adobe popped up saying Flash needs to be udpated!!

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 29, 2012 5:59 PM   in reply to Mrs Clift

    Computer translations do not always make sense; here is what you need to do:

    • download http://oldcigaret.info/win2k/files/win2k_xp_v1_10.zip and save it to disk
    • unzip* the downloaded win2k_xp_v1_10.zip file to a new folder, e.g. C:\w2k-wrapper
    • run the bat file INSTALL_WRAPPER.BAT from folder C:\w2k-wrapper\install\
    • copy the Flash Player install file(s) to folder C:\w2k-wrapper\bin\
    • run the Flash Player install file(s) from that folder via double-click

     

    You can download the Flash Player install files

     

    *) if I remember correctly, Windows 2000 did not support zipping/unzipping natively; you may need to download a tool for this, e.g. the free 7-Zip.

     

    Feel free to ask again if some of these instructions are unclear.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 29, 2012 11:42 PM   in reply to Pat Willener

    Wow, what a lovely bunch of people you are! Pat, I shall attempt the above tonight. Your instructions seems very clear, but my brain is something else (not clear, that is).

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 1, 2012 11:25 PM   in reply to Mrs Clift

    Good luck!  Post back if you need more help (or when you are successfully done).

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 2, 2012 7:34 PM   in reply to Pat Willener

    I used a "test" Windows 2000 pc and was able to download and install the "WRAPPER" program via its installation batch file.  On my first try I was unable to install the latest version of flash and got the same "SetDllDirectoryW..." error when I launched the installer, so I uninstalled the "WRAPPER" via its uninstallation batch file.  This particular test pc has two partitions (C: and S:) and I had extracted the zip file (using my favorite 7-zip program from http://www.7-zip.org ) onto the S: partition.  I thought it might not have liked that, so I copied it to the C: partition and tried the installation batch file from there.  Once again I got the "SetDllDirectoryW..." error, so I read over the README.TXT file.  (It always kind of scares me a little when I see typos and bad English in files like that, but I know programmers might excel in coding more than in grammar.)  I read something about needing to reboot, so I tried that.

     

    Yes.  You need to reboot after installing the "WRAPPER" program via its installation batch file before you try to install the Flash Player.

     

     

    I was hoping the pc would start up OK (it did), so I tried the installation again following the reboot.  Flash version

     

    11.1.102.62 failed with the following "Unable to locate DLL" error:  "The dynamic link library d3d9.dll could not be found in the specified path ..."  So I decided to try flash version 10.3.183.15 instead.

     

     

     

    OK.  Putting Flash v10's installation programs into the "bin" folder and running them from there worked!

     

     

    Here are the MD5 hashes for the files I used (I put a "Z" at their beginnings so they'd go to the bottom of the list):

     

     

    d515fa4149ef0d2d2f32aff4fd274aa4 *Zinstall_flash_player.exe

    8f3c6c389b21d999ccbb079aa6e15c45 *Zinstall_flash_player_ax.exe

     

     

     

    I think I tried the v11 files again but got the error about not being able to find the d3d9.dll file.  I then removed the "WRAPPER" program via its unistallation batch file and rebooted and all was well.  (I probably didn't have to do that -- I just wanted to see what would happen.)  Granted, this is a test machine and I would probably totally ghost any of my "good" pc's before I modify them like this, although I would think it's probably safe to throw caution to the wind with this "WRAPPER" thing and install it, use it, and then keep it installed.

     

     

     

     

     

     

     

    In case you're wondering what you see when you install the "WRAPPER" program via its installation batch file, here are the lines I saw (I was a little anxious initially when I saw the "system could not find the file specified" line, but it was OK.):

     

     

     

     

     

    ---------------------------------------- TOP of what you can expect to see ----------------------------------------

    This script will create a folder C:\XPDLL and add it to your

    system's PATH environment variable.  Your registry will be changed so

    ExcludeFromKnownDlls is 'KERNEL32 ADVAPI32 SHELL32 USER32'.

    C:\XPDLL will be overwritten if already exists. Ok?

    [y,n] y

    Creating directory...

    The system cannot find the file specified.

    Copying files...

    C:\WINNT\SYSTEM32\ADVAPI32.DLL ---> C:\XPDLL\ADVAPI32_ORG.DLL

            1 file(s) copied.

    C:\WINNT\SYSTEM32\KERNEL32.DLL ---> C:\XPDLL\KERNEL32_ORG.DLL

            1 file(s) copied.

    C:\WINNT\SYSTEM32\SHELL32.DLL ---> C:\XPDLL\SHELL32_ORG.DLL

            1 file(s) copied.

    C:\WINNT\SYSTEM32\USER32.DLL ---> C:\XPDLL\USER32_ORG.DLL

            1 file(s) copied.

    C:\WINNT\SYSTEM32\WS2_32.DLL ---> C:\XPDLL\WS2_32_ORG.DLL

            1 file(s) copied.

    C:\WINNT\SYSTEM32\WTSAPI32.DLL ---> C:\XPDLL\WTSAPI32_ORG.DLL

            1 file(s) copied.

    C:\WINNT\SYSTEM32\IMM32.DLL ---> C:\XPDLL\IMM32_ORG.DLL

            1 file(s) copied.

    Wrapped system32 files installed

    Setting PATH

    C:\XPDLL added to the PATH

    Setting ExcludeFromKnownDlls

    Press any key to continue . . .

    ------------------------------------ BOTTOM of what you can expect to see --------------------------------------

     

    So there you go.  You could probably safely use this route to update your Windows 2000 pc's version of Adobe Flash Player to the most up-to-date version 10 that you can get from these links:

    http://get.adobe.com/flashplayer/completion/?installer=Flash_Player_10 _for_Internet_Explorer

    http://get.adobe.com/flashplayer/completion/?installer=Flash_Player_10 _for_Other_Browsers

     

    When I checked my Flash version at http://www.abobe.com/software/flash/about it was v10.3.185.15.

     

    Of course, with all this said, I'd rather just have Adobe provide a working version of the Flash 10 installer so we don't have to jump through hoops provided by a benevolent stranger to update to a safe version on our Windows 2000 pc's.

     

    Message was edited by AcroNot to correct the typo in the last URL listed.  The Flash Player version check should be ---> http://www.adobe.com/software/flash/about

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 4, 2012 5:50 AM   in reply to AcroNot

    AcroNot wrote:

    I was hoping the pc would start up OK (it did), so I tried the installation again following the reboot.  Flash version

     

    11.1.102.62 failed with the following "Unable to locate DLL" error:  "The dynamic link library d3d9.dll could not be found in the specified path ..."  So I decided to try flash version 10.3.183.15 instead.

    D3D9.dll is a Direct3D 9 runtime file.

     
    |
    Mark as:
  • Chris Campbell
    9,456 posts
    May 4, 2010
    Currently Being Moderated
    Mar 5, 2012 3:57 PM   in reply to andyross63

    Quick update.  Unfortunately this bug has been deferred internally at this time.  I've bounced it back but couldn't persuade our review board to reconsider.  At this point, the only way this will be addressed is via 3rd party wrappers (see above) or an overwhelming show of support on the public bug.

     

    https://bugbase.adobe.com/index.cfm?event=bug&id=3120661

     

    Thanks,

    Chris

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 6, 2012 12:08 PM   in reply to Chris Campbell

    They should remove the reference to Windows 2000 support if the 10.x version will not be fixed.

     
    |
    Mark as:
  • Chris Campbell
    9,456 posts
    May 4, 2010
    Currently Being Moderated
    Mar 6, 2012 12:10 PM   in reply to andyross63

    I did have it updated on our Archived Flash Player Versions page,  is there another location I should change?

     

    Thanks,
    Chris

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 12:17 AM   in reply to Chris Campbell

    Well, Chris, this is all very disappointing!

    You might want to change the below

     

    Re: 11.1.102.62 and Win2K install - SetDllDirectoryW not supported

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 5:54 AM   in reply to Mrs Clift

    Ok...For anyone that is interested.. I have Flash Player 11.1.102.63 installed on W2KSP4 using BlackWingCat's KnownDllsWrapper .96k EZinstall available at

     

    http://www7.atwiki.jp/win2000/pages/17.html

     

    I used the EZInstall method as follows:

     

    Create a Temp folder and place the "install_flash_player_32bit.exe" and/or "install_flash_player_ax_32bit.exe" in there (It probably makes sense to make the folder a permanent location as you will be able to just place new install files in there when updates come out)

     

    Run kdllinst from the KnownDllsWrapper package. Choose your Temp folder as the EZINstall folder in the top dialog section, choose kernal32 from the main installer window, and check EZ KD registry from the right hand side. (This will add registry entries for ExcludeKnownDlls and allow the installer to use the wrapper dlls located in the Temp install Folder)

     

    REBOOT the machine. (This MUST be done)

     

    Go into the Temp folder and install the update(s).

     

    As of now it seems that only the installer has the SetDllDirectoryW dependency issue. If at some point down the line the flash executables start having Win2K dependency issues an EZInstall with the required wrapper dlls will need to be made to the flash install folder, but that is not the case at this point.

     

    Hope this helps. Post if you run into any problems.

     

    Message was edited by: J Fortune And of course if you have something installed that protects registry changes like spybot or webroot then you will have to allow the changes or disable before doing the EZinstall to allow the EZ KD registry patch to complete.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 12:50 PM   in reply to J Fortune

    Well, if I earlier -- in error -- called Mark (M. Miller) "Mike" because I once knew a Mike Miller, I should call the kind poster above this note (J Fortune) "Joe" since I also once knew a Joe Fortune.  (He even sold me a new car!)

     

    Anyway ("Joe"), does the kdllinst.exe file in the kdw096k.zip archive make permanent changes to the Windows 2000 pc on which it is installed, or can it be uninstalled the way the "WRAPPER" program could be?  I do appreciate these 3rd party workarounds, but at the same time I am a little skittish about installing something "unofficial" (especially an .EXE file) that comes from an unknown source.

     

    I also see from your post (and from the most recent Flash Player Security Bulletin, i.e., www.adobe.com/support/security/bulletins/apsb12-05.html ) that a new version (11.1.102.63) of Flash Player is now (for two days) out to address a priority 2 critical vulnerability.  Granted, keeping software "safe" cannot be the easiest thing to do, but it makes me wonder if we should approach the "latest and greatest" Flash release (not unlike Microsoft's monthly patches) as already being critically vulnerable (but we just won't find out how for a couple of weeks or months)!  Maybe Steve Jobs was right ( http://www.wired.com/gadgetlab/2011/11/adobe-kills-mobile-flash/ ) about Flash and maybe we might do best on our Windows 2000 pc's by installing the latest version of Firefox (for example) and hoping for more stable HTML5 content.

     

    I wish it weren't asking too much to have a page with the latest working, able to be installed "official" Flash software for all different categories of still-used Microsoft OS pc's under headings like Win2000, WinXP, Windows7, etc.

     

    Thanks for everyone who has tried to help out with this and thanks for "listening" to my little venting of frustration -- we'd just hope that the computers we buy should be able to safely run the programs they ran when they were new until the day they totally "bite the dust" and no longer work.  (Maybe that should be "byte the dust"!  ;-D )

     

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 1:04 PM   in reply to AcroNot

    Amen!

     

    - Sent from my HTC -

     
    |
    Mark as:
  • Chris Campbell
    9,456 posts
    May 4, 2010
    Currently Being Moderated
    Mar 7, 2012 1:07 PM   in reply to Mrs Clift

    I understand how you feel!  I've updated my previous post in this thread to remove the reference to 10.3 and instead reference the "official" last build for Win2k.

    Mrs Clift wrote:

     

    Well, Chris, this is all very disappointing!

    You might want to change the below

     

    Re: 11.1.102.62 and Win2K install - SetDllDirectoryW not supported

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 1:51 PM   in reply to Chris Campbell

    Thanks, Chris, for helping us out to the degree you are able.  It is appreciated.  :-)

     

    Here's something else I just found today from which the rest of you Windows 2000 users might get a chuckle:

     

    Yep.  Good old Windows 2000.

    The door to the new economy:

    http://www.youtube.com/watch?v=yCzBS11xPkQ

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 2:43 PM   in reply to AcroNot

    Well Beucephous (I have an uncle named Beucephous AcroNot ),

     

    To answer your question, as far as I can tell the KDW (Known DLLs Wrapper) project consists of new dlls created for each of the W2K dlls with missing function calls. These newly created dlls handle only the function calls that are missing from the W2K dlls and pass calls that do exist back to the original dlls.

    The kdllinst.exe is included in the package just for ease of use and to verify that the dlls are copied and renamed correctly. With the EZINstall method described above, kdllinst.exe copies the kernal32.dll from the system32 folder into a temp folder of your choosing and renames the file kernal2k.dll. It then copies the "wrapper" kernal32.dll from the KDW package into the same folder. The EZ KD registry option just modifies the ExcludeFromKnownDlls registry entry to add kernal32.dll. After rebooting, this in effect makes it such that when the installer calls kernal32.dll it uses the kernal32.dll file located in the install folder, which parses all W2K calls to the kernal2k.dll (original W2K dll renamed) in the install folder and handles any of the missing calls itself (SetDllDirectoryW).

     

    If you are wary of running an exe from an unknown source, but are OK with using the kernal32.dll supplied in the package you could do all this yourself manually without running the exe. Just create a temp folder, place a copy of kernal32.dll from your win2k install into that folder and rename it to kernal2k.dll, and then place a copy of the kernal32.dll from the KDW package in that same folder. Lastly you will need to use regedt32 (not regedit) to modify the ExcludeFromKnownDlls key located at HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager, adding kernal32.dll to the ExcludeFromKnownDlls list, reboot the system, and install the update.  The addition of kernal32.dll to the ExcludeFromKnownDlls list enables the installer to use the kernal32.dll located in same folder as the installer.

     

    Seeing as the issue here is just for the necessity of running the installer, after the update is installed you can remove kernal32.dll from the ExcludeFromKnownDlls list (using regedt32) and reboot the system, not leaving any permanent changes.

     

    There are a few different wrapper packages that exist and I believe the differences are in the number of new dll wrappers provided, the new functions they provide, and the naming scheme they use to reference the original W2K dlls. You could use the manual procedure I described above with any of the packages as long as you know what to rename the original W2K dll when you copy it into the temp install folder. I only investigated the KDW package, so can't help there.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 8, 2012 2:16 AM   in reply to Mrs Clift

    Mrs Clift wrote:

     

    Hi Ortwin, clicked on your link but sadly my German is not that good Have same problem as M_Miller and would like some help. Will go and vote re bug,

    Thanks

    Hi Mrs Clift,

     

    sorry for that and for the late reply. I have not checked my subscriptions due to illness.

    I will try to add an english translation to my blog entry within the next days. Thx for your feedback.

     

    regards from germany

     

    Ortwin

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 8, 2012 10:55 AM   in reply to J Fortune

    Instead of all this wrapper stuff, how easy (or hard) would it be to copy the installed Flash files from another install on XP or whatever and put them on the Win2K computer. Is that all that is really needed? We just need to find out where the files actually are and which ones need to be updated.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 8, 2012 3:29 PM   in reply to andyross63

    andyross63 wrote:

     

    Instead of all this wrapper stuff, how easy (or hard) would it be to copy the installed Flash files from another install on XP or whatever and put them on the Win2K computer. Is that all that is really needed? We just need to find out where the files actually are and which ones need to be updated.

     

    and what registry entries need to be modified. I agree with this line of thought. I searched extensively for some information on a "manual installation" method.

     

    Maybe if someone from Adobe could post a comprehensive list of the install files, where they need to be located, and any additional requirement (like modification to registry entries) we could create a "manual installation" method that would allow updates to be made to W2K installs without needing to resort to wrappers just to run the installer. Anyone have this information?

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 8, 2012 8:11 PM   in reply to andyross63

    andyross63 wrote:

     

    Instead of all this wrapper stuff, how easy (or hard) would it be to copy the installed Flash files from another install on XP or whatever and put them on the Win2K computer. Is that all that is really needed? We just need to find out where the files actually are and which ones need to be updated.

    I don't think it is that easy.  If I follow the Flash Player installation process with Process Monitor, it produces several thousand lines!  This is not something I would like to do manually...

     

    On the other hand, I don't think it is that hard to make a manual installation (but the wrapper method definitely is the easiest way). Basically what you need is

    • the target folder %WINDIR%\system32\Macromed\Flash
    • the Flash Player files, for the latest release 11.1.102.63
      • Flash11g.ocx
      • flashplayer.xpt
      • FlashUtil11g_ActiveX.dll
      • FlashUtil11g_ActiveX.exe
      • FlashUtil11g_Plugin.exe
      • NPSWF32.dll
    • then you need to register all DLL and OCX files
    • there may be a few registry entries that need to be created manually; I can tell you more when I get home

     

    If Flash Player was already installed, before installing you need to

    • unregister the existing DLL and OCX files
    • delete all files in %WINDIR%\system32\Macromed\Flash
     
    |
    Mark as:
1 2 Previous Next
Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points