Sappy refuses to work on Windows 10 (vbalCbEx6.ocx)

Started by Midna, May 09, 2016, 01:40:37 PM

Previous topic - Next topic

Midna

Would like to make a small correction. It was Dependency Walker that froze, not Process Monitor.

I ran Sappy through Process Monitor and I got a few "file locked with only reader" results for vbalCbEx6.ocx. Why? It's not marked as read-only at all.

Jorpho

#21
I don't know exactly what that means either, but I get the same message here, so I suppose it's nothing to be concerned about.


Does that look similar to what you're seeing?

January 14, 2017, 02:14:23 AM - (Auto Merged - Double Posts are not allowed before 7 days.)

So, oddly enough, I just ran into a very similar problem with AVS2DVD, which was oddly insistent about finding mscomctl.ocx despite it being properly located and registered.

After much gnashing of teeth I applied the instructions found here: I moved mscomctl.ocx out of C:\Windows\SysWOW64, uninstalled AVS2DVD, and then re-installed it.  That's all it took.

Perhaps you should try something similar with vbalcbex6.ocx ?
This signature is an illusion and is a trap devised by Satan. Go ahead dauntlessly! Make rapid progres!