News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon

Blog Archives

  • Where we stand with the Cortana/Search redlining bug

    Posted on September 4th, 2019 at 06:05 woody Comment on the AskWoody Lounge

    We’re stuck between a rock and a very hard place.

    On the one hand, if you’re running Win10 1903 — you may have been pushed — you really need to get the first August cumulative update installed to guard against DejaBlue (which hasn’t been exploited yet).

    On the other hand, there are so many bugs in the first August cumulative update (VB/VBA/VBScript, Windows Sandbox, PXE, MIT Kerberos) that you really should get the second August cumulative update.

    On the third hand, if you install the second August cumulative update, your machine may start redlining.

    Tell me again how Win10 1903 is ready for prime time?

    Computerworld Woody on Windows.

  • Microsoft STILL hasn’t acknowledged the bugs in last Friday’s Win10 1903 cumulative update

    Posted on September 3rd, 2019 at 13:54 woody Comment on the AskWoody Lounge

    Last Friday, Microsoft released KB 4512941, the long-anticipated second August cumulative update for Win10 version 1903.

    Within a few hours, people were complaining on various online forums that installing the update immediately triggered excessive CPU use. I wrote about that on Friday night.

    Since then, explanations and workarounds have appeared all over the place. @EP came up with this list:

    https://news.softpedia.com/news/windows-10-cumulative-update-kb4512941-causing-high-cpu-usage-527226.shtml

    https://www.neowin.net/news/some-windows-10-users-on-1903-are-facing-high-cpu-usage-after-latest-cumulative-updates

    https://www.zdnet.com/article/windows-10-cpu-spikes-1903-update-brings-fixes-but-also-high-usage-issues/

    https://www.bleepingcomputer.com/news/microsoft/windows-10-kb4512941-update-causing-high-cpu-usage-in-cortana/

    one workaround to the problem posted on Softpedia news:
    https://news.softpedia.com/news/how-to-fix-high-cpu-usage-caused-by-windows-10-cumulative-update-kb4512941-527235.shtml

    Günter Born has had two — not one, but two — explainers with detailed analyses. Ends up that making certain registry changes can get the CPU utilization back to normal.

    Most damning, Mayank Parnmar at Windows Latest reported on Saturday:

    It’s important to note that Microsoft actually tested KB4512941 with Windows Insiders in the Release Preview Ring for more than a week before shipping the update to the general public.

    According to some posts on Feedback Hub, reports of high CPU usage were submitted multiple times by testers earlier this week, but the reports appear to have been ignored because they weren’t upvoted enough.

    So now it’s Tuesday, four days after the offal hit the fan… and Microsoft hasn’t said one thing about it.

    Even now, the KB article says:

    Known issues in this update

    Microsoft is not currently aware of any issues with this update.

    And the Release Information Status page says absolutely nothing.

    UPDATE: As I was writing this, MS posted on Twitter (thx, MJF)

  • Cortana isn’t exactly going away, but…

    Posted on July 25th, 2019 at 10:15 woody Comment on the AskWoody Lounge

    Good overview of Cortana’s long-anticipated demise by Tom Warren, over at The Verge.

    Microsoft is now refocusing Cortana and stripping back its direct integration in Windows 10 and the Xbox One. Microsoft has a new vision for Cortana, involving conversational interactions for workers who are organizing their days.

    Don’t know about you, but I’m quite happy with the way my working days are organized. Which is to say, hectically.

    I use Alexa and OK Google all the time, and Siri occasionally. I never understood why anyone would want Cortana. Perhaps “she” will find peace in her new home.

  • Gralla: Will Cortana go the way of Windows Phone?

    Posted on November 23rd, 2018 at 07:20 woody Comment on the AskWoody Lounge

    Signs sure point in that direction.

    [Microsoft has] finally shed the arrogance of believing it can win every fight by spending billions of dollars and using Windows as a battering ram.

    I, for one, won’t miss her.

    Great article by Preston Gralla.

  • Say what? Microsoft moves the Cortana org to sit under Office?

    Posted on October 11th, 2018 at 12:37 woody Comment on the AskWoody Lounge

    Wow. How the mighty have fallen.

    Cortana under Office changes all sorts of things.

    Brad Sams on Petri.

  • Alexa and Cortana talking to each other….

    Posted on August 30th, 2017 at 07:32 woody Comment on the AskWoody Lounge

    … and why I don’t care.

    Here’s an overview from Paul Thurrott, if you’re interested.

    Microsoft’s sales pitch:

    Cortana users will be able to have Alexa shop on Amazon.com and manage their Amazon orders and access many of Alexa’s third-party skills by asking Cortana to open Alexa, just as Alexa users will have access to Cortana’s world knowledge and helpful productivity features such as calendar management, day at a glance and location-based reminders simply by asking Alexa to open Cortana.

    I can envision some people, in some situations, wanting to use Cortana to get to Alexa. In very rare instances I can see using Alexa to get to Cortana. But for most people most of the time – and certainly for me – it’s a big meh.

    Cortana’s “world knowledge” doesn’t hold a candle to Google’s, as any seven-year-old can attest. As for calendar and location-based anything, Google’s way out ahead on those fronts, too.

    Microsoft’s losing the Augmented Reality wars. They’re losing the voice assistant wars. Personally, I use Alexa for home stuff and Google Assistant for everything else that’s voice-friendly. It works. And I don’t have to wait for 20-minute blackouts while my PC updates itself, or bob and weave through mediocre updates.

    Downright distressing for somebody who’s been with Windows since version 286.

    UPDATE: Great article from John Brandon in Computerworld:

    Cortana and Alexa can talk to each other, but it isn’t really a conversation or integration — simply a way for one bot to open the other. Yawn.

  • Does “killing” Cortana really kill Cortana?

    Posted on December 19th, 2016 at 20:25 woody Comment on the AskWoody Lounge

    PKCano has been conducting some interesting experiments. Here are her results to date:

    PRE-TEST #1: I did what appeared to be a clean install. Since we are interested in disabling Cortana, I decided to do whatever the UI had to offer in that direction: Custom install turning off all the offered settings and choosing “Not now” at the “Meet Cortana” screen. Parallels Tools installed on the reboot. This gave me Build 14393.0. Cortana was not off by default as when I initially upgraded from 1511 back at the beginning of Aug.

    Cortana “O” appeared by default in the search box.

    cortana-01

    Cortana did not present a choice to use or not use in the search box popup menu. The notebook was present.

    cortana-02

    There were many choices in the search box settings menu.

    cortana-03

    cortana-04

    Cortana was a choice in the taskbar context menu.

    cortana-05

    There were two entries in the Task Manager that showed activity when I typed, “Cortana” and “Cortana Background Task Host.” DWORDs “BingSearchEnabled” and “CanCortanaBeEnabled” were NOT present under HKCU\Software\Microsoft\Windows\CurrentVersion\Search. DWORD “AllowCortana” was NOT present under HKLM\Software\Microsoft\Windows Search. The keys “Windows Search” and “Search” were NOT present under HKLM\Software\Policies\Microsoft\Windows.

    cortana-06

    PRE-TEST #2: Cumulative Update KB3176495 –> Build 14393.51. Things basically looked the same, maybe a couple more options in the search box popup menu.

    Registry settings were the same.

    cortana-07

    cortana-08

    GPedit: Local Computer Policy\Computer Configuration\Administrative templets\Windows Components\Search had two settings “Allow Cortana” and “Allow Cortana above lock screen,” both not configured. This is same as before

    cortana-09

    Now for the testing.

     

    TEST #1: GPedit: Local Computer Policy\Computer Configuration\Administrative templates\Windows Components\Search

    I set two settings “Allow Cortana” and “Allow Cortana above lock screen” to “disabled”. Rebooted.

    Cortana “o” disappeared from the search box.

    cortana-10

    The Cortana option disappears from the taskbar context menu.

    cortana-11

    Cortana disappeared from the search box popup menu.

    Search box settings are greatly reduced.

    cortana-12

    I still have two Cortana entries in the Task Manager but I believe only the “Cortana” one is active when I type, not the “Cortana Background Task Host.”

    cortana-13

    In GPedit I returned the settings to “Not configured.” See this thread:

    https://www.askwoody.com/2016/win10-anniversary-update-bug-turns-into-turn-off-cortana-feature/

     

    TEST #2: Remember, the two DWORDs “BingSearchEnabled” and “CanCortanaBeEnabled” under HKCU are not present in this install.

    Under HKLM\Software\Policies\Microsoft\Windows I created the key “Windows Search” (NOTE there is a space between) and the DWORD “AllowCortana” set to 0. Rebooted.

    The Cortana “O” disappeared from the search box.

    cortana-14

    Cortana disappeared from the taskbar context menu.

    cortana-15

    Cortana disappeared from the search box popup menu.

    The search box settings are reduced to 2.

    cortana-16

    There is Cortana activity in Task Manager.

    cortana-17

    In each case, I am resetting whatever I changed before so I start from scratch.

    Recall that previously (see link to thread above) the key “Windows Search” under HKLM did not initially exist – I had to create it and the DWORD “AllowCortana”.

    Test #3: Under HKCU\Software\Microsoft\Windows\CurrentVersion\Search the two DWORDs “BingSearchEnabled” and “CanCortanaBeEnabled” were not present in this install. But when Cortana disappeared in the TP and in the early AU, those two DWORDs were present and the DWORD “BingSearchEnabled” was set to 0.

    This time, I had to create those two DWORDs and I set both to 0. Rebooted.

    The Cortana “O” disappeared from the search box.

    cortana-18

    Cortana disappeared from the taskbar context menu.

    cortana-19

    Cortana disappears from the search box popup.

    Search box settings are reduced.

    cortana-20

    There is STILL activity under Cortana in the Task Manager.

    cortana-21

    CONCLUSIONS:

    1. It was the settings under HKCU that caused Cortana to disappear in theTP and the AU initial releases. The other things were not present in those builds, but “BingSearchEnabled” was set to 0 under HKCU.

    1. Enabling the “AllowCortana” in GPedit creates the “Windows Search” key under HKLM and sets the “AllowCortana” DWORD to 1. So basically these two things are equivalent.

    1.  Setting “BingSearchEnabled” (and maybe “CanCortanaBeEnabled”) to 0 underHKCU does the same thing. This may apply the disappearance of Cortana to an individual User as opposed to the entire computer which the GPedit settings probably do.

    1. None of these changes stop the activity of the Cortana processes in Task Manager.

    Want to REALLY squash Cortana?

    Open the Task Manager.

    Open C:\Windows\SystemApps

    Rename the folder “Microsoft.Windows.Cortana_cw5n1h2txyewy.”

    You have to stop the Cortana process in the Task Manager, b/c it’s using the folder.

    You have to be FAST FAST b/c the process restarts quickly.

    Reboot.

    The Cortana “O” still shows in the search box, but the search box is DEAD – you can’t type anything in it.

    Cortana still shows in the taskbar context menu, but the Cortana icon is also DEAD.

    Install Classic Shell and type in the search box. You get a “Microsoft Windows Search Indexer” process that shows activity.

    Don’t know what other effects this might have, but it does the job of killing the Cortana processes and removing them from the Task Manager apparently.

    cortana-22

     

    cortana-23

     

    cortana-24

    cortana-25

  • Dissecting the Cortana numbers

    Posted on December 14th, 2016 at 12:16 woody Comment on the AskWoody Lounge

    Brad Sams has a great back-of-the-envelope analysis of Cortana’s penetration, on Thurrott.com (premium content). He drew on some obscure references ferreted out by @teroalhonen.

    Microsoft claims 145 million monthly active users. Brad takes the number apart, and shows – quite convincingly – that there’s less here than meets the eye. Just for starters, if you type into the Win10 Search box, bingo, there’s another hit for Cortana.

    Another excellent article from Thurrott Premium.