PowerShell ISE - Where are the default snippets after Win10 Upgrade?

So I've upgraded to Win10Pro 1803 17134.1, opened my trusty PowerShell ISE, pressed CTRL+J and nothing happens!? Even the Get-ISESnippet is not showing any results. I'm using the default snippets and don't have any custom snippets under my documents / PowerShell folder.

It seems to be related to OneDrive or Windows 10 update as both my Desktop and Laptop have the same problem.

According to JRV the same issue occurs on 1809 builds.

Link: https://social.technet.microsoft.com/Forums/en-US/47ded9fb-0501-4953-92cc-ef55dbf86fbe/powershell-ise-where-are-the-default-snippets-after-win10-upgrade?forum=winserverpowershell

Best Regards,
Glenn

$PSVersionTable

Name Value
---- -----
PSVersion 5.1.17134.1
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.17134.1
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

my "Ideas" is Powershell ISE should not crash.

https://github.com/PowerShell/PowerShell/issues/6846

teps to reproduce
Use Windows Powershell ISE on Windows Build 17134
Enter the name of any cmdlet, a dash, then press ctrl+Space.
Get-Help -[Ctrl+Space]
Expected behavior
Should show intellisense popup.
Actual behavior
Instead of an intellisense dropdown, a small dot appears.
Messagebox as follows, followed by closing:
---------------------------
Windows PowerShell ISE - Error
---------------------------
An unexpected error has occurred, and Windows PowerShell ISE must close.
---------------------------
OK
---------------------------
Running in the visual studio debugger shows two exceptions, one from Xaml (associated with the appearance of the dot) the other a NullReferenceException which appears to occur in the context of a timer.
If you break on the Xaml exception there is no nullreference exception presumably because of the loss of focus.
Environment data
OS Name Microsoft Windows 10 Pro
Version 10.0.17134 Build 17134
> $PSVersionTable

Name Value
---- -----
PSVersion 5.1.17134.1
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.17134.1
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
More information
Running outside the debugger, instead of the intellisense pop-up I see a tiny dot appear, then the messagebox appears.
Running ISE in the visual studio debugger I see this:
Exception thrown: 'System.ArgumentException' in WindowsBase.dll
'Assertive' is not a valid value for property 'LiveSetting'.

Exception thrown: 'System.Xaml.XamlObjectWriterException' in System.Xaml.dll
Initialization of 'Microsoft.VisualStudio.Language.Intellisense.Implementation.DefaultCompletionSetPresenter' threw an exception.
And:
Exception thrown: 'System.Xaml.XamlObjectWriterException' in System.Xaml.dll
Exception thrown: 'System.Windows.Markup.XamlParseException' in PresentationFramework.dll
Exception thrown: 'System.ArgumentException' in WindowsBase.dll
Exception thrown: 'System.Xaml.XamlObjectWriterException' in System.Xaml.dll
Exception thrown: 'System.Windows.Markup.XamlParseException' in PresentationFramework.dll
And:
Exception thrown: 'System.ComponentModel.InvalidAsynchronousStateException'

The example command given under "INVESTIGATING PIPELINE ERRORS" in the about_Pipelines help topic is incorrrect. the example situation is moving a registry entry from one key to another, in the example it's trying to move the entry "product" from the hklm:\software\mycompany\design registry key to the hklm:\software\mycompany\sales key. The second ("fixed") command at the end:

get-item -path hklm:\software\mycompany\design |
move-itemproperty -dest hklm:\software\mycompany\design -name product

should be:

get-item -path hklm:\software\mycompany\design |
move-itemproperty -dest hklm:\software\mycompany\sales -name product

I also think the source and destination seem switched or misplaced throughout that section of the topic, unrelated to the example error given for the purpose of that section (tracing an error in pipeline binding).

Jea causes an error when you choose 'Default' in SessionType.

Example of PSSC configuration file :
SessionType = 'Default'

PS E:\JEA> $userbase = Get-Credential
Enter-PSSession -ComputerName localhost -ConfigurationName JEASession1 -Credential $userbase
cmdlet Get-Credential at command pipeline position 1
Supply values for the following parameters:
Enter-PSSession : The term 'Measure-Object' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:2 char:1
+ Enter-PSSession -ComputerName localhost -ConfigurationName JEASession ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Measure-Object:String) [Enter-PSSession], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

When trying to join arrays of FileInfo objects, if the first array contains only one element, the following error occurs.

Method invocation failed because [System.IO.FileInfo] does not contain a method named 'op_Addition'.
At line:1 char:1
+ $stuff + $stuff1
+ ~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (op_Addition:String) [], RuntimeException
+ FullyQualifiedErrorId : MethodNotFound

It works as expected as long as the first array contains more than 1 element. See example below:

PS C:\Scripts> $stuff

Directory: C:\Scripts

Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 10/3/2016 2:01 PM 58 LaunchUpdateAllSubversionWorkingCopies.bat

PS C:\Scripts> $stuff1

Directory: C:\Scripts

Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 10/26/2016 1:19 PM 140 DropConnections.sql
-a---- 12/9/2010 4:51 PM 4362 TC50CopyBu.sql
-a---- 10/26/2016 10:04 AM 7355 TIMSCleanup.sql

PS C:\Scripts> $stuff1 + $stuff

Directory: C:\Scripts

Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 10/26/2016 1:19 PM 140 DropConnections.sql
-a---- 12/9/2010 4:51 PM 4362 TC50CopyBu.sql
-a---- 10/26/2016 10:04 AM 7355 TIMSCleanup.sql
-a---- 10/3/2016 2:01 PM 58 LaunchUpdateAllSubversionWorkingCopies.bat

PS C:\Scripts> $stuff + $stuff1
Method invocation failed because [System.IO.FileInfo] does not contain a method named 'op_Addition'.
At line:1 char:1
+ $stuff + $stuff1
+ ~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (op_Addition:String) [], RuntimeException
+ FullyQualifiedErrorId : MethodNotFound

The following error show up when executing 'Update-Help -force':
PS C:\WINDOWS\system32> Update-Help -Force
Update-Help : Failed to update Help for the module(s) 'NetworkControllerDiagnostics, Provisioning' with UI culture(s)
{en-US} : Unable to retrieve the HelpInfo XML file for UI culture en-US. Make sure the HelpInfoUri property in the
module manifest is valid or check your network connection and then try the command again.
At line:1 char:1
+ Update-Help -Force
+ ~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (:) [Update-Help], Exception
+ FullyQualifiedErrorId : UnableToRetrieveHelpInfoXml,Microsoft.PowerShell.Commands.UpdateHelpCommand

PS C:\WINDOWS\system32> $PSVersionTable

Name Value
---- -----
PSVersion 5.1.15048.0
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.15048.0
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

PS C:\WINDOWS\system32>

We started to use results from Get-DscConfigurationStatus in our monitoring (SCOM) and while analyzing the results we noticed that some partials are not showing up in the results of this command even though tests/set/get is performed on the target node. After analyzing different methods we found out that:

* MOF documents generated in C:\Windows\System32\Configuration\ConfigurationStatus seem to limit the results to ~40 last items in DSC configuration
* Get-DscConfigurationStatus and Test-DscConfiguration -Detail all use the same source of information, thus provide same, truncated output
* The only reliable source of information is details.json file generate when -Verbose output is requested, but information there is limited to only part of the info provided by MOF files and works only for interactive runs (when providing Verbose parameter is possible).

It looks to me like some sort of rolling-logs mechanism is used, but instead of keeping multiple files per run, final file is overwritten and thus only recent actions are recorded.