From: Tom Svehla on
I've been starting to see multiple instances of KB974417 fail during install
from WSUS. I've found that you need to un-install KB976569 (released
2/23/10), then install 974417. Then you can re-install 976569.

This will probably only be an issue on machines that do not have .NET
2.0/3.5. 976569 and you are doing a clean new .NET install. KB97659 does not
supersede 974417, as they address different issues, so both are apparently
needed.

Just wondering if anyone else has seen this or is Microsoft aware of this
issue and will they have have a fix down the road.
From: Ǝиçεl on
Hello Tom,

Perhaps tяy the WSUS Newsgroup

<http://social.technet.microsoft.com/Forums/en-US/winserverwsus/threads>

On the web:
WSUS General
<http://www.microsoft.com/communities/newsgroups/list/en-us/default.aspx?dg=microsoft.public.windows.server.update_services>

In your newsreader:
news://msnews.microsoft.com/microsoft.public.windows.server.update_services
-=-

Thanks and good luck !
-=-



Ǝиçεl
◕‿◕
-=-


"Tom Svehla" wrote:

> I've been starting to see multiple instances of KB974417 fail during install
> from WSUS. I've found that you need to un-install KB976569 (released
> 2/23/10), then install 974417. Then you can re-install 976569.
>
> This will probably only be an issue on machines that do not have .NET
> 2.0/3.5. 976569 and you are doing a clean new .NET install. KB97659 does not
> supersede 974417, as they address different issues, so both are apparently
> needed.
>
> Just wondering if anyone else has seen this or is Microsoft aware of this
> issue and will they have have a fix down the road.
From: PA Bear [MS MVP] on
WSUS-specific support forum:
http://social.technet.microsoft.com/Forums/en-US/winserverwsus/threads

Tom Svehla wrote:
> I've been starting to see multiple instances of KB974417 fail during
> install
> from WSUS. I've found that you need to un-install KB976569 (released
> 2/23/10), then install 974417. Then you can re-install 976569.
>
> This will probably only be an issue on machines that do not have .NET
> 2.0/3.5. 976569 and you are doing a clean new .NET install. KB97659 does
> not
> supersede 974417, as they address different issues, so both are apparently
> needed.
>
> Just wondering if anyone else has seen this or is Microsoft aware of this
> issue and will they have have a fix down the road.

From: Ian on
Hi Tom,


Out of about 250 machines, I have 7 which were giving me this error. You fix
resolved the issue thanks. It's a bit of a pain thought! Hopefully Microsoft
will fix this sometime soon.