a few months ago I wrote about my problem with "Faulting module jsc.ni.dll" (https://support.jaksta.com/support/discussions/topics/6000046189). As I figured out this is easily avoidable by either deleting/renaming "jsc.dll" (Jaksta will still work fine without it) or by not choosing "Optimize for your system" during installation, which causes the installer not to install it at all.
So far so good.
Now I noticed that, when you update an older version of Jaksta to a newer one, the installer does not let you choose what options to install or not and does the optimization no matter what you chose for your original installation. So in my case, not having chosen "Optimize for your system" and therefore not having jsc.dll the update caused jsc.dll to be installed and to cause problems again.
Just reporting to help make Jaksta better. No help needed. Thanks.
Sorry you are disappointed with my answer. I have been developing Jaksta and RMC since 2008, so am well aware of the many different issues that different computers can cause applications. :)
jsc.dll is the main stream capture assembly. The fact that not optimising means it JMR still works means there is not an issue with the assembly itself, but with the optimised one generated by your computer. ni.dll files are native images created by the optimise process. Why that is crashing is not possible for me to tell. Possibly AntiVirus is blocking them being loaded?
Are you saying, that using the uninstall/reinstall with the "Delete any existing Settings/Library" unchecked, actually deletes your settings and library? If so then please provide debug logs as as per https://www.jaksta.com/support/windows/technical/jaksta-media-recorder/how-to-generate-debug-logs-6000009063
I'm a little disappointed about this kind of answer. I'm using Jaksta since like forever, even had RMC for example. We, although ofc I don't know if you are the same person, even used to discuss things via email.
Does it really matter what exactly happens behind the optimization process? The result is having jsc.dll which, at least in my case, causes problems. Not matter if the file is created by .NET or Jaksta itself. Maybe jsc.dll causes a problem for more people instead of just me. They might just not be experienced to find the root cause.
Oh and ofc I know that uninstalling first and then reinstalling without said option avoids the problem. But do you seriously expect a user to reconfigure all the settings every time? Why can't Jaksta just obey the option(s) chosen during original installation?
Anyways, I'm sorry for trying to help. It won't happend again.
As mentioned in your other post - jsc.ni.dll is generated by windows for .net applications, and something is wrong with your computer generating that assembly.
If you don't want to run the optimizer then select "Uninstall first, and then reinstall", instead of the in place upgrade. Then uncheck the optimization option on the install. You don't need to remove your settings & library as part of this.