Disabling Cortana Voice Support during OOBE
Written by Anton Romanyuk
Yesterday I came across a Twitter thread in which multiple users detailed their beef with the revamped setup experience of Windows 10 (aka the OOBE). The OOBE was introduced with Windows 10 "Creators Update" (1703): Cortana voice walks the user through the OOBE experience, enabling the user to complete parts of OOBE by responding to spoken prompts. Windows 10 installations using following languages are affected: en-US, es-MX, ja-JP, en-GB, fr-FR, it-IT, de-DE, es-ES, fr-CA, en-CA, en-AU, pt-BR, zh-CN. Exacerbating the issue, Cortana's voice prompts are loud and proud by default and can become quickly irritating when attempting to install multiple machines at the same time. There’s little clear help for fixing it, so in this post, I’ll give you easy steps you can follow to tape up Cortana's cake-hole.
Windows 10 Fall Creators Update (1709) includes a number of enhancements over the previous Windows 10 release in various areas. You can see a detailed list of the changes here. Each major new version of Windows 10 also includes dramatic changes to Microsoft Edge, including a number of performance, security, and compatibility improvements. In addition, Microsoft continues to improve management capabilities for Microsoft Edge in an Enterprise deployment scenario.
As a reader of this blog, I suspect that most of you are already starting to work with Windows 10 Fall Creators Update (1709). As part of that process, you are probably taking a look at provisioned apps - most likely you want to ensure that only a choice selection of apps is being installed, whenever a user logs on either for the first time or after installing a feature update on a Windows 10 computer, because app installation directly impacts logon time.
In a desperate effort to make this blog post worth reading and not go through the indignity of having to write about Windows 10 1709, I have turned to the headline-generating festival currently ongoing on the net: the vulnerability in Trusted Platform Module (TPM) produced by Infineon Technologies AG which could allow security feature bypass.
Group Policy Changes in Windows 10 1709 Preview
Written by Anton Romanyuk
As Windows 10 Fall Creators Update development winds down, it’s the grandiose time to examine updated and new Group Policy settings. There is no official documentation from the Group Policy team at this point, frankly there still might (or will) be a few changes to Group Policy settings. Still, it can't hurt to poke around current ADMX files because there are truly several things duller in our line of work than comparing thousands lines of text. Right?
More...
Microsoft Cuts Features from Windows 10 Pro... Again
Written by Anton Romanyuk
I would never usually be as presumptuous as to suppose that I knew exactly what my thousands tens of readers wanted to hear me talk about this week, but this is clearly a special occasion. Only one thing has been on everyone's mind since Microsoft quietly updated the list of features that are being removed and/or deprecated in the Windows 10 1709 update, and only that thing would be expected to be the subject of an almost-weekly almost-amusing blog post.
Microsoft is Changing the Windows 10 Servicing Model ... Again
Written by Anton Romanyuk
I have an embarrassment of riches regarding what to talk about this week, but instead, and apologies in advance for sounding like a record stuck in a groove, I am going to talk about Windows as a Service.
More specifically, about the changes to the branches. Microsoft is moving Windows 10 to the same servicing as Windows Server which means that they are transitioning from the Current Branch (CB) and Current Branch for Business (CBB) model of Windows releases to a twice-yearly release cadence called the Semi-Annual Channel. The release cadence will align to Windows Server and Office which means you can expect the updates to arrive in in March and in September, each of which with an 18-month servicing timeline. The Creators Update marks the first of the Semi-Annual Channel releases. Additionally, Microsoft is renaming the Long Term Servicing Branch (LTSB) to the Long-Term Servicing Channel (LTSC).
Of late, several customers I work with started deploying Windows 10 clients using an English base image and applying language packs in the process. They ran into a little snag involving localizing UWP apps.