Resolved [Error message "Could not find flash ocx"]

Hi, I get a folder which has the following in it:
Flash32_11_4_402_287 ocx
ActiveXControl
9,416KB
Flash32_11_5_502_110 ocx
ActiveXControl
14,112KB
FlashInstall.log
Text Document
8KB
mms.cfg
1KB

 

Excellent. Now while in that folder, right-click the file named "Flash32 11_5_502_110.ocx" and drag it down to any blank spot, let go of the right-click mouse button and then left click the "Copy here" option in the little menu that appears. You should now see the original named "Flash32 11_5_502_110.ocx" and a new one named "Flash32 11_5_502_110 - Copy.ocx ". Let me know ...

 

Great, yes I have done that -now have 2 files with one stating copy ocx

 

Great. Now right-click the new one (with the word "Copy" in it), select "Rename" and rename it:

flash.ocx​

That's it. Reboot, hibernate and then see if that flash error message pops up again when you bring it out of hibernation.

 

Ok, I have clicked on the copy entry selected rename with flash.ocx and now have an error saying 'cannot rename Copy of Flash32_11_5_502_110: A file with the name you specified already exists. Specify a different name.

 

1. Highlight and copy the following single line of code:
   
   
   Code:

   cmd /c dir C:\Windows\System32\Macromed\Flash>%temp%\$&notepad %temp%\$

   
   
2. In Windows XP, click Start > click Run, press [Ctrl][V] to paste in what you copied above then press the [Enter] key.
   
   
3. A notepad window should pop up with a directory listing in it. Click once anywhere in that window, press [Ctrl][A] to highlight everything and then [Ctrl][C] to copy it.
   
   
4. Start a Reply here to this thread and then press [Ctrl][V] to paste in what you copied.

 

Hi, This is the entry as requested:

Volume in drive C has no label.
Volume Serial Number is CCA0-6A24

Directory of C:\Windows\System32\Macromed\Flash

12/12/2005 22:45 <DIR> .
12/12/2005 22:45 <DIR> ..
12/11/2012 22:46 14,460,344 flash.ocx
10/10/2012 10:00 9,641,400 Flash32_11_4_402_287.ocx
12/11/2012 22:46 14,460,344 Flash32_11_5_502_110.ocx
25/07/2013 20:00 7,358 FlashInstall.log
12/11/2012 22:46 14,460,344 Copy of Flash32_11_5_502_110.ocx
25/07/2013 11:25 47 mms.cfg
6 File(s) 53,029,837 bytes
2 Dir(s) 4,575,772,672 bytes free

 

Looks like the copy worked. "flash.ocx" and "Flash32_11_5_502_110.ocx" are the same size and have the same date and time stamp:

Are you still seeing the same error message?

 

Yes, I have just switched my laptop on from hibernation mode and the message still comes up

 

Hmm... Try putting a a copy of "flash.ocx" in to the "c:\windows" folder, reboot, hibernate and try again.

 

Done that but still getting message

 

Great.

1. Click Start > Run, type C:\Windows and press [Enter]. Scroll down, right-click flash.ocx and select "Delete ".
   
   
2. Go to Adobe.com > Uninstall Flash Player | Windows and follow the instructions there to completely uninstall the Flash Player.
   
   
3. Restart your computer.
   
   
4. Download and install the latest version of Flash Player.
   
   
5. Test for your 'coming out of hibernation error' again and let us know what happens ...

 

Hi,
Sorry for the delay but have been away for a few days and hoped my message had gone away as well!

I have uninstalled and re-installed Flash Player as suggested but the message still keeps coming up

 

I'm afraid I'm fresh out of ideas. Hopefully someone else will drop in soon with something else to try.

 

Hi SypwareDr

Sorry that despite all of your suggestions my error message is still being a pain, however, many thanks for all your help.

 

You're welcome.

(Sure wish I could get my hands on your computer for few minutes. )

 

Yes so do I!! I will get in touch with my internet provider as they did a 'health check' on my laptop on 22nd July and my message appeared after that!!

 

Did you try using System Restore to roll it back to the 21st?

 

Hi Guys,

Well having contacted my IP they have managed to solve my error message - not sure what they did when they remotely assisted me but hey problem solved.I did not go down the root of a system restore in case I undid something!
Many thanks to you all for your invaluable assistance.

 

Good to hear the problem's been resolved. Thanks for letting us know.