Send data when on connected to a restricted/costed network

This policy setting determines whether Windows Error Reporting (WER) checks for a network cost policy that restricts the amount of data that is sent over the network. If you enable this policy setting WER does not check for network cost policy restrictions and transmits data even if network cost is restricted. If you disable or do not configure this policy setting WER does not send data but will check the network cost policy again if the network profile is changed.

Send data when on connected to a restricted/costed network

This policy setting determines whether Windows Error Reporting (WER) checks for a network cost policy that restricts the amount of data that is sent over the network. If you enable this policy setting WER does not check for network cost policy restrictions and transmits data even if network cost is restricted. If you disable or do not configure this policy setting WER does not send data but will check the network cost policy again if the network profile is changed.

Send additional data when on battery power

This policy setting determines whether Windows Error Reporting (WER) checks if the computer is running on battery power. By default when a computer is running on battery power WER only checks for solutions but does not upload additional report data until the computer is connected to a more permanent power source. If you enable this policy setting WER does not determine whether the computer is running on battery power but checks for solutions and uploads report data normally. If you disable or do not configure this policy setting WER checks for solutions while a computer is running on battery power but does not upload report data until the computer is connected to a more permanent power source.

Send additional data when on battery power

This policy setting determines whether Windows Error Reporting (WER) checks if the computer is running on battery power. By default when a computer is running on battery power WER only checks for solutions but does not upload additional report data until the computer is connected to a more permanent power source. If you enable this policy setting WER does not determine whether the computer is running on battery power but checks for solutions and uploads report data normally. If you disable or do not configure this policy setting WER checks for solutions while a computer is running on battery power but does not upload report data until the computer is connected to a more permanent power source.

Turn off tracking of app usage

This policy setting prevents Windows from keeping track of the apps that are used and searched most frequently. If you enable this policy setting apps will be sorted alphabetically in: – search results – the Search and Share panes – the drop-down app list in the Picker If you disable or don’t configure this policy setting Windows will keep track of the apps that are used and searched most frequently. Most frequently used apps will appear at the top.

Boot-Start Driver Initialization Policy

This policy setting allows you to specify which boot-start drivers are initialized based on a classification determined by an Early Launch Antimalware boot-start driver. The Early Launch Antimalware boot-start driver can return the following classifications for each boot-start driver:- Good: The driver has been signed and has not been tampered with. – Bad: The driver has been identified as malware. It is recommended that you do not allow known bad drivers to be initialized. – Bad but required for boot: The driver has been identified as malware but the computer cannot successfully boot without loading this driver. – Unknown: This driver has not been attested to by your malware detection application and has not been classified by the Early Launch Antimalware boot-start driver. If you enable this policy setting you will be able to choose which boot-start drivers to initialize the next time the computer is started. If you disable or do not configure this policy setting the boot start drivers determined to be Good Unknown or Bad but Boot Critical are initialized and the initialization of drivers determined to be Bad is skipped. If your malware detection application does not include an Early Launch Antimalware boot-start driver or if your Early Launch Antimalware boot-start driver has been disabled this setting has no effect and all boot-start drivers are initialized.