Jump to content
The Hotfix Share

cgthamm

Hotfixer
  • Posts

    12,043
  • Joined

  • Last visited

Posts posted by cgthamm

  1. File Name: WindowsXP-KB959252-v2-x86-ITA.exe

    File Submitter: cgthamm

    File Submitted: 22 Sep 2016

    File Category: Italian Windows XP Hotfix Downloads

     

    KB959252 - Error message when you switch the operating system from a dual monitor setting to a single monitor setting on a Windows XP-based computer or on a Windows Server 2003-based computer that has the security update 954211 installed: "Stop 0x0000008E"

     

    Click here to download this file

  2. File Name: WindowsServer2003-KB974803-x86-FRA.exe

    File Submitter: cgthamm

    File Submitted: 20 Sep 2016

    File Category: French Windows Server 2003 Hotfix Downloads

     

    KB974803 - Le contrôleur de domaine s’exécute plus lentement ou cesse de répondre lors de l’exécution du processus de nettoyage

     

    REMARQUE: Une fois le correctif installé, vous devez suivre les instructions d'installation fournies dans l'article de la Base de Connaissances indiqué ci-dessus.

     

    Click here to download this file

  3. File Name: WindowsServer2003-KB974803-x64-FRA.exe

    File Submitter: cgthamm

    File Submitted: 20 Sep 2016

    File Category: French Windows Server 2003 Hotfix Downloads

     

    KB974803 - Le contrôleur de domaine s’exécute plus lentement ou cesse de répondre lors de l’exécution du processus de nettoyage

     

    REMARQUE: Une fois le correctif installé, vous devez suivre les instructions d'installation fournies dans l'article de la Base de Connaissances indiqué ci-dessus.

     

    Click here to download this file

  4. File Name: WindowsServer2003-KB974803-x64-ENU.exe

    File Submitter: cgthamm

    File Submitted: 20 Sep 2016

    File Category: English Windows Server 2003 Hotfix Downloads

     

    KB974803 - The domain controller runs slower or stops responding when the garbage collection process runs

     

    NOTE: After you apply this hotfix, you must follow the steps in the Installation instruction section of the aforementioned Knowledge Base article.

     

    Click here to download this file

  5. After testing with several of my clients' applications, I must report that .NET Framework 4.6.2 has both stablity and reliability problems. I do not have a choice but to recommend avoiding it until Microsoft has published some hotfix rollups for it.

     

    More broadly, all versions of .NET Framework 4.6 (all the "Windows 10 versions," if you will) still have significant stability and reliability issues.

     

    The latest version of .NET Framework that works well, in my experience, is 4.5.2.

     

     

     

     

     

  6. .NET Framework 4.6.2 is now available here:

     

    KB3151800 - The .NET Framework 4.6.2 offline installer for Windows

     

    If you had previously installed the .NET Framework 4.6.2 Preview (KB3120735), I highly recommend you uninstall it first.

     

    From Windows 7, this is straightforward, and can be done from Control Panel->Programs.

     

    From Windows 8.1, this is a little more involved. You have to go to View Installed Updates, and uninstall Update for Microsoft Windows (KB3120803). After that, you need to open an administrative Command Prompt and type:

     

    dism /online /cleanup-image /restorehealth

     

    Once that completes, you can proceed with installing .NET Framework 4.6.2.

     

    If you need a language pack for .NET Framework 4.6.2, you can get it here:

     

    KB3151801 - Microsoft .NET Framework 4.6.2 Language Pack (Offline Installer) for Windows

  7. I have no experience with Windows XP Embedded. That said, I do not believe that .NET Framework hotfixes are specifically targeted to specialized versions of Windows XP.

     

    KB941633 is for the .NET Framework 2.0 with no service pack. Are you sure this hotfix is the correct one for your scenario?

     

    .NET Framework 2.0 SP2 is the "current" version for Windows XP. Perhaps you could try to install an update such as KB2729450, available from the Microsoft Download Center, and see if it resolves your issue.

     

     

     

     

     

  8. File Name: NDP20-KB941633-X86.exe

    File Submitter: cgthamm

    File Submitted: 1 Jun 2016

    File Category: Language Neutral .NET Framework 2.0 Hotfix Downloads

     

    KB941633 - FIX: Error message when you run a client application that is built on the .NET Framework 2.0: "The request was cancelled. An underlying connection that was expected to be open was closed"

     

    NOTE: This hotfix applies to .NET Framework 2.0 with no Service Pack. .NET Framework 2.0SP2 and .NET Framework 3.5SP1 already contain the functionality this hotfix provides.

     

    Click here to download this file

  9. File Name: Windows6.1-KB3125574-v4-x86.msu

    File Submitter: cgthamm

    File Submitted: 1 Jun 2016

    File Updated: 28 Feb 2017

    File Category: Language Neutral Windows 7 Hotfix Downloads

     

    KB3125574 - Convenience rollup update for Windows 7 SP1 and Windows Server 2008 R2 SP1

     

    NOTE: You MUST install KB3177467, available from the Microsoft Download Center, before installing this rollup update.

     

    NOTE: You may want to download and install KB3139923-v2, available from the Microsoft Download Center, after installing this rollup update. Its original version is included in the rollup update, and it has since been updated to version 2. You can alternatively have Windows Update install it for you.

     

    NOTE: There are several known issues with this rollup update, for which Microsoft has now provided resolutions. Please refer to the aforementioned Knowledge Base article for details and instructions.

     

     

    Additional Known Issues:

     

    1. Windows Update may return error 0x80240019 the first time you check for updates following the installation of this rollup update. Should this happen to you, simply wait a few minutes and check for updates again.

     

    2. Windows Update may not be able to successfully finish checking for updates, no matter how long you let it run. Should this happen to you, temporarily disable automatic updating, restart your computer, and manually download and install the following update (available from the Microsoft Download Center):

     

    KB3161608 - June 2016 update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1

     

    Don't forget to re-enable automatic updating afterwards.

     

    3. Microsoft Office 2010 doesn't start when EMET is enabled. The solution is to download and install the June 2016 update follup for Windows 7 SP1 and Windows Server 2008 R2 SP1 (the same one as for Additional Known Issue 2, above). This Known Issue is documented by Microsoft here:

     

    KB3163644 - Microsoft Office 2010 doesn't start when EMET is enabled in Windows 7 or Windows Server 2008 R2

     

    4. Configuring updates may hang at 13% if certain USB devices (e.g. headsets) are connected when you install the rollup update. If this happens to you, let it timeout and roll back (this will take time -- be patient). Worst case, Configuring updates may freeze, in which case you'll have to power down your computer to have it roll back successfully. Once it has rolled back, unplug all USB devices except for mouse and keyboard, and re-install the rollup update. (Alternatively, you can remove any unnecessary USB devices before installing the rollup update and avoid this issue altogether.)

     

     

    Additional information regarding Microsoft's change in servicing model for Windows 7:

     

    Microsoft has changed the servicing model for Windows 7 to make it more like the servicing models it introduced in Windows 8, 8.1, and 10. Specifically, this means that instead of releasing hotfixes, Microsoft will be releasing monthly update rollups that contain all the fixes that would have been released as individual hotfixes.

     

    (Editorial: In general, this is a good thing, as it makes it easier to build and maintain OS deployment images. On the down side, if there is a bug in an update rollup, you are stuck uninstalling the entire rollup, as opposed to just the hotfix with the bug.)

     

    Since this Convenience update rollup was released, there has been a correction to one of the hotfixes included in it (kb3139923-v2). Microsoft also released the May 2016 update rollup (KB3156417). Beginning with the June 2016 update rollup (KB3161608), Windows 7 update rollups became cumulative (i.e. the July 2016 update rollup (KB3172605) includes all the fixes in -- and replaces -- the June update rollup.

     

    Updated 2016-08-17: Microsoft has released the August 2016 hotfix rollup (KB3179573). In yet another case of the right hand being clueless as to what the left hand is doing, this hotfix rollup (like the May hotfix rollup) is NOT cumulative, and must be installed in addition to the other post-KB3125574-v4 updates. Here is the Knowledge Base article for KB3179573:

     

    KB3179573 - August 2016 update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1

     

    Further, this hotfix rollup corrects a problem in SMB, so I took a look around for other recent Knowledge Base articles that discuss SMB issues, and found this:

     

    KB3181029 - SMB file server share access is unsuccessful through DNS CNAME alias

     

    In the Troubleshooting section, Microsoft still recommends applying KB2775511 and its post-requisite hotfixes. To do this successfully, you should apply them before KB3125574-v4.

     

    Updated 2017-02-28: Since I last updated this article, Microsoft released a servicing stack update for Windows 7:

     

    KB3177467 - Servicing stack update for Windows 7 SP1 and Windows Server 2008 R2 SP1: September 20, 2016

     

    Servicing stack updates should always be deployed as soon as possible after they are released. Microsoft also released an additional non-cumulative update rollup:

     

    KB3185278 - September 2016 update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1

     

    Starting in October, 2016, update rollups for Windows 7 became cumulative. As a hotfixer, I am interested by the cumulative updates that include both security updates and hotfixes. Microsoft has designated these as Security Monthly Quality Rollups. The most recently released one is:

     

    KB3212646 - January 2017 Security Monthly Quality Rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1

     

    Microsoft initially had a few problems making the update rollups cumulative. Of particular note, there were issues with supersedence. These now appear to be resolved, and hotfixers can keep their systems up-to-date by installing the most recent Security Monthly Quality Rollup.

     

    -----

     

    What does all of this mean in practical terms? Say you wanted to streamline your Windows 7 installation process. If you choose to follow Microsoft's new servicing model (including its ongoing recommendation to install KB2775511) for Windows 7, start with Windows 7 SP1, and install all of the following:

     

    KB3177467 (the most recent Servicing Stack for Windows 7)

    KB2775511 (the enterprise hotfix rollup)

    +KB2581608 (to automatically apply a required registry entry, which is not included in the enterprise hotfix rollup)

    +KB2752259 (to automatically apply a required registry entry, which is not included in the enterprise hotfix rollup)

    +KB2732673 (a post-requisite for the enterprise hotfix rollup)

    +KB2728738 (a post-requisite for the enterprise hotfix rollup)

    +KB2878378 (a post-requisite for the enterprise hotfix rollup)

    KB3125574-v4 (the April 2016 Convenience update rollup)

    +KB3139923-v2 (a hotfix that was included in KB3125574-v4, but that has updated since its release)

    KB3156417 (the May 2016 update rollup)

    KB3172605 (the July 2016 cumulative update rollup)

    KB3179573 (the August 2016 update rollup)

    KB3185278 (the September 2016 update rollup)

    KB3212646 (the January 2017 Security Monthly Quality Rollup)

     

    With 14 updates/hotfixes, you get a basic up-to-date Windows 7 installation that will work well for many users. You could then install additional updates and hotfixes that you want that are not included in KB3125574-v4. (For example, I install the security updates for Internet Explorer and the hotfixes for Remote Desktop.)

     

    Click here to download this file

  10. File Name: Windows6.1-KB3125574-v4-x64.msu

    File Submitter: cgthamm

    File Submitted: 1 Jun 2016

    File Updated: 28 Feb 2017

    File Category: Language Neutral Windows 7 Hotfix Downloads

     

    KB3125574 - Convenience rollup update for Windows 7 SP1 and Windows Server 2008 R2 SP1

     

    NOTE: You MUST install KB3177467, available from the Microsoft Download Center, before installing this rollup update.

     

    NOTE: You may want to download and install KB3139923-v2, available from the Microsoft Download Center, after installing this rollup update. Its original version is included in the rollup update, and it has since been updated to version 2. You can alternatively have Windows Update install it for you.

     

    NOTE: There are several known issues with this rollup update, for which Microsoft has now provided resolutions. Please refer to the aforementioned Knowledge Base article for details and instructions.

     

     

    Additional Known Issues:

     

    1. Windows Update may return error 0x80240019 the first time you check for updates following the installation of this rollup update. Should this happen to you, simply wait a few minutes and check for updates again.

     

    2. Windows Update may not be able to successfully finish checking for updates, no matter how long you let it run. Should this happen to you, temporarily disable automatic updating, restart your computer, and manually download and install the following update (available from the Microsoft Download Center):

     

    KB3161608 - June 2016 update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1

     

    Don't forget to re-enable automatic updating afterwards.

     

    3. Microsoft Office 2010 doesn't start when EMET is enabled. The solution is to download and install the June 2016 update follup for Windows 7 SP1 and Windows Server 2008 R2 SP1 (the same one as for Additional Known Issue 2, above). This Known Issue is documented by Microsoft here:

     

    KB3163644 - Microsoft Office 2010 doesn't start when EMET is enabled in Windows 7 or Windows Server 2008 R2

     

    4. Configuring updates may hang at 13% if certain USB devices (e.g. headsets) are connected when you install the rollup update. If this happens to you, let it timeout and roll back (this will take time -- be patient). Worst case, Configuring updates may freeze, in which case you'll have to power down your computer to have it roll back successfully. Once it has rolled back, unplug all USB devices except for mouse and keyboard, and re-install the rollup update. (Alternatively, you can remove any unnecessary USB devices before installing the rollup update and avoid this issue altogether.)

     

     

    Additional information regarding Microsoft's change in servicing model for Windows 7:

     

    Microsoft has changed the servicing model for Windows 7 to make it more like the servicing models it introduced in Windows 8, 8.1, and 10. Specifically, this means that instead of releasing hotfixes, Microsoft will be releasing monthly update rollups that contain all the fixes that would have been released as individual hotfixes.

     

    (Editorial: In general, this is a good thing, as it makes it easier to build and maintain OS deployment images. On the down side, if there is a bug in an update rollup, you are stuck uninstalling the entire rollup, as opposed to just the hotfix with the bug.)

     

    Since this Convenience update rollup was released, there has been a correction to one of the hotfixes included in it (kb3139923-v2). Microsoft also released the May 2016 update rollup (KB3156417). Beginning with the June 2016 update rollup (KB3161608), Windows 7 update rollups became cumulative (i.e. the July 2016 update rollup (KB3172605) includes all the fixes in -- and replaces -- the June update rollup.

     

    Updated 2016-08-17: Microsoft has released the August 2016 hotfix rollup (KB3179573). In yet another case of the right hand being clueless as to what the left hand is doing, this hotfix rollup (like the May hotfix rollup) is NOT cumulative, and must be installed in addition to the other post-KB3125574-v4 updates. Here is the Knowledge Base article for KB3179573:

     

    KB3179573 - August 2016 update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1

     

    Further, this hotfix rollup corrects a problem in SMB, so I took a look around for other recent Knowledge Base articles that discuss SMB issues, and found this:

     

    KB3181029 - SMB file server share access is unsuccessful through DNS CNAME alias

     

    In the Troubleshooting section, Microsoft still recommends applying KB2775511 and its post-requisite hotfixes. To do this successfully, you should apply them before KB3125574-v4.

     

    Updated 2017-02-28: Since I last updated this article, Microsoft released a servicing stack update for Windows 7:

     

    KB3177467 - Servicing stack update for Windows 7 SP1 and Windows Server 2008 R2 SP1: September 20, 2016

     

    Servicing stack updates should always be deployed as soon as possible after they are released. Microsoft also released an additional non-cumulative update rollup:

     

    KB3185278 - September 2016 update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1

     

    Starting in October, 2016, update rollups for Windows 7 became cumulative. As a hotfixer, I am interested by the cumulative updates that include both security updates and hotfixes. Microsoft has designated these as Security Monthly Quality Rollups. The most recently released one is:

     

    KB3212646 - January 2017 Security Monthly Quality Rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1

     

    Microsoft initially had a few problems making the update rollups cumulative. Of particular note, there were issues with supersedence. These now appear to be resolved, and hotfixers can keep their systems up-to-date by installing the most recent Security Monthly Quality Rollup.

     

    -----

     

    What does all of this mean in practical terms? Say you wanted to streamline your Windows 7 installation process. If you choose to follow Microsoft's new servicing model (including its ongoing recommendation to install KB2775511) for Windows 7, start with Windows 7 SP1, and install all of the following:

     

    KB3177467 (the most recent Servicing Stack for Windows 7)

    KB2775511 (the enterprise hotfix rollup)

    +KB2581608 (to automatically apply a required registry entry, which is not included in the enterprise hotfix rollup)

    +KB2752259 (to automatically apply a required registry entry, which is not included in the enterprise hotfix rollup)

    +KB2732673 (a post-requisite for the enterprise hotfix rollup)

    +KB2728738 (a post-requisite for the enterprise hotfix rollup)

    +KB2878378 (a post-requisite for the enterprise hotfix rollup)

    KB3125574-v4 (the April 2016 Convenience update rollup)

    +KB3139923-v2 (a hotfix that was included in KB3125574-v4, but that has updated since its release)

    KB3156417 (the May 2016 update rollup)

    KB3172605 (the July 2016 cumulative update rollup)

    KB3179573 (the August 2016 update rollup)

    KB3185278 (the September 2016 update rollup)

    KB3212646 (the January 2017 Security Monthly Quality Rollup)

     

    With 14 updates/hotfixes, you get a basic up-to-date Windows 7 installation that will work well for many users. You could then install additional updates and hotfixes that you want that are not included in KB3125574-v4. (For example, I install the security updates for Internet Explorer and the hotfixes for Remote Desktop.)

     

    Click here to download this file

  11. Found a serious problem in Windows 10 Insider Preview build 14342.

     

    If you run:

    dism /online /cleanup-image /startcomponentcleanup

    the component store becomes corrupted, and this results in Windows Update failing to install updates with error 0x80070643.

     

    Unfortunately, I have not yet found a way to repair the component store.

     

    I am backing up my data, and preparing to re-install W10IP 14342. For the moment, anyway, it appears that the only solution is to avoid using the above command.

  12. As some of my clients have now updated their systems to .NET Framework 4.6.1, I have compiled a list of hotfix rollups for both .NET Framework 4.6 and 4.6.1.

     

    .NET Framework 4.6 ONLY

     

    Hotfix rollups that apply to .NET Framework 4.6 under Windows Vista SP2, Windows Server 2008 SP2, Windows 7 SP1, and Windows Server 2008 R2 SP1:

     

    KB3088957, KB3099851 (both available from The Hotfix Share)

     

    Hotfix rollups that apply to .NET Framework 4.6 under Windows 8 and Windows Server 2012:

     

    KB3088955, KB3099848 (both available from The Hotfix Share)

     

    Hotfix rollups that apply to .NET Framework 4.6 under Windows 8.1 and Windows Server 2012 R2:

     

    KB3088956, KB3099849 (both available from The Hotfix Share)

     

    NOTE: The above hotfix rollups should be installed before installing any hotfix rollups from the list below.

     

    .NET Framework 4.6 and 4.6.1

     

    Hotfix rollups that apply to .NET Framework 4.6 and 4.6.1 under Windows Vista SP2, Windows Server 2008 SP2, Windows 7 SP1, and Windows Server 2008 R2 SP1:

    KB3120241, KB3139551, KB3146716, KB3154529, KB3166741 (available from the Microsoft Download Center)

    KB3179949 (available from Microsoft Update Catalog)

    KB3210136 (see NOTE 1 below)

     

    Hotfix rollups that apply to .NET Framework 4.6 and 4.6.1 under Windows 8 and Windows Server 2012:

     

    KB3120238, KB3139549, KB3146714, KB3154527, KB3166738 (available from the Microsoft Download Center)

    KB3179947 (see NOTE 2 below)

    KB3210133 (see NOTE 3 below)

     

    Hotfix rollups that apply to .NET Framework 4.6 and 4.6.1 under Windows 8.1 and Windows Server 2012 R2:

    KB3120239, KB3139550, KB3146715, KB3154528, KB3166740 (available from the Microsoft Download Center)

    KB3179948 (see NOTE 4 below)

    KB3210135 (see NOTE 5 below)

     

    NOTES:

     

    NOTE 1: KB3210136 is available from Microsoft Update Catalog, but you must search for the parent Knowledge Base article for your OS to get the update, and also install co-requisite updates as follows:

    - For Windows Vista SP2 and Windows Server 2008 SP2, search for KB3210142 on Microsoft Update Catalog to get the update, and also install KB3210129 (Important: KB3078601 is a prerequisite for KB3210129).

    - For Windows 7 SP1 and Windows Server 2008 R2 SP1, search for KB3205402 on Microsoft Update Catalog to get the update, and also install KB3210131.

     

    NOTE 2: KB3179947 is available from Microsoft Update Catalog, but you must search for KB3184951 on Microsoft Update Catalog to get the update.

     

    NOTE 3: KB3210133 is available from Microsoft Update Catalog, but you must search for KB3205403 on Microsoft Update Catalog to get the update, and also install co-requisite update KB3210130.

     

    NOTE 4: KB3179948 is available from Microsoft Update Catalog, but you must search for KB3186208 on Microsoft Update Catalog to get the update.

     

    NOTE 5: KB3210135 is available from Microsoft Update Catalog, but you must search for KB3205404 on Microsoft Update Catalog to get the update, and also install co-requisite update KB3210132.

     

    NOTE 6: The above hotfix rollups should be installed before installing any hotfix rollups from the list below.

     

    .NET Framework 4.6, 4.6.1, 4.6.2, and 4.7

     

    Editorial: 2017 was a rough year for Microsoft with respect to the .NET Framework. There were seemingly endless issues with Previews of Quality Rollups, and even a few with actual Security and Quality Rollups. With the release of the November 2017 Security and Quality Rollup, things have finally stabilized for the first time since December 2016. You can benefit from all of Microsoft's 2017-released work on the .NET Framework 4.6, 4.6.1, 4.6.2, and 4.7 by installing three updates (as applicable to your version of Windows).

     

    NOTE: If you are using .NET Framework 4.6, please install all the updates/hotfixes from the two sections above this one before installing the updates in this section. If you are using .NET Framework 4.6.1, please install all the updates/hotfixes from the section immediately above this one before installing the updates in this section.

     

    Rollups that apply to .NET Framework 4.6 and 4.6.1 under Windows Vista SP2 and Windows Server 2008 SP2, as well as .NET Framework 4.6, 4.6.1, 4.6.2, and 4.7 under Windows 7 SP1 and Windows Server 2008 R2 SP1:

    KB4038923 (available from Microsoft Update Catalog)

    KB4040973 (for Windows Vista/Server 2008, click here; for Windows 7/Server 2008 R2, click here)

    KB4041778 (for Windows Vista/Server 2008, click here; for Windows 7/Server 2008 R2, click here)

     

    Rollups that apply to .NET Framework 4.6, 4.6.1, 4.6.2, and 4.7 under Windows 8 and Windows Server 2012:

     

    KB4038921 (available from Microsoft Update Catalog)

    KB4040971 (available from Microsoft Update Catalog)

    KB4041776 (available from Microsoft Update Catalog)

     

    Rollups that apply to .NET Framework 4.6, 4.6.1, 4.6.2, and 4.7 under Windows 8.1 and Windows Server 2012 R2:

     

    KB4038922 (available from Microsoft Update Catalog)

    KB4040972 (available from Microsoft Update Catalog)

    KB4041777 (available from Microsoft Update Catalog)

     

    -----

     

    WARNING: In the case of Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2, be absolutely sure (as in, check to make sure) that you have already installed either .NET Framework 4.6, 4.6.1, 4.6.2, or 4.7 before applying any of these hotfix rollups. If you happen to have .NET Framework 4.5, .NET Framework 4.5.1, or .NET Framework 4.5.2 installed, these hotfix rollups will still install, and will cause a version mismatch between .NET Framework components that will (at best) cause general system instability, or (at worst) may even result in you not being able to use your system at all.

     

    Further, should you find yourself in this scenario, simply uninstalling the hotfix rollup(s) is insufficient to regain a working system. In addition to doing so, you will have to open an administrative Command Prompt, and type:

     

    dism /online /cleanup-image /restorehealth

     

    Alternatively, you can install a higher version of .NET Framework than you currently have (and, subsequently, its hotfix rollups) to fix this problem.

     

    Following are some articles from the Microsoft Knowledge Base which provide some information on this problem:

     

    KB3118750 - Known issue for security updates 3098779 and 3097997 for the .NET Framework 4.5.1 and 4.5.2 after you install the .NET Framework 4.6 on Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2

     

    KB3136092 - Clarification of the applicability of updates for the .NET Framework 4.6 and 4.6.1

     

    -----

     

    2016/05/20: Added KB3154527, KB3154528, and KB3154529

     

    2016/07/14: Added KB3166738, KB3166740, and KB3166741

     

    2017/02/03: Added KB3179947, KB3179948, KB3199949, KB3210133, KB3210135, and KB3210136

     

    2017/11/18: Added KB4038921, KB4038922, KB4038923, KB4040971, KB4040972, KB4040973, KB4041776, KB4041777, and KB4041778

  13. There is now a second hotfix rollup available for .NET Framework 4.6.1. Here are the relevant Knowledge Base Articles:

     

    For Windows Vista SP2, Windows Server 2008 SP2, Windows 7 SP1, and Windows Server 2008 R2 SP1:

     

    KB3139551 - Hotfix rollup 3139551 for the .NET Framework 4.6.1 and 4.6 on Windows

     

    For Windows 8 and Windows Server 2012:

     

    KB3139549 - Hotfix rollup 3139549 for the .NET Framework 4.6.1 and 4.6 in Windows

     

    For Windows 8.1 and Windows Server 2012 R2:

     

    KB3139550 - Hotfix rollup 3139550 for the .NET Framework 4.6.1 and 4.6 on Windows

     

    These hotfix rollups are available from the Microsoft Download Center.

     

     

    I have now completed a significant amount of testing. Despite the fact that Microsoft has made some corrections to RyuJIT, it is still not possible to use .NET Framework 4.6.1 without the COMPLUS_JitMinOpts=1 system environment variable. Attempting to do so results in an unstable system. In fact, in one case, it was not possible to get a Windows 7 PC running .NET Framework 4.6.1 with KB3120241 and KB3139551 installed to either log off, restart, or shutdown. It had to be forcibly powered off and then restarted.

     

     

    Bottom line, this hotfix rollup makes .NET Framework 4.6.1 better, but there remain RyuJIT issues that Microsoft needs to resolve.

×
×
  • Create New...