Crash when installing update for MATLAB

[Unknown78]

It's happened when I try to update MATLAB R2018b into update 5 using this command

C:\Program Files\MATLAB\R2018b\bin\win64>update_installer.exe -updatepack "X:\x\R2018b"

After that, there are two connection error on the dispatch log, but haven't crashed yet.

C:\WINDOWS\system32>dispatch start --debug
SOCKS server started on localhost:1080
Dispatching to addresses 192.168.42.24@1, 192.168.0.177@1
   request [2bd346] 127.0.0.1:32415
  dispatch [2bd346] 192.168.42.24
     error [2bd346] serverConnection
           Error: connect EADDRNOTAVAIL 127.0.0.1:32415
               at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1106:14)
       end [2bd346] clientConnection
   request [873201] 127.0.0.1:32415
  dispatch [873201] 192.168.42.24
     error [873201] serverConnection
           Error: connect EADDRNOTAVAIL 127.0.0.1:32415
               at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1106:14)
       end [873201] clientConnection

The MATLAB window that was supposed to show the update installer throwing an error

Failed to load URL http://localhost:32415/ui/install/update_installer/update_installer/index.html?matlabroot=C:\Program%20Files\MATLAB\R2018b&helper_launch_path=C:\Users\x\AppData\Local\Temp\mw_F112.tmp&updatepack=X:\x\R2018b with error ERR_SOCKS_CONNECTION_FAILED (-120).

After I closed the window, the dispatch process crashed, here is the cmd log

events.js:174
      throw er; // Unhandled 'error' event
      ^

Error: read ECONNRESET
    at TCP.onStreamRead (internal/stream_base_commons.js:111:27)
Emitted 'error' event at:
    at emitErrorNT (internal/streams/destroy.js:91:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)
C:\WINDOWS\system32>

Here is the correct MATLAB update window.

Here is my system proxy settings

While it is not a crucial bug because I could still successfully update without any problem by turning off my proxy, but still, I would like to report it here.

[Unknown78]

"Don't use the proxy server for local (intranet) addresses" option seems to be worked.

I think to solve this bug involves some kind of prevention from "Unhandled 'error' event" crashing, when the user use proxy for local addresses.