Win10 Anniversary Update 14393.105 misses key fixes, little new in beta build 14915

Topic

New Reply

… and the under-the-shelf Release Preview ring for Win10 Fall Update. InfoWorld Woody on Windows
[See the full post at: Win10 Anniversary Update 14393.105 misses key fixes, little new in beta build 14915]

Reply | Quote

Replies

How can they legally get away with WUDO on by default – they’re not paying for the bandwidth and have no legal right to use it!!!!

Most Users don’t even look at settings. There’s going to be some screaming about this when people get a bill they aren’t expecting.

Reply | Quote

I installed 14915. Some observations:

SettingsPersonalizationColors crashes when opened.

Cortana is not fixed – in my initial upgrade to 1407, HKCUSoftwareMicrosoftWindowsCurrentVersionSearch DWORD BingSearchEnabled was set to 0. This turned off the interactive portion of Cortana, removed the Cortana “O” from the Search Box, and removed Cortana from the taskbar context menu (although the Cortana process was still running in Task Manager and showed activity when typing into the Search Box). I left the setting at 0, and it has not been changed with this Build. Cortana is still “broken.”

Safe Search options have been added to the Search Box settings.

System Restore is OFF by default AGAIN.

Under Windows Update, I had checked to get updates only from my local network, then turned WUDO completely off. The update to 14915 did NOT turn it back on. (Unless WUDO ignores the setting)

Other than “Get Office,” no other CrApps came with this Build.

How to discourage WUDO:
Upgrade.
Reboot.
Run Disk CleanupClean up system files. Check Delivery Optimization. Delete files. (I suspect store app updates leave stuff there too)

Reply | Quote

Although not applying to most of the readers here, it is useful to know that there are other major applications having problems with Windows 10 v1607.
Windows 10 Anniversary Update (v1607) – Citrix Known Issues
http://support.citrix.com/article/CTX216312

Reply | Quote

Although not clearly stated in update history page, but if you look in KB3176934 article, you would see it saying that KB3176938 fixes the PowerShell DSC issue
http://go.microsoft.com/fwlink/p/?LinkId=825551

and the update history actually list Powershell and printing among grouped fixes in last note:
Addressed additional issues with compatibility, remote desktop, BitLocker, (PowerShell), Direct3D, networking policies, Dynamic Access Control ( rules, Microsoft Edge, Connected Standby, mobile device management (MDM), (printing), Fingerprint logon, and Cortana.

Reply | Quote

Dear Woody,

If we are avoiding the Anniversary Update all together, or at least until you give the go ahead, how do we know what additional KBs to avoid other than this Aug, 31st kb3176938?

When you give the go ahead, will it be for those KBs for build 1511 that don’t break things?

Why are we getting updates on any old day they decide to send them out? First, it was the second Tuesday of the month then it became the first and second Tuesday of the month and now it’s any day of the month if we are getting them on the last day of the month, and the 2nd to last day?

People can no longer be prepared to have their computers destroyed by MS now because it’s becoming so random!

I guess it is time to pull out the wushowhide tool a week early.

Reply | Quote

For those interested in Group Policy, here is the up to date reference which include Windows 10.
Group Policy Settings Reference for Windows and Windows Server
https://www.microsoft.com/en-us/download/details.aspx?id=25250

Reply | Quote

Wow. The Win10 list has over 4,000 entries – and it’s up to date (with version 1607) because it has

HKLMSoftwarePoliciesMicrosoftWindowsWindowsUpdate!DeferFeatureUpdatesPeriodInDays

HKLMSoftwarePoliciesMicrosoftWindowsWindowsUpdate!PauseFeatureUpdates

and

HKLMSoftwarePoliciesMicrosoftWindowsWindowsUpdate!DeferQualityUpdates HKLMSoftwarePoliciesMicrosoftWindowsWindowsUpdate!DeferQualityUpdatesPeriodInDays

HKLMSoftwarePoliciesMicrosoftWindowsWindowsUpdate!PauseQualityUpdates

Those are the key registry entries for delaying forced updates, only available in GPEdit for 1607.

Reply | Quote

Checking on it now. Article shortly.

Reply | Quote

Thanks!

Reply | Quote

I’m getting the feeling that patches that break things are delivered by WU, but fixes are only available through the Windows Catalog (printers, Powershell). Is anyone else seeing this trend?

If this is where things are going, it’s going to hit the average User HARD.

Reply | Quote

I think only very few and specific policies have been removed from Windows 10 Pro. Majority of the Group Policies are still common for Windows 10 Pro and Enterprise (or Education which is very much the same with Enteprise, only different licence). The Windows Update related Group Policies should still be in Pro and working (for now at least).

Reply | Quote

That poses an interesting question: Do those new Group Policies’ registry changes take effect in Home?

Reply | Quote

I don’t think it’ll work out that way. See my new article http://www.infoworld.com/article/3114705/microsoft-windows/progress-report-where-we-stand-on-fixes-for-the-big-bugs-in-windows.html

Reply | Quote

Only a few works in Home
when they state that certain policy require Enterprise or Education, the really mean iy
most policies are controlled of affected by the edition Product Policy, which is protected by kernel and SPP service

Reply | Quote

We will need to be on the lookout for large increases in costs from service providers.

Because this will necessarily cause individuals and businesses to, in actuality, be service providers, will it increase their chances of being hacked. With all the holes MS creates in its products it seems as it it would be a point of concern for many people and businesses, etc.

Reply | Quote

Citrix is used extensively in my previous job — that’s how our huge user base connected remotely.

Reply | Quote

It is all about numbers and priorities.
How many end-users are really affected by the mentioned functional issues?

Reply | Quote

I will leave this answer to those who are working with Home versions. Those editions are restricted versions and as such there are inherent limitations. There is no excuse for Pro versions not to work though.

Reply | Quote

@abbodi86 knows Windows in the deepest detail and this is not common knowledge.
I remember few years ago when I was trying to understand why Windows 2003 Server 32-bit was able to use PAE (36-bit addressing of RAM, more than 3 GB RAM), while Windows XP was not, both being built on almost the same components. I found exactly the same thing like @abbodi86. There are hard-coded components related to licence and that behaviour can be bypassed (illegally) only by replacing the locked-down components. However, by replacing the kernel, would that Operating System still be the same or will become the version of the new kernel?

Reply | Quote

How about the “icon text left justified” bug introduced in 1607? Has this been fixed by this new cumulative update?

Hope for the best. Prepare for the worst.

Reply | Quote

Nope, it’s left justified in the latest beta build too, 14915. Looks like it’s a “feature” not a bug.

Reply | Quote

Here’s a detailed thread about the matter:
http://forums.mydigitallife.info/threads/39411

if you don’t have a membership in MDL forums, here’s the contents:
http://pastebin.com/raw/zN2Pxx8r

Reply | Quote

(And if you aren’t a member of MDL, you should be! Great stuff.)

Reply | Quote

Ridiculous. Surely Microsoft can fix it if it wants to by now?

Microsoft really wants to drive users like me away, it seems. Another reason not to touch the crap called Windows 10.

Hope for the best. Prepare for the worst.

Reply | Quote

I do Citrix design and is currently my primary focus. Windows in all its detail is somehow implicit and a must in order to be an effective Citrix engineer.

Reply | Quote

Hi Woody, I already had big problems installing KB 3176934 successfully and ended up blocking this patch with wushowhide (after you told me how).

Now I’m facing the same problem with KB3176938;
the update process never succeeds after rebooting. And after each reboot, Windows tries to install it again and fails…

This is getting really annoying, don’t know what to do next. Should I block this (and maybe all coming updates) too? Or should I reinstall Win10 and hope for the best? Or is there something else I could try?

Hope you or someone else can help. I am not a noob, but also no expert, and this lousy update thing is growing over my head…

Reply | Quote

Thank you @abbodi86 for extracting the info from MDL. Very interesting for understanding the philosophy behind Windows licensing and the artificial limits imposed in different editions. I suppose it has only academic value, since there are much easier ways to achieve the same outcome which is proposed in the original post.
I am not (yet) a member at MDL, but as Woody says, I should 🙂

Reply | Quote

I wouldn’t worry about KB3176938. It’s going to be overridden by the cumulative update coming on Sept 13. Barring some amazing piece of malware, you aren’t going to get infected in the interim.

Just keep using Chrome or Firefox, don’t use Flash, and you’ll be fine.

Reply | Quote