Cannot instantiate PowerShell V5 object
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
- Alexander Riedel
- Posts: 8479
- Last visit: Thu Mar 28, 2024 9:29 am
- Been upvoted: 37 times
Re: Cannot instantiate PowerShell V5 object
Please select PowerShell V5 in the ribbon and see if that works.
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
- darkprofit
- Posts: 15
- Last visit: Tue Jan 07, 2020 5:45 am
Re: Cannot instantiate PowerShell V5 object
Nope same issue this time it says "Cannot instantiate PowerShell V5 object: 80070002>> Script Ended"
Script is write-host "Test."
Script is write-host "Test."
- Alexander Riedel
- Posts: 8479
- Last visit: Thu Mar 28, 2024 9:29 am
- Been upvoted: 37 times
Re: Cannot instantiate PowerShell V5 object
80070002 means "File not found".
So that means that either the dll you previously registered successfully is no longer there (check please)
or that you selected 32 bit instead 64 bit since you only re-registered the 64 bit part
or, more likely, one of the dependencies is missing or corrupt.
https://github.com/isindicic/DependencyWalker.Net
This might help you determine what disappeared from your system. It is pretty rare but on occasion a .NET framework installation gets corrupted.
So that means that either the dll you previously registered successfully is no longer there (check please)
or that you selected 32 bit instead 64 bit since you only re-registered the 64 bit part
or, more likely, one of the dependencies is missing or corrupt.
https://github.com/isindicic/DependencyWalker.Net
This might help you determine what disappeared from your system. It is pretty rare but on occasion a .NET framework installation gets corrupted.
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
- darkprofit
- Posts: 15
- Last visit: Tue Jan 07, 2020 5:45 am
Re: Cannot instantiate PowerShell V5 object
I'll try that. Soon I will be reimaging the machine that should take of the issue.