Quote:
Originally Posted by eschwartz
(The issue actually came up several times that I can remember.)
I think the issue basically boiled down to some registry key pointing at the original location of the MSI -- apparently Windows Installer service isn't clever enough to stop looking for it and proceed with the uninstall if the MSI was on a disk that is no longer available?
Cleaning the registry with CCleaner would fix the problem.
|
I suspect you're right, I can't recall details either.
But be wary of CCleaner on Win 10.
A few days after my upgrade I noticed a lot of registry crud, in Autoruns, Notification settings etc.
So I thought, ah-ah, CCleaner will take care of that. So I blithely ran it as I've been doing in Win 7 for the past few years - until all entries it thought were crud were gone. And then I discovered I'd wrought absolute havoc, the system was a shambles.
So I thought, ah-ah, no worries I'll restore the registry I saved on before first run of CCleaner. Oh, no... Windows says it can't apply the registry patch.
Luckily I'd taken a restore point shortly before I decided to use CCleaner, and I was able to restore from it.
There's a warning at the Piriform site suggesting that CCleaner registry may cause problems on Windows 10 - would make more sense if CCleaner itself popped a message - "Warning, Win10 detected - registry cleaning may not work properly - use at your own risk".
BR