California Dmv an Unexpected Error Occurred Please Try Again

Windows has several congenital-in troubleshooters which can actually assist with some of the most mutual issues you lot might be faced upwardly against. The troubleshooter might not ever solve the trouble yous were experiencing at the moment simply it will display what went wrong and you lot can narrow down your search for the right answer.

Windows 10 troubleshooters tin exist located in the Settings app under the Update & Security department. For example, if yous are experiencing issues with your Internet connection, you can try running the Internet Connections troubleshooter.

However, sometimes the troubleshooter simply won't start and it will display this mistake bulletin: "An Unexpected Error Has Occurred. The Troubleshooting Wizard Can't Go on." This can be quite annoying, especially if you were trying to solve a problem that has been bugging you for a while. Follow the solutions below in order to find out how to solve this issue.

Solution 1: If the Problem Occurred After an Update

If the solution you were having occurred afterward y'all have performed an update or afterward Windows installed it on its own, you lot might be able to solve the issue only by resetting your Windows Update components, as this worked for plenty of users who were struggling with the exact same problem:

1. Let'due south proceed with the solution by killing the following services which are the cadre services related to Windows Update: Background Intelligent Transfer, Windows Update, and Cryptographic Services. Disabling them before we start is crucial if you want the residue of the steps to perform smoothly.
2. Search for "Command Prompt", right-click on it, and select the "Run as administrator" option. Re-create and paste the following commands and make sure you click Enter afterward each one.

internet stop $.25
cyberspace cease wuauserv
net stop appidsvc
net end cryptsvc

3. After this, you lot will accept to delete some files which should exist deleted if y'all want to go on with resetting the update components. This is also washed via Command Prompt with administrative privileges.

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

4. The following step can exist skipped if this is not concluding resort. This step is considered to be the ambitious approach simply it will definitely reset your updating process from its very cadre. So we tin recommend that you endeavour this out. It has been suggested by a lot of people on online forums.
5. Change the name of the SoftwareDistribution and catroot2 folders. In order to practise this, at an administrative control prompt, re-create and paste the post-obit commands and click Enter after copying each one.

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

6. The following commands will help us reset the BITS (Background Intelligence Transfer Service) and the wuauserv (Windows Update Service) to their default security descriptors. Make sure you don't change the commands below then it's for the best if y'all simply copy them.

exe sdset $.25 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)

7. Allow's navigate dorsum to the System32 folder in order to proceed with the solution at hand.

cd /d %windir%\system32

8. Since we have completely reset the BITS service, we will need to reregister all of the files necessary for the service to run and operate smoothly. Still, each of the files requires a new command in order to make it reregister itself so the process may stop upwardly being lengthier than what you are used to. Copy the commands one by one and make sure you don't leave out any of them. Here is a list of files which need to be reregistered forth with the corresponding commands next to them.
9. Some files may have been left backside after these processes and then we are going to look for them in this pace. Open up 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

10. Click on the Components central and bank check the correct side of the window for the following keys. Delete them all if you lot locate any of them.

PendingXmlIdentifier
NextQueueEntryIndex
AdvancedInstallersNeedResolving

11. The next affair we are going to do is reset Winsock by copying and pasting the post-obit command back into the administrative Command Prompt:

netsh winsock reset

12. If y'all are running Windows 7, 8, eight.one, or 10, at a command prompt, copy the post-obit control, and tap the Enter key:

netsh winhttp reset proxy

13. If all of the steps in a higher place have gone through painlessly, you can now restart the services you lot killed in the very first footstep by using the commands beneath.

net first bits
internet start wuauserv
net commencement appidsvc
net start cryptsvc

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

Solution ii: Employ the Chkdsk Utility

Some users claim that using the chkdsk utility helped fixed their consequence almost immediately as these errors sometimes occur if the hard disk files have gone corrupt or similar. The procedure is quite like shooting fish in a barrel but it may accept a while for the tool to stop.

From Command Prompt

1. Turn on your computer and log into Windows 10
2. Press the Windows key in order to open the Start Menu, select the search button or beginning typing immediately, and type in "cmd"
3. Select "Command Prompt" which should be the kickoff issue, correct-click on information technology, and select the Run as administrator option.
4. When Command Prompt launches, blazon in the post-obit command:
5. chkdsk C: /f /r /x
6. The parameters for this command can be explained like this:
7. /f selection will try to fix whatever found errors
8. /r option will search for bad sectors and recover any readable data
9. /x option will force the drive y'all're virtually to check to be dismounted before the tool begins a scan
10. If the C: bulldoze is in apply, type Y to run a scan at your PC's side by side restart. If then, you should leave Command Prompt and restart the computer in order to make the scan run at the next startup.

From My Estimator

1. Turn on your figurer and log into Windows 10.
2. Double-click on This PC (My Computer) in gild to open up it and right-click on the drive y'all would like to run a check on. Select the Properties option and navigate to the Tools tab.
3. Navigate to the Error checking section and select the Check option.
4. 
5. If you run into the following message, click Scan drive to begin the scan:
6. Y'all don't need to scan this drive
   Nosotros haven't found any errors on this bulldoze. You can still scan the drive for errors if you lot want.
7. You can keep using you computer during the browse. If any errors are constitute, you lot can decide if you lot want to prepare them immediately. Depending on the results of this browse, the tool will form the results:
8. 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 constitute.
   
9. If errors occur on your drive, you'll see this bulletin instead:
   Restart your computer to repair file organization. You lot can restart right away or schedule the error fixing on next restart.

Solution 3: Repair .NET Framework

This detail method may audio strange but it appears that a contempo installation of Microsoft .Net Framework may be a cause for this outcome. If this is indeed the case, the problem should be able to solve itself in a couple of minutes.

1. Open up your Windows Settings and navigate to the Apps section if you are using Windows x.
2. Open up Control Panel >> Programs and Features, if you are using an older Windows Bone.
3. Locate .NET Framework on the listing of your installed programs listing and click on "Uninstall/Change".
4. A window should open up with several choices and yous should be able to choose the Repair option instead of remove.
5. The wizard will starting time to repair the installation on .Net Framework and y'all should now exist able to run whatsoever troubleshooter without problems.
6. If this doesn't work, y'all tin can always try to simply reinstall .NET Framework.

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

Some of the services essential for the troubleshooting wizards are:

Diagnostic Service Host service
Diagnostic System Host service
Diagnostic Policy service

Without these services, the troubleshooter has no take chances of starting and so you lot should really check if these services are configured to run at all.

1. If you are using a version of Windows older than Windows ten, the easiest way for you to access the services running on your PC is clicking on the Commencement button and navigating to the Run dialog box.
2. Type "services.msc" in the dialog box and wait for the listing of services to open.
3. If you are using Windows 10, you tin can also access Services by using the Ctrl + Shift + Esc key combination in social club to bring upwards Task Managing director.
4. Navigate to the Services tab in Chore Director and click on Open up Services at the bottom of its windows, adjacent to the gears icon.

Subsequently you take successfully open up Services, follow the instructions beneath.

1. Locate the Diagnostic Service Host service by clicking on the Proper noun cavalcade in order to sort the services in an alphabetical lodge.
2. Correct-click on the Diagnostic Service Host service and click on Properties.
3. Navigate to the Startup type and set information technology to Automatic (Delayed Start).
4. If the service is not running, you will be able to click on Starting time only nether the Service status.

The service should start at present and you won't accept any issues dealing with it in the hereafter. However, you lot may receive the following error message when y'all click on Start:

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

If this occurs, follow the instructions below to prepare information technology.

1. Follow the steps i-4 from the instructions below in club to open service's backdrop.
2. Navigate to the Log On tab and click on the Browser… button.
3. Nether the "Enter the object name to select" box, type in your reckoner's name and click on Cheque Names and wait for the name to become authenticated.
4. Click OK when yous are done and blazon in the administrator password in the Password box when you are prompted with it.
5. Click OK and close this window.
6. Navigate dorsum to Diagnostic Service Host service's properties and click Beginning.
7. Close everything and check to come across if the service is still running.

Notation: If you still detect certain bug, open Services once again by post-obit the instructions higher up and echo the same process for services named Remote Diagnostic Organisation Host service
and Diagnostic Policy service. Brand sure there are started and that their startup type is set on Automatic.

Kevin is a dynamic and cocky-motivated information technology professional person, with a Thorough noesis of all facets pertaining to network infrastructure design, implementation and assistants. Superior record of delivering simultaneous large-calibration mission critical projects on time and nether budget.

sydnoragnight.blogspot.com

Source: https://appuals.com/fix-unexpected-error-occurred-troubleshooting-wizard-cant-continue/

Share this post