Mod Activation Error


Error while activating mod 'Free Upgrades':
Sysyem.IO.FileNotFoundException: Could not load file or assembly 'Gibbed.Volition, Version=1.0.0.0, Culture=nuetral,
PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
File name:'Gibbed.Volition, Version=1.0.0.0, Culture=nuetral,
PublicKeyToken=null'

at ax.a(Stream A_0, String A_1, Boolean A_2)
at u.c(Stream A_0, String A_1)
at u.b(String A_0, String A_1)
at u.aa()

WRN: Assembly binding is turned OFF.
To enable assembly bind failure logging, set the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog]

I tried activating mods with mod manager and got this what can be done?

I'd say it looks like the gibbed files are missing. If you're running it right from the archive extract it first, or maybe your copy is busted and needs to be redownloaded

WTF means what the fuck. Case closed.

Sysyem.IO.FileNotFoundException
Could not load file or assembly
Version=1.0.0.0, Culture=nuetral, PublicKeyToken=null'
or one of its dependencies.

Indicates .net errors. Version 1.0.0.0 indicates that it was written in version 1.0. Usually newer versions of .net can run older programs. I don't know what versions the Mod Manager is dependent on.

There are a few versions of .net. It's basically a programming 'language' that M$ uses. They are up to version 4.6.x right now.

The Mod Manager files could be corrupt
The Game could be corrupt
The OS files could be corrupt
The .net binaries / settings could be corrupt

If there are no other issues with the system (sluggishness / crashes) then try these steps:

.net verification utility:
https://blogs.msdn.microsoft.com/astebner/2013/11/06/net-framework-setup-verification-tool-and-cleanup-tool-now-support-net-framework-4-5-1/

Make sure that comes back happy for all versions that it finds installed. If it does, either download the Mod Manager again, and run the new copy, or try your copy on another machine.

If it doesn't come back happy ('verification failed') then try the cleanup utility on the same page, and reinstall whatever version was removed:

https://blogs.msdn.microsoft.com/astebner/2008/08/28/net-framework-cleanup-tool-users-guide/

There was an issue once with 1.0 on XP I believe that forcibly removing it with that cleanup utility caused issues. The procedure for me, now is to download the relevant offline (full) installer, before running the cleanup utility against the problem version. Then re-installing the downloaded version before restarting the system. Some versions are builtin to windows:

https://msdn.microsoft.com/en-us/library/bb822049%28v=vs.110%29.aspx?f=255&MSPPError=-2147217396

If you have to reinstall .net then its a good idea to run windows update afterwards for minor bugfixes, and security patches.

If it still throws errors, try:
Verifying the game with Steam (if a steam game)
Verifying the file system with Windows (C: drive, or 'Boot' partition, and the drive where RF:G, and the mod manager are on.

chkdsk C: /F (fixes errors)
chkdsk C: /R (recovers data from bad sectors)
chkdsk C: /B (rescans bad sectors)

Each one of these is more thorough, and takes longer than the last one. All will require a reboot (for the C: drive). I have had checkdisk fail multiple times in a row before it finally succeeded. If you run 'chkdsk' by itself, and it pronounces the disk clean, don't believe it. Even if the error is fixed. Typically I will do 'chkdsk /b', and just let it run. /b may take a couple of hours depending on drive size, and SSD, or HDD.

If you need to use checkdisk it is worth checking the Windows Event Viewer for Storage Controller / Disk Errors
CompMGMT.msc > Event Viewer > Windows Logs > System (select those under: Right Click 'System' Log > Filter Event Log > Click the Drop Down menu for 'Event sources' > Select at least: disk, Disk

The disk number here should correlate to the numbers under Storage > Disk Management.

These group of Event sources are also related to the storage subsystem (not all are active, it is driver & feature dependent):

iaStorA
IAStorDataMgrSvc
iaStorV
megasas
MegaSR
Sdstor
SiSRaid2
SiSRaid4
StorageSpaces-Driver
StorageSpaces-ManagementAgent
storahci
storflt
StorPort
StorSqm
storvsc
storvsp

Verifying the system binaries with system file checker (sfc.exe /scannow). Usually this one is a waste of time (it verifies signed files match their signature), and those usually aren't the problem.

If still having issues run memtest x86 to test memory. I usually let it run for over a day on a suspect machine:

Ultimate Boot CD (Contains memtest, sometimes there are 'kernel panic' issues):
http://www.ultimatebootcd.com/

memtest:
http://www.memtest86.com/

Intel Processor Diagnostic Utility:
https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool

If running an AMD processor the best you can do is StressCPU, or Prime95. StressCPU is bundled in the UBCD as well.

Finally you can also test the graphics card using Furmark. They have some other good tools as well:
http://www.ozone3d.net/benchmarks/fur/

All of these tools can run continuously, but shouldn't be left unattended, generally the worst that will happen is a Blue Screen, Hard Hang, or Thermal Shutdown.