http://bugs.winehq.org/show_bug.cgi?id=19781
--- Comment #44 from Kai Blin kai.blin@gmail.com 2010-01-05 06:37:12 --- (In reply to comment #43)
It's obvious, but it's usually totally safe to ignore, so I do ignore it.
Can you generate that warning only in situations where it really matters?
Currently it's generated when secur32.dll is loaded and fails to initialize the NTLM provider. That seemed like a sane spot for me.
It might make sense to add another error in the rpcrt at the point where it expects to use the RPC_C_AUTHN_WINNT AuthSvc and that's not provided. However, that'll only help for apps that get to the secur32 code via the rpcrt4 code.
Apps that explicitly use secur32 show different patterns of selecting the provider they want to use, and on secur32.dll load is the only sane spot to complain about ntlm_auth missing.