File Association errors after SP2 upgrade

Since upgrading Vista Home Premium to Service Pack 2, I have started getting a file association error when I try to click on a wide range of functions. This error occurs in many places, including many Control Panel functions (but not .cpl files). For this reason, I can’t provide full details about my system, because clicking on System also produces the error. However, my computer is an Acer Aspire M3201 with an AMD Phenom X3 chip.

The error message is: This file does not have a program associated with it for performing this action. Create an association in the Set Associations control panel.

The error also occurs when I try to access System Restore so I can’t roll back the upgrade. Some malware experts on another board guided me through all kinds of tests with specialised software and determined that the problem almost certainly is not due to an infection of any kind, but they can’t say what is causing it.

The error does not occur when I click on normal executables. Those run correctly. It does occur if I click on \system32\control.exe. It also occurs if I right-click on Computer and then click Properties. I don’t get it if I right-click the Start Menu and then click Explorer, but I do get it if I click Explore. I also get it in other places.

When the error occurs, different things appear above the error message in the blue section of the message box. When I click on a Control Panel function, it says Explorer.exe. In other places it may say ::{21EC2020-3AEA-1069-A2DD-08002B30309D}\::{335A31DD-F04B-4D76-D6B47CF3...

I have tried searching the net but have been unable to find anything like this. Other File Association error issues either affect all executables (not my problem) or really are File Association errors. I don’t think that is what is going on here, but honestly I don’t have a clue and I sure hope someone who knows more than I do can help me with this. The SP2 upgrade I used, by the way, was called Windows6.0-KB948465-X86.exe (my OS version is 32-bit). This came from a technician friend, who swears he downloaded it straight from the Microsoft site.

Any help would be much, much appreciated.

Not sure if it will work but you might try using System Restore from a command prompt:

Start System Restore from a command prompt

Also you could try using Last Known Good configuration. In future it's a good idea to take system image snap shots using an image backup program before attempting any changes that have a high degree of risk. Even though HD are expensive now you may be able to get a bargain on an external USB drive. I try to get my machines with the SP already on. I've had very bad luck trying ti install SP on machines after the fact. It's generally more hassle than it's worth. If you need specific fixes you're better off installing the ones you need and leave the rest alone.

Some people have better luck. It's not important how easy it goes on for them. It only matters if it generally installs easily for you.

A couple of good free imaging apps are Macrium Reflect Free and Easus ToDo Backup free. But you can find more on www.thefreecountry.com

My guess would be registry issues however in your situation it might be too corrupt to repair. You can try last know good configuration however those are deleted after the next successful boot up regardless as to whether or not your computer is usable. In addition those settings are kept in the registry. It can be really hard and sometimes impossible to recover from a corrupted registry. The time it takes to recover could easily exceed how long it would take to reinstall, update, and set up another installation of windows.

As for installing service packs, I've never had any problems however I don't use automatic updates but do the full download directly from Microsoft's website. Miles is right that backing up is really important and if you had done an image ahead of time all you'd have to do in your case would be to use the image to store your system to how it was before the service pack.

Thank you for your responses. I had not yet come to the point of thinking about things like a command line (or image) restore, but I decided to give it a try and that, at least, worked flawlessly, so I am now back to SP1 and everything seems normal again.

Would it be naive of me to wonder why Microsoft still issues upgrades that hose perfectly good functioning systems? I know Vista had a bad reputation when it first appeared, but I would have thought that kind of thing would have improved by now.

I still would be interested to know what happened, and why this problem occurred. I would also still like to upgrade to SP2 if there is a way to do that without crippling the OS. Does anyone have any ideas what could have been responsible for the result I got and how I might be able to prevent or solve this the next time around?

Thanks again for the input.

There are lots and lots of fixes in service packs and many clones out there. Unless I really need a fix I tend not to put it on. But sometimes I will attempt to install a service pack just because there's a tendency to do some testing when these packs come out. There's not enough time to do a lot of testing with updates coming out willy-nilly. Just my personal opinion. But the safest way to try installing an SP is to back up your system as an image first.

I tried updating Vista to SP1 about half a dozen times. I knew there was quite a difference between Vista pre SP1 and Vista SP1 because I bought another machine that had SP1 already on. Hardly had to tweak it at all, whereas the pre SP1 Vista machine I spent months tuning it. I finally gave up and put W7 on instead. That's why I say the lazy man's way is to buy the PC with the SP already on. It seems to be running fine so I haven't even tried to put SP1 on the W7 machine. If it ain't broke don't fix it.

All this assumes you buy off the shelf systems like I do. If you're a builder that's a whole 'nuther ballgame. Talk to the builder guys for best advice in that case.

For me I've haven't had a problem with service packs but I do the full download. Perhaps those are more reliable. The safest time time to do it is after a fresh install because there isn't as much for it to potentially destroy.

It could be that the download provided to you was corrupted. I would install the update directly from the Microsoft website.

I wouldn't attempt anything without making an image backup first. The System Restore bail out doesn't always work. No sense taking chances after you just dodged the bullet.

I believe if you go on Windows Seven forum you can still find out how to get Windows Seven install discs. If Vista is clunky enough it's bugging you it may be better just to move up to Windows Seven. Some of the features like Snap and windows moving around unexpectedly bugged me at first. After awhile you get used to it. Plus once you get progress bars in the task bar buttons for stuff like file download, you don't want to go back to "52% done" text above the taskbar button for the app.

By the way, many people don't know this, but you can totally legally evaluate Windows Seven for 90 days or longer before deciding to activate. By 3 months you'll probably be hooked and not want to use Vista. I would not recommend Windows Seven Service Pack though. Not unless it has a specific fix you need. If one of the install discs has it integrated that may be ok.

I think I will just stick with SP1. I will also install an image backup utility. That definitely makes sense.

Thanks for all the good suggestions.

I think if you stick with SP1, you won't get any security updates.