Hi all. I'm a new backer — bought the Privateer Starter Pack back in March and I still haven't managed to get in-game once. I'll be upfront: I'm not a highly technical PC person. I get by. I got an AI assistant to go through my launcher logs with me because I was completely stuck, and what it found seems worth sharing. If I've misread any of this, please tell me, and I'll be happy to be corrected — I just want to fly my Cutlass. The symptom: "Base Pack Verification Error — Failed to verify Basepack — Error code: 5006" I've now tried a clean install on three completely different machines. All three failed. | | Machine 1 | Machine 2 | Machine 3 | |---|---|---|---| | Type | Desktop (Overclockers UK) | Desktop (PCSpecialist) | ASUS Vivobook laptop | | CPU | AMD Ryzen 9 5900X | AMD Ryzen 9 7900X3D | Intel Core 7 150U | | Graphics | RTX 4060 | RTX 5080 | Intel integrated | | Drive | Crucial MX500 SATA SSD | PCSpecialist 2TB NVMe | WD SN5000S NVMe | | Windows | 11 Pro 25H2 | 11 Home 25H2 | 11 Home 25H2 | | Launcher | 2.15.4 | 2.16.0 | 2.16.0 | AMD and Intel. Discrete and integrated graphics. SATA and NVMe. Desktop and laptop. Two different system builders. The bit that surprised me. The logs show that the actual failure occurs during the patching stage, not during the download. The download finishes fine every time. Then this appears: [CigDataPatcher] Worker threw: Installer exception: UNKNOWN ERROR: CopyToChunk failed: rChunk.nBytesToBeWritten: 4289, nBytesToWrite 8192, nSize 15871, rChunk.FreeSpace 8192, rChunk.nStartOffset 46590595072, nRemainingBytes 15871 [Pipeline] Error: BaseP4kCorruptedError Machine 1 and Machine 3 both failed at the identical byte position: 46590595072. Same chunk numbers too (FreeSpace 8192, nBytesToBeWritten 4289). Separate downloads, totally different hardware, same byte. Machine 1 did it twice on two different days. After that, hitting Verify fails instantly with P4K ERROR ... Central Directory Position not found, which I gather means the file is genuinely broken at that point. Machine 2 failed at different offsets, but its attempts weren't fresh full installs — one was patching 4.8.3 back on 9 July, the other only needed about 1GB, so it was working from different data. Things I've already ruled out (with a lot of help, and a lot of hours): - Disk space — logs show the check passing with 561GB / 615GB spare immediately before the failure. I cleared ~700GB off machine 1 chasing this before we found the real error. - Install location — machines 2 and 3 used the launcher's own default (C:\Program Files\...), machine 1 used a clean custom path outside Program Files with the launcher run as admin. Same byte, both ways. So I don't think it's a permissions thing. - Corrupt download — the download completes and reports done every time. And random corruption wouldn't hit the same byte twice on different computers. - Hardware — three unrelated machines, different CPU brands, different drive types. - Launcher version — happens on both 2.15.4 and current 2.16.0. - Game version — happens on 4.8.3 (July) and 4.9.0 (August). All three are on Windows 11 25H2, build 26200.9168 — which is now the only thing they have in common besides the installer itself. I genuinely don't know if that's meaningful or just what everyone's running right now. My questions: 1. Has anyone else hit BaseP4kCorruptedError at offset 46590595072 on a fresh 4.9.0 install? If it's the same byte for others, that points at the base pack file everyone's downloading rather than anything on our end. 2. Does changing the download region in Download Settings actually fetch from a different source? Happy to try if so. 3. Is there any way to get a known-good base pack, or a workaround while this is looked at? 4. Am I missing something obvious? Genuinely happy to be told I've got the wrong end of the stick. I've got full logs from all three machines, and I'll post them if that helps. Five months in and I've never seen the inside of a ship — any pointers gratefully received.