Obviously you don't, or you wouldn't be here asking for something that is unnecessary. Not only do you seem to not understand what a registry update file is, or how it's treated by the OS, but you seem to think that you're going to find the answer on a Cnet forum. Cnet caters to the technically clueless by and large. I've said it numerous times... From a business perspective, there's absolutely nothing wrong with that, but it doesn't help people like you when you come to a place where most people have no concept of what programming is. So that is the second major blunder, or oversight if that doesn't bruise your ego as much, that you made with a single post, that was effectively about two sentences long.
I get that it probably looked like I dismissed you out of hand, but you made at least two major errors in a single, very short, posting. All I did was pick up on those two errors you made, and use it to make a pretty reasonable inference about your overall skill level. Not to get all zen buddhist, but it's only when we start to understand what it is we don't understand that we have truly learned anything. You haven't even figured that much out yet.
I'm a pretty poor programmer on my best days. I can usually take something someone else has already written and modify it for my needs, but that's about the extent of it. Still, I can think of at least one way around your little problem. It's an ugly kludge, but it would work. The better method would be to spend the time and energy learning the Win32 API for whatever language I was using. That would be a far more elegant and flexible long term solution. Of course it would require learning a bit about the Win32 API in general, and that would probably require learning some OS design theory, which would probably require learning some lower level programming languages, which is a lot of work that most people just aren't willing to do. So you keep building on top of an increasingly fragile foundation, just praying to all the gods that were, are, and ever will be, that the whole thing won't come crashing down around you. There are simply no shortcuts here. You have to put in the time to learn these things. If you're unwilling or unable, hand the project off to someone else, maybe consider a different line of work. There's no shame in recognizing your limits. We can't all Kobe Bryant level basketball players, or Tiger Woods level golfers, or Albert Einstein level intellectuals.
If you set your ego aside for a minute, and take an objective view of the situation, you'll probably find that I'm right. That's why you got so defensive: I struck at a nerve. You don't yet understand what you don't understand. You need to take a couple of steps back and shore up your skill set. Once you do that, the answer to your question should be pretty self-evident.
And just for the record, this is the whole teach a man to fish methodology. I give you the answer, or an answer anyway, and you haven't really learned anything. You spend the time to develop your skill set to encompass this problem, you won't need my help, or anyone else's.