Any exception causes prompt to silently fall back to default

[dkaszews]

I have spent some time trying to diagnose why the module does not work on my new system, until I run prompt manually and saw it throw an exception "hostname is not recognized as a name of cmdlet or executable". Since it appears that PowerShell will silently fall back to default prompt PS> on any exception, it might be worth to wrap it in try-catch to provide some feedback to the user. In my case I just had to install missing inettools package, but it took me some time to figure out that is the root cause.