Scotty369
Honorable Member
- Joined
- Apr 22, 2012
- Messages
- 31
- Thread Author
- #1
Hi All
New to the forums but have been a computer user since 1980, so I do have a lot of background. About 2 weeks ago I made a mistake cleaning up installer files. I'd made this same mistake last year but didn't realize it right away and it caused all my MSO links to stop working unless I launched the root program. That time I re-installed MSO14 and it corrected everything.
This time I caught the problem almost immediately, as files I r.clicked on launched a Win Installer window, which I had to cancel or wait to resolve, and another popup asked for a disc to a program, and after canceling that the normal popup menu arrived. I only had to do this once with my Opus Directory program (replacement for Explorer). I restored the files I'd cleaner and a registry b/u but some damage remained.
For whatever reason, MSO would not allow re-install although it was registered in CP. Other programs I wanted to remove would no uninstall. Windows update was having problems with NET Framework 4 update. (Solved that by repairing the file).
So I have this ongoing problem with Explorer no program association, can't d.click on links to open files in MSO, and Win Installer trying to launch on r.clicks or d.clicks on files.
I've search the net extensively on these problems and seen many similar complaints about various programs showing the "no program associated" error etc. but I have not seen any rock solid solutions, and I must have tried at least 2 dozen fixes from articles I researched.
I believe the heart of the problem is in Explorer and I'm trying to figure out if there is a way to repair Explorer. There is a possiblilty Explorer itself is OK, because when doing a re-image this weekend to go back to the 15th and start over, explorer opened when needed by the MS engine behind restore operations.
The other possibility is with Installer, but I've updated the Installer and various other things to no avail.
Finally there is MSO and something corrupt there.
So, anyone got some suggestions on how any of these might be tackled? Do you think they are inter-related or is one problem causing all else?
Thanks, Scotty369Link Removed
New to the forums but have been a computer user since 1980, so I do have a lot of background. About 2 weeks ago I made a mistake cleaning up installer files. I'd made this same mistake last year but didn't realize it right away and it caused all my MSO links to stop working unless I launched the root program. That time I re-installed MSO14 and it corrected everything.
This time I caught the problem almost immediately, as files I r.clicked on launched a Win Installer window, which I had to cancel or wait to resolve, and another popup asked for a disc to a program, and after canceling that the normal popup menu arrived. I only had to do this once with my Opus Directory program (replacement for Explorer). I restored the files I'd cleaner and a registry b/u but some damage remained.
For whatever reason, MSO would not allow re-install although it was registered in CP. Other programs I wanted to remove would no uninstall. Windows update was having problems with NET Framework 4 update. (Solved that by repairing the file).
So I have this ongoing problem with Explorer no program association, can't d.click on links to open files in MSO, and Win Installer trying to launch on r.clicks or d.clicks on files.
I've search the net extensively on these problems and seen many similar complaints about various programs showing the "no program associated" error etc. but I have not seen any rock solid solutions, and I must have tried at least 2 dozen fixes from articles I researched.
I believe the heart of the problem is in Explorer and I'm trying to figure out if there is a way to repair Explorer. There is a possiblilty Explorer itself is OK, because when doing a re-image this weekend to go back to the 15th and start over, explorer opened when needed by the MS engine behind restore operations.
The other possibility is with Installer, but I've updated the Installer and various other things to no avail.
Finally there is MSO and something corrupt there.
So, anyone got some suggestions on how any of these might be tackled? Do you think they are inter-related or is one problem causing all else?
Thanks, Scotty369Link Removed