Woody Leonhard

About the Author Woody Leonhard


Win10 Fall Creators Update’s rapid, rocky rollout

A week ago today, Microsoft rolled out the “RTM” build of Windows 10 Fall Creators Update (FCU), version 1709, build 16299.15 – which should’ve been immediately upgraded to 16299.19. At least anecdotally, the initial push brought in far more Win10 machines than any previous rollout. I’ve seen few reports of problems from those who had FCU thrust upon them, but there are plenty of problems among those who installed the upgrade manually.

Yesterday, Windows servicing and delivery director John Cable talked about the phased rollout approach on the Windows Blog. Cable said:

To read this article in full or to leave a comment, please click here

Read more 0 Comments

Excel, Access, external DB driver errors linked to this month’s patches

Read more 0 Comments

How to block Windows 10 Fall Creators Update from installing

Some people want to install the latest version of Windows 10 the moment it’s available. They’ll line up — intentionally or not — to participate in a beta testing cycle that’s disguised as a four-month-or-so exercise, designed to winnow the last bugs out of the new version before it’s deemed ready for corporate use.

If you want to help beta test an unpolished version of Win10, you don’t need to do a thing. Microsoft plans to release Fall Creators Update on Oct. 17 and will roll it out over your machine when the company figures it’s fit.

On the other hand, you might want to consider waiting until any initial problems get ironed out, keeping Win10 Fall Creators Update off your machine until you’re ready for it. Blocking the update isn’t easy, in many cases. But if you’re persistent, you can do it.

To read this article in full or to leave a comment, please click here

Read more 0 Comments

Microsoft patch problems persist: bad release sequences, CRM blocks and more

We’re sitting at PT+2 — two days after Patch Tuesday — and the problems continue to roll in. Here are the latest mug shots in a rapidly devolving rogue’s gallery.

If you’ve been following along, you know about the initial problems I reported on Tuesday — the Word zero-day, TPM patches that don’t patch, known and acknowledged bugs in Windows patches. You saw the late bloomers I reported on Wednesday — delayed, failed and rolled back Windows patches, a non-existent Flash update, confusingly no .NET security patches, an incorrect description of the CVE-2017-11776 fix, and more TPM follies.

To read this article in full or to leave a comment, please click here

Read more 0 Comments

Early reports of myriad Microsoft Patch Tuesday problems

This month’s massive bundle of Patch Tuesday patches almost certainly contains more than a few surprises, and they’re only starting to surface. Here’s a rundown of what I’ve seen in the wee hours of Wednesday morning.

There are lots of reports of delayed, failed and rolled back installations of KB 4041676, the Win10 Creators Update (version 1703) monthly cumulative update, which brings 1703 up to build 15063.674. A quick glance at the KB article confirms that there are dozens and dozens of fixes in this cumulative update — a remarkable state of affairs, considering the Fall Creators Update, version 1709, is due on Oct. 17.

To read this article in full or to leave a comment, please click here

Read more 0 Comments

Another banner Patch Tuesday, with a Word zero-day and several bugs

It’s going to be a banner patching month. I count 151 separate security patches and 48 Knowledge Base articles, as well as the odd Security Advisory.

The Windows patch Release Notes point to four known bugs:

The cumulative update for Win10 Creators Update, version 1703 — which sports dozens of fixes — has a couple of problems: Systems with support enabled for USB Type-C Connector System Software Interface (UCSI) may experience a blue screen or stop responding with a black screen when a system shutdown is initiated, and it may change Czech and Arabic languages to English for Microsoft Edge and other applications.

To read this article in full or to leave a comment, please click here

Read more 0 Comments

Duck! Windows and Office patches are coming

If you’re running Windows, do yourself a favor and put Automatic Update on a temporary hold. Then wait and see if anything comes bursting apart at the seams.

Last month, there was good reason to install specific patches shortly after they were released — at least if you couldn’t train yourself to avoid the “Enable Editing” button in Word. But by and large, if you could avoid that button, there were myriad reasons why waiting a bit before installing the September patches paid off.

To read this article in full or to leave a comment, please click here

Read more 0 Comments

It’s time to install the September patches for Windows and Office

If you’ve already installed some (or all) of the September patches, you’ve watched a parade of problems pass by. The first stab at September’s Windows 10 Creators Update, version 1703, patch brought all sorts of problems to Edge — crashes, stalls and worse. It also brought some unlucky HP computer owners five to 10 minutes of black screens every time Windows restarted. Those problems were fixed earlier this week.

The Windows 8.1 patch made it impossible to log on with a Microsoft account. (I know, some of you think that’s a feature.) The Windows 7 patch made Internet Explorer sprout a new search box. We had a report of the Windows 7 patch breaking activation on certain Dell machines, but it appears that’s an isolated problem. The .NET Security and Quality Rollup makes certain custom images turn black. None of those bugs have fixes, but at least you’ll be prepared before installing the patch — and you’ll know where to look for problems.

To read this article in full or to leave a comment, please click here

Read more 0 Comments

Microsoft Patch Alert: Where we stand with September’s Windows and Office patches

Microsoft’s foray into quantum computing sure sounds neat, but those of us stuck with real programs on real computers have been in something of a quandary. Once again this month, we’ve hit a bunch of stumbling blocks, many of which were pushed down the Automatic Update chute.

Before we dissect the creepy-crawlies this month, it’s important to remember that you have to get the .Net patches installed, unless you fastidiously refrain from clicking the “Enable Editing” button in Word.

To read this article in full or to leave a comment, please click here

Read more 0 Comments

Microsoft releases KB 4040724 fix for bugs introduced in this month’s Win10 1703 patch

Those of you who cringed after installing Patch Tuesday’s missive for Windows 10 Creators Update, version 1703, can breathe a small sigh of relief. Two of the known bugs in that patch — one that scrambled Edge, another that black-screened HP computers for 10 minutes at a stretch — have been fixed, almost two weeks later. Microsoft also says it fixed cellular connectivity problems.

If all of the buggy cumulative updates make you feel a bit creepy, compare and contrast the reality to last week’s announcement that Windows 10 Creators Update is the “best and most reliable” version of Windows 10.

To read this article in full or to leave a comment, please click here

Read more 0 Comments

Win 8.1 monthly rollup leaves customers unable to use Microsoft account

This month’s Patch Tuesday brought some weird Windows bugs, but this one’s probably the worst.

I’m seeing reports all over the web that folks running Windows 8.1 aren’t able to log in to their computers using a Microsoft account. Microsoft’s response at this point is that they’re aware of the problem, but if you want to use your machine, you need to log on with a local account.

cannot sign in to ms accountWoody Leonhard/IDG

That isn’t a whole lot of help for people who haven’t set up a local account or need to get to something on the machine that’s only available to the Microsoft account.

To read this article in full or to leave a comment, please click here

Read more 0 Comments