You could try using DependencyWalker's Profiling feature
to supplement those diagnostics. Both symptoms could mean
something else than the modules involved in the regsvr32.exe
command were the cause of the symptom. E.g., the initpki.dll
module might actually be there but the missing module could be
something that it calls. Ditto for the 0x80070005 symptom;
however, with that one it also could be that Vista wants you
to run it as an Administrator.
BTW these regsvr32 repair procedures are normally given to XP users.
I do not know what all differences Vista users can see when using them.
In any case, I would try booting in command mode to try them
to minimize security/obscurity factors. FYI they were originally
part of the old IE Repair procedure which was always done
*during* a boot to minimize interferences.
Also, here is a script which would give you more of the same,
Downloading it and then running it during a command mode boot
might be easier than trying to remember how to type all those
regsvr32.exe commands in the command line. ; )
Note that in order to have it execute a re-registration of initpki.dll
you would have to uncomment a line in it:
The reregistration of the crypto functionality (initpki) is commented out.
it is very rarely necessary and takes a long time to finish.
In case you really need it, please look in the script (at the end)
and activate it.
This code seems to be a rare occurrence for Vista users.
No definitive documented solution that I can see...
(Microsoft search for
(0x8009200D OR 8009200D) Vista (MSFT OR MVP)
also found with
(0x8009200D OR 8009200D) Vista -inurl:communities