I have a pretty customized profile.ps1 loaded in my %windir%\system32\windowspowershell\v1.0 path, however when I open a shell, $profile points to a file Microsoft.PowerShell_profile.ps1 profile (that doesn't even exist) from C:\Users\ap.first.last\Documents\WindowsPowerShell\
I've never seen this behavior before, and refreshing my knowledge on how profiles are handled in powershell has me confused why it's not respecting, and loading, my %windir% profile.
Can anyone with more insight offer any ideas as to why this is happening? If I move my custom profile.ps1 to that Documents path, even name it the same, it still doesn't load.
The only error messages I'm getting when loading the console are in reference to snap-ins trying to connect to old server names that are no longer valid, leading me to believe that it is somehow loading a "cached" version.