Newsletter Archives
-
Win10 1709 programs come back from the dead on reboot
There’s a new “feature” in Win10 Fall Creators Update that automatically restarts every program that was running when you reboot.
Which is precisely what most people don’t want. None of the usual Autoruns-type tweaks can turn it off.
Computerworld Woody on Windows
-
Another report of Win10 Creators Update (1703) users getting pushed to Fall Creators Update (1709), even with defer updates set
If you’re using Win10 1703, and you want to wait a bit to move to 1709, there may be a problem.
Yesterday, Microsoft announced that 1709 is “fully available for all compatible devices running Windows 10 worldwide!” (their exclamation point, not mine). Gregg Keizer has the details.
What I’m hearing – and can’t yet confirm – is that 1703 PCs with “feature update deferral” set to 365 days are getting pushed onto 1709.
Computerworld Woody on Windows.
UPDATE: Here’s another report of a “hard” bug in 1709:
Windows 10 Fall Creators Update is hit by a new bug that prevents installation, especially for devices with Intel’s X299 chipset and an NVMe SSD drive.
Thx SB.
-
MS-DEFCON 4: Time to get patched, unless you’re using Win10 Fall Creators Update, version 1709
If you got stuck with 1709 and it’s too late to roll back, stop using Internet Explorer or Edge, and wait until Microsoft gets its act together.
Computerworld Woody on Windows.
-
Brinkmann: Win10 1709 group policy setting incorrectly blocking cumulative updates?
Martin Brinkmann has uncovered a very strange group policy behavior in Win10 Fall Creators Update, version 1709, and written about it on ghacks.
It looks like the setting “After a Preview Build or Feature Update is released, defer receiving it for this many days” may, in fact, defer cumulative updates (which Microsoft insists on calling “quality updates”).
Switching the value back to 0, or disabling the policy altogether (which has the same effect), has Windows 10 pick up the missing cumulative updates immediately according to the user who reported the issue on Microsoft’s Technet forum.
That Technet post includes detailed step-by-step instructions for recreating the behavior. It also includes a note that poster Klaasklever has “seen reports that this issue is also caused by setting to defer Feature Updates in the Windows Update Settings within the normal Windows Settings App.”
Looks like it’s yet another bug in 1709.
-
Win10 v1709 “Preview Builds/Feature Updates deferral” Group Policy blocks Security Updates
This came in from Klaasklever
FYI:
The Win 10 v1709 “Select when Preview Builds and Feature Updates are received”
Group Policy (located under Computer Config –> Admin Templates –>
Windows Components –> Windows Update –> Windows Update for Business)
incorrectly blocks all Cumulative Security Updates.If enabled and set to anything greater than 0 days, not only feature updates
(i.e. upgrades to a new semi-annual Windows Version) are blocked,
but all cumulative security updates are wrongly blocked as well!This might cause some headaches for admins…
See my following post on Technet:
Cheers!
KlaaskleverIs anyone else seeing this behavior? -
Problem reported with folder permissions on Win10 1709, Office 2016
I bumped into an odd problem, reported by Sulpher212 on Reddit:
Office Standard 2016 64 bit – MAK – Volume Licensing
Users are having issue if they try to save Word or Excel documents they get errors regarding to permissions, or “Document could not save”, this is only on 1709, if the user is rolled back to 1703 documents save fine.
Poster that_computer_guy123 confirms:
We recently installed 1709 update for Windows 10 Enterprise N and Office 2016 Pro Plus. Two days ago we started having an issue where users couldn’t save from within any Office apps to their redirected folders or share drives, only to the local C:\ drive.
As you can see from the Reddit thread, this appears to be a hard bug and may be related to this month’s non-security Office updates – but it’s only showing up on Win10 Fall Creators Update, version 1709.
Has anybody out there seen this?
-
Bloomberg Terminal conflicts with Win10 Fall Creators Update
Bloomberg is advising that customers running Bloomberg Terminal need to refrain from upgrading to Win10 FCU, version 1709. Per their professional support page:
Known issue with Windows 10 Fall Creators Update
In October 2017, Microsoft released Windows 10 Fall Creators Update (OS build: 16299.19 and 16299.15). The update introduced issues that are known to interfere with the Bloomberg Terminal. We are working with Microsoft to resolve these issues. In the meantime, please refrain from updating your PCs to affected versions.
As I’ve advised many times, 1709 isn’t yet ready for prime time.
-
More Surface woes. This time it’s the Surface Pen and Win10 Fall Creators Update
If your Surface Pen suddenly stops working, there’s another possible cause. Before you change your battery or go out and buy another Pen, make sure you read this.
Computerworld Woody on Windows.
If you haven’t yet seen the Flickergate site, and you own a Surface, now might be a good time to drop by.