Apr 21, 2010 06:23 PM|Lester K|LINK
I did not touch dotnet3 at all. Just did exactly as I listed.
I did work on the latest failed dotnet3.5 patch.
On that one I removed all dotnet3 and 3.5 then ran wuauclt /detectnow
That seemed to resolve that failed patch issue.