Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
NOT paging in ISE but am getting that same error RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I am getting the same error reported in all the discussions about how stupid it is that paging works in the powershell console but not in the ISE, that is, 

    out-lineoutput : The method or operation is not implemented.
    + CategoryInfo          : NotSpecified: (:) [out-lineoutput], NotImplementedException
    + FullyQualifiedErrorId : System.NotImplementedException,Microsoft.PowerShell.Commands.OutLineOutputCommand

    The thing is, this worked until a few weeks ago. And I am not using paging, I promise!

    The line that is probably causing the problem is likely to be `New-Item -Path $NewPath1 -ItemType "directory"`. $NewPath1 expands to a path/filename that is valid and does not currently exist. And the corresponding line works in the regular console. The new directory is created by the cmdlet, before the "not implemented" error is thrown. I've tried (briefly) looking to see if I can figure out whether it is the New-Item cmdlet that got corrupted in a recent update (I'm using Insider Preview 18334) and whether it is possible to restore the functionality without reverting to the release version of Windows but haven't gotten very far.

    So -- is this something new in Powershell ISE in the insider's preview? Or is my install messed up somehow, or some other change on the system is causing ISE to barf?

    • Moved by Bill_Stewart Friday, March 15, 2019 8:06 PM This is not "break/fix" forum
    Tuesday, February 12, 2019 8:29 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    You will have to ask this question in the preview forum.  The issue is not present in standard ISE. 

    I suspect that you have installed an old abandoned copy of a preview.  I suggest uninstalling it and using the distributed version of ISE.

    \_(ツ)_/

    Tuesday, February 12, 2019 8:57 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Also  note that the ISE "Preview" was released more than 3 years ago and is not usable on current versions of PowerShell.

    Release date of preview: "<time class="entry-date published" datetime="2016-01-20T11:22:00+00:00">January 20, 2016"</time>

    <time class="entry-date published" datetime="2016-01-20T11:22:00+00:00">The distributed version of ISE already has all of the preview components.  Microsoft seems to no longer be updating ISE since the release of WMF 5.1 and is not likely to continue with it until a community version is available.  For a more sophisticated visual code editor you can switch to VSCode.</time>

    <time class="entry-date published" datetime="2016-01-20T11:22:00+00:00"></time>

    \_(ツ)_/

    Tuesday, February 12, 2019 9:01 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    So thanks for the reply, I think.

    I don't remember installing a "preview" of ISE that is separate from the standard distribution, and there is no option I can find in the Powershell_ISE menus to learn its version, but the file properties dialog says that it is 10.0.18334.1, which implies to me that it is, or soon will be, part of the 19H1 Windows 10 release, which is getting finishing touches for release in a few weeks. (18334 is the most recent Insider Preview, announced on February 8, and it is installed as a package, not as individual packages, so this ISE is what comes with it.) So instead of telling me to go to the (non-existent, as far as I can tell) forum for an abandoned preview, how about thinking of this as an advanced question that everyone will face in a few weeks, whether or not they are part of Insider Preview for Windows 10 (not for just Powershell), except for those using Powershell Core. 

    The question I asked is, am I seeing a "feature" of the Powershell_ISE that will be the release version in a few weeks? If not, how do I troubleshoot? Surely someone at Microsoft will know if this represents a change to the Powershell package that is included with all the standard Windows 10 installs that everyone is supposed to be seeing in a few weeks, or if it's a glitch in the 18334 release to be fixed shortly, or if it is more likely to be something with my machine.

    I'm mostly just asking where to start with troubleshooting.

    If Powershell_ISE is being deprecated, why is it included in 19h1? If I need its version number to troubleshoot, how do I find it? $PSVersionTable isn't working in the ISE (same error):

    > $PSVersionTable

out-lineoutput : The method or operation is not implemented.
    + CategoryInfo          : NotSpecified: (:) [out-lineoutput], NotImplementedException
    + FullyQualifiedErrorId : System.NotImplementedException,Microsoft.PowerShell.Commands.OutLineOutputCommand

    From the regular powershell console which also shows file version 10.0.18334.1, that results in 

    > $PSVersionTable

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




    • Edited by M Cook Wednesday, February 13, 2019 1:29 PM
    Wednesday, February 13, 2019 1:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Please, this forum is about SCRIPTING. You obviously have a problem with your system. We cannot help you here with your problem. This is a peer to to peer forum about scripting.

    If you're using a Windows installation of the insider program you should contact Microsoft. I'd reccommend reinstalling Windows to have a fresh system with a defined and clean state.

    Live long and prosper!

    (79,108,97,102|%{[char]$_})-join''

    Wednesday, February 13, 2019 1:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I read in one of your posts that you were using the preview version.  Your information posted last indicates the correct version.

    I can only recommend doing a system repair as a solution.

    I also see that your version looks like you are running an insider preview version of Windows 10. If that is the case then you will need to report it to the appropriate insider forum.

    The current version on current Windows 10(1809) is "5.1.17763.316".

    I would still recommend a system repair.

    One possibility can also be a bad module in your module path.  Try running "Get-Command on the faulty command to see where it is coming from.

    \_(ツ)_/

    Wednesday, February 13, 2019 5:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The get-command as requested:

    > get-command New-Item

out-lineoutput : The method or operation is not implemented.
    + CategoryInfo          : NotSpecified: (:) [out-lineoutput], NotImplementedException
    + FullyQualifiedErrorId : System.NotImplementedException,Microsoft.PowerShell.Commands.OutLineOutputCommand

    Get-Command sounded promising, but as you can see, the same problem exists with that cmdlet. When I run it in the plain PS console, I get 

    C:\Users\user                                                                                                    
λ  get-command New-Item                                                                                            
                                                                                                                   
CommandType     Name                                               Version    Source                               
-----------     ----                                               -------    ------                               
Cmdlet          New-Item                                           3.1.0.0    Microsoft.PowerShell.Management      
                                                                                                                   
                                                                                                                   
C:\Users\user                                                                                                     
λ  get-command get-command                                                                                         
                                                                                                                   
CommandType     Name                                               Version    Source                               
-----------     ----                                               -------    ------                               
Cmdlet          Get-Command                                        3.0.0.0    Microsoft.PowerShell.Core

    Is it common for cmdlets in the base distribution to be different versions?

    I take it from the comments here that Microsoft hasn't warned anyone here about a change to Powershell ISE like this that is coming in a few weeks, so maybe we can be hopeful that this is just a glitch in the Preview and it will get fixed or reverted by release. 

    I did report this in the Feedback Hub, and there are a number of others who have also reported this error. So far no response from Microsoft.

    Thursday, February 14, 2019 8:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    It appears that you are trying to run PowerShell Core.  Remove that form you system and try again.  GThe W10 and WMF 5.1 versions can only use the base commands as the first item:

    PS D:\scripts> get-command New-Item

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Cmdlet          New-Item                                           3.1.0.0    Microsoft.PowerShell.Management


PS D:\scripts>

    You can also look to see where the module is being loaded from like this:

    Get-Module Microsoft.PowerShell.Core | select path

    That path should not be in your $env:psmodulepath

    \_(ツ)_/

    Thursday, February 14, 2019 9:07 PM