We all know that using the Windows Action Center, we can resolve issues with our system using Check for solutions button mentioned against an issue. Thus time to time, we have to deal with different problems and accordingly, we have to check for the fixes. But recently I found that whenever I hit the Check for solutions button in the Action Center, I received the following error:
Problem connecting to the Windows Error Reporting service. Some of the reports could not be uploaded to the Windows Error Reporting service. Please try again later.
As evident from the error message, this problem is related to the working of the Windows Error Reporting service and its dependency services. If they’re not working correctly, you’ll keep getting this error message. Thus due to this hitch, you can’t check for solutions in the Action Center and hence, you might have many issues for your PC that remain unresolved.
Problem connecting to the Windows Error Reporting service
The Windows Error Reporting Service helps Microsoft and Microsoft partners diagnose problems in the software you use and provide solutions. We have earlier blogged about how to enable or disable Windows Error Reporting Service. Today we will see how to fix this problem.
1. Press Windows Key + R and type services.msc in the Run dialog box:
2. In the Services window, scroll down and look for the Windows Error Reporting Service. If you’re facing this issue, the service may be not be Running. Double click on this service to open its Properties.
3. In the below shown window, make sure the Startup type is either Manual or Automatic. Then click on Start option if the service is not running on your system. Click Apply followed by OK, when you’re done with making changes.
You can now close Services window and restart the machine. After rebooting, you can check for solutions to the problems in Action Center, you’ll find that the issue has been resolved successfully.
Hope this helps!
Here are some additional troubleshooting steps if you find that your Windows Services will not start.
See this post if you receive WerMgr.exe or WerFault.exe Application Error.