Does the machine you are running on have FIPS turned on?

We had problems with registering Stimulsoft 2017.1 on FIPS machines because the encryption algorithm being used for the key is not FIPS-Compliant. Looks like the same error we got.

Ok, worked around that problem by hosting the winforms version in WPF with the <winformshost> provision, and now printing works in windows 10, BUT We use FIPS and when I try to register the license key on a FIPS-enabled windows 10 machine, I get the following: System.Reflection.TargetInvocationExcep...

It seems to work properly when we let stimulsoft open its own viewer window, but when showing in the StiViewerControl it behaves differently. Why would this be?

My network will not allow access to file sharing services.

Test case attached

Symptoms are:
Windows 7: prints properly except for print to pdf produces a corrupted file.

Windows 10: with a directly attached printer, will produce printed output on windows 10 but headers are cut off
with a network printer, produces no output. Print to pdf produces a corrupted file.

The test case (test case 2 .zip) is back on page one of this thread

Thank you very much.. we appreciate it.

Aleksey Andreyanov was handling the issue, but told me that XBAP was as-is. Can you please help?

Done.