Skip to content

PowerShell v6.1.0-preview.4: Broken output for Get-ChildItem #7353

@hrxn

Description

@hrxn

Steps to reproduce

Simply run ls -Force in your usual Home-directory (i.e. C:\Users\Hrxn, for example)...

ls -fo

Expected behavior

Output (snipped)

    Directory: C:\Users\Hrxn


Mode                LastWriteTime         Length Name                                                                                                                                                  
----                -------------         ------ ----  
[....]
-a----       29.11.2015     15:39            265 lynx.cmd                                                                                                                                              
-a-h--       25.07.2018     01:59       16515072 NTUSER.DAT                                                                                                                                            
-a-hs-       03.05.2018     06:57        2949120 ntuser.dat.LOG1                                                                                                                                       
-a-hs-       03.05.2018     06:57        3145728 ntuser.dat.LOG2                                                                                                                                       
-a-hs-       03.05.2018     06:57          65536 NTUSER.DAT{91ed9ba6-4e96-11e8-a51f-00224d878c36}.TM.blf                                                                                               
-a-hs-       03.05.2018     06:57         524288 NTUSER.DAT{91ed9ba6-4e96-11e8-a51f-00224d878c36}.TMContainer00000000000000000001.regtrans-ms                                                          
-a-hs-       03.05.2018     06:57         524288 NTUSER.DAT{91ed9ba6-4e96-11e8-a51f-00224d878c36}.TMContainer00000000000000000002.regtrans-ms                                                          
---hs-       03.05.2018     07:03             20 ntuser.ini                                                                                                                                            
-arhs-       03.05.2018     07:03            426 ntuser.pol                                                                                                                                            
-a----       30.09.2016     20:26            821 SciTEUser.properties
[....]

Actual behavior

Output (snipped)

    Directory: C:\Users\Hrxn


Mode                LastWriteTime         Length Name
----                -------------         ------ ----
[....]
-a----       29.11.2015     15:39            265 lynx.cmd
             25.07.2018     01:59       16515072 NTUSER.DAT
             03.05.2018     06:57        2949120 ntuser.dat.LOG1
             03.05.2018     06:57        3145728 ntuser.dat.LOG2
             03.05.2018     06:57          65536 NTUSER.DAT{91ed9ba6-4e96-11e8-a51f-00224d878c36}.TM.blf
             03.05.2018     06:57         524288 NTUSER.DAT{91ed9ba6-4e96-11e8-a51f-00224d878c36}.TMContainer00000000000000000001.regtrans-ms
             03.05.2018     06:57         524288 NTUSER.DAT{91ed9ba6-4e96-11e8-a51f-00224d878c36}.TMContainer00000000000000000002.regtrans-ms
---hs-       03.05.2018     07:03             20 ntuser.ini
-arhs-       03.05.2018     07:03            426 ntuser.pol
-a----       30.09.2016     20:26            821 SciTEUser.properties
[....]

As you can probably see, the output is somewhat garbled.
The Mode/Attributes for some files are missing, when it should be -a-hs-. Seems like some rendering issue.
Running v6.1.0-preview.4 in Administrator Mode exhibits the same behavior.

Environment data

> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.1.0-preview.4
PSEdition                      Core
GitCommitId                    6.1.0-preview.4
OS                             Microsoft Windows 10.0.17134 
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

NB: The Expected Behavior / Working Output was done with the OS Powershell (PSVersion 5.1.17134.165)

OS info:

Windows 10 Pro
1803

OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.17134 N/A Build 17134

Would be interesting to know if someone can reproduce...

PS:
I don't even know what these files are.. probably not important anymore?

Metadata

Metadata

Assignees

Labels

Issue-BugIssue has been identified as a bug in the productResolution-FixedThe issue is fixed.WG-Engine-Providersbuilt-in PowerShell providers such as FileSystem, Certificates, Registry, etc.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions