Fatal CLR Error 80004005
Posted: Wed Jun 17, 2015 11:04 am
I wish to share how I fixed a problem that didn´t allow me connect to the game.
First of all, my computer is running Windows 7
When I was starting from the regular launcher, I got CLR Error: 80004005. I've tracked down the problem, and I can get it to work If i make a clean swipe and remove .NET and reinstall it without rebooting. Then is supposed to work fine, but as soon as I hit windows update, it prompts me to do a couple of security updates for .NET, and then I was back to it not working again. I tried tons of different methods for removing and re installing.
My Solution: Go to "C:\Windows" and right click on the "Microsoft.NET" folder and click Properties. Click the "Security" Tab, then click the "Advanced" button. Click the "Owner" Tab, then click the "Edit..." button. Select your current user account, then check the box that says "Replace owner on subcontainers and objects" and then click "Ok".
Problem solved (for now at least). As it turns out, the programs simply didn't have the proper permissions needed to run.
Wish it can be useful for more people like it was for me.
First of all, my computer is running Windows 7
When I was starting from the regular launcher, I got CLR Error: 80004005. I've tracked down the problem, and I can get it to work If i make a clean swipe and remove .NET and reinstall it without rebooting. Then is supposed to work fine, but as soon as I hit windows update, it prompts me to do a couple of security updates for .NET, and then I was back to it not working again. I tried tons of different methods for removing and re installing.
My Solution: Go to "C:\Windows" and right click on the "Microsoft.NET" folder and click Properties. Click the "Security" Tab, then click the "Advanced" button. Click the "Owner" Tab, then click the "Edit..." button. Select your current user account, then check the box that says "Replace owner on subcontainers and objects" and then click "Ok".
Problem solved (for now at least). As it turns out, the programs simply didn't have the proper permissions needed to run.
Wish it can be useful for more people like it was for me.