Configuration system failed to initialize on Windows 10 [Solved]

By April Cai in Common Errors Tags: Windows 10



Some users reported that Configuration system failed to initialize error appears on their Windows 10. It happened when they run a newly installed app or run an app after adding a web service to it. If you are reading this article, it’s very likely you also face such error. Not to worry. Right here, this guide will be telling you the effective methods to fix it.

Try one at a time:

  1. Run System File Checker tool 
  2. Check your config file
  3. Delete the old config file

Fix 1: Run System File Checker tool


Corruptions in Windows system files can cause Configuration system failed to initialize error. Thus we can run System File Checker tool to check and fix the error.

1)  On your keyboard, press the Windows logo key  + X key at the same time to open the quick access menu.

2)  Click Command Prompt(Admin) to run Command Prompt as administrator.

Click Yes when prompted by User Account Control.

3) On the command prompt window, type sfc /scannow and hit Enter. Wait for it till Verification 100% Complete.



System File Checker will help you restore the corrupted files automatically.

4) When it’s done, close the command prompt window. Check if the error still exists.

Fix 2: Check your config file


Make sure inside the configuration element of your config file, the first child is configSections element.

1) On your keyboard, press the Windows logo key  and at the same time to open the File Explorer.

2) Go to C: Windows \ Microsoft.NET \ Framework64 \ v2.0.50727 \ CONFIG.



3) Right-click on the config file of the app which exist the error. Choose Edit. ( we recommend you use Notepad++.to modify )



4) When the config file is open, check inside the configuration element, ensure the first child is configSections element.



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>.

5) Save the changes on config file and close edit window. Check if the error still appears.

Fix 3: Delete the old config file

1) On your keyboard, press the Windows logo key  and at the same time to open the File Explorer.

2) Go to C: \ Users \ username \ AppData \ Local \ appname and delete the app config file.

3) Go to C: \ Users \ username \ AppData \ Roaming \ appname and delete the app config file.

4) Restart your app and check if the error still occurs.


  • Osthman Zain

    I’m trying now…thanks

  • Ananda the Programmer

    Awesome Solution…. thanks a lot…. you saved a me a lot time …!
    keep it up.. 🙂

  • Calvin Cedarleaf

    go to uninstall programs and look for anything from Lavasoft as the publisher. Could be “web companion”, “ad adware”, etc. Delete these programs. Restart and you should be good to go.

    • UnEthicalDemon

      MVP Thank you!

  • Steve Kiley

    I just did the sfc /scannow.
    The log file shows hundreds of errors, which have been repaired.
    I have been running Windows Insider Preview for quite a while.
    Yesterday my PC crashed 3 times with a green screen of death after an upgrade on 17th August.
    I decided to restore the previous version, and so far so good.
    Why on earth do we have to run commands to do what Microsoft should be doing automatically when installing new software?

  • April Cai

    Hi, dulla
    Because Configuration system failed to initialize could happen varies on the different apps by different users. In No.3 please locate the one you faced the error with please.

    • octa fadhila

      Excuse me, why if the error when you first start windows ? What appname me errased ?

  • Dorado

    i have this error on windows 8. when the windows runs, this error appear
    . how can i fix it. thank you

  • Jito463

    The third option – deleting the config file – fixed the problem for me on Windows 7. Though in my case it was only under Local Appdata, so you may want to clarify that it’s either/or. In any event, thanks for posting this. The last time it happened I was unable to find any information on the error and resorted to a fresh install of Windows. This saved me a lot of hassle.

    Having said that, the second option is not very clear.

    “Then you can remove the configuration element right below configuration dialog.”

    Even as a computer tech by trade, I find that confusing. Do you mean to delete just the ConfigSections portion? To delete everything under ConfigSections? The whole thing completely? Regardless, I didn’t need it fix my problem, but you may want to correct it for others in the future.

    • April Cai

      Thanks for your feedback. Glad that the third option helps you.
      I also feel so sorry that it made you confused. And I have revised it. Thank you.