@FredB
Hello Fred,
The patch is available and the documentation is listed at:
https://support.microsoft.com/en-us/topic/windows-11-version-22h2-update-history-ec4229c3-9c5f-4e75-...
ProSeries engine team cannot fix this issue or offer more than what has been suggested. It has to be a fix from Microsoft and it has been done. It is provided in update 22H2.
Here are the details about this issue that haven't been previously posted.
ProSeries uses a large memory space because all the various Fed and State forms get loaded in memory upon startup. Because it uses a large memory space (to handle a robust calc engine to perform the many automated calcs you use), It requires larger than a 2gig memory space which was typical for a 32bit application. We made that change a few years ago to accommodate. So, we at the ProSeries engine team use a 4gig memory space. This year TY22 is now 64bit, but we still allocate the 4 gig memory space using a command provided by .net (IMAGE_FILE_LARGE_ADDRESS_AWARE). This flag is set during compile time to allow ProSeries to have said 4gig memory space during runtime. However, in Windows 11, this flag was no longer available in the operating system so it was shrinking the memory space back down to 2gig, and it presented as the issue you observed. We contacted Microsoft informing them of the missing flag for .net in Windows 11, they created the patch and served it up as it is available now. You may further wonder why it wasn't caught. Well, Windows 11 is new and has not been vetted for as long as Windows 10 has been. So most all our testing occurs in Windows 10 where the largest portion of our clients still reside. The brave few who venture into new Windows operating systems do encounter such omissions and or problems. This will not come down as a ProSeries update. You will have to use Windows Update to get this patch in your operating system. I hope this answers your questions.
This discussion has been locked.
No new contributions can be made. You may start a new discussion
here
