RuneApps forums

pekempy

Member

Registered: 2018-02-17

Posts: 1

Standalone .dll error

When launching Standalone on certain PCs (specs of one), it fails to launch. Below are the error messages:

Alt1 error report
Version: 1.4.5
The type initializer for '<Module>' threw an exception.
The C++ module failed to load during appdomain initialization.

   at Runeapps.Alt1.IconManager._SetIcon()

   at Runeapps.Alt1.IconManager.SetIcon()

   at Runeapps.Alt1.IconManager.StartUp()

   at Runeapps.Alt1.Alt1ApplicationContext.Startup(Object pointlessarg1, EventArgs pointlessarg2)

   at 

Going to try reinstalling Visual C++ Redistributable & .NET and report back, posting this in case it doesn't work/for others that may have the issue

1. Reinstalled Vis C++ Redist
2. Tested Alt-1 Unsuccessful
3. Repaired .NET 4.7.1
4. Tested Alt-1 Unsuccessful
5. Re-downloaded Alt-1 Standalone v1.4.5
6. Tested Alt-1 Unsuccessful

Last edited by pekempy (2018-02-17 14:56:43)

De Karma Knecht

Guest

Re: Standalone .dll error

I got the exact same error (MSVCP120_CLR0400.dll as well) and read through some other posts. I did the same thing as the user above me did (reinstalling C++, uninstalling older .NET software and installing the newest one) and I still get the same error. I'm absolutely clueless on what to do though would love to use Alt 1 because of its useful clue function. I wonder if the OP found a solution now or if someone else is able to help out.

DBC

Guest

Re: Standalone .dll error

Ditto the error above Win 10 thank you

Alt1 error report
Version: 1.4.5
The type initializer for '<Module>' threw an exception.
The C++ module failed to load during appdomain initialization.

   at Runeapps.Alt1.IconManager._SetIcon()

   at Runeapps.Alt1.IconManager.SetIcon()

   at Runeapps.Alt1.IconManager.StartUp()

   at Runeapps.Alt1.Alt1ApplicationContext.Startup(Object pointlessarg1, EventArgs pointlessarg2)

   at

Skillbert

Administrator

Registered: 2014-12-30

Posts: 1,061

Re: Standalone .dll error

I'll check this out before the next release. I'm suspecting that the dll file is outdated. For normal .NET installations this file isn't necessary however a different version of this problem came up earlier and it was fixed by adding that dll for people that don't have it.