Skip to main content

 How to block Running  windows network diagnostics in Microsoft Edge Browser


disable 2 windows service as below.



then also do the below registry key.


To disable running Windows Network Diagnostics in Microsoft Edge browser using the registry, you can follow these steps:

  1. Open Registry Editor: Press Win + R, type regedit, and hit Enter.
  2. Navigate to the Microsoft Edge Registry Key: Go to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge If the Edge key doesn't exist, you may need to create it.
  3. Create a New DWORD Value: Right-click on an empty space in the right pane, select "New" > "DWORD (32-bit) Value".
  4. Name the DWORD: Name it as AllowNetworkDiagnostics.
  5. Set the Value: Double-click on AllowNetworkDiagnostics and set its value to 0 to disable Windows Network Diagnostics.
  6. Close Registry Editor: After making the changes, close the Registry Editor.

Once you've done this, Windows Network Diagnostics should be disabled in Microsoft Edge browser. If you ever want to enable it again, you can either delete the AllowNetworkDiagnostics DWORD or set its value to 1 or delete the AllowNetworkDiagnostics entry, depending on your preference. Remember to always be cautious when making changes to the registry, as incorrect changes can cause system issues.

Comments

Post a Comment

Popular posts from this blog

ESM Log size is full - How to clear

                                            ESM log Size is full ---- How to Clear If your getting the below error in event viewer you can follow the below steps and solve it. Generally when we open Dell open manage console, suddenly we see that Hardware log status is showing critical and event logs are filling saying ESM log is full... We need to clear the ESM logs regularly before it reaches 100%. However please follow the below command and procedure before clearing the logs. Open Dell Manage console, go to logs tab. Then select ESM logs, you will see an export option. Export the logs and save it on local drive for future use. Now open command prompt and Runas administrator. Type omconfig system esmlog action=clear Done, ...
Post a Comment
Read more
  PowerShell DSC log amount issue on operating system drive Overview Problem Impact Microsoft Ticket (Workaround) solution References Overview When using PowerShell DSC on a configured system in some (seldom) cases it can lead to log amount issues in a specific folder. The following folder grows (over time) so several GB size holding hundreds and thousands of JSON log files as visible in the following screenshot: Also sometimes it looks like this: Problem The problem is (but must not be) related to DSC configuration issues as far as it could be analyzed. The log folder „Configuration Status“ is filled with sometimes up to 7 Megabyte sized JSON files. This log folder (based on our analysis) is used for sending reports to report server but is not cleaned up automatically. Impact Some PowerShell DSC managed systems need extensive disk space due to log directory grown to 40 Gigabyte plus. This causes an alert in disk space / availability monitoring and could in some cases lead to non w...
Post a Comment
Read more

Vm backup failling with snapshot error (156)An error occurred while saving the snapshot: Failed to quiesce the virtual machine.

  Hi Everyone, I am here back with another issue. If anyone is getting error taking backup snapshot of a virtual machine and getting the below error. Vm backup failling with snapshot error (156)An error occurred while saving the snapshot: Failed to quiesce the virtual machine. Apr 28, 2021 2:22:55 AM - Critical bpbrm (pid=15849) from client XXXXX: FTL - vSphere_freeze: Snapshot task for virtual machine XXX-YYY (/vmmor/vm-341) failed, 0 retries remaining, error type: 263, error message: An error occurred while saving the snapshot: Failed to quiesce the virtual machine.. Apr 28, 2021 2:23:08 AM - Critical bpbrm (pid=15849) from client XXXX: FTL - vfm_freeze: method: VMware_v2, type: FIM, function:...
Post a Comment
Read more