Test failures: System.Diagnostics.Tests.ProcessStartInfoTests on windows.11.amd64.clientpre #60191

Activity

1. ghost added

   area-System.Diagnostics.Process

   on Oct 8, 2021
2. ghost added

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Oct 8, 2021
3. jeffhandley

   added

   needs-further-triageIssue has been initially triaged, but needs deeper consideration or reconsiderationIssue has been initially triaged, but needs deeper consideration or reconsideration

   and removed

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Oct 9, 2021
4. jeffhandley

   added this to the Future milestone on Oct 9, 2021
5. am11 commented on Oct 16, 2021

   

   am11

   on Oct 16, 2021

   Member

   More actions

   --- a/src/libraries/System.Diagnostics.Process/tests/ProcessStartInfoTests.cs
   +++ b/src/libraries/System.Diagnostics.Process/tests/ProcessStartInfoTests.cs
   @@ -1318,7 +1318,7 @@ private void VerifyNotepadMainWindowTitle(Process process, string filename)
                string expected = Path.GetFileNameWithoutExtension(filename);
   
                process.WaitForInputIdle(); // Give the file a chance to load
   -            Assert.Equal("notepad", process.ProcessName);
   +            Assert.Equal("notepad", process.ProcessName, ignoreCase: true);
   
                // Notepad calls CreateWindowEx with pWindowName of empty string, then calls SetWindowTextW
                // with "Untitled - Notepad" then finally if you're opening a file, calls SetWindowTextW

   while this will fix the assertion failure. As to the reason for the difference, it could be:

   • it is spelled as Notepad.exe under system32 on that particular machine or generally on that version of windows?

   • the underlying Win32 API, NtQuerySystemInformation's documentation seem to provide no version-to-version compatibility guarantees:

     NtQuerySystemInformation may be altered or unavailable in future versions of Windows. Applications should use the alternate functions listed in this topic.

     Issue 55685 processname optimisation #59672 is changing ProcessName to use QueryFullProcessImageName which may (or may not) return the lower case on Windows 11. If someone with rights can run outerloop pipeline on that PR, we will find out.

   • something else?
6. dotnet-policy-service commented on Apr 17, 2026

   

   dotnet-policy-serviceBot

   on Apr 17, 2026 – with Dotnet Policy Service

   Contributor

   More actions

   Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

   This process is part of our issue cleanup automation.
7. dotnet-policy-service

   added

   backlog-cleanup-candidateAn inactive issue that has been marked for automated closure.An inactive issue that has been marked for automated closure.

   no-recent-activity

   on Apr 17, 2026