Microsoft Germany agrees to stop forcing Windows upgrade downloads

Another interesting post from Günter Born involves Microsoft’s commitment to never again download Windows upgrade files before receiving user permission.

Computerworld Woody on Windows

Brad Smith, MS chief legal officer, leaves US Commerce Dept’s Digital Economy Board of Advisors

Post coming in Computerworld

I’m temporarily removing the ban on political commentary, but only on this comment thread, in honor of Brad’s decision.

The ban on swearing remains in place, however, and you’re always welcome to tackle any subject in the Rants forum.

Happy eclipse, everybody.

Off to see the solar eclipse

Rahu

Credit: Nongnit

Resilient File System (ReFS) “Create” ability being pulled from Win10 Pro

@abbodi86 just noted a change in the list of features deprecated (removed) from Win10 Fall Creators Update, version 1709, expected this October or so.

That document now says:

Resilient File System (ReFS)

Creation ability will be available in the following editions only: Windows 10 Enterprise and Windows 10 Pro for Workstations.

Creation ability will be removed from all other editions.  All other editions will have Read and Write ability.

(added: August 17, 2017)

Microsoft’s Resilient File System (ReFS) was introduced in Server 2012, and has been built into all versions of Windows 10. Few individuals bother with it, but PCs that handle massive amounts of data can benefit from ReFS’s improved data handling, the ability to create truly huge logical drives, regardless of physical drive space limitations, built-in redundancy, and removal of many of the limitations imposed by the current file system, NTFS.

Mauro Huculak at Windows Central has a good overview of how to use ReFS on any Windows 10 machine.

Apparently, in the future, all Win10 machines will be able to use ReFS volumes – but only Enterprise and Win10 Pro for Workstations users will be able to create them.

Think of it as another way to convince Win10 Pro users to spend the extra bucks for Win for Workstations. I expect we’ll see more differentiating features before details on Win for Workstations roll out. Price, for example.

Amazon Echo hits $99

No doubt Amazon is getting ready to launch the Echo 2 (or Amazon Echo Creators Update Pro for Workstations, North American Fall Edition = AECUPFWNAFE, in Microsoft nomenclature).

That said, I’ve never seen a cheaper Echo. It’s the whole thing. $99.

I use my Echo and Dot constantly as an intercom, and frequently for all sorts of other things.

Use the link on the right and AskWoody gets a small kickback — no cost to you, of course.

Microsoft offers solution to the KB 4034658 Update Server red-lining problem

On August 11, in Computerworld, I mentioned a disturbing phenomenon: the problem-plagued August cumulative update for Windows 10 Anniversary Update (version 1607), KB 4034658, was causing WSUS servers to redline.

On August 16, I posted a short article about the bug, pointing to an analysis by Scott Williams.

Microsoft has finally fessed up to the problem – and posted a complex workaround. Jarrett Renshaw, on the Technet blog, now says:

Recently, we’ve seen an increase in the number of high CPU/High Memory usage problems with WSUS, including WSUS in a System Center Configuration Manager environment – these have mostly corresponded with Update Tuesdays.

Microsoft support has determined that the issue is driven primarily by the Windows 10 1607 updates, for example KB4022723, KB4022715, KB4025339, etc. See here for the list of Windows 10 1607 updates.

Microsoft is also aware of a known issue with KB4034658 that will cause Windows 10 1607 clients to run a full scan after install – Microsoft is investigating and the latest information is available here.

These updates have large metadata payloads for the dependent (child) packages because they roll up a large number of binaries. Windows 10, versions 1507 (Windows 10 RTM) and 1511 updates can also cause this, though to a lesser extent.  Windows 10, version 1703 is still recent enough that the metadata is not that large yet (but will continue to grow).

For those of you trying to push cumulative updates for 1607 through an Update Server, you’ve seen the problem. It’s refreshing for Microsoft to admit the problem exists — ten days after the patch went out.

Renshaw offers a complex solution. Definitely something you want to keep in your back pocket, if you’re trying to run WSUS or SCCM with Win10 machines.

Looking at a 1 TB Surface Pro 2017? Make sure you know what you’re getting

The new 1 TB Surface Pro 2017 actually has two 512 GB drives buried inside, leading to a panoply of problems: Automatically running Defrag overworks the drives, and you can’t restore a full image. Some solutions, but no acknowledgment from Microsoft.

Computerworld Woody on Windows.

Have you seen the big bug fix for Win10 Anniversary Update, KB 4034661?

Microsoft says it released the patch yesterday, and it’s supposed to go out the Automatic Update chute. I haven’t seen it. Have you?

Computerworld Woody on Windows.

“In the interim, my old advice stands. It’s still too early to install any August patches.”

UPDATE: Microsoft finally fixed the KB article so it no longer says this patch will come out the Automatic Update chute. It’s a preview patch – like many more before it.