Woody Leonhard's no-bull news, tips and help for Windows, Office and more… Please disable your ad blocker – our (polite!) ads help keep AskWoody going!
Home icon Home icon Home icon Email icon RSS icon
  • Microsoft Excel vs Google Sheets

    Posted on August 16th, 2017 at 06:36 woody Comment on the AskWoody Lounge

    Preston Gralla puts them head-to-head and comes up with some startling (but not unexpected!) results. The write-up is “for business,” but the results are applicable to everyone.

    I’ve started using Sheets whenever I can.

  • .NET Framework 4.7 is now available for Win7 SP1

    Posted on June 14th, 2017 at 07:49 PKCano Comment on the AskWoody Lounge

    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

  • “2017-05 Update for Windows 10 version 1607” KB 3150513 appears over and over again

    Posted on May 8th, 2017 at 06:27 woody Comment on the AskWoody Lounge

    UPDATE: InfoWorld Woody on Windows

    I’m seeing it on my main production machine, too. It shows up on the list of installed updates (installed 2 May), but also appeared this morning on the list of updates ready to install.

    Poster Neil Hobbs on the Microsoft Answers forum says:

    If you have a look at the update in the Microsoft Update Catalog at the following URL, you’ll notice that it has been updated – the name and the KB reference has been updated;

    https://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=a9262201-26d9-464b-ab32-106e4652db0c

    Therefore the reinstall is due to this.

    Sure enough, the Microsoft Update Catalog shows it was last modified on May 4. If you go to the usual Update Catalog URL, you can see three different versions of the update, for 32-bit and 64-bit Win10 1607, and one for Server 2016 64-bit.

    On April 24, I wrote in InfoWorld about the new version of 3150513 being pushed onto all versions of Windows.

    Then on May 2 I talked about Günter Born’s discovery that there was a re-issue of KB 3150513 for 1607 only. A look at the KB page turned up key files dated April 27.

    Now, when I look at the KB page, I see that the key files were updated again, this time on May 3.

    The weird terminology — starting with “2017-05 Update …” throws off alphabetized lists of patches, as noted by NetDef yesterday.

    Günter Born has a rundown of more problems with KB 3150513 and KB 4015219 (the Win10 1511 cumulative update). According to the Update Catalog, both were re-issued on May 4. The last official cumulative update for 1511 appeared on April 11. This new one’s undocumented, as best I can tell.

    It would be interesting to know if this latest cumulative update for 1511, dated May 4, increments the build number above 10586.873 (which is the official build number for the release on April 11). If the number has been incremented, I don’t see any reference to it, anywhere, official or unofficial. If the number has NOT been incremented, somebody is playing fast and loose with the build numbering system.

    Sounds to me like somebody screwed this one up big-time.

  • Has KB 4013073, the MS17-006 IE cumulative update, been pulled?

    Posted on March 15th, 2017 at 12:28 woody Comment on the AskWoody Lounge

    I just saw a note at the SANS Internet Storm Center that it isn’t available in WSUS.

    I don’t see it in the Microsoft Update Catalog.

    Any idea if MS17-006 was pulled? If so, what was the problem – and is there a solution?

    UPDATE: No, it wasn’t pulled. @ch100 has the facts.

  • Amazon S3 cloud storage is down on the east coast

    Posted on February 28th, 2017 at 12:49 woody Comment on the AskWoody Lounge

    The Register:

    “Amazon Web Services is scrambling to recover from a cockup at its facility in Virginia, US, that is causing its S3 cloud storage to fail.

    The internet giant did not provide details on the cause of the breakdown that is plaguing storage buckets hosted in the US-East-1 region. The malady has led to major sites, including Imgur and Medium, falling offline, missing images or running like treacle. Just to stress: this is one S3 region that has become inaccessible, yet web apps are tripping up and vanishing as their backend evaporates away.”

    I haven’t seen any problems with AskWoody yet, but my fingers are crossed, wood duly knocked.

  • Muslims unite to repair Jewish cemetery

    Posted on February 22nd, 2017 at 10:05 woody Comment on the AskWoody Lounge

    Credit: KTTN

    St. Louis Muslims are raising money to repair Chesed Shel Emeth Cemetery, which was trashed over the weekend.

    Donate here. I did.

  • Cut through the bafflegab of Windows 10 versions, branches, updates and builds

    Posted on February 14th, 2017 at 12:17 woody Comment on the AskWoody Lounge

    Here’s a very down-to-earth description of Windows 10 and how it’s being upgraded.

    InfoWorld Woody on Windows

    Interesting. The tech press is only now (15 Feb) picking up on the news that Win10 1507 goes end-of-life in May. That’s not a huge deal as most people aren’t using 1507 any more, but it gives a guidepost for how future versions of Win10 will live and die.

  • No, you don’t want KB3216755, the Insider Preview Ring version of the next cumulative update

    Posted on January 25th, 2017 at 12:10 woody Comment on the AskWoody Lounge

    Repeat after me: No, you don’t want the latest Release Preview of Windows 10.

    Last night, Microsoft rolled out KB3216755 for PCs and 14393.726 on Win10 Mobile. You will only see the patch in Windows Update if you’ve signed up for the Insider Program, and set your Insider ring to Release Preview.

    I’ve said it before, many times: The Release Preview ring is an arcane place. Unless you are specifically testing future Win10 cumulative updates for an overriding reason – perhaps you’re supporting or developing an application for Windows 10, or you’re charged with distributing cumulative updates to a zillion machines – you do NOT want to be on the Release Preview ring.

    In fact, the situation’s so confusing, I rate it as one of the top 6 things wrong with the Windows Insider program.

    4. Release Preview ring builds aren’t beta builds and need a different name

    No doubt it was easier for Microsoft to roll the Release Preview function into the Windows Insider beta build machine, but that commingling has led to endless confusion.

    On the one hand you have beta builds — test copies of the next version of Windows. Right now, those builds are numbered 14931, and they’ll keep getting larger.

    On the other hand, you have Release Preview builds — precursors to the next cumulative update for the current version of Windows.

    The Windows Insider program caters to both those who are beta testing the next version of Windows and those who are testing the next cumulative updates to the current version of Windows. You bet it’s confusing — and the discrepancy contributes to the “Release Preview and Slow ring” misidentification.

    The fixes distributed in KB 3216755 for PCs (and 14393.726 on Win10 Mobile) will show up, some day. They’ll likely emerge as the non-security part of Win10 1607’s next Patch Tuesday cumulative update. But unless you really want to be an unpaid beta tester, stumbling with known problems in KB 3216755, steer clear.

    Repeat after me: No, you don’t want the latest Release Preview of Windows 10.