Exception in pocc.exe

[dezmand07]

Hello. I found a bug in the pocc.exe compiler.
In Windows 11 23H2 (build 23631) compilation is fine.
But in Windows 11 24H2 (build 26100) the error is 0xC0000005


The exception in pocc.exe occurs when closing handles with the CloseHandle function in ntdll.SbSelectProcedure on the movaps instruction.
For Windows 11 24H2 (build 26100) the movaps instruction requires that the operand address be aligned to 16 bytes


Fix it please.

[HellOfMice]

Very interesting, but we can't do anything.

[TimoVJL]

Bit strange, if only pocc.exe suffer that kind of problem 

[John Z]

No expert here but isn't is also strange that programs created with the theorized non-alignment issue in prior versions of Windows apparently still run fine in Win 11 24H2? I would assume that the issue should affect running programs not just the Pelles Compiling/Linking process ?

Fortunately for me I have a WIN10 system running that could not handle the downgrade to WIN 11 
Unfortunately not the case for my main computing system which is still 23H2 so far but any day now it could go to the dark side...

John Z

[Vortex]

Hi  dezmand07,

Any chance to repeaet the test on Windows 10?

[HellOfMice]

Is it good now

[dezmand07]

Hi Vortex.

I have Windows 10 22H2 (build 19045) installed on a Hyper-V VM.
At the moment, I continue to develop my projects from a virtual machine, since my main operating system is Windows 11 24H2 (build 26100).
I don’t see any problems with IDE Pelles C in Windows 10.

[John Z]

Hi,

At the start of this particular thread regarding WIN 11 24H2 'bug'/impact on Pelles C the file ntdll.dll was pointed to as being involved.

The attached shows where two ntdll.dll files are system32 and SysWOW64.
On my WIN 11 23H2 the file version in both places is 10.0.2261.4541 and the create date and file size are shown in the attachment.

Can someone with a WIN 11 24H2 system check on the version of the ntdll.dll files to verify it is different?

John Z

[HellOfMice]

Here are he version of NTDLL.DLL before and after installing the V24 version

[Vortex]

Retrieving the version of a file with Visual Basic script :

Code: [Select]

' http://blogs.technet.com/b/heyscriptingguy/archive/2005/04/18/how-can-i-determine-the-version-number-of-a-file.aspx

strComputer = "."

Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")

Set colFiles = objWMIService.ExecQuery _
    ("Select * from CIM_Datafile Where Name = 'C:\\Windows\\System32\\ntdll.dll'")

For Each objFile in colFiles
    Wscript.Echo objFile.Version
Next

[dezmand07]

John Z,

Windows 11 24H2 (build 26100.2605)
ntdll.dll (System32) - 10.0.26100.2454
ntdll.dll (SysWOW64) - 10.0.26100.2605

[John Z]

Thanks all,

Good to know and record.


John Z

[CandCPlusPlus]

Is this a bug in Windows 11? I wonder if this was fixed by Microsoft for patch Tuesday. Can anyone test it?

[HellOfMice]

If you don't use the IDE for compiling & linking there is no problem

[CandCPlusPlus]

If Pelles ever creates a workaround for this, I'd recommend having a way to disable the workaround in the options as it's possible that Microsoft may fix this problem in the future and possibly already has fixed it this patch Tuesday. Could anyone test Pelles C after applying the newest update today? I don't have a Windows 11 computer running at the moment.