G
Guest
My Dell XPS 410 with Windows Vista came with some demo software--including
Roxio Creator DE, which expired before I had opportunity to use it. Nice.
When I went to uninstall this software using Vista's Programs and Features
tool, there were five or six different Roxio entries. None of them had a name
that would indicate that it would uninstall the whole suite--so I uninstalled
them entry-by-entry. For each uninstall, the same type of error dialog
appeared:
"Error writing to file C:\Config.msi\cc1c24f.rbf. Verify that you have
access to that directory."
Each time, the file name was different, but the location was the
same--C:\Config.msi. Each time, I checked the contents of the C:\Config.msi
folder; it was empty--not even a hidden or system file.
I saw this with some other software that I uninstalled, too.
All of the software uninstalled--at least, I *think* it did; the entries no
longer appear in the Programs and Features list.
Is this error to be expected when uninstalling pre-installed software? What
causes it? I don't recall deleting the contents of the C:\Config.msi folder
myself.
Roxio Creator DE, which expired before I had opportunity to use it. Nice.
When I went to uninstall this software using Vista's Programs and Features
tool, there were five or six different Roxio entries. None of them had a name
that would indicate that it would uninstall the whole suite--so I uninstalled
them entry-by-entry. For each uninstall, the same type of error dialog
appeared:
"Error writing to file C:\Config.msi\cc1c24f.rbf. Verify that you have
access to that directory."
Each time, the file name was different, but the location was the
same--C:\Config.msi. Each time, I checked the contents of the C:\Config.msi
folder; it was empty--not even a hidden or system file.
I saw this with some other software that I uninstalled, too.
All of the software uninstalled--at least, I *think* it did; the entries no
longer appear in the Programs and Features list.
Is this error to be expected when uninstalling pre-installed software? What
causes it? I don't recall deleting the contents of the C:\Config.msi folder
myself.