windows 10 v1703 - Creators Update incompatible with AllocationPreference MemTopDown?

for testing my own application for compatibility with LargeAddressAware (LAA) i have set the AllocationPreference of the windows "Memory Management" to MEM_TOP_DOWN as suggested in https://stackoverflow.com/a/22745579

"MemTopDown.reg" (requires windows reboot):

REGEDIT4
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]
"AllocationPreference"=dword:00100000

--

on my test environment i have now upgraded to Windows 10 Version 1703 (Creators Update).

by coincidence i have noticed that other 32bit applications that also are LAA enabled are now crashing. for example:

• firefox 53.0


• chrome 58.0.3029.81


• adobe acrobat reader dc 17.009.20044


• irfanview 4.44


• xmind 8 (3.7.1.201612151837)


• ms excel 16.0.4522.1000


• ms powerpoint 16.0.4266.1001

those type of crashes all are pointing to:

Faulting module name: CoreMessaging.dll, version: 10.0.15063.0

--

question:
is there any known bug with windows 10 (version 1703) and the AllocationPreference switch?

--

edit:
to address the initial comments: this question is about a test environment with the AllocationPreference registry switch enabled - which is not there by default! it's a custom switch to better identify application bugs with memory addresses.
but here it seems to be a bug with the windows OS itself: it seems that any 32bit application with LAA enabled would crash in case the MemTopDown switch is set.

the symptom is not observed on earlier service pack levels of windows 10.
the symptom is not observed on other versions such as windows 7.

--

edit2:
a note to all those initial "comments": i have now added the registry switch to this question.
just add it to your system, reboot, and see all LAA 32bit applications crash ...
to revert back simply remove that registry entry, again.

--

edit3:
now adding a screenshot from my WER crash dumps (windows error reporting) on http://sysdev.microsoft.com/
it is pointing to "microsoft::coreui::dispatch::useradapter_handledispatchnotifymessage":

Answer

This is now fixed with cumulative update KB4025342 (2017-07-11) - or later.

It carries the version number 10.0.15063.483.