Windows 10: ShareApp lets you control Windows 10 Privacy settings using PowerShell scripting files

SharpApp is a free portable tool that builds on the Windows PowerShell engine and script files. It can be effectively used to disable Windows 10 […]

This article ShareApp lets you control Windows 10 Privacy settings using PowerShell scripting files first appeared on TheWindowsClub.com.

read more...

 

Windows 10 Creators Update to Feature New Levels of Privacy Control

Just a tiny step closer before I'll upgrade to windows 10....

 

Windows 10 Creators Update to Feature New Levels of Privacy Control

Come'on. Even tho it offers a privacy setting, it's still not good enough.

There's a very good article on What data Windows 10 sends to Microsoft and how to stop it – HackMag what explains what your W10 OS is doing on the background and what type of data it is sending.

Making a privacy setting still submits the very basic tracking data to various servers, and no-one actually knows what is happening with that.

Windows 7 never had any privacy killing features aboard, untill they pushed an update to even computers with automatic updated turned off, offering the same type of stuff.

People need to be aware that this is just a 'small' step into a future where privacy is just no more. This privacy will be gone the more the masses keep signing up to services in exchange for their data. W10, Google, Facebook, they are all a perfectly good example of company's who became too big.

Remove telemetry updates for Windows 7 and 8.1

Some good stuff.

 

Powershell Scripts in the Windows 10 OS and script execution policy of "Allow only Signed scripts"

We have the group policy " Turn on Script execution" enabled and set to "Allow only Signed scripts".

Will this affect the powershell scripts used in the Windows 10 operating System or does windows have something inbuilt that overrides the settings we apply. I'm thinking that it would block even the W10 built in scripts.

An example of what I am talking about are the 246 .ps1 files in the various diagnostic directories in c:\windows\diagnostics\system\ . our diags never come back with issues even when deliberately disabling components before running.

other areas that Powershell scripts live that I have found with a quick search -

C:\Windows\WinSxS\wow64_microsoft.powershell.odatautils_31bf3856ad364e35_10.0.17763.1_none_d60dcab1d9234fab

C:\Program Files (x86)\WindowsPowerShell\Modules\Microsoft.PowerShell.Operation.Validation\1.0.1\Diagnostics\Comprehensive

C:\Program Files\WindowsPowerShell\Modules - various folders in here.

Do we need to sign all powershell scripts that come with the OS?

Does Microsoft have a method of doing this?

Is there a list of script files that come with the OS so we don't just do a sign all approach, then find we have signed malware files.

we could probably configure something in the build task sequence to sign what is there initially. Is there any plan in place for Microsoft to start signing their scripts?

Will this be an ongoing process as updates are applied and files replaced, do we need to have a process in place to sign all PS1 files in the OS?