Yeah, neither do I at this point. I'm also not a programmer so making full sense of the dump is beyond me.
First, a few points about UURollup v11
1) Two versions of process explorer included. Nice.
2) Caused nvidia display driver service to temporarily hang at startup.
3) May have been premature on saying v11 fixed ssl cert issue. It just may be throwing an exception before it even gets to that point.
Anyway, so today I decided to mess around a bit. First I uninstalled Office 2003 so I can get MS Update working again.
[Note to self - either install Office as the last thing I ever do or just fore-go it for Ashampoo/SoftMaker Office 2010 or 2012.
2010 works fine on a stock win2k]
MS Update offered me two patches for .NET and re-offered Rollup 1.
Back to SQL. I uninstalled v11 which caused win2k to reboot before logon prompt appears. Went into safemode and installed Rollup 2.
After restart I installed v10d and went back to sql. So now we're back to the beginning of not being able to create ssl certificate.
Just for the fun of it I decided to add bits and pieces of v11 to v10d to see what happens. With each addition I'd try and reinstall sql server.
The copying of bits was done via a Linux rescue system. The following dlls were added to the system (system32 & dllcache)...
user32 - no go (meaning the same ssl cert issue)
crypt32, cryptui, wintrust - no go
rsaenh - no go
userenv - no go
Following added just for the fun of it...
cryptsXP, credui, wintruXP, xpsp#res files - no go
Given that those files from v11 didn't change anything I then reinstalled all of v11. SQL Server throws an exception.
Hmm, maybe it's the included uxtheme.dll I thought. Nope.
This could be kernel related or anything for that matter.
BTW, an almost identical exception error was found at MS when I was searching last week with a supposed fix being cumulative update 15
for sql server 2005 sp3. Thing is I can't test that because sp3 itself won't finish installing and thus CU15 can't find any instance to update.
I'm finished for this week. I'll resume testing next week on my next days off.
You should try a different version of SQL server to see if it works or not.