Is there any update on this? 

Does changing 32 bit to 64 bit work?  Do you need to upgrade to 2023?  

Thanks for any update,

Chris

Is there any update on this? 

Does changing 32 bit to 64 bit work?  Do you need to upgrade to 2023?  

Thanks for any update,

Chris

Yes changing to 64 bit worked.  

Unfortunately, the issue may occur in Sage 100 2023 also.  (It happens in a variety of Sage 100 versions)

It is related to Windows version 22H2 and has been reported in both Windows 11 22H2 and Windows 10 22H2 from what I understand.

The current workaround is to run the 32_64_bit_switch_utility.exe from the Sage 100 installer used to install Sage 100 (it is in installation files) to convert from 32-bit Sage 100 to 64-bit Sage 100.  

Otherwise, it would be possible to kill the stuck DTR or other register and then re-launch that Register from the Sage 100 menu directly - the issue is with one Register process calling the next Register process automatically.

I talked with my reseller, Keith Fitzgerald at Back Bay Accounting Software Consultants, and he advised not switching to 64 bit as he has seen troubles with that.  We have some add-ons like IIG, GetX, and WebSite Pipeline. 

Instead, he showed me how to configure Windows 11 workstations so they work with 32 bit Sage.  My new Windows 11 workstation did all my sales updates last night just like my Windows 10 workstations have been doing.  I have to test with other updates today still, but I am pretty excited. 

Thank you,

Chris

Can you share what he had you change to help those that can't switch to 64 bit?

reg add "HKCU\Software\Microsoft\Print\UnifiedPrintDialog" /v "PreferLegacyPrintDialog" /d 1 /t REG_DWORD /f

I ran this for each user on the windows 11 computer.   I ran it last night for my admin account and all worked.  Today, I tried doing sales update with my regular user account without running this, and it hung during the update.  I ran this to add the registry entry and then retried and the sales update went right through.  This command was run in a CMD window as administrator at the C:\ prompt.  

Chris

This has been verified. Works like a charm!

Tried this with a client that is experiencing the issue and it did not resolve the problem 

Hi Bob, sorry to hear it did not work for you.  Did you check the registry key to make sure it was there after you ran the command?  It is in the current user, so it has to be done for each user, ie you cannot do it with an administrator user and then have a regular user log in and have it work for them, you have to add it to the registry for that user also.  I learned that the hard way. 

Good luck, I hope you can make it work.  

Chris

this "solution" has not worked on any of my clients having this issue...  before you ask, yes I did make sure this was run under the user login as well as the administrator login and neither helped.

We also can't go to 64 bit for many of my customers due to 3rd party software or other integrations.

As more clients move to Windows 11 workstations we are seeing this spread and becoming an even bigger issue all around!

Beevet
We converted to 64 bit.  1/2 hour process and eliminated the issue entirely with the exception of ops management daily parts update posting.  I do need to post the gl portion as a seperate task.  Worth the 1/2 investment.