Windows 10

Cumulative Update for Windows 10 Version 1607: August 31, 2016

August 31, 2016 — KB3176938 (OS Build 14393.105)
This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:
-Improved reliability of Windows Ink Workspace, Microsoft Edge, File Server, Windows kernel, Microsoft Component Object Model (COM), Cluster Health Service, Hyper-V, multi-factor authentication (MFA), NTFS file system, PowerShell, Internet Explorer 11, facial recognition, graphics, Windows Store, and Windows Shell.
-Improved performance related to purchasing Windows Store apps.
-Improved battery life of wearable devices (such as the Microsoft Band) while Bluetooth is connected and idle.
-Improved compatibility of using Xbox One controllers with various games.
-Addressed issue with incorrect character mapping between Japanese and Unicode for the question mark.
-Addressed issue that prevents the download and initialization of .NET objects in Internet Explorer 11.
-Improved support of new near-field communication (NFC) chips for Windows 10 Mobile.
-Addressed issue with game or app audio not resuming after ending a call on Windows 10 Mobile.
-Addressed additional issues with compatibility, remote desktop, BitLocker, PowerShell, Direct3D, networking policies, Dynamic Access Control (DAC) rules, Microsoft Edge, Connected Standby, mobile device management (MDM), printing, Fingerprint logon, and Cortana.

This did not fix my freezing issue. Win10 AnniUpdate is still unusable on my main rig. Ridiculous.
Are you guys at Microsoft trying to drive me to go to Linux full time?

Win10 AnniUpdate removed the ability to disable the lock screen via Group Policy.
I’ve been getting lots of questions on this issue and in my search for answers I cannot see where anyone has come up with a solution that works for everyone.
I’m having an issue helping with this because I never see the lock screen.
– My desktop is set to auto login ( bottom of page: https://www.tweakhound.com/2015/12/09/tweaking-windows-10/4/ )
– All my power plans disable all power saving when plugged in.
– If I’m going to be away from my computer for more than 10-15 minutes I shut it down. So. even unplugged it never hits the Sleep threshold.

As I said above. I’ve not seen a single solution that seems to work for everyone and survives reboots.
Well, there seems to be one. BUT, I am unsure of the cost of this tweak (aside from the obvious error logs). It is:
Rename the folder C:\Windows\SystemApps\Microsoft.LockApp_cw5n1h2txyewy .
I DO NOT RECOMMEND THIS. I haven’t had time to research it.
***Update – Reader Koos says this did not work. Can anyone confirm this?

 
Has anyone found a solution?

I’m not a big fan of the Microsoft Community or Microsoft MVP’s but occasionally someone in that group stands out. Andre Da Costa is one of them and he has just published 2 excellent Wiki articles. Read’em and bookmark’em for tomorrow.
How to download official Windows 10 ISO files
How to Upgrade to Windows 10 Anniversary Update version 1607 using ISO File

Ed Bott has called B.S. on the Forbes reporter that claimed Microsoft was gonna allow us to fully control Win10’s privacy options.
Geeze. I reckon only time will tell.
Here is the real gem from Microsoft’s statement to Ed:
“Executives believe that existing privacy controls are reasonable for consumers and there’s no need for a drastic change.”

As I sat for 2 and 1/2 hours waiting for the local tire guys to put 2 new fracking tires on my wife’s car, reader Dave sent me the link to:
Ed Bott: When it comes to Windows 10 privacy, don’t trust amateur analysts
The article discusses the article I linked to Sunday. Some random dude took a stab at trying to figure out who/what Win10 was connecting to. Apparently that post has been deleted. I didn’t talk too much about it except to say I had made a similar attempt last September. I was hoping my readers would see that my results were almost totally opposite from his. I don’t know if anyone saw it or not.
Anyway, Ed completely dismantles this guys test and takes folks who were doing “I told you so’s” to task. I think Ed may have been a tad hard on the guy in the original post. He was just making an attempt at some Geekery. He didn’t ask for half the tech world to read it. The reporters sourcing the story deserve the blame for sensationalizing it. Ed does give it to them with both barrels.
Agree with him or not, it is a must read.

***UPDATE, 14:15hrs
The guy that Ed takes to task above has learned from Microsoft that:

Contacting me again a Microsoft spokesperson explained the company now wanted to speak about the issue. In short: Microsoft is taking action. It has decided to release updates “later this year” which will enable users to fully control all background telemetry and data tracking and, if desired, disable it completely. Microsoft also asked me to stress that disabling these background operations is something it would “strongly recommend against”.

My takeaway is that our incessant bitching to and about Microsoft on this issue has produced the second caving in by Microsoft in the last week. One button to shut it all down is what we asked for and it looks like we will get it.
Congrats to us!
and
Congrats to Microsoft!