SAPIEN Technologies

Currently, the only way I can reproduce this is if I use a path that has to be computed for the Assembly. For example: Add-Type -LiteralPath (Resolve-Path -Path .\MathLibrary.DLL) I've noted this and will be finding out if we can resolve this, but in the meantime, if I use something like the followi...

Awesome! I'm glad to hear that solved the problem

If you have any further issues, please don't hesitate to post again.

First, I'd like to point out that we're going to be modifying the registry so before continuing on it is best to make a backup that you can revert to in the case of an unforeseen mishap. That being said, here's a list of the keys we need to have removed ( NOTE: The value within the {} might be diffe...

Ah hah! In that case, I do believe I have a fix for this. We'll have to remove a few specific registry entries but it should solve the problem.

Let me track down the exact keys and I'll post them here in just a moment.

Quick follow-up as this reminds me of a previous issue we had:

Have you upgraded to 2017 then downgraded to 2016 at any point? Even if it was a simple uninstall and reinstall and you never executed any scripts.

Doing a quick look through the log, it's referring to the previous years' installation as opposed to the current year.

I'll speak with the team and look into this and get back as soon as I have some more information.

A couple follow-up questions to help diagnose what's going on here: Where are your scripts located? Are they on your local machine or are you accessing a file server of sorts? Does this happen in a regular PowerShell console or just within PowerShell Studio? What're your settings for your execution ...

I've managed to reproduce this on my end and have filed an internal bug report.

Thank you for bringing this to our attention. When I have some news to share, I'll be sure to post it here.

Hey froaderick, After speaking with the team, we believe the 2nd error you mention regarding The I/O operation... is more of a red herring and unrelated to the Cannot instantiate PowerShell V5... error. The 80070002 error states that a file is missing, and with the steps we've taken, we're positive ...

Hey OldLost,

I've heard back from the team and if you wish to add an assembly to a specific file, you must use the Add-Type cmdlet in that individual script.

If you wish for the entire project to have access, you would place the Add-Type cmdlet in your Startup.pss for the project.