The original article described the frustration of finding an older Messenger component bundled with Windows and then discovering that removing it was not as straightforward as removing an ordinary application.
The account concerned older Windows releases. It should not be treated as a procedure for every version of Windows or every application that has used the Messenger name.
A hidden component entry
The source discussed the file C:\Windows\inf\sysoc.inf and an entry associated with the bundled messaging component. Its example included a hide flag that affected whether the component appeared in a removal interface.
The author described removing that flag, restarting the computer and then returning to the Windows component-management screen. It also advised making a backup before editing the file.
Why the process confused people
The article's main criticism was the gap between the user's simple goal and the number of technical steps suggested to achieve it. Showing hidden files, editing configuration and restarting were a substantial detour for someone who only wanted to remove an unwanted application.
The author attributed that difficulty to the way the component had been integrated and presented. That judgement is part of the original commentary.
Different products shared similar names
Windows Messenger, MSN Messenger and Windows Live Messenger were not interchangeable names for one unchanging package. A procedure concerning one bundled component could easily be mistaken for instructions about another client.
That is one reason an old file-level recipe should not be applied solely because an application has a familiar name.
How to read the procedure now
This English edition preserves what the article was discussing without recommending edits to a current system. Use the removal method documented for the actual operating-system version and application involved.
Do not assume that a system file from an older release exists, has the same purpose or should contain the same line on a different computer.
The companion utility article
The source later introduced ZapMessenger as an alternative from that period. That page is also historical coverage, rather than a current removal-tool recommendation.