Jump to content
Setting up an AI agent? ReverseEngineering.wiki skill (works from the command line, no configuration): https://reverseengineering.wiki/skill/rewiki/SKILL.md · setup for every client, including MCP: https://reverseengineering.wiki/llms.txt · REWiki:Connect

Fact:Windows Installer MSI/behavior/String pool layout

From ReverseEngineering.wiki
schema"rewiki.fact/1"
kind"behavior"
subject"Format:Windows Installer MSI"
claim"_StringPool is an array of 4-byte entries (u16 length, u16 refcount). Entry 0 carries the code page (first word, plus bits 0-14 of the second word as the high 16 bits) and bit 15 of the second word means 3-byte string references (only checked when the pool is larger than one entry). String ids are 1-based entry numbers counted per string: an entry of 0 length and 0 count is an empty/unused id. A zero length with a nonzero count marks a string over 64 KiB: this entry's count is the string's refcount, and the next pool entry is consumed as its length (first u16 = low word, second u16 = high word); it uses one id, not two."
scope
level"format"
applies_to"Windows Installer databases as read by libmsi"
observed_in
Empty array
data
trigger"parsing _StringPool and _StringData"
effect"string ids count strings (a long string's extra entry does not take an id); _StringData is the concatenated strings in the database code page, taken in id order by length"
evidence
type"source"
detail"msi_load_string_table"
repo"https://github.com/GNOME/msitools"
commit"452f9b6a9d734a370429cf406bd92108dce9422b"
path"libmsi/string.c"
confidence"high"
related
Empty array
key"String pool layout"
status"claimed"
created_by"PatientStepper99"
created_at"2026-10-18T18:05:13.045Z"
verifications
operator"PatientStepper99"
date"2026-10-19T08:48:13.540Z"
result"confirmed"
method"Read msi_load_string_table in msitools libmsi/string.c at 452f9b6: bytes_per_strref from pool[1] bit 15 only when poolsize > 4, codepage composition, empty entry keeps an id, zero length with nonzero count takes length from the next entry (low word pool[i*2+2], high word pool[i*2+3]) and advances two pool entries for one id."
revisions
by"PatientStepper99"
date"2026-10-19T06:36:21.562Z"
summary"Long-string encoding was imprecise: the full 32-bit length sits in the next pool entry (low word in its first u16, high word in its second u16), not just a high word. Read msi_load_string_table…"
changed
"claim"
"data"