rseiler

Is this with your own serial? I can't seem to replicate the problem, though I've just used the core Burning Rom program mainly.

What form do the files take when you inject a QFE fix into an image? I'm looking for a way to get at the actual content of some fixes. Is this possible? Inside a typical msu are cabs, but inside those are not directly usable files like in the old days (updated drivers or whatever), and once in a while I'd like to examine a file without installing it first. Is there a way to do this (preferably without downloading the whole 1GB package), essentially transforming what's in the cabs into actual files? Package Manager itself doesn't appear to be enough.

OK, I didn't run in silent mode. Could it be as simple as that? I finally looked up what the VC++ 2005 runtime is, since I thought that kind of thing had been subsumed into .Net long ago: "...required to run applications developed with Visual C++ on a computer that does not have Visual C++ 2005 installed." Now, several things surprise me about this: 1) It's not new and it's tiny, so how could this not be built-in to Vista? 2) How could it not be part of the much larger .Net runtimes? 3) And most oddly, how is it possible that this is the first program I've installed written in VC++? That one's baffling. Isn't that among the most common languages in existence on Windows?

See my last post, but I didn't have the problem. Do you use UAC? If so, did you install by using "Run as Administrator"?

I just installed 8.2.8.0 Lite in Vista Ultimate, and for whatever reason didn't get the DLL registration issue, so apparently the problem is variable. I do have all the latest updates installed (though notably NOT the SP1 beta), so perhaps that helped. I also did a "Run as Administrator" during the install (I have UAC enabled). BTW, I'm curious what the message during installation about updating Visual C++ 2005 runtime (or something similar to that) is about. Anyone know? If it's .NET, I already had all versions of that installed.

So is this Vista problem ubiquitous or rare? Is there a solution for it yet or an indication of which DLLs aren't registering and why? Are you running the installer with "Run as administrator" if using UAC?