You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running ScubaGear on a virtual machine that is configured with \\UNC file paths instead of the standard C:\ I received the error message "Cannot bind to parameter 'InputObject' because it is null" and "The specified path is invalid." It also shows a path that starts with "Microsoft.Powershell.Core\FileSystem::\\xenprofile10" and based on my debugging the prefix before the "\\" is what was causing the problem. I doubt that this configuration is common in the wild because we haven't had a bug report about this before, but the fix is easy so we can correct it with little effort.
Screenshots
The fix
Screenshot of the code that is the root cause in ScubaConfig.psm1 (notice the Path field)
To fix this change the Path field to ProviderPath and then the DefaultOutPath won't have that Microsoft.Powershell funny business in front of it anymore.
The text was updated successfully, but these errors were encountered:
🐛 Summary
When running ScubaGear on a virtual machine that is configured with \\UNC file paths instead of the standard C:\ I received the error message "Cannot bind to parameter 'InputObject' because it is null" and "The specified path is invalid." It also shows a path that starts with "Microsoft.Powershell.Core\FileSystem::\\xenprofile10" and based on my debugging the prefix before the "\\" is what was causing the problem. I doubt that this configuration is common in the wild because we haven't had a bug report about this before, but the fix is easy so we can correct it with little effort.
Screenshots
The fix
Screenshot of the code that is the root cause in ScubaConfig.psm1 (notice the Path field)
To fix this change the Path field to ProviderPath and then the DefaultOutPath won't have that Microsoft.Powershell funny business in front of it anymore.
The text was updated successfully, but these errors were encountered: