Windows 10: Windows 10 PRO - can it still kill Cortana via GPEdit.msc ?

After the WIn10 Creator's edition, can you still permanently kill Cortana via GPEdit ?

(I know on Win10 Home its extremely hard to get rid of Cortana.)

:)

 

turning off Cortana

If you have Windows 10 Pro you can go into Group Policy and disable it there.

Press Win+R and enter gpedit.msc and navigate to Computer Configuration/Administrative Components/Search, and there you can disable Allow Cortana.

 

If I can't stop Cortana then can I make it launch Fire Fox

If you have Windows 10 Pro or above you can use gpedit.msc to disable Cortana. Navigate to Computer Configuration/Administrative Templates/Windows Components/Search and there disable Allow Cortana.

Have a look at Options/Search for Firefox. There you can specify your default search engine and specify that Windows is to use this search engine for its searches.

 

Hello Bansaw, *Smile

Yes, you can still disable Cortana if you like.

*Arrow Enable or Disable Cortana in Windows 10 Windows 10 Apps Features Tutorials

 

I've got Win10 Pro so I used GPEdit to disable her in the policies, but Cortana is still in the background processes.
When I had Wiin10 HOme, I would physically rename the SearchUI folder in the WIndows dir. But that had its drawbacks.
Now I have Win10 Pro Creators.

Is there a 3rd party app that totally shuts Cortana down and limits telemetry? Wahts the best way of terminating Cortana these days?
(I know with major updates she comes back.. : ( )

 

The tutorial I posted above will only disable Cortana the personal assistant, and not the Cortana process (SearchUI.exe) used by Windows Search.

Windows Search is not the same as Cortana despite it sharing the same process name.

 

When I say Cortana, I mean "Microsofts spy on my computer sending stuff back to headquarters". How would I know for sure if the Cortana still appearing in background tasks is not sending info back to MS?
I wonder if there is a firewall or network monitor out there that can tell me?...........

 

Or get a reality check and stop being paranoid.

 

Run a Non-Insider Build and turn everything off in Settings.