There is an official way from Microsoft though.
https://support.microsoft.com/en-us/kb/3080351
German computer magazine c't has a small .reg file as a download setting described keys.
http://www.heise.de/ct/downloads/04/1/7/1/6/6 … 6/3/NoWin10.zip

Solarstorm wrote:

There is an official way from Microsoft though. https://support.microsoft.com/en-us/kb/3080351 German computer magazine c't has […]
Show full quote

There is an official way from Microsoft though.
https://support.microsoft.com/en-us/kb/3080351
German computer magazine c't has a small .reg file as a download setting described keys.
http://www.heise.de/ct/downloads/04/1/7/1/6/6 … 6/3/NoWin10.zip

The group policy thing does not always work for me and the Reg key is nice and all, but not everyone wants to use 3'd party stuff, A lot of workplaces have rules on stuff like that.
I know there are a lot of better options out there, but as far as I know this is the best one without using any third party apps, scrips and keys.

I just follow Microsoft's guide. No problems.

Jade Falcon wrote:

not everyone wants to use 3'd party stuff, A lot of workplaces have rules on stuff like that.

Any workplace restricting such things most likely does not allow users to be taking ownership of system folders, if they even allow access to those folders.

Solarstorm wrote:

There is an official way from Microsoft though. https://support.microsoft.com/en-us/kb/3080351 German computer magazine c't has […]
Show full quote

There is an official way from Microsoft though.
https://support.microsoft.com/en-us/kb/3080351
German computer magazine c't has a small .reg file as a download setting described keys.
http://www.heise.de/ct/downloads/04/1/7/1/6/6 … 6/3/NoWin10.zip

^^^^
This

In the guide, below "Computer configuration" there is a section called "Windows registry" which states to disable the same key that is stated in the .reg file download.

Scroll down to "Hide the Get Windows 10 app (notification area icon)", and it states to set the value "HKLM\Software\Policies\Microsoft\Windows\Gwx DisableGwx = 1", which again is the same key as stated in the .reg file. Do what MS state, if you delete the key, some MS bot might think your OS platform hasn't been notifiied about the update and put these keys back in at some point in the future anyway. Rather, set them to disabled.

Both sources state the same key, just different ways to do it with the same outcome. So I would trust the .reg file (its not entirely 3'rd party, more like a script interpreted to change the reg key values).

Doing anything else might place you outside any support should the shtf, and could be considered 3rd party by MS.

I worked in several IT departments and not being allowed to install/use unimproved software is pretty common, but being allowed to change file permission and access to system files on workstations is pretty common, it's servers and mission critical system that tend to be more restive. Anyway I find M$ guide to be dodgy at best.
I applied it to a lot of pc's only to find gwx coming back.

I'd rather trust documented group policy / registry keys, than mess with permissions of files in the Windows system directory. I got burned in the past when I screwed something up and the system could not get access to its own files, causing erratic behavior. And I am sure I am not the only one.

collector wrote:

Jade Falcon wrote:

not everyone wants to use 3'd party stuff, A lot of workplaces have rules on stuff like that.

Any workplace restricting such things most likely does not allow users to be taking ownership of system folders, if they even allow access to those folders.

^^^^
This then...

If your authorisation doesn't allow you to install programs then your have little say in stopping a windows 10 installation, this will be governed by admin which will walkover any credentials/attributes you set on a dir to stop files being copied into it.

Either you become god and stop the evil penetrating your machine..(one must become admin)

or

Your fighting god, and my money is on a smite! (you are a user, in admins playground)

In summary, its a nice idea, but won't work because there are powers at play here (admin) who you cannot compete with. 😀

Jade Falcon wrote:

I worked in several IT departments and not being allowed to install/use unimproved software is pretty common, but being allowed to change file permission and access to system files on workstations is pretty common, it's servers and mission critical system that tend to be more restive. Anyway I find M$ guide to be dodgy at best.
I applied it to a lot of pc's only to find gwx coming back.

Changing file permissions on system files requires local administrator rights. Those two combined and you can override mostly any management.

I think you are giving your previous workplaces too much credit by calling them IT departments.

ZellSF wrote:

I think you are giving your previous workplaces too much credit by calling them IT departments.

I worked in the IT departments so I had admin right. I seen/worked for plenty of places were one has to have and software ok'd by marketing, security and even a board. But changing permissions tend kept within the IT department and maybe security.

Right now at the place I work for I head up the IT department, but any non free software has to be OK'd by marketing, and free solftware has to be ok'd by the IT department as a hole and the head of marketing if it not used to fix computers or only used on IT staff computers only. If you work in any company that has outdated policys or policy writen up by old school folks you can bet it will be like that.

^^^
What a load of bull. Seriously.

Jade Falcon wrote:

Right now at the place I work for I head up the IT department, but any non free software has to be OK'd by marketing, and free solftware has to be ok'd by the IT department as a hole and the head of marketing if it not used to fix computers or only used on IT staff computers only.

Seems like a simple registry change would fall under the auspices of "to fix computers".

If you "head up the IT department", then you should be implementing tools like SCCM, WSUS and GPO's to make these sorts of changed. If you're running from machine to machine doing these sorts of things, you're doing it wrong!!

Got to try these things out for my Windows 7 VM. I need it for testing and I need it to remain Windows 7 😉

Interesting way to fix this, made a screen shot as this thread is likely to go down the memory hole. :s

All never10 does is change those 2 registry settings in the Microsoft document. And will optionally delete the win10 bits that were downloaded without your permission. It's an 80kb non-installing exe from a trusted source. It's all I use on non domain joined PCs.

Jade Falcon wrote:

ZellSF wrote:

I think you are giving your previous workplaces too much credit by calling them IT departments.

I worked in the IT departments so I had admin right. I seen/worked for plenty of places were one has to have and software ok'd by marketing, security and even a board. But changing permissions tend kept within the IT department and maybe security.

File permissions is what allows you to run software, or limit user access to anything. If you're not limiting file permissions on system files, you're basically just asking users nicely to go along with your idea of limiting software.

Asking nicely and monitoring people is not the way to manage computers. Actually enforcing proper policies is. If you work in a place with a marketing department, security department and that answers to a board that sounds like a huge enough corporation that you need to be thinking scaleability.