CSP (Type:71) v3.0.3293 KC2 Release OS:Windows CPU:IA32 FastCode:READY,ENABLED.
CSP (Type:75) v3.0.3293 KC2 Release OS:Windows CPU:IA32 FastCode:READY,ENABLED.
Listing Available Provider Types:
Provider type Provider Type Name
1 RSA Full (Signature and Key Exchange)
3 DSS Signature
5 Microsoft Office Outlook/Exchange Cryptographic Service Provider

12 RSA SChannel
13 DSS Signature with Diffie-Hellman Key Exchange
18 Diffie-Hellman SChannel
71 GOST R 34.10-94 Signature with Diffie-Hellman Key Exchange
75 GOST R 34.10-2001 Signature with Diffie-Hellman Key Exchange
Total: SYS: 0.047 sec USR: 0.000 sec UTS: 0.421 sec
[ErrorCode: 0x00000000]



Listing Available Providers:
Provider type Provider Name
75 GOST R 34.10-2001 Cryptographic Service Provider
75 GOST R 34.10-2001 KC2 CSP
71 GOST R 34.10-94 Cryptographic Service Provider
71 GOST R 34.10-94 KC2 CSP
1 eToken Base Cryptographic Provider
1 Gemplus GemSAFE Card CSP v1.0
1 Microsoft Base Cryptographic Provider v1.0
13 Microsoft Base DSS and Diffie-Hellman Cryptographic Provider
3 Microsoft Base DSS Cryptographic Provider
18 Microsoft DH SChannel Cryptographic Provider
1 Microsoft Enhanced Cryptographic Provider v1.0
13 Microsoft Enhanced DSS and Diffie-Hellman Cryptographic Provider

5 Microsoft Exchange Cryptographic Provider v1.0
12 Microsoft RSA SChannel Cryptographic Provider
1 Microsoft Strong Cryptographic Provider
1 Schlumberger Cryptographic Service Provider

Provider types and Provider Names have been listed.
Total: SYS: 0.031 sec USR: 0.000 sec UTS: 0.078 sec
[ErrorCode: 0x00000000]

Результат выполнения команды:

Hashing is better than trashing.

The startig message length is 66
The length to be allocated is 168 bytes.
168 bytes of memory have been allocated.
The message to encode has been opened.
Data has been added to the message to encode.
Message encoded successfully.
The message has been opened for decoding.
The encoded data is added to the message to decode.
The message type has been obtained.
The message is a hashed message. Proceed.
The length 66 of the message obtained.
Memory for the decoded message has been allocated.
Message decoded successfully
The decoded message is
A razzle-dazzle hashed message
Hashing is better than trashing.

Verification of hash succeeded.
The data has not been tampered with.
Test program completed without erroe.
Total: SYS: 0.094 sec USR: 0.000 sec UTS: 0.324 sec
[ErrorCode: 0x00000000]

Самое интересное, что вкладки Крипто-Про "Алгоритмы" и "Безопасность" сейчас заполнены как положено. Но вот после выполнения какой именно команды это произшло, к сожалению, не отследил (будем предпологать, что после последней).
Чем могла быть вызвана проблема и как правильней её решать впредь?