Balto352

Will do, thanks for the info. I'm getting 0x20010004 errors back to back now.

There was an update today so I logged on and.......................0x20010006 immediately! Tried again and I spawned in at my camp, only my camp wasn't anywhere on the map. It's just comical at this point. Does anyone now what this update was for?

I get an immediate 0x20010006 error every time I try to launch online. Usually two in a row, and then I am usually able to get through. I've noticed that I am more successful getting through when choosing the Free Roam option instead of spawning at my camp. It's not always successful, but it works more often than not. The disconnects have become much more frequent for me recently. Yesterday, 2 out of 3 bounty missions disconnected me as soon as I was within about 25 meters from returning to the Sheriff with the bounty. I have even begun getting a new error code: 0x20010004; has anyone else got this? After that, I decided not to do anymore bounty missions and went collecting. I didn't get disconnected when collecting at all, and I spent a few hours doing it. I was able to complete a trade delivery without a disconnect as well (though I was on the edge of my seat expecting it). This is really unacceptable.

I think the error 0x20010006 is also related to the camp. I get this error every time I try to log on. Usually twice in a row. There was a time where I got it about 5 or 6 times in a row, so I selected to spawn in free roam instead of selecting to spawn in my camp and it worked immediately. Today, I got the error again when selecting my camp. I thought I'd give it the ol' two attempts and I'll select free roam, but the 2nd attempt spawned me into another player's camp. Mine was nowhere to be found. I think that the game struggles to find a server where it can place your camp, and it results in the 0x20010006 error. This could also be why selecting a pvp activity works for people who get this error as well. They really need to sort this out.

Happy to help!!

What I do to spawn an ambush is: Go to Lemoyne, in Bayou Nwa, go to the road along the Kamassa River, head north on that road (it will take you along to the left of the Stranger's shack; but as soon as you get past the fork that would take you over the covered bridge that heads to Rhodes, turn your back to the direction you want to go (north) for a minute or two (this will allow the game to spawn the ambush). Then head north along the road and the ambush should spawn (you should see the carriage block your path). If not, travel down the road (north) and back and repeat. You should be able to spawn the ambush. Hopefully this isn't as confusing as it looks. It really does work for me, though.

Have you tried this: Press the Windows key and type "msconfig" open the menu.On the Services tab of the System Configuration dialog box, click to select the Hide all Microsoft services check box, and then click Disable all.On the Startup tab of the System Configuration dialog box, tap or click Open Task Manager.On the Startup tab in Task Manager, for each startup item, select the item and then click disable.Close Task Manager. On the Startup tab of the System Configuration dialog box, tap or click OK, and then restart the computer. This worked for me after a few days troubleshooting with Rockstar Support. I went back into my Services tab to try to find out which program was causing the issue. It turned out to be Asus Sonic Studio 3. I disabled it upon launch and I close the program before I launch the Rockstar Games Launcher, and I can play the game. I can start Asus Sonic Studio 3 after I Launch the Rockstar Games Launcher and run the game without issue. I hope this helps!!