I have a WinXPproSP3 machine that has
c:\windows\sys32\macromed\flash\Flash6.ocx
in its file structure.
Most odd.
This machine runs MSSE v2 and is fully patched via auto-update.
It does not run 24/7 (as many of my clients do). I use it as my
forward test platform for 'normal human PC usage.'
I figure that it gets what it needs from MS when I spin it up.
Correct?
It has never made a peep until now while using Secunia PSI.
Secunia gave up and could do no upgrade to this file.
Fine.
This machine has never needed, or been allowed to load/run
Adobe Flash. 3 days of research netted 3 old removal trys. All failed.

The file remains chronically 'read-only.' My desktop creds, the
admin desktop creds, Safe Mode boot, ?, nothing allows
resetting the 'read-only' flag of this file.
Suspect deeper baddie. Fine.
Who? What?

Best I have done is rename the file to 'Flash6.$$$.'
Still can not delete it.

If I had DOS, I think I might be able to drill down and kill this
file. I have DOS, but no way to load it. PC has no floppy drive.
And, my usb floppy drive is not a bootable object.

I do have a bootable (old) CD with (?) WinPE 6. Think this gives
me a virtual ram-based windows playground. Can this approach
allow me to delete/remove the offending file?

Yes, understand that there may be further digging, or, give up and
format to a new OS install. Fine. This is NOT a critical client. ATM, it is
a personal learning tool.
Best,
Duncan

Reply via email to