WARNING(0x00040073)

[Bullierun86]

just updated day z updated mods and met by this
tried launcher and dza launcher but still receive this error help would be greatly appreciated

[MaCk BlaCk]

We are all getting it, buddy ! Wish there was a fix. I have 2 Servers running and no one can get in them.

Do you have CF running, as it seems to be something to do with that. But not sure.

[Bullierun86]

found a fix for thta but now get new error

[MaCk BlaCk]

What was the fix and whats the new error

[MaCk BlaCk]

verifySignatures = 0; // Verifies .pbos against .bisign files. (only 2 is supported)

Set this to 0 in the cfg ...this worked for me. Looks like some one has messed up a key / bsign file.

I suspect Muchstuffpack or CF tbh !! but not sure

[budoske]

same..some servers working fine, others are not with that error message. Also my friend cant connect to some servers which are good for me so its just weird idk.. if anyone found a fix pls tell it

[Tusbru]

Since the last 1.12 update, DayZ dev's changed the way servers load mods, it seems the mods now need to have the MODNAME (@CF) instead of the MODID (@1559212036).

[MaCk BlaCk]

Originally posted by Tusbru:

Since the last 1.12 update, DayZ dev's changed the way servers load mods, it seems the mods now need to have the MODNAME (@CF) instead of the MODID (@1559212036).

PLEASE CHANGE IT BACK....

[Liberty Looter]

Any fix now?

[Apex]

So, I did some extensive troubleshooting ever since 1.12 came out, and I narrowed it down to one specific thing:

Newer drives, and I'm not sure how widespread this is, but my new drive has this, have as type exFAT or FAT32. DayZ will run FAT32, which is why you can run it on non-modded servers, and in very specific circumstance modded servers.

However, some mods like CF and other mods (i.e. MuchStuffPack MSP) will not run on these two types for some reason or another.

Once I moved my game and mods over to one of my NTFS drives, it ran with no problem again.

If anyone who encounters this error can please let me know if they have DayZ (or their mods!) installed on a drive not of type NTFS, I can look further into the issue.

[Bullierun86]

re name mod ids to mod names on gtx server

[ROGUE[WOLF]]

the servers also don't like spaces in the mod names.

[Levas Ala HappyWurst]

Hello same problem WARNING(0x00040073) i did, everything but still in this errror

[Nova Cat v. Wendigo]

I'll guess I'm stuck in this stupid Georgie boat getting sucked in by pennyz as well. It doesn't specify which mod I'm missing but I'm not missing any I weird used all 3 launchers.

[Nova Cat v. Wendigo]

One fix I did was set steam workshop to high priority it worked for me and one other

[Levas Ala HappyWurst]

Originally posted by The Lion:

So, I did some extensive troubleshooting ever since 1.12 came out, and I narrowed it down to one specific thing:

Newer drives, and I'm not sure how widespread this is, but my new drive has this, have as type exFAT or FAT32. DayZ will run FAT32, which is why you can run it on non-modded servers, and in very specific circumstance modded servers.

However, some mods like CF and other mods (i.e. MuchStuffPack MSP) will not run on these two types for some reason or another.

Once I moved my game and mods over to one of my NTFS drives, it ran with no problem again.

If anyone who encounters this error can please let me know if they have DayZ (or their mods!) installed on a drive not of type NTFS, I can look further into the issue.

I havent NTFS Drive and all time giving me that error what i have to do with that ? wait on hotfix or ?