DB Hung and _mprshut crashed when database was stopped

All databases hung and PROSHUT crashed on one database when it was stopped
On all databases, client sessions terminated abnormally and a flurry of logouts were recorded
Disconnecting a remote client crashed the remote server on the largest database
New client/server connections fail and new remote servers cannot be started
When the database was shutdown it had to it had to immediately forceably destroy every direct shared-memory connection (ie all remote servers, background processes, shared-memory clients) then the _mprshut process itself crashed
After the PROSHUT crashed, the database Broker was still running connected to shared memory with no disk activity

Other databases shutdown completing transaction backouts
The largest database uses -B and -B2 totaling 52 GB of shared memory 

Overlaying the Windows system events, there was a Windows Update which ties in with the pre-ceeding client terminations and remote server crash.
Followed by an application install (AppXSVC) where after the shutdown process terminated abnormally, whatever other application install was going on at the time looks to be a contributing factor or was equally affected:

Applying OS upgrades to a server hosting an online database/application environment,
or new applications that touch any of the OpenEdge online envioronment files on disk/executables/memory/network layers
should be delayed until it can be shutdown.

Reboot the Server then restart the OpenEdge Application environment.