Hi Brian and everyone else.
I just saw your video on register the DLLs in the windows folder. I think you got that idea from the same UVK feature, haven't you?

I'm glad I'm not the only one who believes this procedure can fix lots of windows errors. Nice work!
Too bad I didn't know you were making the video, cause I could have given you a hand to improve it.
The thing is: Some dlls have both
DllInstall and
DllRegisterServer entry points. This must be the reason why you got those regsvr32.exe errors. These files should be registered with the command:
regsvr32.exe /s /i dllnameThis is the correct way to register all the functions and objects the dll supports. Others have the
DllInstall entry point, but not the
DllRegisterServer. For these ones the command should be:
regsvr32.exe /s /i /n dllnameFor the UVK's Register system dlls function, I created a list of these dlls:
The ones that should be run registered with regsvr32.exe /s /i dllname are:In the 2008 family (Vista, 7):
shell32.dll accessibilitycpl.dll certcli.dll certmgr.dll dsquery.dll dsuiext.dll photowiz.dll urlmon.dllIn the 2003 family:
autodisc.dll browseui.dll certcli.dll certmgr.dll dsquery.dll dsuiext.dll eventcls.dll fldrclnr.dll msieftp.dll w32time.dll userenv.dll urlmon.dll themeui.dll swprv.dll shsvcs.dll shimgvw.dl shgina.dll shell32.dll shdocvw.dll photowiz.dll ntmssvc.dll netplwiz.dll mydocs.dllThe ones that should be run registered with regsvr32.exe /s /i /n dllname are:In the 2008 family (Vista, 7):
ieframe.dll ntvdm64.dll themeui.dll w32time.dll wininet.dllIn the 2003 family:
comctl32.dll credssp.dll digest.dll ieframe.dll wininet.dll p2p.dllNot all the rest of the DLLs have the DllRegisterServer entry point, but if you register them with the command:
regsvr32.exe /s dllname(just like in the video), no error should occur, regsvr32 calls the DllRegisterServer function, which doesn't exist and closes.
A bit late, but maybe this will still help someone.
Kind regards.
Fred