Newsletter Archives

  • .NET Framework 4.7 is now available for Win7 SP1

    This question from poster @CraigS526

    I upgraded not long ago to .Net Framework 4.6.2 JUST to get Longer File names and had No Issues. It never came up in Win Update to go from 4.6.1 — to ( .2 ) — so IF it is Not an option in June, is there any reason NOT to Install 4.7 Manually?

    .NET Framework 4.7 has just recently become available for Win7 SP1. Perhaps it would be a good idea to do some research on the problems with installation and use in Win7 SP1 before moving forward.

    Read here about the DirectX Dependency

    The DirectX dependency is now available in the Preview of Monthly Rollup released via Windows Update on May 16, 2017. The Monthly Rollup is also available for deployment via WSUS and the Microsoft Update Catalog under the following Knowledge Base Article ids:

    Windows 7 SP1 and Server 2008 R2 SP2: KB4019265
    Windows Server 2012: KB4019218

    The DirectX dependency is also available outside of the Monthly Rollup as an independent/standalone package in the Microsoft Update Catalog. Due to its relatively smaller size as compared to the Monthly Rollup package, this standalone package may be preferable for ISVs that need to redistribute the .NET Framework 4.7 with their application.

    Please see the following for more information: The .NET Framework 4.7 installation is blocked on Windows 7, Windows Server 2008 R2 and Windows Server 2012 because of a missing d3dcompiler update.

    And some information on known issues can be found here.

    .NET Framework 4.7 is also available for Win8.1 as a recommended update through Windows Update as of June 2017. It is also available for versions Win10, and as a part of Win10 Creators Update.

    Join us for further discussion on .NET Framework 4.7 on Win7 SP1 at Our .Net Framework 4.7 Upgrade Intentions

  • Windows 7 SP1 downloads dry up at Microsoft distributor Digital River

    If you want “genuine” Win7 SP1 bits, they just got harder to find.

    InfoWorld Tech Watch.

  • MS-DEFCON 4: Get patched, but don’t install IE 10 or KB 2670838

    With a rather ho-hum collection of patches coming this Tuesday, it’s time to get caught up.

    March’s Black Tuesday patches didn’t ring many bells. But there are two ancillary downloads – and a patch from February that’s still causing problems – that should give you pause.

    First, if you are running Windows 7 and you haven’t updated to Service Pack 1, now’s the time to do it. Microsoft released Win7 SP1 in February of 2011 — yes, more than two years ago — but it just started including SP1 in “automatic update” runs. If you look at your pending updates and SP1 is on the list, block out some time to run it (say, ten minutes, maybe more), and let ‘er rip.

    Second, the late-February patch known as KB 2670838 is still causing problems. The patch should NOT be offered – should not be pre-checked – when you look at the Windows update list. Don’t shoot yourself in the foot, and don’t check the box to install it.

    Third, details are all over the map, but a lot of people are complaining about the new version of Internet Explorer, IE 10, screwing up their Windows 7 systems. Simple solution: don’t install IE 10. If you’re running Windows 8, you already have IE 10, and it doesn’t seem to be causing any problems. If you have an earlier version of Windows, IE 10 isn’t even offered. IE 10 on Win7 seems to be a stinker. Once again, IE 10 is not pre-checked in the update list. Don’t check it.

    As always, avoid installing driver updates from Microsoft (go directly to the manufacturer’s site, or your PC manufacturer’s site), and if you’re offered Silverlight, laugh heartily; uninstall it if you have to.

    With those thoughts in mind, I’m moving us down to MS-DEFCON 4: There are isolated problems with current patches, but they are well-known and documented here. Check this site to see if you’re affected and if things look OK, go ahead and patch.

  • What you need to know about Windows 7 Service Pack 1

    InfoWorld Tech Watch blog.

  • Minor problems installing Win7 Service Pack 1

    Again, for emphasis, I do NOT recommend that you install Win7 SP1 yet. There isn’t enough meat to it to justify installing it yet.

    That said, Ed Bott has a good overview of some (apparently infrequent) glitches with the SP1 installer.