Why is a registry file called a “hive”?

Date:August 8, 2003 / year-entry #17
Tags:history
Orig Link:https://blogs.msdn.microsoft.com/oldnewthing/20030808-00/?p=42943
Comments:    9
Summary:Useless trivia day. Why is a registry file called a "hive"? Because one of the original developers of Windows NT hated bees.  So the developer who was responsible for the registry snuck in as many bee references as he could.  A registry file is called a "hive", and registry data are stored in "cells", which...

Useless trivia day.

Why is a registry file called a "hive"?

Because one of the original developers of Windows NT hated bees.  So the developer who was responsible for the registry snuck in as many bee references as he could.  A registry file is called a "hive", and registry data are stored in "cells", which is what honeycombs are made of.


Comments (9)
  1. MartinJ says:

    I guess a bad pun would be to talk about honeypots…

  2. Brian Randell says:

    Hmm, I thought it had to do with that fact that the data was structured using B-trees?

  3. BrianJ says:

    So, do you know the deal with MZ of MZ header fame? Is that really someone’s initials? If so, whatever became of the real MZ?

  4. Raymond Chen says:

    MZ is indeed Mark Zbikowski. He still works at Microsoft and is one of the nicest guys it’s been my pleasure to have met.

  5. Thomas Lee says:

    And here I thought the analogy was meant to refer to the notion that if you mess around (with the registry) and do not know what you are doing – you will get stung (or additional practice in reinstallation).

  6. Ok, so I’m coming to this 8 months late :) Mark actually interviewed me, it was absolutely the most pleasant of my on-campus interviews :).

  7. Raymond Chen says:

    Commenting on this article has been closed.

  8. An edge case that can result in a buffer overrun.

  9. It didn’t do quite as much back then.

Comments are closed.


*DISCLAIMER: I DO NOT OWN THIS CONTENT. If you are the owner and would like it removed, please contact me. The content herein is an archived reproduction of entries from Raymond Chen's "Old New Thing" Blog (most recent link is here). It may have slight formatting modifications for consistency and to improve readability.

WHY DID I DUPLICATE THIS CONTENT HERE? Let me first say this site has never had anything to sell and has never shown ads of any kind. I have nothing monetarily to gain by duplicating content here. Because I had made my own local copy of this content throughout the years, for ease of using tools like grep, I decided to put it online after I discovered some of the original content previously and publicly available, had disappeared approximately early to mid 2019. At the same time, I present the content in an easily accessible theme-agnostic way.

The information provided by Raymond's blog is, for all practical purposes, more authoritative on Windows Development than Microsoft's own MSDN documentation and should be considered supplemental reading to that documentation. The wealth of missing details provided by this blog that Microsoft could not or did not document about Windows over the years is vital enough, many would agree an online "backup" of these details is a necessary endeavor. Specifics include:

<-- Back to Old New Thing Archive Index