Windows encoding table Russian letters. Using DISM Console Utility

Krakozyabry- what kind of word is so interesting? This word is usually used by Russian users to refer to incorrect / incorrect display (encoding) of characters in programs or the Operating System itself.
Why does this happen? You will not find an unambiguous answer. This may be due to the tricks of our "favorite" viruses, it may be due to a malfunction of the Windows OS (for example, the power went out and the computer turned off), the program may have created a conflict with another or the OS and everything "flew". In general, there can be many reasons, but the most interesting one is "It took it and broke itself like that."
We read the article and find out how to fix the problem with encoding in programs and Windows OS, since it happened.

Who still does not understand what I mean, here are a few:

By the way, I also got into this situation once and there is still a file on my Desktop that helped me cope with it. Therefore, I decided to write this article.

Several "things" are responsible for displaying the encoding (font) in Windows - these are the language, the registry and the files of the OS itself. Now we will check them individually and point by point.

How to remove and fix krakozyabry instead of Russian (Russian letters) in the program or Windows.

1. We check the installed language for programs that do not support Unicode. Maybe he got lost.

So, go along the path: Control Panel - Language and regional standards- Advanced tab
There we are looking for the language to be Russian.

In Windows XP, in addition to this, there is a list of "Conversion tables code pages" at the bottom and there is a line with the number 20880 in it. You need to have Russian there too

6. The last point, in which I give you a file that helped me fix everything sometime, and that is why I left it as a keepsake. Here is the archive:

There are two files inside: krakozbroff.cmd and krakozbroff.reg

Their principle is the same - to correct in all ways hieroglyphs, squares, questions or exclamation marks in programs and Windows OS (in common people krakozyabry). I used the first one and it helped me.

And finally, a couple of tips:
1) If you are working with the registry, then do not forget to make a backup ( backup) in case something goes wrong.
2) It is advisable to check the 1st point after each item.

That's all. Now you know how to fix remove / fix Krakozyabry (squares, hieroglyphs, exclamation and question marks) in the program or Windows.

In the early 90s, when the USSR collapsed and the borders of Russia were opened, we began to receive software products Western production. Naturally, they were all English-speaking. At the same time, the Internet began to develop. The problem of russification of resources and programs arose sharply. Then the Russian encoding Windows 1251 was invented. It allows you to correctly display the letters of the Slavic alphabets:

Russian;
Ukrainian;
Belarusian;
Serbian;
Bulgarian;
Macedonian.

The development was carried out by the Russian representative office of Microsoft together with the companies "Dialogue" and "Paragraph". Self-written developments were taken as a basis, which in 1990-91 were in circulation among the few IT ideologists in Russia.

To date, more than universal way encode characters - UTF-8 (Unicode). It represents almost 90% of all software and web resources. Windows 1251 is used 1.6% of the time. (Information from Web Technology Surveys)

Site encoding utf 8 or windows 1251?

To answer this question, you need to understand a little what encoding is and how they differ. Text information, like any other, is stored in the computer in an encoded form. It's easier for us to think of it as numbers. Each character can occupy one or more bytes. Windows 1251 is a single-byte encoding and UTF-8 is an eight-byte encoding. This means that in Windows 1251 only 256 characters can be encoded.
Since everything comes down to the binary system of calculus, and a byte is 8 bits (0 and 1), then maximum number combinations is 28 = 256. Unicode allows you to represent a much larger number of characters, and each can be allocated a larger size.

Hence the advantages of Unicode follow:

In the header of the site, indicate the encoding that is used. Otherwise, "krakozyably" will be displayed instead of symbols. And Unicode is standard for all browsers - they catch it on the fly as the default.
The site symbols will remain the same, regardless of the country in which the resource is loaded. It does not depend on the geographical location of the servers, but on the language software client workstations. A resident of Portugal obviously uses the keyboard and all software, including the operating system, in his native language. His computer most likely does not have Windows 1251 at all. And if this is so, then sites in Russian will not open correctly either. Unicode, in turn, is "hardcoded" into any OS in any language.
UTF-8 allows you to encode large quantity characters. On this moment 6 out of 8 bytes are used, and Russian characters are encoded with two bytes.
That is why it is preferable to use a universal encoding, rather than a highly specialized encoding, which is used only in Slavic countries.

Windows Encoding Table 1251

For programmers and website developers, it is sometimes necessary to know the symbol numbers. For this, special encoding tables are used. Below is a table for Windows 1251.

What to do if the command line encoding has crashed?

Sometimes you may come across a situation when incomprehensible characters are displayed instead of Russian in the command line. This means that there was a problem with the encoding of the command Windows strings 7. Why 7? Because, starting with the 8th version, UTF-8 is used, and in the seven there is also Windows 1251.
The chcp 866 command can help solve the problem at the same time. The current session will work correctly. But to fix the error drastically, you need a registry.

Have a great day!

Windows-1251 - character set and encoding, which is the standard 8-bit encoding for all Russian Microsoft versions Windows. This encoding is quite popular in Eastern European countries. Windows-1251 compares favorably with other 8-bit Cyrillic encodings (such as CP866, KOI8-R and ISO 8859-5) by the presence of almost all characters used in traditional Russian typography for ordinary text (only the accent mark is missing). Cyrillic characters are in alphabetical order.
Windows-1251 also contains all symbols for languages close to the Russian language: Belarusian, Ukrainian, Serbian, Macedonian and Bulgarian.
In practice, this turned out to be enough for the Windows-1251 encoding to take hold on the Internet until the spread of UTF-8.

Windows Character Code Table-1251

Dec	Hex	Symbol	Dec	Hex	Symbol
000	00	NOP	128	80	Ђ
001	01	SOH	129	81	Ѓ
002	02	STX	130	82	‚
003	03	ETX	131	83	ѓ
004	04	EOT	132	84	„
005	05	ENQ	133	85	…
006	06	ACK	134	86	†
007	07	BEL	135	87	‡
008	08	BS	136	88	€
009	09	TAB	137	89	‰
010	0A	LF	138	8A	Љ
011	0B	VT	139	8B	‹
012	0C	FF	140	8C	Њ
013	0D	CR	141	8D	Ќ
014	0E	SO	142	8E	Ћ
015	0F	SI	143	8F	Џ
016	10	DLE	144	90	ђ
017	11	DC1	145	91	‘
018	12	DC2	146	92	’
019	13	DC3	147	93	“
020	14	DC4	148	94	”
021	15	NAK	149	95
022	16	SYN	150	96	–
023	17	ETB	151	97	—
024	18	CAN	152	98
025	19	EM	153	99	™
026	1A	SUB	154	9A	љ
027	1B	ESC	155	9B	›
028	1C	FS	156	9C	њ
029	1D	GS	157	9D	ќ
030	1E	Rs	158	9E	ћ
031	1F	US	159	9F	џ
032	20	SP	160	A0
033	21	!	161	A1	Ў
034	22	"	162	A2	ў
035	23	#	163	A3	Ћ
036	24	$	164	A4	¤
037	25	%	165	A5	Ґ
038	26	&	166	A6	¦
039	27	"	167	A7	§
040	28	(	168	A8	Yo
041	29	)	169	A9	©
042	2A	*	170	AA	Є
043	2B	+	171	AB	«
044	2C	,	172	AC	¬
045	2D	-	173	AD
046	2E	.	174	AE	®
047	2F	/	175	AF	Ї
048	30	0	176	B0	°
049	31	1	177	B1	±
050	32	2	178	B2	І
051	33	3	179	B3	і
052	34	4	180	B4	ґ
053	35	5	181	B5	µ
054	36	6	182	B6	¶
055	37	7	183	B7	·
056	38	8	184	B8	e
057	39	9	185	B9	№
058	3A	:	186	BA	є
059	3B	;	187	BB	»
060	3C	<	188	BC	ј
061	3D	=	189	BD	Ѕ
062	3E	>	190	BE	ѕ
063	3F	?	191	Bf	ї
064	40	@	192	C0	A
065	41	A	193	C1	B
066	42	B	194	C2	V
067	43	C	195	C3	G
068	44	D	196	C4	D
069	45	E	197	C5	E
070	46	F	198	C6	F
071	47	G	199	C7	Z
072	48	H	200	C8	AND
073	49	I	201	C9	Th
074	4A	J	202	CA	TO
075	4B	K	203	CB	L
076	4C	L	204	CC	M
077	4D	M	205	CD	N
078	4E	N	206	CE	O
079	4F	O	207	CF	NS
080	50	P	208	D0	R
081	51	Q	209	D1	WITH
082	52	R	210	D2	T
083	53	S	211	D3	Have
084	54	T	212	D4	F
085	55	U	213	D5	NS
086	56	V	214	D6	C
087	57	W	215	D7	H
088	58	X	216	D8	NS
089	59	Y	217	D9	SCH
090	5A	Z	218	DA	B
091	5B	[	219	DB	NS
092	5C	\	220	DC	B
093	5D	]	221	DD	NS
094	5E	^	222	DE	NS
095	5F	_	223	DF	I AM
096	60	`	224	E0	a
097	61	a	225	E1	b
098	62	b	226	E2	v
099	63	c	227	E3	G
100	64	d	228	E4	d
101	65	e	229	E5	e
102	66	f	230	E6	f
103	67	g	231	E7	s
104	68	h	232	E8	and
105	69	i	233	E9	th
106	6A	j	234	EA	To
107	6B	k	235	EB	l
108	6C	l	236	EC	m
109	6D	m	237	ED	n
110	6E	n	238	EE	O
111	6F	o	239	EF	NS
112	70	p	240	F0	R
113	71	q	241	F1	with
114	72	r	242	F2	T
115	73	s	243	F3	at
116	74	t	244	F4	f
117	75	u	245	F5	NS
118	76	v	246	F6	c
119	77	w	247	F7	h
120	78	x	248	F8	NS
121	79	y	249	F9	SCH
122	7A	z	250	FA	b
123	7B	{	251	FB	NS
124	7C	\|	252	FC	b
125	7D	}	253	FD	NS
126	7E	~	254	FE	NS
127	7F	DEL	255	FF	I am

Description of special (control) characters

Originally, the ASCII control characters (range 00-31, plus 127) were designed to control hardware devices such as teletypewriters, punched tape input, and more.
Control characters (other than horizontal tabs, line feeds, and carriage returns) are not used in HTML documents.

Special (control) characters

Code	Description
NUL, 00	Null, empty
SOH, 01	Start Of Heading, start of heading
STX, 02	Start of TeXt, beginning of text
ETX, 03	End of TeXt, end of text
EOT, 04	End of Transmission, end of transmission
ENQ, 05	Enquire. I ask for confirmation
ACK, 06	Acknowledgment. I confirm
BEL, 07	Bell, bell
BS, 08	Backspace, go back one character
TAB, 09	Tab, horizontal tab
LF, 0A	Line Feed, line feed Now in most programming languages it is denoted as \ n
VT, 0B	Vertical Tab, vertical tab
FF, 0C	Form Feed, Page Feed, New Page
CR, 0D	Carriage Return Now in most programming languages it is denoted as \ r
SO, 0E	Shift Out, change the color of the ink ribbon in the printing device
SI, 0F	Shift In, return the color of the ink ribbon in the printing device back
DLE, 10	Data Link Escape, switch channel to data transmission
DC1, 11 DC2, 12 DC3, 13 DC4, 14	Device Control, device control symbols
NAK, 15	Negative Acknowledgment, do not acknowledge
SYN, 16	Synchronization. Sync symbol
ETB, 17	End of Text Block, end of text block
CAN, 18	Cancel, canceling a previously passed one
EM, 19	End of Medium, end of data carrier
SUB, 1A	Substitute Placed in place of a character whose value was lost or corrupted during transmission
ESC, 1B	Escape Escape Sequence
FS, 1C	File Separator, file separator
GS, 1D	Group Separator, group separator
RS, 1E	Record Separator, record separator
US, 1F	Unit Separator, unit separator
DEL, 7F	Delete, delete the last character.

Sometimes, due to one reason or another, Windows users experience something that leads to encoding failure. Some kind of newly installed program, a virus, manipulations in the registry, you never know ... Here the encodings have disappeared and that's it!

A similar thing happened to me the other day. In some Russified programs, some of the interface labels began to look as if, instead of letters, the prints of birds' paws were inserted there:

To be honest, I spent almost two days looking for a solution to the problem. On all forums and services of "questions and answers", in all manuals and instructions, all as one repeated the same solution recipe, which may have helped someone. But not for me. And only when my brains began to boil and all hope for a solution to the problem left me, everything fell into place.

The search results, I decided to issue in " One-stop guide to solving all encoding problems in operating rooms Windows systems XP and Windows Vista / 7". Although it may not be so universal already ...;)

Solving encoding problems in Windows XP:

Paragraph 1. First you need to make sure that the Russian language is installed for programs that do not support Unicode.

We open « Control Panel» and double click on the icon « » ... Go to the tab « Additionally» « ».

After that, find item 20880 in the list located on the same tab and put a tick next to it:

Point 2. It is possible that problems with the encoding are caused by a violation system settings fonts.

To restore font settings download this archive

Point 3. The next step is to change the registry keys that are responsible for encodings. It is advisable to make these changes only as a last resort and only if all the previous points did not lead to anything.

this archive

Solving encoding problems in Windows Vista / 7:

1. As in the case of Windows XP, first make sure that the Russian language is set for programs that do not support Unicode.

We open « Control Panel» and double click on the icon « language and regional standards» ... Go to the tab « Additionally» and set the Russian language as « A language for non-Unicode programs»:

Save changes and restart your computer. If the problem persists, go to step 2.

2. To restore the font settings, download this archive and run the file that is in it, ignoring all system warnings:

Restart the system. If the problem persists, go to step 3.

3. The next step is to change the registry keys that are responsible for encodings. It is advisable to make these changes only as a last resort and only if all the previous points did not lead to anything.

To make these changes, download this archive and run the file in it. As in the previous paragraph, system warnings will appear.

After these changes, you will also need to restart the system.

4. If all of the above did not help, you need to change the names of the following code page files in the folder C: \ Windows \ System32:

The file " c_1252.nls" on " c_1252.nls.bak»
The file " c_1253.nls" on " c_1253.nls.bak»
The file " c_1254.nls" on " c_1254.nls.bak»
The file " c_1255.nls" on " c_1255.nls.bak»

Since these files are protected from modification, it is advisable to use a wonderful program to perform this operation. You can download the program from

As is known, Windows 10 supports the installation of language packs with which you can change the localization of the interface operating system... The concept of a system language is very closely related to this. The system language is not the one that was added with language pack, but the one that was selected during the installation of the system itself. If you are working on a corporate computer, the language of which was changed through the installation MUI -packages, you might want to know which language was originally used on the system.

Ways to determine system language several.

Let's consider them in order.

Using DISM Console Utility

Run as administrator command line and run the dism / online / get-intl command in it. Get the result in a few seconds.

Pay attention to the parameter "Language user interface default" ... Its meaning will be the system language.

Using PowerShell Console

Run the console as administrator and run the command :: InstalleduICulture .

Parameter value DisplayName will point to the system language. Also pay attention to the parameter LCID, it contains the language code written in windows registry(see below).

Using Registry Editor and Decode Table

Team regedit open registry editor and expand the branch

HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Nls \ Language

In the right column of the editor window, find the string parameter (he is at the very bottom) and see its meaning.

It is represented by a four-digit code, for decryption of which you should use the decoding table on the site MSDN... In our example, the code 0419 corresponds to the Russian language.