• Understanding .NET patches

    • This topic has 19 replies, 6 voices, and was last updated 13 years ago.
    Author
    Topic
    #482827

    OK, I’ve always followed Susan Bradley’s advice and steered away from .NET patches on my XP system.
    Yesterday I installed a great new PC Mag utility that required .NET 4 and I grudgingly allowed it to install.
    Now I have 6 KB patches sitting in my update que and after reading all the horror stories about broken installs I’m having second thoughts.
    I decided I would forgo the neat new utility and uninstall .NET 4
    BUT – add/remove tells me I not only have .NET 4 but also 2, 3 and 3.5 already installed, along with Silverlight 4.1
    I don’t remember installing them….

    Here’s my question – should I just uninstall the whole .NET family along with Silverlight?
    What will stop working if I do?
    Can I recover if I break something?

    I also found MSXML 4.0 and 6.0 Parser. Who are they?

    I guess I need to pay more attention to my installation logs…

    Any thoughts?:huh:

    Viewing 14 reply threads
    Author
    Replies
    • #1329758

      What operating system are you running?

      I don’t agree at all with removing previous versions of .Net. Why would you?!

      • #1329774

        I’m running XP, fully patched.
        I guess my concern is with the experience others have had trying to install the multiple security patches and running into partial installs and other problems requiring special tools to uninstall the Framework, modify the registry and a multitude of other problems.

    • #1329783

      I can only speak by my own experience, which was never anything like that. I think the number of cases was not that meaningful (although people who have problems are always more vocal about it).

      Until you have problems, which you may never actually have, I would do nothing, that is, other than what I would do anyway – keep a regular image backup of my working system, image before installing any updates and then use that in case of problems.

      Windows XP is installed in hundreds of millions of computers with different specs and different software configurations. IMHO, the .net update issue is grossly overrated. Of course, when an issue occurs with your machine, it’s always a “serious” issue, so the solution is not, IMO, to run a skeleton machine, software wise, in order to minimize problems, the solution is to be ready to face them and recover fast, if they happen. An image backup can be the solution, for this problem, if it ever occurs, and for many other problems.

      • #1330458

        I can only speak by my own experience, which was never anything like that. I think the number of cases was not that meaningful (although people who have problems are always more vocal about it).

        Until you have problems, which you may never actually have, I would do nothing, that is, other than what I would do anyway – keep a regular image backup of my working system, image before installing any updates and then use that in case of problems.

        Windows XP is installed in hundreds of millions of computers with difference specs and different software configurations. IMHO, the .net update issue is grossly overrated. Of course, when an issue occurs with your machine, it’s always a “serious” issue, so the solution is not, IMO, to run a skeleton machine, software wise, in order to minimize problems, the solution is to be ready to face them and recover fast, if they happen. An image backup can be the solution, for this problem, if it ever occurs, and for many other problems.

        Good points all. I am running Win7 Home Premium and have just installed all .net patches as they have come along and have never had a problem of any kind. And I do have a rigorous backup procedure automated and a system image just in case, but I’ve never had a problem, nor has anyone I know. My company is still running XP Pro and we install patches two weeks after release across our network, after they’ve been vetted, and all of the .net patches have worked just fine there too. I think the problem must be smaller than we’ve been led to believe. :^)

    • #1329827

      I am getting problems with a couple of new updates to the .NET Framework 1.1 SP1 on XP, and I have tried all the fixes/uninstalls/reinstalls that I can find.
      I shall just leave it to fail the updates each time that Windows Update tries to install them.
      Or just uninstall .NET 1.1 again, and see if anything objects!

      It would be awfully nice to know which pieces of software required which version of the .NET Framework (if any version at all!).

      I uninstalled the Java Runtime Environment years ago, and have since found only one program other than Libre Office/Open Office which needs it.

      Why do we have to put up with all this apparently rarely-used Stuff that gets updated every few weeks?

      BATcher

      Plethora means a lot to me.

      • #1329828

        Well, I hear the reasonableness here and admit it makes sense.
        I have the system images I need to protect against failed patches.
        I suppose I could just try the installs one at a time and see how it goes.
        Let me think about it…
        And thanks for the advice.

    • #1329829

      I’m sure everyone has read Susan’s latest article:
      http://windowssecrets.com/patch-watch/time-for-a-net-update-we-cant-ignore/
      That was what started me down this bunny trail.
      I suppose an alternative is to take BATcher’s approach and uninstall them all and wait to see who objects.
      Sigh…

    • #1329836

      No, not “uninstall them all” – just the one(s) you have problems with!

      BATcher

      Plethora means a lot to me.

    • #1329846

      Different versions can exist without previous ones. If the .net patches are security ones, it may make sense to remove the corresponding version if the patches can’t be installed, but even that may not be needed. My choice is to act on concrete situations, not the possibility of future issues…

      • #1329875

        I really need to do some homework here.
        Why are there so many different versions of .NET?
        Are they unique for different types or languages of development programs?
        Is Silverlight strictly for the development of IE add-on’s?
        If I uninstall it will my IE lose any functionality?

        I know that I intentionally installed .NET 4, but have no idea how the other versions got installed, as well as Silverlight.
        Did MS do it with an update or patch I didn’t inspect fully?

        Sorry about that, but this is an area I just don’t have a good handle on – can you tell?

    • #1329884

      The different .net versions represent an evolution of the .net framework throughout time. 4.5 is currently in beta and maybe will be integrated in Windows 8. It will surely be made available as a download to other Windows versions.

      .Net is a very interesting framework to develop programs both for Windows and for web development. Through ports such as Mono, it can also be used to develop for Linux, Android and even iOS.

    • #1329890

      Ok, so can I uninstall all previous versions to 4 wihout crippling software that was developed with, say, .NET 2.0?

    • #1329892

      No, you cannot do that. Programs that were developed for 2.0, need 2.0. Actually 3.0 and 3.5 require 2.0 present, as they are extensions to 2.0.

    • #1329893

      Got it. Thanks.
      OK, so I’m going to follow your advice, update my system image, install the patches one at a time and see how it goes.
      My OS has been quite stable for years and I don’t expect any surprises.
      But, as you say, the secret is to be prepared to deal with them when they come…
      Thanks.

    • #1329899

      Good luck :).

    • #1329955

      Well, six patches later, done one at a time, they all seemed to go in successfully.
      They sure took a lot of time to do their thing during installation.
      But all checks are green, all patches show up in Add / Remove and no sirens went off.

      So, I am now committed to .NET, it seems, and expect traffic every Patch Tuesday until I move on to W7.
      Maybe I should get busy on that update!

      Thanks again for the help and hand-holding here.

    • #1329957

      Glad that it all went well. I believe that’s what happens in most cases :).

    • #1330033

      DrRon: Not to burst your bubble, but W7 does not get you out of patch tuesday, and it does not get you out of frequent .net updates, either. I’m running W7 on 3 pc’s and have programs needing .net on them all. It still seems like a constant stream of updates to .net.

    • #1330464

      There is at least one web site, the Grant County Map Server that requires Silverlight to access it. I found out one day when I tried to access that same site while running Ubuntu. I have found that the web site error message will inform you that you need Silverlight to access it. I can’t believe the taxpayers got stuck with a proprietary system, but hey, it’s government. What else can you expect?

    Viewing 14 reply threads
    Reply To: Understanding .NET patches

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: