Dwaine Maggart wrote:OK. Just want to double check: The NFO looks like there could be a USB Audio device of some sort on the system. So you're sure you don't have USB headphones/microphones or audio I/F connected?
yep, just a couple of cables for disconnected devices, but the only audio I/O is a speaker that uses a speaker jack. I unplugged the unused cables anyway.
Dwaine Maggart wrote:VPNs have been known to cause startup issues. I see you have a NordVPN. If you have a way to temporarily disable that as a test, that would be helpful.
Take the system off the Internet and temporarily disable the Windows Firewall and see if that helps. If so, you may need to add an access rule.
It was not actively running, but disabling the background service did not seem to help anyway.
Dwaine Maggart wrote:Anything else that might interfere with network ports on the system could cause an issue. Open a PowerShell in Admin mode and enter the following, and see if that shows anything:
Get-NetTCPConnection | Where-Object { $_.State -eq "Listen" -and $_.LocalPort -eq 1144 } | ForEach-Object { (get-process -id $_.OwningProcess).Description }
It should return nothing. If it returns something, that something is possibly blocking Resolve access to a TCP port it needs.
This returned nothing as expected.
Dwaine Maggart wrote:And speaking of TCP ports, some people have found their DynamicPortRange have been restricted by something, and this can also block Resolve from a TCP port it needs. Do the following to ensure the normal default TCP range, in a Admin level PowerShell:
netsh int ipv4 set dynamicportrange protocol=tcp startport=49152 numberofports=16384
Hopefully one of these things is helpful.
That may have done the trick - R16 has started 3-4 times in a row now. It seems like a pretty slow startup, but it works. I'll keep an eye and see if it seems stable now. Thank you for all the help!