Configuration system failed to initialize on Windows 10 (Solved)
Sometimes you may experience error “Configuration system failed to initialize” while trying to launch an application on your PC. This problem usually caused by some third-party application, when the system is unable to correctly launch any target application. Corrupted system files, Problems with any third-party applications, wrong configuration files are some common reason cause this issue, and uninstalling some application to change the configuration files help fix the error Configuration system failed to initialize on Windows 10.
If you are getting this error with .net framework it’s recommended to uninstall it and download and install the latest version from Microsoft’s official site.
Contents
Run System File Checker
This error usually caused becaused of bad configurations present on your computer. Lets try run the SFC scan and check if there are any integrity violations. If there are, we can run the DISM command to fix them.
Open command prompt as administrator,
Type command sfc /scannow and press the enterkey,
This process may take some time as your entire windows files are being scanned by the computer and being checked for corrupt phases.
Let the scanning process complete 100%, once doen restart your PC.
![system file checker utility Windows 10](https://static.wixstatic.com/media/94d44a_02482806a6ac49c0aecd3bf5539b077f~mv2.jpg/v1/fill/w_778,h_365,al_c,q_80,enc_auto/94d44a_02482806a6ac49c0aecd3bf5539b077f~mv2.jpg)
Note: If you encounter any error while running the system file checker where Windows states that it found some error but was unable to fix them Then run the dism command DISM /Online /Cleanup-Image /RestoreHealth
This will download the corrupt files from the Windows update servers and replace the corrupt ones.
Perform a Clean Boot
Windows clean boot allow your computer to start with minimum of drivers and programs. And with only basic services enabled and all other services disabled, you can check if the application launched as normal.
Press windows key + R, type msconfig and press enter key,
Move to services tab, then check the box next to hide all microsoft services. all Microsoft related services will be disabled
Then Click Disable all button this will disable all the third-party services.
Click Apply to all the change, and ok.
![Hide all Microsoft services](https://static.wixstatic.com/media/94d44a_fec533efa6e941c9ad0c1ed879407a99~mv2.jpg/v1/fill/w_571,h_385,al_c,q_80,enc_auto/94d44a_fec533efa6e941c9ad0c1ed879407a99~mv2.jpg)
Now open taskmanager, and move to startup tab,
Select each service one by one and click Disable button.
Finally restart your computer and check if the configuration system failed to initialize error message disappears.
Check your config file
Lets check if this error generated by the configuration files of microsoft framework.
Press Windows key + E to open file explorer,
Navigate to the following path. C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG
Right-click on the config file of the application of which the error occurs and select Edit (You can use Notepad++ for a clearer view of the config file instead of using the default notepad).
![address bar](https://static.wixstatic.com/media/94d44a_1fd5bb4362c14e62954b168263a8c1b1~mv2.png/v1/fill/w_693,h_217,al_c,q_85,enc_auto/94d44a_1fd5bb4362c14e62954b168263a8c1b1~mv2.png)
When the config file is open, check inside the configuration element, ensure the first child is configSections element.
![configSections](https://static.wixstatic.com/media/94d44a_5f31050bf42e4ccdacdb3239a011c10f~mv2.png/v1/fill/w_972,h_325,al_c,q_85,enc_auto/94d44a_5f31050bf42e4ccdacdb3239a011c10f~mv2.png)
If the error appears on your windows 10, the first child may probably isn’t configSections element inside the configuration element. Then you can remove the configuration element between <configuration> and <configSections>.
Save the changes on config file and close edit window. Check if the error still appears.
If nothing is working out for you, try to create a new local account on your computer and try to access the application again.
Also read:
Comments