I see many people having this problem on the PC beta, so i'll try to give as much information about it as i can. [b]What happens ?[/b] People get kicked to the main menu during the first mission "homecoming", preventing them from ever reaching orbit to play either the strike or PVP. [b]When does it happen ?[/b] This happens at 3 points in the mission : -When loading the first mission after creating/picking a character (about 5% of the time) -After the plaza, right next to the whistling cleaner-bot[b]*[/b] (70%) -After Amanda's cutscene, when loading the command ship (25%) [b]*[/b]When this happens after the cleaner-bot, the door right next to him takes over a minute to open, and after that nobody spawns. No Ikora, no cabal ship, no enemies and not even Amanda when you reach the end of the empty area. After a few minutes the player gets kicked. On rarer occasions, the door doesn't open at all and you're kicked straight away. [b]Some tests[/b] Everytime, we get this "spinach" error code, with no more information other than a suggestion to check my network, which i did. On every test, i ran the game with no other program running and with the Geforce Experience overlay disabled. I'm on W10. I'm connected through gigabit ethernet cable, never getting under 40Mb/s down and 10Mb/s up, 11ms ping with no packet loss. [b]My ISP is Belgacom, and my modem is a Technicolor b-box3[/b]. Trying public and private network profiles makes no difference, neither does disabling/enabling UPnPlay and soft/hard resetting the modem between attempts (or rebooting the PC for that matter). Turning off firewalls or changing regions doesn't help. The only thing i haven't tried is port-forwarding, but i don't want to mess with these right now. [b]Things i've read here on the forums[/b] Apparently, this happened a lot during the console beta as well, under the error code "Moose". People hypothesized it had to do with Technicolor modems, but a friend of mine has been playing the PC beta for hours with his Technicolor TC7210.V (his ISP is Voo) without any problems. [u]If you have the same problem, please post that kind of information in the comments. That might help the devs isolate the problem.[/u] There's a [b]workaround[/b] which involves using your phone as a mobile hotspot or using VPNs, apparently. I hope this additional information helps you fix the problem.