PX4 SITL Error Connecting to Socket

Hello everyone,
I am running PX4 Toolchain on Windows 10. I am running into this the “Error [PX4_Daemon] error connecting to socket” when trying to run Jmavsim through Simulink/MATLAB or run-console. The jMAVsim simulation popped up but I cannot use interact with it, and QGroundControl is not connected to the vihicle. I saw other posts about using sudo, but I don’t think I can do that on windows. Does anyone have any idea on how to fix this? I already tried to uninstall and reinstall but it didn’t work either. I am new to this so I very much appreciate your help. Below are the error on PX4 terminal and error on Simulink.

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

SITL ARGS
sitl_bin: /cygdrive/c/Users/XXXX/AppData/Local/Temp/PX4_CO~1/PX4HOS~1/px4.exe
debugger: none
program: jmavsim
model: none
src_path: /cygdrive/c/PX4/home/Firmware
build_path: /cygdrive/c/PX4/home/Firmware/build/px4_sitl_default
empty model, setting iris as default
SITL COMMAND: “/cygdrive/c/Users/dtl17003/AppData/Local/Temp/PX4_CO~1/PX4HOS~1/px4.exe” “/cygdrive/c/PX4/home/Firmware”/ROMFS/px4fmu_common -s etc/init.d-posix/rcS -t “/cygdrive/c/PX4/home/Firmware”/test_data
INFO [px4] Creating symlink /cygdrive/c/PX4/home/Firmware/ROMFS/px4fmu_common → /cygdrive/c/PX4/home/Firmware/build/px4_sitl_default/tmp/rootfs/etc
ERROR [px4_daemon] error binding socket


| ___ \ \ \ / / / |
| |/ / \ V / / /| |
| __/ / \ / /
| |
| | / /^\ \ ___ |
_| / / |_/

px4 starting.

INFO [px4] Calling startup script: /bin/sh etc/init.d-posix/rcS 0
Buildfile: C:\PX4\home\Firmware\Tools\jMAVSim\build.xml

make_dirs:

compile:

create_run_jar:

copy_res:

BUILD SUCCESSFUL
Total time: 0 seconds
Options parsed, starting Sim.
Starting GUI…
Feb 28, 2022 1:53:12 PM java.util.prefs.WindowsPreferences
WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(…) returned error code 5.
3D [dev] 1.6.0-pre12-daily-experimental daily

ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
ERROR [px4_daemon] error connecting to socket
Error: no autostart file found (etc/init.d-posix/ERROR [px4_daemon] error connecting to socket_*)
ERROR [px4] Startup script returned with return value: 256
pxh>

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

MATLAB System block ‘Flight_director/PX4 uORB Read2/SourceBlock’ error occurred when invoking ‘setupImpl’ method of ‘px4.internal.block.Subscriber’. The error was thrown from ’
‘C:\ProgramData\MATLAB\SupportPackages\R2021b\toolbox\target\supportpackages\px4+px4+internal+block\Subscriber.p’ at line 201
‘C:\Program Files\MATLAB\R2021b\toolbox\target\codertarget\sltoolstrip\m+codertarget+internal+sltoolstrip\ConnectedIOHandler.m’ at line 102
‘C:\Program Files\MATLAB\R2021b\toolbox\target\codertarget\sltoolstrip\m+codertarget+sltoolstrip\EmbeddedHardwareBoardContext.m’ at line 440’.

Caused by: Cannot create a communication link with the remote server. Please check the input arguments(ADDRESS and PORT) and make sure the server is running.
Additional Information: No connection could be made because the target machine actively refused it