• .NET patches — manual installation only — released

    Home » Forums » Newsletter and Homepage topics » .NET patches — manual installation only — released

    Tags:

    Author
    Topic
    #126363

    Windows 7 and 8.1 non-security .NET updates are now available, but only through the Microsoft Catalog. Details on the Windows Software Update site.
    [See the full post at: .NET patches — manual installation only — released]

    3 users thanked author for this post.
    Viewing 8 reply threads
    Author
    Replies
    • #126367

      I guess it’s fair enough that these updates aren’t available through WU as they are non-security updates and we’re in the “security updates only” phase of life support for Windows 7 at least, I don’t follow Windows 8.1 as I have no interest in that version – and will not have in January 2020 when it will be a straight choice between sticking with Windows 7 (likely) or upgrading to Windows 10 (unlikely) depending on what happens between now and then.

      • #126370

        Windows 7 still and will get non-security updates until 2020

        those updates are specific to fix certain issue, and will probably incorperated in the next .NET Security Quality Rollup

        5 users thanked author for this post.
        • #126373

          Indeed. From https://blogs.msdn.microsoft.com/dotnet/2017/07/24/net-framework-july-2017-preview-of-quality-rollup/:

          “This set of changes will be made available on Windows Update to the broader set of Windows versions in August 2017. The known issue will be resolved in that update.”

          5 users thanked author for this post.
          • #126384

            Thanks for the clarification. It wasn’t clear initially that this was just a preview update.

            1 user thanked author for this post.
            • #126398

              I probably said it a million times already.
              The Catalog downloads are not for non-professional users.
              Even more so, the Catalog only (non-WU, non-WSUS) downloads are not normally visible even to professional users, unless they have an alerting system in place and they only address specific issues (they are hotfixes and not regular updates).

              2 users thanked author for this post.
    • #126381

      What is KB4032113.  I received it on Automatic update.  Group A.  .Net framework

      • #126387

        KB4032113 is the July 2017 Preview Rollup for .NET 3.5.1 on Win7

        3 users thanked author for this post.
    • #126382

      Will this be released through Windows Update at some point?

      • #126390

        “This set of changes will be made available on Windows Update to the broader set of Windows versions in August 2017. The known issue will be resolved in that update.”

        1 user thanked author for this post.
    • #126472

      From .NET Framework July 2017 Quality Update (July 25, 2017):

      “You can now install the July 2017 Quality Update for the .NET Framework. It applies to multiple Windows versions.

      This update resolves known issue 4033488. It is recommended on machines that have installed the July 2017 Preview of Quality Rollup or the May 2017 Preview of Quality Rollup.”

      3 users thanked author for this post.
      • #126581

        Fix to the preview patches.
        Isn’t everyone here aware of why those updates have “preview” in title?

        • #126585

          There was debate at this site about whether the preview monthly updates should be regarded as ready for production use. A comment from a Microsoft employee in the blog post in post
          #126373 seems to indicate that, at least for the .NET preview monthly updates, the answer is that they should be regarded as not necessarily ready for production usage.

          • #126590

            Another way to put it is to cosider the preview patches equivalent to the Insider Preview releases for Windows 10 and only with a large amount of tolerance equivalent to the CB releases.
            For me personally CB releases are good enough, Insider Previews are usable, but not everyone would agree.

    • #126576

      I ran this install on Win 7 Pro

      It removes D3DCompiler_47.dll from system32 folder.

      Canon printer software would not start up complaining the file was missing.  So I found reference to KB40189990 addresses D3D file error on Win 7 and Server 2012 Update for the d3dcompiler_47.dll component on Windows Server 2012, Windows 7, and Windows Server 2008 R2 

      Basically it restored missing dll and probably added things I don’t want.  In reality, to nit pick MS is probably petty based on all the EULAs for other things I actually need to run hardware.  Will just save that file on laptop before updating .NET.

    • #126682

      Every time I click on the link for the Microsoft Update Catalog for the manual download, it brings me to a blue page (http://www.catalog.update.microsoft.com/Install.aspx?q=4035510&referringpage=Search.aspx) that says “Microsoft Update Catalog” in the upper left corner on top of a globe, but nothing else is there. There is no information, link for file, or anything else that gets me to the download. Is there a better link for the manual download? This one doesn’t do anything for me. Thanks.

      • #126684

        Try this link MS Update Catalog

        Type the number (without the “KB”) into the search box

        • #126696

          I tried it first in IE11, but all I got was a momentary glimpse of the download links and then got error number 8DDD0020. But it worked fine in Chrome and got the download there. Any idea what causes that error number in IE11? I searched for an explanation, but nothing seems to resolve it. Thanks much.

          • #127179

            I tried it first in IE11, but all I got was a momentary glimpse of the download links and then got error number 8DDD0020. But it worked fine in Chrome and got the download there. Any idea what causes that error number in IE11? I searched for an explanation, but nothing seems to resolve it. Thanks much.

            Here’s your answer: In IE, you need to enable BOTH first party cookies and DOM storage. However, this advice also applies to anyone using Firefox (as I primarily do) or other browsers as well.

            In IE, click the”gear” looking icon in upper right corner of browser and select “Internet options” from the drop-down menu. Now, click the “Privacy” tab at the top of the new box. Move the slider to the Low setting and click Apply at the bottom of the box. I’ve tried other higher settings (“Medium”, etc.) and the page won’t load with anything higher than “Low”.

            If you have custom cookie settings, then just click the “Advanced” button in the “Privacy” tab and then check to make sure the heading under “First party Cookies” is set to “Accept”, then click “Apply” at the bottom of the box. If it’s already set, then just proceed with the next paragraph’s step.

            Now, click the “Advanced” tab at the top of the Internet options box, and scroll all the way down the settings until you get to the heading labeled “Security”. It will have a padlock icon next to it. Under that heading, click the box next to the entry labeled “Enable DOM Storage”, which should place a check mark in the box. Now click “Apply” at the bottom of the box and then “OK” at the bottom of the box and you should be all set!

            To be sure, clear the browser’s cache out so you get a fresh reload of the page PKCano referenced in his post above, #126684.

            I hope this helps!

            1 user thanked author for this post.
    • #126803

      i have a question about the net patch i did not download the preview for july kb 4032113 do i  need to do that before i download the update which i think is kb4035510.

      • #126839

        KB4035510 does not show the July preview (KB4032113) as a pre-requisite:

        Prerequisites
        To apply this update, you must have the .NET Framework 4.6, 4.6.1, 4.6.2, or 4.7 installed.

        The previews will eventually show up in subsequent updates, and are not required to be installed prior to that happening.

        Please note that this month’s .NET update (KB4035510) is for touch-enabled or stylus-enabled systems that have the May preview (KB4104616) installed, to fix/prevent known issues. It is not a security update.

        1 user thanked author for this post.
        • #127084

          This is the best information I’ve seen so far.  Thanks!

          Being 20 something in the 70's was far more fun than being 70 something in the insane 20's
    • #126838

      I’m confused — the quote from the MSDN blog post given above by MrBrian says the “production” level fix will be available on Windows Update in August, but down in the comment section, Rich Lander says “We intend to do another preview release in August and then have all the fixes go “live” in September on patch Tuesday”…

      1 user thanked author for this post.
    • #127082

      I’m confused too.  Either there is a real, bona-fide, do-something-good .NET update or there isn’t.  Please forgive me but all this talk about previews and how things are done in Win 10 doesn’t seem to do me any good as a Win 7 user who doesn’t do previews.  So, until someone can give me a good reason for doing this update, I’m holding off!  Maybe they’ll have something more concrete in August?  September?

      Again, please forgive me, this is very irritating.  It’s like M$ is going out of their way to make things as hard as possible for those of us who don’t wish to be Lemmings.

      Being 20 something in the 70's was far more fun than being 70 something in the insane 20's
    Viewing 8 reply threads
    Reply To: .NET patches — manual installation only — released

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

    Your information: