Cumulative Update KB4512941 Windows 10 v1903 build 18362.329 - Aug. 30 Win Update

maurice naggar · 08 Sep 2019

@CountMike You mention you disabled Cortana.
What adjustment did you make , & where & how ( I mean did you follow some article ? or did you use built-in options in Windows Settings ? or just some manual Regedit ?
I'm just curious.

CountMike · 08 Sep 2019

maurice naggar said:

@CountMike You mention you disabled Cortana.
What adjustment did you make , & where & how ( I mean did you follow some article ? or did you use built-in options in Windows Settings ? or just some manual Regedit ?
I'm just curious.

Cumulative Update KB4512941 Windows 10 v1903 build 18362.329 - Aug. 30-image.png

There's also this way How to Disable Cortana in Windows 10 but I found it later.

Ztruker · 08 Sep 2019

Count. that is hardly a "legal" way. It's still using a 3rd party app to manipulate OS internals

Cleaner than manually hacking the registry I'll admit.

Brink · 08 Sep 2019

CountMike said:

There's also this way How to Disable Cortana in Windows 10 but I found it later.

In addition:

Enable or Disable Cortana in Windows 10

Try3 · 08 Sep 2019

Ztruker said:

Count. that is hardly a "legal" way. It's still using a 3rd party app to manipulate OS internals

Cleaner than manually hacking the registry I'll admit.

Rich,

I applaude your assertion of the rights of MS in respect of Windows 10 licence terms 2c(iv) & 2c(vi). It is extremely commendable.
- However, neither of these restrictions is in any way more breached or less breached if third-party utilities have been involved.
- The breach is in the work around not in the tool used to achieve it. Arguably, the breach was initially in the reverse engineering that was conducted in order to figure out what work around was required.
- No definition of allowable work arounds has been produced by MS [but many of us commonly assume a right to alter Windows' Registry].
- If it ever came to the point of damages claims by MS, a plausible defence might well be that, since MS has inserted into the Registry warnings that altering specific Registry keys is a breach of licence terms, altering other Registry keys is not a breach.
- Isn't life fun.

Denis

kado897 · 08 Sep 2019

Try3 said:

Rich,

I applaude your assertion of the rights of MS in respect of Windows 10 licence terms 2c(iv) & 2c(vi). It is extremely commendable.
- However, neither of these restrictions is in any way more breached or less breached if third-party utilities have been involved.
- The breach is in the work around not in the tool used to achieve it. Arguably, the breach was initially in the reverse engineering that was conducted in order to figure out what work around was required.
- No definition of allowable work arounds has been produced by MS [but many of us commonly assume a right to do precisely that].
- If it ever came to the point of damages claims by MS, a plausible defence might well be that, since MS has inserted into the Registry warnings that altering specific Registry keys is a breach of licence terms, altering other Registry keys is not a breach.
- Isn't life fun.

Denis

And in this case it is emulating what Group Policy does for those not fortunate enough to have it.

Mutoidi · 08 Sep 2019

kado897 said:

And in this case it is emulating what Group Policy does for those not fortunate enough to have it.

Win 10 'Home' user says: "Nicely Put!"

maurice naggar · 08 Sep 2019

Just some general new remarks. I have not used winaero or shutup10 or any other tweak-adjustment mentioned here.
Doing fine thank you. I have only used the Privacy options in Windows 10 Settings.

My registry does not have entries to block or disable Cortana.
It does not have [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Search]
"AllowCortana"=dword:00000000

That sub-key does not ship with the O S

It does have "CanCortanaBeEnabled"=dword:00000001

H T H

jimbo45 · 08 Sep 2019

Try3 said:

Rich,

I applaude your assertion of the rights of MS in respect of Windows 10 licence terms 2c(iv) & 2c(vi). It is extremely commendable.
- However, neither of these restrictions is in any way more breached or less breached if third-party utilities have been involved.
- The breach is in the work around not in the tool used to achieve it. Arguably, the breach was initially in the reverse engineering that was conducted in order to figure out what work around was required.
- No definition of allowable work arounds has been produced by MS [but many of us commonly assume a right to alter Windows' Registry].
- If it ever came to the point of damages claims by MS, a plausible defence might well be that, since MS has inserted into the Registry warnings that altering specific Registry keys is a breach of licence terms, altering other Registry keys is not a breach.
- Isn't life fun.

Denis

Hi folks

without getting into theoretical legal posturizing - or Court test cases - one has to ask the question that if the registry was really the province of Ms then why would they supply simple tools for anybody to view the contents and change them easily --regedit is hardly the most difficult tool to use either.

I'm sure anybody testing this stuff in almost any Court in most parts of the world where decent legislation, proper business contracts and free elections are available would throw this type of case straight out back on to the street. !!

Cheers
jimbo

Try3 · 08 Sep 2019

I agree.

Denis