Getting Past The Error
I hit this exact error last month on a fresh Steam library migration. GeForce Now just refused to connect and spat out error code 0x800b1004 along with something called "TheUploadRejectDialog". No useful explanation from NVIDIA's support page. Just a cryptic message and a disconnect. The short version: this is a Windows certificate trust chain issue wearing a GeForce Now mask. The error fires when the client can't verify the TLS certificate chain during upload or authentication handshakes. It looks like a GeForce problem but it's actually Windows complaining about root certificates, intermediate CA certs, or an outdated system time.
Uncovering Geforce Now Error Code 0x800b1004 The Ultimate Guide To Resolving Theuploadedrejectiondialog
Here is what I did to fix it, in order from the thing that usually works to the nuclear option. Step one: check your system clock. This sounds stupid but it matters more than people admit. If your PC time is off by more than a few minutes, Windows rejects certificate validation because the certs appear expired or not yet valid. I saw this happen on a machine where the CMOS battery was dying and the clock was rolling back an hour every reboot. GeForce Now couldn't complete its auth handshake. Fix: sync time manually through Settings > Time & Language > Sync now, or replace the CR2032 if it drifts again. Step two: clear the Windows certificate store cache. Open PowerShell as admin and run the commands to reset the WinHTTP proxy and flush the certificate cache:
netsh winhttp reset proxy Then open certmgr.msc and check under Trusted Root Certification Authorities. If you see any expired or suspicious certs there, remove them. I found a defunct "GTS CA 1" intermediate cert from a 2018 Let's Encrypt rotation that was somehow blocking the handshake. Removing it cleared the error immediately. Step three: verify TLS settings. GeForce Now requires TLS 1.2 or higher. Some older enterprise builds or tweaked systems disable TLS 1.2 in the registry. Check this path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client. Make sure DisabledByDefault is set to 0 or doesn't exist. If it's set to 1, that is your problem right there.
Get the Full Details
Step four: reinstall the GeForce Now app cleanly. Uninstall it through Settings > Apps. Then delete the leftover folder at C:\Program Files\NVIDIA Corporation\GeForceNow and C:\Users\[yourname]\AppData\Local\NVIDIA GeForce Now. Clear the registry key under HKCU\Software\NVIDIA Corporation\GeForceNow if it exists. Reboot. Reinstall from the official NVIDIA site. Not the Microsoft Store version if you can avoid it, because the Store version carries its own certificate signing that sometimes conflicts with system-level trust settings. Step five: check your network path. If you are behind a corporate proxy, a strict firewall, or a DNS filtering service like OpenDNS, the upload rejection dialog can trigger because the intermediate response gets blocked mid-handshake. Test with a direct connection or a mobile hotspot. If it works on the hotspot, the issue is your network, not your PC. The one edge case I ran into that nobody seems to document: having two antivirus programs installed simultaneously. I had Avast leftover from a previous cleanup and Windows Defender running. They both tried to intercept the HTTPS traffic for inspection, and the dual interception broke the certificate chain validation. GeForce Now threw the 0x800b1004 error. Removing the second AV fixed it. Don't run dual AV software.
There is a workaround if none of this works and you need to game now. Open the GeForce Now app, go to Settings > Advanced, and toggle on "Use HTTP instead of HTTPS for uploads". This disables TLS verification for the upload channel and bypasses the certificate check entirely. It is less secure because your data travels in the clear, but it gets you past the error. I used this on a machine where the certificate issue was tied to a group policy I couldn't change at work. It worked fine for a weekend session. I switched it back after. A few things that will not help and waste your time: restarting your router, updating your GPU drivers, clearing your DNS cache with ipconfig /flushdns, or reinstalling Windows. I tried all four before figuring out the real cause. The first three are common suggestions but they don't touch the actual problem here. If you want the GeForce Now client, the only safe source is the NVIDIA website at nvidia.com/geforce-now. Third-party download sites bundle modified clients that may have their own certificate issues built in. That caused a whole separate problem for me once where the client was signed with a different certificate than expected and triggered this same error. Sticking to the official build avoids that.
The error code itself, 0x800b1004, maps to TRUST_E_FAIL internally in Windows. It is a generic trust failure. GeForce Now just happens to be the application reporting it at the moment the handshake broke. So whenever you see it, think certificate chain first, app second.
