Microsoft .NET Framework 3.5 Service Pack 1

[stenews]

Hi to everyone...
I hope someone of you could give an hand to understand that:
Recently, as I use to do systematically, I launched windows update to check my system for the latest available fixes.
This time I saw a big, over 200MB, update:
Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update (KB951847) x86

Date last published: 1/27/2009
Download size: 248.4 MB

Microsoft .NET Framework 3.5 Service Pack 1 is a full cumulative update that contains many new features building incrementally upon .NET Framework 2.0, 3.0, 3.5, and includes cumulative servicing updates to the .NET Framework 2.0 and .NET Framework 3.0 subcomponents. The .NET Framework 3.5 Family Update provides important application compatibility updates.
After I restarted the system I saw in the event viewer log many unusual warning messages (see the screen shot attached)...why?
Should I really need this update or I can/should leave it there?
What do you suggest to do with it?

Thanks for any help,
Stefano.

P.S.
I'm running Windows Xp Pro SP3

[Inspector.Gadget]

Look them up at http://www.eventid.net/

[stenews]

Hi Inspector.Gadget and thanks for your reply, but I'm still in trouble with it. :confused:
I mean, I read many of those comments while I was goggling the net (before post here) but I'm still not able to understand its exact nature...
Is it something to worry about or I can forget it?
Have you did this kind of update?
If yes, have you had the same warning messages than me?
Is it something important for the overall stability/performance of my system?

Thanks again for your interest...
Bye,
Stefano.

[laserfan]

Stefano, today is 27-Feb and your screen shot is from 29-Jan!? If these are the only errors you received, and you've booted/rebooted your PC many times since then, I'd say don't worry about it, and leave it alone.

I've installed this update on several of my PCs, with different OS, and no problems here.

[stenews]

hi mate and really thanks for your help too!
you're right... when you said that!
today is 27-Feb and your screen shot is from 29-Jan!? I try to explain that...
when I first did the update and I rebooted my PC I saw those warnings messages and because they involve .NET Framework I was immediately in a worry because I roughly know that it plays an important part in the "video environment" so I took my Acronis last week image and I restored it, after that moment I didn't update my installation any more and I start to dig the net looking for any reasonable explanation about that...until now.

Sorry for the long story but.. that's all.
Stefano.

P.S.
you said that:I've installed this update on several of my PCs, with different OS, and no problems here and of course you have no warning message...haven't you?

[laserfan]

...and of course you have no warning message...haven't you?No I have not.

I can only say that you will have to decide if the warnings bothered you enough that you don't want to try it again. But honestly you need to look INSIDE the warnings for the exact message you got, not just at the error "title" list, to see what they are saying to you.

stenews I personally have given-up trying to fight MS and its many updates, deciding instead to try to stay current with everything, and allow Windows Automatic Updates to alert me to all new downloads. This was a big one but went smoothly for me.

BTW I did this update "by hand", separately downloading from Windows Update Catalog, and later installing separately, and I recall that the 248Mb update included four executables. Then I ran every one of them individually, in "name" order. Worked fine. Then I went to Windows Update to see if MS, after examining my PC, was satisfied and it was. Just FYI as to how I did it.

There are a couple of utilities here that rely on .NET 3.5 so I wanted to be up-to-date. :)

[stenews]

I see your point...but ...you need to look INSIDE the warnings for the exact message you got, not just at the error "title" list, to see what they are saying to you I can't do that any more because I leaved from the previous windows installation...but of course I'll try to install the update again and may be now I'll follow your procedure.
Where did you download the all packages? I mean could you post me the URL you used with a brief review of your procedure?

Thanks for all! I really appreciate that.
Stefano.

[laserfan]

It's the Microsoft Update Catalog (http://catalog.update.microsoft.com/v7/site/Home.aspx) site, where you can download anything individually--useful for corporate environs or (in my case) a home w/a lot of PCs and limited Web access. I only download once, then deploy to all.

No procedure to install, just download and run all the executables therein.

[stenews]

okay...thanks again mate.

Just one more question:
Do you think that it exists a particular "order" to follow when one stars to update?
I mean, should I do an update before another one?
In case which is your habits in doing that?

Thanks again and bye,
Stefano. :thanks:

[laserfan]

I don't think the order makes a difference. I think I just did 'em starting from the biggest to the smallest. Here's what mine were named, and this order. The "ochelper" didn't do anything when I double-clicked on it. Not sure why, nor do I care as the other four worked! Good luck!

X86_IA64_AMD64-all-dotnetfx35_3dce66bae0dd71284ac7a971baed07030a186918.exe
X86_IA64_AMD64-all-ndp20sp2-kb958481-x86_04fcde4b28dd4f6db7548831d35d1c6bf38e1335.exe
X86_IA64_AMD64-all-ndp30sp2-kb958483-x86_2b03b54c0972c16ab6ce75f42ac4877af87ce844.exe
X86_IA64_AMD64-all-ndp35sp1-kb958484-x86_8b5036b48590c52e3edba8e297cd3017b7a3043c.exe
X86-en-ochelper_21f0eb887bce203dee7e4309f525b454bb63b7be.exe

[stenews]

Hi laserfan and sorry if I ask your help again...
I just completed to upgrade and I decided to post you all the screen shots that are showing the details of those warning messages...I hope you or someone else would give them a look for me. :rolleyes:

Bye and I'm really thank to you for all!!
Stefano.

P.S.
Keep in mind that there is even "one" more bunch of this warning messages that comes just before those ones and because of they say the same things, I'm posting just the screen shot without any properties windows.

@ neuron2,
I apologize for the inconvenient and I fell really embraced about that :o.
It will not happened any more that's for sure.
I removed all those pictures and I followed straight away your suggestion.

http://img15.imageshack.us/img15/4086/netframep5hl3.png
http://img17.imageshack.us/img17/8969/netframep4xv2.png
http://img18.imageshack.us/img18/6717/netframep3fw3.png
http://img21.imageshack.us/img21/4707/netframep2gk6.png
http://img23.imageshack.us/img23/351/netframep1ec6.png
http://img6.imageshack.us/img6/8180/netframebeforesp1.png

[Guest]

Please use a file upload site for large numbers of large attachments. I'll approve these but in the future, please use an upload site for masses of data.

[mitsubishi]

They don't look like anything to worry about. Some stuff was already there because you were updating, IIS updates and components weren't installed because IIS isn't installed, nothing really going wrong, just warnings in case you need to trace something later.

If something had gone awry during installation the installer would most likely have aborted.

[stenews]

hi mitsubishi and many thanks for reply :)
I see your point... just a question please, what is IIS?
Is it nothing really important to me? right?

by,
Stefano.

[Doom9]

IIS = Internet Information Server. You can safely ignore the ASP.NET warning (note that it's a warning only.. warnings can or can not be serious.. unless you have errors in the logs, there's definitely no reason for concern and I'd even go as far as to say that as long as your computer doesn't misbehave, ignore errors as well. Every computer I've seen had a number of warnings and errors that could safely be ignored. It's like you not calling your doctor every time you have a little itch (unless you're a hypochondriac).

[stenews]

you're right mate...I defnly over estimated all the story!
Thanks for your help too.

Bye,
Stefano.