Windows problem reporting журнал

***

Что такое Windows Error Reporting 

Когда в возникают проблемы с оборудованием или программами (например, аппаратное или программное перестаёт работать или работает некорректно), Windows создает отчёт о проблеме, который предназначен для отправки в Microsoft (чтобы отыскать решение проблемы).

Начиная с операционной системы , на смену «инструменту анализа сбоев или аварий» Dr. Watson пришла Windows Error Reporting (WER) – Служба регистрации ошибок Windows (другие названия – Отчеты о проблемах и их решениях, Отчеты о проблемах и решения).

Служба регистрации ошибок Windows представлена следующими файлами (все расположены в каталоге \Windows\System32\):

– wer.dll (Библиотека сообщений об ошибках Windows);

– wercon.exe (Отчеты о проблемах и их решениях);

– wercplsupport.dll (Отчеты о проблемах и их решениях);

– werdiagcontroller.dll (WER Diagnostic Controller);

– WerFault.exe (Отчет об ошибках Windows);

– WerFaultSecure.exe (Отчеты об ошибках Windows);

– wermgr.exe (Windows Problem Reporting);

– wersvc.dll (Служба регистрации ошибок Windows);

– wertargets.wtl.

Когда происходит сбой какого-либо процесса (программы), служба Windows Error Reporting запускает – в сеансе ошибочного процесса – свою (WerFault.exe),

передавая идентификатор (PID) процесса в командную строку WerFault:

При этом отображается окно Microsoft Windows с сообщением об ошибке – «Прекращена работа <Название_программы>. При следующем подключении к Интернету Windows может провести поиск способа устранения этой ошибки»:

При нажатии на кнопку Показать подробности проблемы можно ознакомиться с сигнатурой проблемы:

Сигнатуры проблем сохраняются в отчётах об ошибках, которые хранятся в каталоге \Users\Master\AppData\Local\Microsoft\Windows\WER\ReportArchive\, каждый отчет – в отдельной папке Report******** (например, Report0a003e48), в файле Report.wer.

Примерное содержимое файла Report.wer:

Version=1

EventType=APPCRASH

EventTime=129234418886148269

ReportType=2

Consent=1

Response.type=4

Sig[0].Name=Имя приложения

Sig[0].Value=iexplore.exe

Sig[1].Name=Версия приложения

Sig[1].Value=8.0.6001.18928

Sig[2].Name=Штамп времени приложения

Sig[2].Value=4bdfa327

Sig[3].Name=Имя модуля с ошибкой

Sig[3].Value=mshtml.dll

Sig[4].Name=Версия модуля с ошибкой

Sig[4].Value=8.0.6001.18928

Sig[5].Name=Штамп времени модуля с ошибкой

Sig[5].Value=4bdfb76d

Sig[6].Name=Код исключения

Sig[6].Value=c0000005

Sig[7].Name=Смещение исключения

Sig[7].Value=000da33f

DynamicSig[1].Name=Версия ОС

DynamicSig[1].Value=6.0.6002.2.2.0.768.3

DynamicSig[2].Name=Код языка

DynamicSig[2].Value=1049

DynamicSig[22].Name=Дополнительные сведения 1

DynamicSig[22].Value=fd00

DynamicSig[23].Name=Дополнительные сведения 2

DynamicSig[23].Value=ea6f5fe8924aaa756324d57f87834160

DynamicSig[24].Name=Дополнительные сведения 3

DynamicSig[24].Value=fd00

DynamicSig[25].Name=Дополнительные сведения 4

DynamicSig[25].Value=ea6f5fe8924aaa756324d57f87834160

UI[2]=C:\Program Files\Internet Explorer\iexplore.exe

UI[3]=Прекращена работа Internet Explorer

UI[4]=Windows может провести поиск способа устранения этой ошибки в Интернете.

UI[5]=Искать решение проблемы в Интернете и закрыть программу

UI[6]=Проверить наличие способа исправления ошибки в Интернете позднее и закрыть программу

UI[7]=Закрыть программу

FriendlyEventName=Остановка работы

ConsentKey=APPCRASH

AppName=Internet Explorer

AppPath=C:\Program Files\Internet Explorer\iexplore.exe

***

Как запустить службу Отчеты о проблемах и их решениях

Нажмите Пуск –> Панель управления –> Отчеты о проблемах и их решениях;

– в окне Отчеты о проблемах и их решениях в меню Задачи доступны следующие опции:

   · Искать новые решения (необходимо открытое соединение с Интернетом);

   · Показать проверяемые проблемы (прокручиваемый список проблем, для которых требуется найти решение);

   · Показать журнал проблем (проблемы, обнаруженные Windows);

   · Изменить параметры (выбор способа проверки на наличие решений в случае неполадок – Автоматически выполнять поиск решений или Запрашивать проверку на возможные проблемы);

   · Очистить журнал проблем и их решений (очистка журнала проблем для освобождения дискового пространства).

***

Честно говоря, автору статьи ни разу не удалось решить проблемы Windows с помощью Службы регистрации ошибок (да и статус вдохновляет на самостоятельный поиск решений таких проблем!). Значимость этой службы мне видится в том, что она помогает самостоятельно.

Сидоров

***

•

•

•

•

•

•

Служба Windows Error Reporting (WER) служит для сбора и отправки отладочной информации о падении системных и сторонних приложений в Windows на сервера Microsoft. По задумке Microsoft, эта информация должна анализироваться и при наличии решения, вариант исправления проблемы должен отправляется пользователю через Windows Error Reporting Response. Но по факту мало кто пользуется этим функционалом, хотя Microsoft настойчиво оставляет службу сбора ошибок WER включенной по умолчанию во всех последних версиях Windows. В большинстве случае о службе WER вспоминают, когда каталог C:\ProgramData\Microsoft\Windows\WER\ReportQueue\ начинает занимать много места на системном диске (вплоть до нескольких десятков Гб), даже не смотря на то что на этом каталоге по умолчанию включена NTFS компрессия.

Картинка с сайта: winitpro.ru

Служба Windows Error Reporting

Служба Windows Error Reporting при появлении ошибки показывает диалоговое окно, предлагающее отправить отчет об ошибке в корпорацию Microsoft. Когда в Windows вы видите сообщение об ошибке
YourApp has stop working
, в это время в служба Windows Error Reporting запускает утилиту WerFault.exe для сбора отладочных данных (могут включать в себя дамп памяти).

Данные пользователя сохраняются в профиль пользователя:

%USERPROFILE%\AppData\Local\Microsoft\Windows\wer

Системные данные – в системный каталог:

%ALLUSERSPROFILE%\Microsoft\Windows\WER\

Служба Windows Error Reporting представляет собой отдельный сервис Windows. Вы можете проверить состояние службы командой PowerShell:

Get-Service WerSvc

Внутри каталога WER\ReportQueue\ содержится множество каталогов, с именами в формате:

• Critical_6.3.9600.18384_{ID}_00000000_cab_3222bf78
• Critical_powershell.exe_{ID}_cab_271e13c0
• Critical_sqlservr.exe__{ID}_cab_b3a19651
• NonCritical_7.9.9600.18235__{ID}_0bfcb07a
• AppCrash_cmd.exe_{ID}_bda769bf_37d3b403

Как вы видите, имя каталога содержит степень критичности события и имя конкретного exe файла, который завершился аварийно. Во всех каталогах обязательно имеется файл Report.wer, который содержит описание ошибок и несколько файлов с дополнительной информацией.

Очистка папки WER\ReportQueue в Windows

Как правило, размер каждой папки в WER незначителен, но в некоторых случаях для проблемного процесса генерируется дамп памяти, который занимает довольно много места. На скриншоте ниже видно, что размер файла дампа memory.hdmp составляет около 610 Мб. Парочка таким дампов – и на диске исчезло несколько свободных гигибайт.

Картинка с сайта: winitpro.ru

Чтобы очистить все эти ошибки и журналы штатными средствами, откройте панель управления и перейдите в раздел ControlPanel -> System and Security -> Security and Maintenance -> Maintenance -> View reliability history -> View all problem reports (Control Panel\System and Security\Security and Maintenance\Problem Reports) и нажмите на кнопку Clear all problem reports.

Картинка с сайта: winitpro.ru

Для быстрого освобождения места на диске от файлов отладки, сгенерированных службой WER, содержимое следующих каталогов можно безболезненно очистить вручную.

• C:\ProgramData\Microsoft\Windows\WER\ReportArchive\
• C:\ProgramData\Microsoft\Windows\WER\ReportQueue\

Следующие команды PowerShell удалят из каталога каталогов WER все файлы, старше 15 дней:

Get-ChildItem -Path  'C:\ProgramData\Microsoft\Windows\WER\ReportArchive' -Recurse | Where-Object CreationTime -lt (Get-Date).AddDays(-15) | Remove-Item -force -Recurse
Get-ChildItem -Path  'C:\ProgramData\Microsoft\Windows\WER\ReportQueue' -Recurse | Where-Object CreationTime -lt (Get-Date).AddDays(-15) | Remove-Item -force –Recurse

Для очистки каталогов WER в пользовательских профилях используйте такой скрипт:

$users = Get-ChildItem c:\users|where{$_.name -notmatch 'Public|default'}
foreach ($user in $users){
Get-ChildItem "C:\Users\$User\AppData\Local\Microsoft\Windows\WER\ " –Recurse -ErrorAction SilentlyContinue | Remove-Item –force –Recurse
}

Отключение Window Error Reporting в Windows Server

В Windows Server 2019/2016/2012R2 вы можете управлять состоянием WER с помощью PowerShell. Вы можете отключить службу Windows Error Reporting:

Get-Service WerSvc| stop-service –passthru -force
Set-Service WerSvc –startuptype manual –passthru

Но есть более корректные способы отключения WER в Windows. В версии PowerShell 4.0 добавлен отдельный модуль WindowsErrorReporting из трех командлетов:

Get-Command -Module WindowsErrorReporting

Картинка с сайта: winitpro.ru

Проверить состояние службы Windows Error Reporting можно командой:

Get-WindowsErrorReporting

Для отключения WER, выполните:

Disable-WindowsErrorReporting

Картинка с сайта: winitpro.ru

В Windows Server 2012 R2 можно отключить запись информации об ошибках Windows Error Reporting через панель управления (Control Panel -> System and Security -> Action Center -> раздел Maintenance -> Settings -> выберите опцию I don’t want to participate, and don’t ask me again

Картинка с сайта: winitpro.ru

Отключаем сбор и отправки отчетов об ошибках в Windows 10

В Windows 10 нельзя отключить Error Reporting через панель управления. В графическогм интерфейсе можно только проверить ее статус (Система и безопасность ->Центр безопасности и обслуживания -> секция Обслуживание). Как вы видите, по умолчанию параметр Поиск решения для указанных в отчетах проблем включен (Control Panel -> System and Security -> Security and Maintenance -> Maintenance -> Report problems = On).

Картинка с сайта: winitpro.ru

HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting нужно создать новый параметр типа DWORD (32 бита) с именем Disabled и значением 1.

Можно отключить сбор ошибок WER для конкретных пользователей:

reg add "HKCU\Software\Microsoft\Windows\Windows Error Reporting" /v "Disabled" /t REG_DWORD /d "1" /f

Или отключить WER для всех:
reg add "HKLM\Software\Microsoft\Windows\Windows Error Reporting" /v "Disabled" /t REG_DWORD /d "1" /f

Картинка с сайта: winitpro.ru

Измените параметр реестра и проверьте статус параметра Поиск решения для указанных в отчетах проблем в панели управления. Его статус должен изменится на Отключено.

Картинка с сайта: winitpro.ru

Отключение Windows Error Reporting через GPO

Также вы можете управлять настройками службы Windows Error Reporting через групповые политики.

Запустите редактор локальной (
gpedit.msc
) или доменной GPO (
gpmc.msc
) и перейдите в ветку реестра Computer Configuration -> Administrative Templates -> Windows Components -> Windows Error Reporting (Компоненты Windows -> Отчеты об ошибках Windows). Для отключения сбора и отправки ошибок через WER включите политику Disable Windows Error Reporting (Отключить отчеты об ошибках Windows).

Аналогичная политика есть в пользовательском разделе политик (User Configuration).

Картинка с сайта: winitpro.ru

Обновите GPO (перезагрузка не потребуется).

В результате в Windows перестанут формироваться сообщения об ошибках Windows и отправляться в Microsoft.

Are you experiencing slow performance on your computer? You might be surprised to learn that Windows Problem Reporting could be the cause. When this feature consumes a high amount of CPU resources, it can significantly impact the speed and responsiveness of your system. But don’t worry, there are ways to address this issue and improve your computer’s performance.

Windows Problem Reporting is a built-in feature in Windows operating systems that allows users to report any issues or errors they encounter. It collects data about software crashes and performance problems to help Microsoft analyze and fix them. However, when this feature becomes overwhelmed or misbehaves, it can result in excessive CPU usage, leading to sluggishness and delays in your system’s operation.

If you’re experiencing Windows Problem Reporting using high CPU, you’re not alone. This issue can be caused by several factors, including software conflicts, corrupt system files, or incompatible hardware drivers. To resolve it, start by updating your Windows operating system and all device drivers. Next, perform a full system scan for malware and viruses. If the problem persists, try disabling the Windows Error Reporting service or adjusting the reporting settings. If all else fails, seek professional assistance or contact Microsoft support for further troubleshooting.

Картинка с сайта: softwareg.com.au

Understanding Windows Problem Reporting

Windows Problem Reporting is a feature in the Windows operating system that collects and sends error reports to Microsoft, allowing them to analyze and fix issues. These error reports help Microsoft identify software and hardware problems that users encounter and continuously improve the performance and reliability of Windows. However, some users have reported experiencing high CPU usage due to the Windows Problem Reporting process.

What Causes High CPU Usage in Windows Problem Reporting?

There can be several reasons behind the high CPU usage related to Windows Problem Reporting:

• Software Conflicts: Conflicts between different software applications running on your computer can cause the Windows Problem Reporting process to consume excessive CPU resources.
• Corrupted System Files: If certain system files essential for the functioning of Windows Problem Reporting get corrupted, it can lead to high CPU usage.
• Malware Infection: Malicious software or viruses that infect your system can interfere with various processes, including Windows Problem Reporting, leading to increased CPU usage.
• Outdated Drivers: Outdated or incompatible device drivers can sometimes cause conflicts with Windows Problem Reporting, resulting in high CPU usage.

Impact of High CPU Usage in Windows Problem Reporting

Excessive CPU usage by Windows Problem Reporting can have several negative impacts on your computer’s performance and user experience:

• Sluggish System Performance: When the CPU is overloaded with the Windows Problem Reporting process, it can slow down other tasks, making your computer run slowly and affecting overall performance.
• Increased Power Consumption: High CPU usage generates excess heat, causing your computer’s fans to work harder, resulting in increased power consumption and potentially shorter battery life on laptops.
• Unresponsive Applications: If the CPU is busy dealing with the high CPU usage caused by Windows Problem Reporting, it can make other applications unresponsive or freeze temporarily.
• Potential Data Loss: In extreme cases, where the CPU is pushed to its limits due to high CPU usage, there is a risk of data loss or system crashes if the problem is not addressed promptly.

How to Identify High CPU Usage by Windows Problem Reporting?

If you suspect that Windows Problem Reporting is causing high CPU usage on your computer, you can follow these steps to identify and confirm the issue:

• Open the Task Manager by right-clicking on the taskbar and selecting «Task Manager» from the menu.
• Select the «Processes» or «Details» tab, depending on your Windows version.
• Look for the process named «Werfault.exe» or «Windows Problem Reporting» in the list of active processes.
• If the CPU usage of this process is consistently high (above 50% or more), it indicates a potential problem.

Once you have confirmed that Windows Problem Reporting is causing high CPU usage, you can take appropriate measures to resolve the issue.

Methods to Fix High CPU Usage by Windows Problem Reporting

Here are some effective methods you can try to fix the problem of high CPU usage caused by Windows Problem Reporting:

1. Update Windows and Drivers

Make sure your Windows operating system is up to date, as Microsoft frequently releases updates that address performance issues and bugs. Similarly, update your device drivers by visiting the manufacturer’s website and downloading the latest versions compatible with your hardware.

Updating both Windows and drivers can resolve compatibility issues and improve system stability, potentially resolving the high CPU usage problem.

2. Perform a Full System Scan

Scan your computer for malware using a reputable antivirus or antimalware software. Malicious programs can interfere with various system processes, including Windows Problem Reporting, leading to high CPU usage. Remove any detected threats and perform a full system scan regularly to prevent future infections.

3. Disable Windows Error Reporting

If you find that the high CPU usage caused by Windows Problem Reporting persists, you can try disabling the Windows Error Reporting feature:

• Open the Control Panel and navigate to «System and Security.»
• Select «Action Center» and then click on «Change Action Center settings» in the left sidebar.
• Click on «Problem reporting settings» and choose «Never check for solutions» option.
• Click «OK» to save the changes.

Seek Expert Assistance

If you have tried the above methods and are still experiencing high CPU usage due to Windows Problem Reporting, it is recommended to seek assistance from a professional. An expert can perform in-depth analysis and troubleshooting to identify and resolve the underlying cause of the issue.

Remember that high CPU usage can have multiple causes, and it’s important to rule out other potential factors before concluding that Windows Problem Reporting is solely responsible for the issue.

Exploring Other Factors Related to Windows Problem Reporting High CPU

In addition to the causes and solutions mentioned earlier, there can be other factors related to Windows Problem Reporting that can contribute to high CPU usage. These factors include:

Windows Problem Reporting Service Settings

The settings of the Windows Problem Reporting service can impact its behavior and resource usage. By modifying these settings, you can potentially mitigate high CPU usage:

• Reduce the frequency of error reporting: Decreasing the frequency of error reports sent to Microsoft can help reduce the strain on CPU resources.
• Limit the number of error reports: Instead of allowing an unlimited number of reports to be sent, consider setting a limit to prevent excessive resource usage.

Application Compatibility Telemetry

Application Compatibility Telemetry is another Windows feature that collects data to improve application compatibility. However, this feature can also contribute to high CPU usage. To address this, you can:

• Disable Application Compatibility Telemetry: You can disable the Application Compatibility Telemetry feature if you find it causing high CPU usage. This can be done through the Group Policy Editor or Registry Editor.

Configuration Changes

Certain configuration changes and optimizations can help reduce the impact of Windows Problem Reporting on CPU usage:

• Adjust the reporting mode: You can change the reporting mode for Windows Problem Reporting to «Queued» or «Disabled» to minimize CPU usage.
• Disable automatic solution retrieval: Disabling the automatic retrieval of solutions for reported errors can reduce the CPU load caused by Windows Problem Reporting.

Remember to exercise caution when making changes to system settings and consult the appropriate documentation or seek expert guidance if needed.

In conclusion, high CPU usage caused by Windows Problem Reporting can impact system performance and user experience. By understanding the underlying causes and implementing the appropriate solutions or optimizations, you can alleviate this issue and ensure smoother operation of your Windows system.

Windows Problem Reporting High CPU

Windows Problem Reporting is a feature of the Windows operating system that collects and sends information about system errors, crashes, and other issues to Microsoft. However, sometimes this process can consume a significant amount of CPU resources, causing your computer to slow down.

If you are experiencing high CPU usage due to Windows Problem Reporting, there are a few steps you can take to resolve the issue:

• Update your Windows operating system to the latest version. Microsoft often releases updates and patches that address performance issues.
• Disable Windows Problem Reporting temporarily. This can be done by going to the Control Panel, clicking on System and Security, and selecting «Action Center». From there, click on «Change Action Center settings» and uncheck the option for «Problem reporting».
• Scan your computer for malware. Malicious software can sometimes cause high CPU usage. Use a reliable antivirus program to scan your system.

If these steps do not resolve the issue, it is recommended to seek professional assistance from an IT technician or contact Microsoft support for further guidance.

Frequently Asked Questions

If you’re experiencing high CPU usage due to Windows Problem Reporting, you may have questions on how to resolve this issue. Here are some commonly asked questions related to Windows Problem Reporting and high CPU usage.

1. Why is Windows Problem Reporting causing high CPU usage?

Windows Problem Reporting is a feature in Windows that collects and submits information about system errors and crashes to Microsoft. When this feature is enabled and encounters errors, it can sometimes lead to high CPU usage as it processes and submits the error reports. The high CPU usage is often temporary and should subside once the error reports are submitted.

If you notice consistent high CPU usage due to Windows Problem Reporting, it may indicate a larger issue with your system or specific application errors. In such cases, troubleshooting steps may be required to resolve the underlying problem.

2. How can I reduce the high CPU usage caused by Windows Problem Reporting?

To reduce high CPU usage caused by Windows Problem Reporting, you can try the following steps:

1. Disable Windows Problem Reporting: Go to the Control Panel > Action Center > Change Action Center settings. Under the «Maintenance» section, uncheck the box next to «Check for solutions to problem reports.» This will prevent Windows Problem Reporting from collecting and processing error reports, reducing CPU usage.

2. Limit the number of error reports: You can configure Windows Problem Reporting to collect and submit error reports only for specific programs or opt to send them only when connected to an external network. This can help reduce the load on your CPU.

3. Disable error reporting for specific applications: If you notice high CPU usage specifically related to certain applications, you can disable error reporting for those applications. This will prevent Windows Problem Reporting from collecting and processing error reports for those specific programs.

4. Update your system and applications: Outdated software can sometimes lead to compatibility issues and errors that trigger high CPU usage. Make sure your operating system and applications are up to date to avoid such problems.

5. Run a malware scan: Malware infections can also cause high CPU usage. Use a reliable antivirus software to scan your system and remove any potential threats that may be contributing to the issue.

3. Can I completely disable Windows Problem Reporting?

Yes, it is possible to completely disable Windows Problem Reporting. However, keep in mind that by disabling this feature, you will not be able to submit error reports to Microsoft or receive recommended solutions for system errors. To disable Windows Problem Reporting:

1. Go to the Control Panel > Action Center > Change Action Center settings.

2. Under the «Maintenance» section, uncheck the box next to «Check for solutions to problem reports.»

Disabling Windows Problem Reporting may be suitable for users who prefer to handle troubleshooting and error resolution themselves or have alternative methods to collect and analyze error data.

4. Is there a way to limit the CPU usage of Windows Problem Reporting?

Windows Problem Reporting does not have built-in settings to limit its CPU usage directly. However, you can indirectly limit its impact on CPU usage by following the steps mentioned in question 2, such as disabling it or limiting error reports for specific programs or network connections.

If you are experiencing persistent high CPU usage due to Windows Problem Reporting, it is recommended to investigate further to identify the underlying cause. It may be necessary to troubleshoot other system components or applications that are contributing to the problem.

5. Are there any alternative error reporting tools I can use instead of Windows Problem Reporting?

Yes, there are alternative error reporting tools available that can be used instead of Windows Problem Reporting. Some popular options include:

— Third-party crash reporting software: These tools provide enhanced error reporting capabilities and allow you to customize the reporting process.

— Application-specific error reporting: Many applications have their own error reporting mechanisms built-in. These tools can provide specific information about application-related errors and crashes.

In summary, the Windows Problem Reporting process can sometimes consume a high amount of CPU resources on your computer. This can impact the performance of your system and may cause it to slow down or freeze. To address this issue, you can try disabling the Windows Error Reporting service or adjust its settings to minimize the impact on your CPU. Additionally, regularly updating your Windows operating system and keeping your drivers up to date can help prevent any compatibility issues that may contribute to the high CPU usage.

If you continue to experience high CPU usage from Windows Problem Reporting, it may be helpful to scan your system for malware or perform a clean boot to identify any conflicting applications. Remember to always exercise caution when modifying system settings or installing third-party software, as these actions can have unintended consequences and pose security risks. It’s always a good idea to consult with a professional if you are unsure about any adjustments you need to make to resolve the issue. By taking these steps, you can optimize your CPU usage and maintain the performance of your Windows computer.

Problem Reporting is otherwise called “Error Reporting,” which is a help turned on by default in all adaptations of Windows. This article will help you disable Windows Problem Reporting in Windows 10.

When Windows recognizes a hardware or programming mistake, it will consequently gather analytic information and report it to Microsoft. For security concerns, you might not want it. You may likewise need to disable problem reporting to try not to send private data about your PC to Microsoft because you’re not associated with the web constantly, or just to quit being provoked by the irritating alerts.

Why do you need to disable windows problem reporting in Windows 10?

There’s a need to disable Windows problem reporting in Windows 10 due to the following reasons:

1. Avoid annoying Windows alerts.

2. To avoid sending private data about your PC to Microsoft

Though Error Reporting helps us handle our error reports and send our hardware and application issues directly to Microsoft, it has its drawbacks of privacy-related issues. So let us look at the way to protect our computers from these privacy threats. Below given are solutions as to how you can disable Windows Problem Reporting in Windows 10:

Solution 1: Use Group Policy

Follow the given steps to apply the Group Policy settings in Windows 10:

1. In the Windows search box, type MMC and open the top result. MMC stands for Microsoft Management Console.

2. After it opens, click the File menu.

3. Now, select the Add/Remove Snap-in option, and then under it, click on the Group Policy Object Editor snap-in.

Картинка с сайта: www.pcasta.com

4. Next, click the Add button, the Browse button, and click the Users tab.

5. Now, you can choose the user or group you want to apply a specific set of configurations.

6. Finally, click the OK button, the Finish button, and click the OK button.

Картинка с сайта: www.pcasta.com

7. Now, click the File menu and select the Save As option.

8. Lastly, type a name for the snap-in and choose a location to store this console.

9. Finally, tap the Save button to apply changes.

Solution 2: Run SFC Scan

You can perform a System File Checker Scan using the following steps:

1. In the search box on your taskbar, type CMD.

2. From there, right-click Command Prompt and then select Run as Administrator

3. In the box that appears, type sfc/scannow.

Картинка с сайта: www.pcasta.com

4. Lastly, press Enter and restart your computer.

Solution 3: Run the Windows Memory Diagnostics

To diagnose memory problems on Windows 10 follow the subsequent steps:

1. Firstly, open the Control Panel.

2. Now, click the System and Security option.

Картинка с сайта: www.pcasta.com

3. Next, click on Administrative Tools and then double-click the Windows Memory Diagnostic shortcut.

Картинка с сайта: www.pcasta.com

4. Finally, you can click the Restart now button and check the problems options.

Solution 4: Try using the Registry Editor

You can use the Registry editor using the following steps:

1. Firstly, type Regedit in the Windows search box located on the taskbar.

2. After the dialogue box appears, select Registry Editor from the results.

Solution 5: Turn Off Windows Error Reporting Service

You can turn off the Windows Error Reporting Service using the given steps:

1. Firstly, open the Run dialog box from the Windows Start button.

2. In the Run dialogue box, enter services.msc.

3. Now, right-click the Windows Error Reporting Service and then click on Properties.

4. Next, select Disabled from the menu option, which is located next to Startup type.

Картинка с сайта: www.pcasta.com

5. Finally, click Apply to carry out the changes.

Frequently Asked Question

Q1. How do I repair Windows 10 without a disk?

Answer: To repair Windows 10 without a disk, follow the steps mentioned below:

1. Firstly, open the Windows 10 Advanced Startup Options menu by pressing the F11 key.

2. Now, go to the Troubleshoot menu and click on Advanced options.

3. Under, Advanced options select Startup Repair.

4. You now need to wait for a few minutes until Windows 10 fixes the startup problem.

Q2. Will I lose everything when I reinstall Windows 10?

Answer: No, you will be able to keep all your files and software if you reinstall Windows 10. However, there is a possibility that the reinstallation might delete certain things such as custom fonts and Wi-Fi credentials. But you need not worry; keeping this issue in mind, the setup also creates an old Windows folder with everything from your previous installation.

Q3. What will reset this PC do in Windows 10?

Answer: Reset This PC is a repair tool used for serious operating system problems in Windows 10. This tool also has the option to keep your personal files and removes any software you have installed. It is only after doing this that it reinstall Windows.

Q4. Will resetting my PC fix driver issues?

Answer: Yes, resetting Windows 10 will partially fix your driver issues, as the newly installed drivers would be updated ones. However, you might need to download specific drivers again that Windows was unable to find automatically.

Q5. How do I stop the Blue Screen of Death Windows 10?

Answer: You can prevent the Blue Screen of Death Windows 10 by uninstalling the faulty updates. You can do it by following the given steps:

1. Open Settings in the Device Manager.

2. In the Device Manager, go to Update & Recovery and click the Windows Update option.

3. Next, click on Update history and then click on Uninstall updates.

Conclusion

We hope the article helped you in understanding how we can disable Windows Problem Reporting in Windows 10. However, if you are still unable to disable the Error Reporting, then you can connect with us via the chat box at the bottom right or through the comment section below. We’ll try to help you solve the issues with your Windows.