Here's mineWe're investigating this now but having a hard time replicating it. Could we please get the cpatch.log to check if we can spot the issue? It should be located in:
C:\Users\{User}\AppData\Local\Paradox Interactive\launcher-v2
Here's mineWe're investigating this now but having a hard time replicating it. Could we please get the cpatch.log to check if we can spot the issue? It should be located in:
C:\Users\{User}\AppData\Local\Paradox Interactive\launcher-v2
Yeah, I've tried turning everything off but it didn't help (real time virus/threat protection AND firewall). Using just windows defender.Much appreciated, they are being checked as we speak. Last night a customer with the same issue reached out to us and said he solved it by completely disabling his anti virus program. I'm assuming you've all done this but if you haven't turned it off please do so and give it another try. It would also be great to know what AV programs you're using.
Ahem, apparently for me it is Windows Defender, which seems to block the 1.3.1 launcher An usually discreet MS application blocking a MS Store app, ok...Much appreciated, they are being checked as we speak. Last night a customer with the same issue reached out to us and said he solved it by completely disabling his anti virus program. I'm assuming you've all done this but if you haven't turned it off please do so and give it another try. It would also be great to know what AV programs you're using.
If you go into Ransomware, controlled folder access, Apps Allowed Through, there's a list of recently blocked apps - you can add them to exceptions in there.Btw I see no easy way to add a ms store app to Defender's exceptions.
It's not the randomware protection that blocks the launcher, but Defender real time protection.If you go into Ransomware, controlled folder access, Apps Allowed Through, there's a list of recently blocked apps - you can add them to exceptions in there.
There is still no solution to this problem.In all honesty I've never dealt with WD realtime protection, it's not come up to me as a problem in and of itself - it's always been the Ransomware feature that's got in the way.
I know MS make it almost impossible to access the MS store game installation folders, perhaps they figure that makes them immune to malware.
In the meantime, you can re enable realtime protection even BEFORE launching the actual game: if the launcher is visible, you are good to go.Same issues as above. Found a workaround using all the tips above. I disabled by going to Windows Security->Virus & Threat Protection->disabled 'Real-time Protection'. Back in business...will just need to remember to reenable every time i finish playing.
Hi all,Same issues as above. Found a workaround using all the tips above. I disabled by going to Windows Security->Virus & Threat Protection->disabled 'Real-time Protection'. Back in business...will just need to remember to reenable every time i finish playing.
2021-03-28 21:49:25 [repository] [WARNING] failed to make metadata path repository.json world writable: failed to chmod C:\Users\Sebastian\Documents\Paradox Interactive\Crusader Kings III\mod\pdx_11746\.cpatch\87fa0fb0-ef91-11ea-a735-2b61572cb70a\repository.json: No mapping between account names and security IDs was done.
2021-03-28 21:49:25 [repository] [WARNING] failed to make metadata signature repository.json.asc world writable: failed to chmod C:\Users\Sebastian\Documents\Paradox Interactive\Crusader Kings III\mod\pdx_11746\.cpatch\87fa0fb0-ef91-11ea-a735-2b61572cb70a\repository.json.asc: No mapping between account names and security IDs was done.
Hard to see how that could cause the game to fail to start though.2021-03-28 21:49:25 [repository] [WARNING] failed to make keypath _keys/public.gpg world writable: failed to chmod C:\Users\Sebastian\Documents\Paradox Interactive\Crusader Kings III\mod\pdx_11746\.cpatch\87fa0fb0-ef91-11ea-a735-2b61572cb70a\_keys\public.gpg: No mapping between account names and security IDs was done.