[BUG] Windows Minion did not return but salt-call is working

[RubiksHacker]

I'm currently experiencing an issue with SaltStack versions 3006.9 and 3007.1. When I try running a command from the minion, I am able to pull information from the Salt master; however, if I try running it from the Salt master, it gives the error "Minion did not return. [No response]". I have tried the following steps as part of my troubleshooting, but the issue remains unresolved:

Troubleshooting steps performed:

• Restarted both the minion and the master
• Tried increasing the timeout value from the default 5 to 300
• Tried reinstalling multiple times

Minion and Master Details:
Minion: Windows Server 2022 Standard
Master: Oracle 8.10

Minion to Master Call:

PS C:\ProgramData\Salt Project\Salt\var\log\salt> salt-call state.apply windows_common
[ERROR ] Failed to set UTC to True
Bad value for option -c.

local:

      ID: timezone UTC
Function: timezone.system
    Name: UTC
  Result: False
 Comment: Failed to set UTC to True
 Started: 03:51:33.346787
Duration: 68.712 ms
 Changes:

---

      ID: W32Time
Function: service.running
  Result: True
 Comment: The service W32Time is already running
 Started: 03:51:34.025212
Duration: 25801.968 ms
 Changes:

---

      ID: restart_W32Time
Function: cmd.run
    Name: powershell.exe -Command "Restart-Service -Name W32Time"
  Result: True
 Comment: Command "powershell.exe -Command "Restart-Service -Name W32Time"" run
 Started: 03:51:59.889682
Duration: 3908.761 ms
 Changes:
          ----------
          pid:
              5300
          retcode:
              0
          stderr:
          stdout:

---

      ID: Spooler
Function: service.disabled
  Result: True
 Comment: Service Spooler is already disabled, and is in the desired state
 Started: 03:52:03.798443
Duration: 15.635 ms
 Changes:

---

      ID: RemoteRegistry
Function: service.disabled
  Result: True
 Comment: Service RemoteRegistry is already disabled, and is in the desired state
 Started: 03:52:03.814078
Duration: 0.0 ms
 Changes:

---

      ID: MSDTC
Function: service.disabled
  Result: True
 Comment: Service MSDTC is already disabled, and is in the desired state
 Started: 03:52:03.814078
Duration: 0.0 ms
 Changes:

---

      ID: basic_setup
Function: pkg.installed
  Result: True
 Comment: All specified packages are already installed
 Started: 03:52:03.892200
Duration: 956.458 ms
 Changes:

---

      ID: disable_smbv1
Function: cmd.run
    Name: powershell.exe -Command "& {Disable-WindowsOptionalFeature -Online -FeatureName smb1protocol -NoRestart}"
  Result: True
 Comment: Command "powershell.exe -Command "& {Disable-WindowsOptionalFeature -Online -FeatureName smb1protocol -NoRestart}"" run
 Started: 03:52:04.848658
Duration: 32011.385 ms
 Changes:
          ----------
          pid:
              3296
          retcode:
              0
          stderr:
          stdout:
              WARNING: Restart is suppressed because NoRestart is specified.


              Path          :
              Online        : True
              RestartNeeded : True

Summary for local

Succeeded: 7 (changed=2)
Failed: 1

Total states run: 8
Total run time: 62.763 s
PS C:\ProgramData\Salt Project\Salt\var\log\salt>

From Master to Minion Call:

[cpadmin@qasalt salt]$ sudo salt SKUMARVDI grains.get os -t 500 -l debug
[DEBUG ] Reading configuration from /etc/salt/master
[DEBUG ] Including configuration from '/etc/salt/master.d/reactor.conf'
[DEBUG ] Reading configuration from /etc/salt/master.d/reactor.conf
[DEBUG ] Using cached minion ID from /etc/salt/minion_id: qasalt
[DEBUG ] Missing configuration file: /root/.saltrc
[WARNING ] Insecure logging configuration detected! Sensitive data may be logged.
[DEBUG ] Configuration file path: /etc/salt/master
[DEBUG ] Reading configuration from /etc/salt/master
[DEBUG ] Including configuration from '/etc/salt/master.d/reactor.conf'
[DEBUG ] Reading configuration from /etc/salt/master.d/reactor.conf
[DEBUG ] Using cached minion ID from /etc/salt/minion_id: qasalt
[DEBUG ] Missing configuration file: /root/.saltrc
[DEBUG ] MasterEvent PUB socket URI: /var/run/salt/master/master_event_pub.ipc
[DEBUG ] MasterEvent PULL socket URI: /var/run/salt/master/master_event_pull.ipc
[DEBUG ] Closing AsyncReqChannel instance
[DEBUG ] Marking 'base64_encode' as a jinja filter
[DEBUG ] Marking 'base64_decode' as a jinja filter
[DEBUG ] Marking 'md5' as a jinja filter
[DEBUG ] Marking 'sha1' as a jinja filter
[DEBUG ] Marking 'sha256' as a jinja filter
[DEBUG ] Marking 'sha512' as a jinja filter
[DEBUG ] Marking 'hmac' as a jinja filter
[DEBUG ] Marking 'hmac_compute' as a jinja filter
[DEBUG ] Marking 'random_hash' as a jinja filter
[DEBUG ] Marking 'rand_str' as a jinja filter
[DEBUG ] Marking 'file_hashsum' as a jinja filter
[DEBUG ] Marking 'http_query' as a jinja filter
[DEBUG ] Marking 'ifelse' as a jinja global
[DEBUG ] Marking 'strftime' as a jinja filter
[DEBUG ] Marking 'date_format' as a jinja filter
[DEBUG ] Marking 'raise' as a jinja global
[DEBUG ] Marking 'match' as a jinja test
[DEBUG ] Marking 'equalto' as a jinja test
[DEBUG ] Marking 'skip' as a jinja filter
[DEBUG ] Marking 'sequence' as a jinja filter
[DEBUG ] Marking 'to_bool' as a jinja filter
[DEBUG ] Marking 'indent' as a jinja filter
[DEBUG ] Marking 'tojson' as a jinja filter
[DEBUG ] Marking 'quote' as a jinja filter
[DEBUG ] Marking 'regex_escape' as a jinja filter
[DEBUG ] Marking 'regex_search' as a jinja filter
[DEBUG ] Marking 'regex_match' as a jinja filter
[DEBUG ] Marking 'regex_replace' as a jinja filter
[DEBUG ] Marking 'uuid' as a jinja filter
[DEBUG ] Marking 'unique' as a jinja filter
[DEBUG ] Marking 'min' as a jinja filter
[DEBUG ] Marking 'max' as a jinja filter
[DEBUG ] Marking 'avg' as a jinja filter
[DEBUG ] Marking 'union' as a jinja filter
[DEBUG ] Marking 'intersect' as a jinja filter
[DEBUG ] Marking 'difference' as a jinja filter
[DEBUG ] Marking 'symmetric_difference' as a jinja filter
[DEBUG ] Marking 'method_call' as a jinja filter
[DEBUG ] Marking 'yaml_dquote' as a jinja filter
[DEBUG ] Marking 'yaml_squote' as a jinja filter
[DEBUG ] Marking 'yaml_encode' as a jinja filter
[DEBUG ] The functions from module 'local_cache' are being loaded by dir() on the loaded module
[DEBUG ] LazyLoaded local_cache.get_load
[DEBUG ] Reading minion list from /var/cache/salt/master/jobs/19/22400df968ad9984bd9e931ae4c3b8bed7c5b1d4d922603cd3886ad6d157c2/.minions.p
[DEBUG ] get_iter_returns for jid 20250124033454217825 sent to {'SKUMARVDI'} will timeout at 03:43:14.410561
[DEBUG ] Checking whether jid 20250124033454217825 is still running
[DEBUG ] Closing AsyncReqChannel instance
[DEBUG ] retcode missing from client return
[DEBUG ] return event: {'SKUMARVDI': {'failed': True}}
[DEBUG ] The functions from module 'localfs' are being loaded by dir() on the loaded module
[DEBUG ] LazyLoaded localfs.init_kwargs
[DEBUG ] The functions from module 'localfs' are being loaded by dir() on the loaded module
[DEBUG ] LazyLoaded localfs.init_kwargs
[DEBUG ] The functions from module 'no_return' are being loaded by dir() on the loaded module
[DEBUG ] LazyLoaded no_return.output
SKUMARVDI:
Minion did not return. [No response]
The minions may not have all finished running and any remaining minions will return upon completion. To look up the return data for this job later, run the following command:

salt-run jobs.lookup_jid 20250124033454217825

[DEBUG ] Closing IPCMessageSubscriber instance

[welcome]

Hi there! Welcome to the Salt Community! Thank you for making your first contribution. We have a lengthy process for issues and PRs. Someone from the Core Team will follow up as soon as possible. In the meantime, here’s some information that may help as you continue your Salt journey.
Please be sure to review our Code of Conduct. Also, check out some of our community resources including:

• Community Wiki
• Salt’s Contributor Guide
• Join our Community Slack
• IRC on LiberaChat
• Salt Project YouTube channel
• Salt Project Twitch channel

There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Community Events Calendar.
If you have additional questions, email us at saltproject@vmware.com. We’re glad you’ve joined our community and look forward to doing awesome things with you!