Permissions Issue

I've been using Vista Ultimate with all current updates for over a year
without any installation issues, but for the past month I've been having
problems with program updates not installing due to access being denied.
Specifically: Error 1310. Error writing to file: c:\Config.Msi\... .rfb.
Verify that you have access to that directory. Also encountered similar
problems with QuickBooks and iTunes+QuickTime updates. I started having
problems with searching in Outlook 2007 last week and tried a repair. That's
when I narrowed down what was going on (or not). I've remedied that by
reindexing, but now get an error about Custom UI Runtime Error in MS Access
Outlook Add-in for Data Collection and Publishing ... An error occurred
while calling the callback: "Ribbon_GetDCVisible." I've consulted with a
Dell tech and another Vista-savvy tech. I've tried logging on as
Administrator (which I am also), creating a new administrator profile, Aaron
Stebner's SubInACL recommendation:
http://blogs.msdn.com/astebner/archi...04/739820.aspx . After this I
was able to install the QuickBooks update, but not iTunes, nor can I
accomplish a repair to MSO 2007 Pro. I've installed the latest versions of
Windows Installer and .NET Framework. UAC is disabled. Does anyone have any
suggestions for further action? And information on why this started
happening?

Thanks,
Cathy

Does disabling UAC remove the ability for the loader to detect
legacy programs and provide needed virtualization?

Have you tried it with UAC enabled?

"Cathy C" <cchristian@xxxxxx> wrote in message
news:edken2WzIHA.5108@xxxxxx

I've tried it both ways. How would I know about detection of legacy problems
and virtualization without UAC being enabled? What do I need to check to
see?


"FromTheRafters" <Erratic@xxxxxx> wrote in message
news:%23qee7GazIHA.3504@xxxxxx

I was just 'grasping at straws' - people are too quick to disable
UAC without considering that UAC is more than just annoying
action confirmation boxes.

Since you tried it both ways, it probably wasn't the cause. Some
legacy programs may require the 'program compatibility' feature
of Vista to operate correctly. Type 'program compatibility' into
the help search box for more information.

"Cathy C" <cathy.christian@xxxxxx> wrote in message
news:5A58914D-D2D1-42EF-8333-B0C31C0D96BA@xxxxxx