Cirrus There Was an Unexpected Error Please Try Again

Windows has several built-in troubleshooters which tin can really aid with some of the most common issues yous might be faced up against. The troubleshooter might not always solve the trouble you were experiencing at the moment but it will display what went wrong and yous tin narrow down your search for the right answer.

Windows ten troubleshooters tin can be located in the Settings app nether the Update & Security department. For example, if yous are experiencing problems with your Internet connection, you tin endeavor running the Internet Connections troubleshooter.

Yet, sometimes the troubleshooter but won't kickoff and it will display this error message: "An Unexpected Error Has Occurred. The Troubleshooting Wizard Can't Continue." This can exist quite abrasive, especially if y'all were trying to solve a problem that has been bugging you for a while. Follow the solutions below in club to find out how to solve this issue.

Solution i: If the Problem Occurred After an Update

If the solution you were having occurred later on you have performed an update or after Windows installed information technology on its own, y'all might be able to solve the event just by resetting your Windows Update components, as this worked for plenty of users who were struggling with the exact same trouble:

Let's proceed with the solution by killing the following services which are the core services related to Windows Update: Background Intelligent Transfer, Windows Update, and Cryptographic Services. Disabling them before we start is crucial if you want the remainder of the steps to perform smoothly.
Search for "Command Prompt", right-click on information technology, and select the "Run as administrator" option. Copy and paste the following commands and make certain you click Enter subsequently each one.

internet stop $.25
internet stop wuauserv
net stop appidsvc
net terminate cryptsvc

After this, you will have to delete some files which should be deleted if you desire to continue with resetting the update components. This is as well done via Command Prompt with authoritative privileges.

Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"

The following step can be skipped if this is not last resort. This stride is considered to be the aggressive approach just information technology will definitely reset your updating process from its very core. So we tin recommend that you try this out. It has been suggested by a lot of people on online forums.
Change the name of the SoftwareDistribution and catroot2 folders. In order to do this, at an administrative control prompt, copy and paste the post-obit commands and click Enter afterwards copying each one.

Ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak
Ren %systemroot%\system32\catroot2 catroot2.bak

The following commands will help us reset the $.25 (Background Intelligence Transfer Service) and the wuauserv (Windows Update Service) to their default security descriptors. Make sure you don't modify the commands below so it'due south for the best if y'all simply copy them.

exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)

Allow's navigate dorsum to the System32 folder in club to go along with the solution at mitt.

cd /d %windir%\system32

Since we have completely reset the BITS service, we volition need to reregister all of the files necessary for the service to run and operate smoothly. Withal, each of the files requires a new control in society to make it reregister itself so the process may terminate up being lengthier than what you are used to. Re-create the commands one by one and make certain you lot don't leave out any of them. Here is a list of files which demand to exist reregistered along with the respective commands next to them.
Some files may have been left behind after these processes so nosotros are going to look for them in this step. Open the Registry Editor by typing "regedit" in either the search bar or the Run dialog box. Navigate to the following key in Registry Editor:

HKEY_LOCAL_MACHINE\COMPONENTS

Click on the Components central and cheque the right side of the window for the following keys. Delete them all if y'all locate any of them.

PendingXmlIdentifier
NextQueueEntryIndex
AdvancedInstallersNeedResolving

The next thing we are going to practice is reset Winsock by copying and pasting the following command back into the administrative Control Prompt:

netsh winsock reset

If you are running Windows vii, viii, 8.1, or ten, at a control prompt, copy the post-obit command, and tap the Enter fundamental:

netsh winhttp reset proxy

If all of the steps above have gone through painlessly, you tin now restart the services yous killed in the very start stride by using the commands below.

net kickoff bits
net kickoff wuauserv
net start appidsvc
net start cryptsvc

Restart your computer after following through with all of the steps which are listed.

Solution 2: Employ the Chkdsk Utility

Some users merits that using the chkdsk utility helped fixed their issue almost immediately every bit these errors sometimes occur if the hard disk files have gone corrupt or like. The process is quite like shooting fish in a barrel but it may take a while for the tool to finish.

From Command Prompt

Turn on your reckoner and log into Windows x
Printing the Windows key in social club to open the Start Menu, select the search push button or outset typing immediately, and type in "cmd"
Select "Control Prompt" which should exist the first result, right-click on information technology, and select the Run as administrator option.
When Control Prompt launches, type in the following command:
chkdsk C: /f /r /x
The parameters for this command tin can be explained like this:
/f pick will endeavor to ready any found errors
/r option volition search for bad sectors and recover whatsoever readable data
/x option will forcefulness the drive yous're about to check to be dismounted before the tool begins a scan
If the C: drive is in use, type Y to run a scan at your PC's next restart. If and then, you should exit Command Prompt and restart the computer in social club to brand the scan run at the next startup.

From My Computer

Turn on your computer and log into Windows 10.
Double-click on This PC (My Estimator) in gild to open up information technology and right-click on the bulldoze you lot would similar to run a check on. Select the Properties choice and navigate to the Tools tab.
Navigate to the Error checking department and select the Check option.
If yous encounter the following message, click Scan drive to begin the browse:
You don't need to browse this drive
Nosotros haven't found whatsoever errors on this drive. You can withal browse the drive for errors if yous want.
Y'all can keep using you figurer during the scan. If whatsoever errors are found, you can make up one's mind if y'all desire to gear up them immediately. Depending on the results of this scan, the tool volition course the results:
If no errors occur on your drive, you'll see this message:Your drive was successfully scanned
Windows successfully scanned the drive. No errors were plant.
If errors occur on your drive, y'all'll see this message instead:
Restart your figurer to repair file organization. You tin restart correct abroad or schedule the error fixing on next restart.

Solution three: Repair .Cyberspace Framework

This item method may sound strange simply information technology appears that a recent installation of Microsoft .NET Framework may be a cause for this consequence. If this is indeed the instance, the problem should be able to solve itself in a couple of minutes.

Open your Windows Settings and navigate to the Apps department if you are using Windows 10.
Open Control Panel >> Programs and Features, if you are using an older Windows OS.
Locate .NET Framework on the listing of your installed programs list and click on "Uninstall/Change".
A window should open with several choices and you should be able to cull the Repair option instead of remove.
The sorcerer volition start to repair the installation on .Cyberspace Framework and y'all should now be able to run any troubleshooter without problems.
If this doesn't piece of work, you can e'er effort to simply reinstall .Net Framework.

Solution 4: Make Certain Some of the Essential Services are Running

Some of the services essential for the troubleshooting wizards are:

Diagnostic Service Host service
Diagnostic Organisation Host service
Diagnostic Policy service

Without these services, the troubleshooter has no chance of starting so yous should actually cheque if these services are configured to run at all.

If yous are using a version of Windows older than Windows 10, the easiest way for you to admission the services running on your PC is clicking on the Start push button and navigating to the Run dialog box.
Blazon "services.msc" in the dialog box and wait for the listing of services to open.
If y'all are using Windows ten, you can likewise access Services by using the Ctrl + Shift + Esc key combination in order to bring up Chore Manager.
Navigate to the Services tab in Job Managing director and click on Open up Services at the bottom of its windows, adjacent to the gears icon.

Later yous have successfully open Services, follow the instructions below.

Locate the Diagnostic Service Host service by clicking on the Name cavalcade in order to sort the services in an alphabetical society.
Right-click on the Diagnostic Service Host service and click on Properties.
Navigate to the Startup blazon and gear up information technology to Automated (Delayed Start).
If the service is not running, you will be able to click on Start merely under the Service status.

The service should start now and you lot won't take whatever problems dealing with it in the future. Even so, you lot may receive the following fault message when you click on Get-go:

"Windows could not start the Diagnostic Service Host service on Local Computer. Error 1079: The business relationship specified for this service differs from the business relationship specified for other services running in the same process."

If this occurs, follow the instructions below to ready it.

Follow the steps one-4 from the instructions below in order to open service's backdrop.
Navigate to the Log On tab and click on the Browser… button.
Nether the "Enter the object name to select" box, type in your computer's name and click on Check Names and wait for the proper name to become authenticated.
Click OK when you are done and type in the administrator password in the Countersign box when you are prompted with it.
Click OK and shut this window.
Navigate back to Diagnostic Service Host service's properties and click Start.
Close everything and bank check to come across if the service is withal running.

Annotation: If you however detect certain issues, open up Services again by following the instructions higher up and echo the same process for services named Remote Diagnostic System Host service
and Diagnostic Policy service. Make sure there are started and that their startup type is assault Automatic.