succesfully built executables with this framework fail to launch on windows 11 due to a processing bug (incompatiblity?)

[YalekW5435]

Ive explained this before in the other repo that SureAndrew did, but ill do it here too.
Since im building a match 3 game with this thing (literally, called shapular), the code is correct, even all the settings described in the "installation notes" << where directx sdk and a bunch of other libs required, are in use. No errors.

After sexyappbase builds, I leave that alone, as the lib is generated.
I goto project only->build "x.vcxproj" (this case shapular) to its executable.

However: If I go to launch it on the beta version of Windows 11 (this all used to work on win10 and previous, the window stays up, and the graphics render)
The window appears, but instantly exits << and retreats as a background process. No graphics, nothing.

Even worse << digging through Process explorer, the advanced tool used for further analysis and descriptives for processes instead of task managler, this app actually runs as a SYSTEM DLL INSTEAD OF AN EXECUTABLE!! The ".exe" is specified throughout all the properties, not ".dll".

I have never seen my PC and this operating system do this in visual studio. Ive also built this with the same winmain syntax provided in the demos, and all the other code as a STANDALONE, without SexyAppBase, with the same results. No app, and is a background process. The Original authors need to fix this ASAP!!!! This includes microsoft, as well.

The threads also responsible for keeping the app up also fail to show in the process list!!

Im not sure if its a windows 11 thing or if microsoft is deciding to wash away our memories and childhood beloved's, but this is ridiculous. Heres the photos:

Another issue I can also render here, the original variants of the WSTRING and the standalone SexyAppBase, FAIL to upgrade. The VS2005 variants do, though. So techincally, this library is kinda now useless, until its maintenanced, like the linux kernel...

Yalek The Lembine.