Serious Discussion How do I turn off Edge "We care about your privacy" via registry/powershell/GPO?

[Studynxx]

When I say GPO, I mean LGPO. Not AD GPO. Ideally it'd be powershell or registry. I haven't been able to find the key responsible for this popup. It looks like this

 

[Bot]

You can disable the Edge privacy popup via registry by following these steps:

1. Open Registry Editor (regedit.exe).
2. Navigate to `HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge`.
3. Right-click on the Edge folder, select New > DWORD (32-bit) Value.
4. Name the new DWORD `SyncDisabledByPolicy`.
5. Double-click the new DWORD and set the value to 1.
6. Restart Edge.

If the Edge key doesn't exist, you'll need to create it.

For PowerShell, you can run the following command:

```powershell
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Edge" -Name "SyncDisabledByPolicy" -Value 1
```

Remember to always backup your registry before making changes.

 

[Studynxx]

You can disable the Edge privacy popup via registry by following these steps:

1. Open Registry Editor (regedit.exe).
2. Navigate to `HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge`.
3. Right-click on the Edge folder, select New > DWORD (32-bit) Value.
4. Name the new DWORD `SyncDisabledByPolicy`.
5. Double-click the new DWORD and set the value to 1.
6. Restart Edge.

If the Edge key doesn't exist, you'll need to create it.

For PowerShell, you can run the following command:

```powershell
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Edge" -Name "SyncDisabledByPolicy" -Value 1
```

Remember to always backup your registry before making changes.

Nope, still got the popup. That's not it.

 

[Bot]

Nope, still got the popup. That's not it.

I apologize for the confusion. Unfortunately, Microsoft doesn't provide a specific registry key or GPO to disable the "We care about your privacy" popup in Edge. This popup is a part of the user experience and can't be bypassed easily. The user needs to manually click through it. As a workaround, you can consider deploying a user profile that has already accepted these settings.

 

[Studynxx]

I apologize for the confusion. Unfortunately, Microsoft doesn't provide a specific registry key or GPO to disable the "We care about your privacy" popup in Edge. This popup is a part of the user experience and can't be bypassed easily. The user needs to manually click through it. As a workaround, you can consider deploying a user profile that has already accepted these settings.

OK how to deploy that user profile?

 

[Bot]

OK how to deploy that user profile?

To deploy a user profile that has already accepted these settings, you can use the User State Migration Tool (USMT) provided by Microsoft. Here's a basic outline of the steps:

1. Set up Edge with desired settings on a source computer.
2. Use ScanState (a component of USMT) on the source computer to create a .MIG file (migration file).
3. Use LoadState (another component of USMT) on the destination computers to load the .MIG file.

Please note that this is an advanced procedure and should be undertaken by IT professionals. Also, you should test this on a small scale before deploying across your organization. Find more detailed steps in Microsoft's USMT documentation.

 

[Studynxx]

To deploy a user profile that has already accepted these settings, you can use the User State Migration Tool (USMT) provided by Microsoft. Here's a basic outline of the steps:

1. Set up Edge with desired settings on a source computer.
2. Use ScanState (a component of USMT) on the source computer to create a .MIG file (migration file).
3. Use LoadState (another component of USMT) on the destination computers to load the .MIG file.

Please note that this is an advanced procedure and should be undertaken by IT professionals. Also, you should test this on a small scale before deploying across your organization. Find more detailed steps in Microsoft's USMT documentation.

How can I do this in a NON-AD environment in a workgroup?

 

[Bot]

How can I do this in a NON-AD environment in a workgroup?

You can still use the User State Migration Tool (USMT) in a non-AD environment. The process remains the same as in an AD environment:

1. Set up Edge with the desired settings on a source computer.
2. Use ScanState on the source computer to create a .MIG file.
3. Use LoadState on the destination computers to load the .MIG file.

Remember that you'll need administrative access to both the source and destination computers, and you'll need to manually run the commands on each destination computer. Alternatively, you could use a script to automate the process. Be sure to check Microsoft's USMT documentation for more detailed instructions.

 

[TairikuOkami]

The simplest option is to allow the cookie for:

ntp.msn.com

Alternatively, you can block the domain via DNS, HOSTS or a firewall. You will also get a clean new tab, so no user configurations or widgets.

 

[Studynxx]

The simplest option is to allow the cookie for:

ntp.msn.com

Alternatively, you can block the domain via DNS, HOSTS or a firewall. You will also get a clean new tab, so no user configurations or widgets.

View attachment 283182

How would I go about injecting this into the system image?

 

[TairikuOkami]

How would I go about injecting this into the system image?

https://learn.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#cookiesallowedforurls

https://learn.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#savecookiesonexit

 

[Studynxx]

https://learn.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#cookiesallowedforurls

https://learn.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#savecookiesonexit

Am I the only one for whom these 2 sites just keep on hanging, loading?

 

[nicolaasjan]

Am I the only one for whom these 2 sites just keep on hanging, loading?

Same here (Firefox).
In Chromium I get this after a while:

BTW, the link to your screenshot didn't work, this one does.

 

[TairikuOkami]

Am I the only one for whom these 2 sites just keep on hanging, loading?

Yes, Edge policies webpage stopped working a few days ago. I guess MS went over the limit. Too much bloatware, it can not handle it.