[Bug 54020] New: The 32-bit ntdll:wow64 fails on Windows 11

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=54020

Bug ID: 54020
           Summary: The 32-bit ntdll:wow64 fails on Windows 11
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Windows
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ntdll
          Assignee: [e-mail]
          Reporter: [e-mail]

The 32-bit ntdll:wow64 fails on Windows 11:

wow64.c:254: Test failed: wrong len 0
wow64.c:255: Test failed: wrong teb 0000004C / 00000000
wow64.c:258: Test failed: GdiBatchCount not set
wow64.c:282: Test failed: wrong peb 00000000 / 00000002
wow64.c:285: Test failed: wrong len 0
wow64.c:295: Test failed: wrong len 0
wow64.c:301: Test failed: wrong ImagePathName ptr 00000000 / 00000000-00000000
wow64.c:302: Test failed: wrong CommandLine ptr 00000000 / 00000000-00000000
wow64.c:303: Test failed: wrong WindowTitle ptr 00000000 / 00000000-00000000
wow64.c:304: Test failed: wrong Desktop ptr 00000000 / 00000000-00000000
wow64.c:305: Test failed: wrong ShellInfo ptr 00000000 / 00000000-00000000
wow64.c:331: Test failed: debugging failed
wow64.c:333: Test failed: wrong len 0
wow64.c:460: cs 0023 ss 002b fs 0053
wow64.c:782: Test failed: unknown module 7ffb1ed00000 L"wow64base.dll" found
wow64.c:782: Test failed: unknown module 7ffb20100000 L"wow64con.dll" found

See https://test.winehq.org/data/patterns.html#ntdll:wow64

The values are pretty stable from one run to the next but do change from time
to time (causing false positives). Note also that the 64-bit version fails on
Windows 11 too but the failures there are pretty different (see bug 54019).

[Bug 54020] The 32-bit ntdll:wow64 fails on Windows 11

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=54020

François Gouget  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |source, testcase

[Bug 54020] The 32-bit ntdll:wow64 fails on Windows 11

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=54020

--- Comment #1 from François Gouget  ---
The first set of failures (lines 254 to 460) happen in test_peb_teb() which
uses "C:\windows\syswow64\notepad.exe" as a test subject. So this may be
related to bug 54504: this path is now remapped to a 64-bit executable instead
of being a 32-bit one.

The last two failures are in test_modules() and have been fixed (commit
bf48ebf2a477).

[Bug 54020] The 32-bit ntdll:wow64 fails on Windows 11

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=54020

François Gouget  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
      Fixed by SHA1|                            |de3ecada243b6cf5fc65afc8963
                   |                            |4142a8de76401
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from François Gouget  ---
This is fixed:

commit de3ecada243b6cf5fc65afc89634142a8de76401
Author:     Eric Pouech 
AuthorDate: Tue Feb 21 17:34:55 2023 +0100

ntdll/tests: Use msinfo32.exe instead of notepad.exe.

Under Windows 11, notepad.exe has been migrated into the UWP framework,
    and can no longer be launched as a 32bit process:
    - even if c:\windows\syswow64\notepad.exe is still a 32 bit PE file
    - the process created from c:\windows\syswow64\notepad.exe is not a
      wow64 process.

So use msinfo32.exe instead. Like notepad.exe, it's a gui application,
    present on Wine and all test-bot:ed windows platforms. But unlike
    notepad.exe, it's not an UWP app on Windows 11.

Signed-off-by: Eric Pouech

[Bug 54020] The 32-bit ntdll:wow64 fails on Windows 11

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=54020

Alexandre Julliard  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #3 from Alexandre Julliard  ---
Closing bugs fixed in 8.4.