New
#21
I hope someone is still watching this
Home Premiunm 64 bit SP1 on Dell XPS 8300 (with problem) and Dell Inspiron (updates installed fine)
I have the same problem from the August updates but the suggested updates, KB2533523, KB2468871, KB2539636 all end with a Fatal Error.
The log is attached. (all three are the same in the error section) I have been working with MS and all of their suggestions on fixing Windows Update have failed also.
The three here ended with Error=2502 and Error=2503
I am signed in as the hidden admin to have all rights.
If anyone has any ideas it would be greatly appreciated.
As a former QA analyst I have and two (I think) very important clues for someone who knows Net Framework and W7 update process better than I.
1. Is Net Framework there or is that what failed in the August restart?
My trail----
msconfig (doing a clean boot)
hide all Microsoft Services
Microsoft .NET Framework NGEN V4.0.30319 x86 AND x64 do not get hidden and the 'Manufacturer' is listed as UNKNOWN
Go to services
the V4.0.30319 x64 and x86 are there, delayed start, both stopped, both logon as local system account
the V2.0.50727 x64 and x 86 are both disabled.
Since the manufacturer is unknown it would seem to me partial failure during update lost some subset of needed data.
so
2. I run sfc /scannow to find corrupted dlls that sfc cannot fix.
msdaosp.dll V6.1.7601.17514
member file cannot be reapaired, source file in store also corrupted
odbccp32.dll V6.1.7601.17514
member file cannot be reapaired, source file in store also corrupted
jsproxy.dll V8.0.7601.17601
member file cannot be reapaired, source file in store also corrupted
odbctrac.dll V6.1.7601.17514
member file cannot be reapaired, source file in store also corrupted
odbcjt32.dll V6.1.7601.17514
member file cannot be reapaired, source file in store also corrupted
SO.......
Can I resolve 2503 and 2502 errors from these Net Framework self installs?
Go get the dll's from my other dell, drop them in and then let sfc.exe fix it?
Please help me out if you have any ideas.
Tried every update fix approach in the KB already.
Elmo