ok dams
I think that this problem does relate to either an unregistered DLL or windows API, caused by the reg cleaner without the name though I dont think there are many options.
apparently 32bit and 64 bit use different calls so you could try the 32 bit explorer
alternatively other than a re-install
it may be an idea to look at a third party solution one
Here is old but may work. suggest you have a look for modern alternative . I would keep checking error log to see if the error message appears and then try to re-register the missing call.
if I do come accross anything I will post here
good luck!
think you may need it as there does not seem to be any info on this fault that i can find.