Tuesday, 12 December 2017 10:04

Disabling Cortana Voice Support during OOBE

Written by
Rate this item
(10 votes)

image

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.

Unattended installations make it easy to keep Cortana quiet. Simply add following registry tweak to Unattend.xml right before the tag </RunSynchronous>:

<RunSynchronousCommand wcm:action="add">
<Description>disable driver update</Description>
<Order>5</Order>
<Path>reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v DisableVoice /d 1 /t REG_DWORD /f</Path>
</RunSynchronousCommand>

Note: You may need to adjust <Order>5</Order> value to match your unattend.xml

Sounds simple enough. However, Johan Arwidmark mentioned on Twitter a cooler way of setting the registry value. Personally, I like his approach better because - at least when applied to Microsoft Deployment Toolkit - it saves me the necessity to apply changes to each unattend.xml in my deployment shares. Grab his script from GitHub and add it to your Post-Install phase:

image

Be aware that according to Microsoft documentation shipping a device with Cortana voice support disabled is an unsupported configuration. From my point of view, this bit applies only to OEMs. However, should you wish to restore the default behavior, add a PowerShell script towards the end of your task sequence. Something along these lines should do the trick:

Remove-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE" -Name "DisableVoice" -Force

To wrap this up, I noticed, that there is still a rumor floating around that you can use SkipMachineOOBE to bypass Windows Welcome. To put it in the simplest terms:

Stop using SkipMachineOOBE. Stop using SkipMachineOOBE. STOP USING SkipMachineOOBE!

This setting has been deprecated in Windows 8 and needs to hit the landfill. You should never ever ship a computer with the SkipMachineOOBE setting configured to true. Some Windows features may not function, as they depend on Windows Welcome values such as ProtectYourPC, which does not include a default value.

Read 30812 times Last modified on Tuesday, 12 December 2017 10:48

Recent Posts

  • Windows 10 21H2 Built-In Apps: What to Keep
    The development of the Windows 10, version 21H2 is finished and the update will soon be available for download from…
    Written on Wednesday, 20 October 2021 11:41
  • Group Policy Changes in Windows 10 21H2
    As Windows 10, version 21H2 update development winds down, Microsoft is now preparing for the final release of the Windows…
    Written on Wednesday, 20 October 2021 07:20
  • Group Policy Changes in Windows 10 20H1 Preview
    As Windows 10 Vibranium Update (20H1) development winds down, Microsoft is now beginning the phase of checking in the final…
    Written on Tuesday, 14 January 2020 04:51
  • An alternative ESU MAK Activation Solution
    This blog post was shared with me by a colleague of mine, Daniel Dorner, a Microsoft Premier Field Engineer. It’s…
    Written on Wednesday, 04 December 2019 21:04
  • The Case of Missing UE-V Templates
    My customers often deal with unexpected Windows behavior and this case is no different. This particular one is especially interesting…
    Written on Tuesday, 03 September 2019 12:20
  • The Case of Changing Default Printer
    While I sometimes long for the day when I no longer have to deal with unexpected Windows 10 behavior, there’s…
    Written on Wednesday, 14 August 2019 20:36