2 Replies Latest reply on Mar 31, 2018 10:24 AM by jbond

    RadeonSettings - Error on startup (0xc0000142)


      Hi community,


      for some time I now get this error message on each startup (see screenshot). ('Application could not be started correctly. (0xc0000142) )


      There are no further errors - and after the error message I am able to start Radeon Settings manually - only this error message is annoying.


      I already updated the Radeon software several times - also did a complete deinstall and new installation. But the error remains the same.


      Any ideas?





      Win10 (64bit)

      ADM Radeon R9-280x

      Radeon Software: Adrenalin 18.3.4

        • Re: RadeonSettings - Error on startup (0xc0000142)

          This links give some good tips on how to resolve the error. FIX: The application was unable to start correctly (0xc0000142) - Appuals.com


          But before you do that try this first:


          Try this basic method of uninstalling and reinstalling AMD Drivers.


          First download the correct Full AMD driver set from AMD Support for your GPU Card.


          Make sure your Windows 10 is fully updated via Windows Update (including Optionals).


          Disconnect the Internet from your computer to prevent it from installing a different GPU Driver than the one you are installing.


          Use Windows 10 Uninstall to uninstall all AMD Drivers and software. Then use DDU in safe mode to completely eliminate all traces of the old AMD drivers and software related to the GPU.


          Delete C:\AMD Folder. This prevents New and Old AMD driver files from installing and corrupting the installation process.


          After rebooting from DDU, Reinstall the new AMD Full set of drivers. If it installed correctly, again delete C:\AMD folder to save Hard Disk space and reconnect to the Internet.

          2 of 2 people found this helpful
          • Re: RadeonSettings - Error on startup (0xc0000142)

            Thanks - with DDU I did another "clean" reinstall... and now no more error.

            2 of 2 people found this helpful