If you experience Invalid Class [0x80041010] when starting SQL Server Configuration Manager, see Michael Aspengren’s MSDN Blog Post for the solution. This solution fixes the original issue, but then you are presented with a second issue: Provider load failure [0x80041013].
To fix the Provider load failure [0x80041013] issue, locate your SQL Server installation medium. In my case I am using SQL Server 2016 Developer Edition. Then run sql_common_core.msi, which in my case is located as follows: en_sql_server_2016_developer_x64_dvd_8777069\x64\Setup\sql_common_core_msi\sql_common_core.msi. Note: You will need to run this installation as an administrator in order for it to install. So open a command prompt as administrator, and then type msiexec /i sql_common_core.msi and press enter. You should find that you can now open SQL Server Configuration Manager 2016.