Installer cannot access c:\program data

[Robin Bignall]

Well, I ran sfc /scannow and it said it had repaired some files, but
classic menu still can't write to c:\ProgramData. Quite weird really,
for I've installed and uninstalled a few programs since then, and the
installs write to the folder without trouble; the uninstalls delete from
it successfully.

Now I find that my Blackberry software, also a .msi, won't update with
same problem. It must be ownership and / or permissions, I'd have
thought.
Could some helpful person look at c:\AppData and tell me
- who owns, or should own, the folder
- who has what permissions.

 

[Rob]

Now I find that my Blackberry software, also a .msi, won't update with
same problem. It must be ownership and / or permissions, I'd have
thought.
Could some helpful person look at c:\AppData and tell me
- who owns, or should own, the folder
- who has what permissions.

Both Administrators and SYSTEM must have full control.
Users need read, list & read/execute.
Owner is Administrator, but all sub-folders are owned by SYSTEM.

HTH,

 

[Robin Bignall]

Both Administrators and SYSTEM must have full control.
Users need read, list & read/execute.
Owner is Administrator, but all sub-folders are owned by SYSTEM.

HTH,

Thanks, Rob. I'll check that.

 

[Robin Bignall]

Both Administrators and SYSTEM must have full control.
OK

Users need read, list & read/execute.
OK

Owner is Administrator, but all sub-folders are owned by SYSTEM.

OK.

It all seems to be OK.

Now Blackberry is telling me that the latest version is installed, when
the install failed. Classic Menu still won't install. Both are telling
me that C:\programdata is "a network resource that is unavailable".

Is programdata one of these peculiar folders that is not a folder but is
a junction point, or something, and I should be looking for ownership
and permissions of something completely different?

 

[Gene E. Bloch]

OK.

It all seems to be OK.

Now Blackberry is telling me that the latest version is installed, when
the install failed. Classic Menu still won't install. Both are telling
me that C:\programdata is "a network resource that is unavailable".

Is programdata one of these peculiar folders that is not a folder but is
a junction point, or something, and I should be looking for ownership
and permissions of something completely different?

ProgramData is just a folder. And it (for some value of 'it') is case
insensitive, so ignore that I used upper case.

Your problem mystifies me, so my above answer is the only way that I can
show my knowledge...

 

[Robin Bignall]

ProgramData is just a folder. And it (for some value of 'it') is case
insensitive, so ignore that I used upper case.

Your problem mystifies me, so my above answer is the only way that I can
show my knowledge...

My computer doesn't like me
It even hates me
I think I'll go eat worms.

 

[Gene E. Bloch]

My computer doesn't like me
It even hates me
I think I'll go eat worms.

That may be the best plan yet.

Translation: it's obviously frustrating, and I have no idea what can be
done other than ... eat worms.

In reality, you do have my sympathy.

 

[Robin Bignall]

That may be the best plan yet.

Translation: it's obviously frustrating, and I have no idea what can be
done other than ... eat worms.

In reality, you do have my sympathy.

Thanks. It really is puzzling because the ownerships and permissions
seem ok. The messages don't help, either. Why should the installers
see C:\ProgramData as "a network resource that is unavailable" when it's
on the system disk? And when I terminate the process I get "previous
version failed to uninstall" when, for Classic Menu, there is no
previous version. I think it means that in both cases the installers do
not have write access to ProgramData for some mysterious reason,
although both system and administrators do.

 

[Robin Bignall]

Thanks. It really is puzzling because the ownerships and permissions
seem ok. The messages don't help, either. Why should the installers
see C:\ProgramData as "a network resource that is unavailable" when it's
on the system disk? And when I terminate the process I get "previous
version failed to uninstall" when, for Classic Menu, there is no
previous version. I think it means that in both cases the installers do
not have write access to ProgramData for some mysterious reason,
although both system and administrators do.

I now find that I get the same message if I try to uninstall anything,
even with Revo uninstaller. It really is screwed up!

I need to run "repair your system" from the Windows 7 disk, but I have
the problem that the system will not reboot. Does anyone know if it can
be run from safe mode?

 

[Dave-UK]

Thanks. It really is puzzling because the ownerships and permissions
seem ok. The messages don't help, either. Why should the installers
see C:\ProgramData as "a network resource that is unavailable" when it's
on the system disk? And when I terminate the process I get "previous
version failed to uninstall" when, for Classic Menu, there is no
previous version. I think it means that in both cases the installers do
not have write access to ProgramData for some mysterious reason,
although both system and administrators do.

Have you tried the Microsoft Fixit for installation problems?

http://support.microsoft.com/mats/Program_Install_and_Uninstall

 

[Robin Bignall]

Have you tried the Microsoft Fixit for installation problems?

http://support.microsoft.com/mats/Program_Install_and_Uninstall

Funny you should say that, Dave. I just discovered and ran it a few
minutes ago. It says it has fixed the problem, and it will do a forced
uninstall of any program that you want to get rid of (by running down
the list of programs in "Programs and features") and clicking on one.
This I did to get rid of Java, which apparently has a major exploit in
it).

However, the Install fixit also runs down the same list, and since I
can't install Classic Menu it doesn't find it in the list. So I still
have the same install problem.

I also ran sfc /scannow using the Windows install disk as source.
No problems found, so my system files are presumably OK.