"Don Wiss" <donwiss@no_spam.com> wrote in message
news:5qorq1525k5u9doiomi41c47hjsfh8qnaq@4ax.com
....
> DoRegistryUpdates:SetupInstallFromInfSection Failed for
> ProductInstall.GlobalRegistryChanges.Install error: 0x5
> ***
>
> INF_REGISTRY Failed
> ***
>
> DoInstallationoRegistryUpdates failed
> ***
>
> Access is denied.


This is a symptom of a permissions problem but there are insufficient
details here to know what the exact cause is.

There is supposedly a verbose log option on the install which might
elaborate on this but so far I have not been helped by that option.

My technique to supplement these log messages is to use concurrent tracing
by RegMon and FileMon. In this case you would suspect that RegMon
would provide the ultimate detail but it might be very difficult to wade through
just a raw RegMon trace even if you were able to guess at an appropriate
set of filters. Therefore, I would run FileMon too, principally to associate
timestamps with the above log records so you can then correlate the records
in the RegMon trace. In order to do this you just need to have a filter for FileMon
which captures writes to the install log and use options Clock Time and
Show Milleseconds on both tools. Usually there is sufficient variation
in the lengths of the log records that it isn't too difficult pattern matching
on their lengths to find the correct set of records in the FileMon trace.
BTW I use XP's Notepad's Status bar (which requires Word Wrap off)
to show me the lengths of the log records. Note that the most you get
in terms of a timestamp from the log itself is the second that the job started
which isn't terribly helpful.


Good luck

Robert Aldwinckle
---