Just wanted to pipe in and say that I got the same problem after the 1803 update, but I am not running 32-bit Windows, but 64-bit.
If I disable protected services, NOD32 starts up fine without errors messages. Re-enabling it and restarting immediately reverts me back to the original problem (i.e. no need to wait a few hours).