The troubleshooters in Windows 10 provide a great way to troubleshoot and locate certain problems. But sometimes these troubleshooters also give errors. For example, many users have reported receiving the following error message while running the troubleshooter.
There was an unexpected error. The troubleshooting wizard cannot continue. Error code: 0x80070002
Here are the solutions that work for this strange problem.
Correction- 1 Change service configuration-
1. Write "Services“And then press Log in to access Utility Services.
2. In the Services window, double click on him "Smart fund transfer service“To change it.
3. Just set "Start type: 'for"Automatic".
4. Then click on "Home“To resume service.
5. Next, click on “To apply"Y"ok".
6. Go back to Services, scroll down a bit and double click on the "Cryptographic Services".
7. Similarly, click on the drop-down menu for 'Start type:'. You choose "Automatic" to boot.
8. Next, click on “Home“To start the service immediately.
9. Click on 'To apply", Followed by a simple click on"ok".
10. In a similar method, double click on him "Windows update"Service.
11. In the same procedure as before, set the startup type "Automatic'.
12. Don't forget to click on "HomeTo start the service, if you haven't already.
13. Click sequentially on "To apply"And then in"ok".
After you have automated all of these services, you need to close the Services file.
Solution 2: Reset the IP settings
1. First, click on the Windows icon and then type “cmd".
2. Once you see that "Symbol of the system'in the raised window, right click on it and choose "Run as administrator".
3. When the System Symbol file appears, execute this line. Simply to write this and press'Log in'.
ipconfig / flushdns
4. What you need to do next is reset the Windows sockets. To do this, run this code in the terminal.
netsh winsock reset
Close the terminal e start again your system.
Solution 3: Use the Notepad file
1. close pad in the Windows 10 taskbar search.
2. Click pad Icon to open Notepad.
3. Now copy and paste the following code below into Notepad.
@echo off net stop wuauserv cd %systemroot% ren SoftwareDistribution SoftwareDistribution.old net start wuauserv net stop bits net start bits net stop cryptsvc cd %systemroot%system32 ren catroot2 catroot2.old net start cryptsvc regsvr32 Softpub.dll regsvr32 Wintrust.dll regsvr32 Mssip32.dll regsvr32 Initpki.dll /s echo Restarting Computer shutdown.exe -r -t 00
4. Now in Notepad, click archive.
5. Choose Save eat.
6. In the File Name section, provide the name Fixer.bat.
7. In the file type Choose All files from the drop-down menu.
8. Save this file to your desktop.
9. Now click and run this file once.
Your problem will be solved.
Solution 4: Check the service manager
1. Search Services in Windows 10 Taksbar.
2. Now open Supervisor.
3. Now in the Service Manager window, check if the following services are running.
Diagnostic Policy Service. Make sure the startup type is automatic.
Diagnostic Service Host. Make sure the startup type is Manual.
Host of the diagnostic system. Make sure the startup type is Manual.
4. If the services are not running, click Home to start these services and edit the file kind of start as above for each of the services.
Note: - If you first click on one of these non-running services, some users may encounter the error listed below.
Windows was unable to start the diagnostic service host service on the local computer. Error 1079: The account specified for this service is different from the account specified for other services running in the same process
To get rid of this, follow the steps given below: -
1. The right mouse button on the particular service that generated the error and click Property.
2. Now click Log into Tongue.
3. Then choose Look.
4. Now, in the section that says Enter the name of the object to select a section, just write yours Computer user name.
5. Then click Check the names and then choose ok.
6. Now go back and try starting the service again.
Solution 5: repair the installation of .Net framework
1. Go to Control Panel.
2. Click Uninstall a program.
3. Now Right-click in the .NET Framework and choose Uninstall the changes.
4. Now choose repairs .net Framework to its original stage.
Most likely, your problem has been solved.
