Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Be wary, you will NOT be the only one with this issue in the coming days when the sh!t hits the fan - hundreds will be affrected. Pearl Abyss was made aware of this back when I told several GM's about it upon discovering the fix -- but was swiftly brushed off.
The storm is inevitable...
(Exchanging the files in the bin64 folder would not make a difference as this is a conflict issue with Windows 10's new security measures flagging XINGCODE3 -- and even so, I surmise it would no doubt be frowned upon by the developers)
Thanks for the answer, it's good to know why this is happening.
I like that sort of stubborness in a person, who's willing to try and exhaust all avenues before ultimately giving up. However, be absolutely certain that exchanging files from that folder is allowed, as XINGCODE3 would no doubt generate a unique identifier for a player's PC -- so mitigating that in any way could be a bannable offense. Just be careful.
At any rate, try allowing the files 'xcorona.xem' as well.
Some chap said that they used FAB to bypass this error, but that was back then, so give FAB a try, and I'll post his quote below as well.
So yeah, if what you've tried, apart from the bin64 exchange (which I don't recommend you doing, lol) doesn't work, give the above quote a try.
All the best!
EDIT: okay so I stumbled on something that was heading in that same direction, sweet, going to try that out and by following your advice I'll put the BIN64 exchange to the side for the time being.
I don't have FAB, but I was able to exclude them all in Windows Security Centre. I recall another fella who had this issue and he was unable to add anything XINGCODE3 related as well. And, he had missing program files as well. ODD. But of course, I do NOT have this issue at all as I'm on 17083, so maybe that's why I have the downloaded XINGCODE 3 program files present, when it fully initiated and download all the protocols needed.
What's your Windows 10 version and build?
Aye, didn't think it would work, XINGCODE is extremely sensitive and it's executed on kernel, running with the highest security privileges, it can't be fooled by a simple file exchange. Good of you to revert it back to your own files though.
version 1709 build 16299.309
And coincidentally windows wants me to update, I'm gonna do that and make sure I can revert if necessary.
How did the update go? The update should take you to 16299.334, and as such, this version and build is NOT normally associated with this "Fail To Init Security" issue. Have you tried deleting your usercache folder and the game's Cache folder?
Delete the 'usercache' folder titled 'Black Desert' located in your Documents folder.
C:\Local Drive > Users > (your username) > Documents > Black Desert
Delete the 'Cache' folder in the game's directory as well.
C:\ > Program Files (x86) > Steam > steamapps > Common > Black Desert Online > Cache
Thanks by the way for trying to help me out so much! Very much appreciated.
[04/08/2018::14:15:35] [MSG] file download : bin64\xc\na\1\x3.xem
[04/08/2018::14:15:36] [MSG] file download : bin64\xc\na\1\xcorona.xem
[04/08/2018::14:15:37] [MSG] file download : bin64\xc\na\1\xcorona_x64.xem
[04/08/2018::14:15:38] [MSG] file download : bin64\xc\na\1\xnina.xem
[04/08/2018::14:15:38] [MSG] file download : bin64\xc\na\2\x3.xem
[04/08/2018::14:15:38] [MSG] file download : bin64\xc\na\2\xcorona.xem
[04/08/2018::14:15:40] [MSG] file download : bin64\xc\na\2\xcorona_x64.xem
[04/08/2018::14:15:41] [MSG] file download : bin64\xc\na\2\xnina.xem
no xm.xem, seemed peculiar to me, but I don't know is this is entirely related since XIGNCODE is a separate program that is also instealled in a different location. Google is not helping me anymore. I have also made a ticket already but who knows it'll take 2 weeks before I get answered.
Ah, but still, it wouldn't matter, the standalone launcher should still have the Cache folder in the Black Desert Online folder. However, since you've reinstalled it, chances are, the game has not had the chance of creating that Cache folder yet, as it cannot even load past the process of acquiring the XINGCODE download
Oh, and you're most kind, and welcome - so it's no problems at all. I've been there myself, with this very issue when I asked the tech team about it - only to be shafted (I was so disappointed), with them telling me to roll back and out of the Insider Preview Build. So I set out to find a workaround to it, instead of giving up.
The xingcode.log file can be located at: C:\Program Files (x86)\Black Desert Online\bin64\xc\na\2
Just type the subject "Fail To Init Security" and you can leave the body of the email empty (if you so wish), as they'll figure out what's happening through the attached xingcode.log file anyway.
I have asked people for help before and don't remember anyone on a forum helping me out so much, it's nice to see someone really trying to help others, in any way.
Ah, I undersatnd that all too well, I've been there too with no replies, heh. And you are indeed a nice person. : )
Oh, and BTW, please do keep us posted, should you get a reply from Welbia.