Rabbitmq crashes in Windows 2012 after upgrading NetWorker to 19.13.0.2 or 19.12.0.4

The NetWorker service crashes shortly after upgrading to version 19.13.0.2 or 19.12.0.4 on Windows Server 2012/2012 R2. 

The following messages can be seen in daemon.raw log

2025-12-12 02:20:29 AM  ... rmq: Crash dump is being written to: D:\Program Files\EMC NetWorker\nsr\tmp\RabbitMQ\cores\erl_crash.dump...
2025-12-12 02:21:30 AM  ... Server Warning event: Connection failure in RabbitMQ - Message bus unable to open socket connection to host 'localhost' on port 5671: a socket error occurred

2025-12-11 20:04:31.519000 === CRASH REPORT ===
crasher:
  initial call: user_drv:init/1
  pid: <0.65.0>
  exception error: no match of right hand side value
    {error,
      {'SetConsoleMode','The parameter is incorrect.\r\n'}}
  in function prim_tty:init/1 (prim_tty.erl, line 222)
  in call from user_drv:init/1 (user_drv.erl, line 174)
  in call from gen_statem:init_it/6 (gen_statem.erl, line 984)

These 2 versions of NetWorker (19.12.0.4, 19.13.0.2), along with 19.4, bundle the version 4.1.1 of RabbitMQ, which uses Erlang/OTP version 26 or higher.

Windows Server 2012/2012 R2 does not support Erlang/OTP 26, which RabbitMQ 4.1.1 requires.

NetWorker compatibility guide marks Windows 2012/2012 R2 as EOSL/EOL but does not say it is unsupported.

However, Windows Server 2012 (including 2012 R2) lacks support for Erlang/OTP 26, specifically the console functionality modes ENABLE_VIRTUAL_TERMINAL_INPUT/PROCESSING introduced in Windows 10 Threshold 2 (1511) and Windows Server 2016. The Erlang runtime attempts to set console mode and receives the error 'SetConsoleMode','The parameter is incorrect.' , causing a crash in prim_tty:init/1 .

Windows upgrade is needed to a more recent OS version that supports RabbitMQ 4.1.1 or higher (like Windows 2016 or later)

In the meantime, if you already upgraded to 19.13.0.2, you can downgrade to 19.13.0.1; likewise, you can downgrade from 19.12.0.4 o 19.12.0.3.