Determining what caused an error isn't as hard as you think it might be. There's a lot of information online about every single error you could possibly ever get. You just have to know where to look. A lot information about error codes can be found in Microsoft's Developer Network's huge database on information for programmers, but that may not be such an easy task for most of us. So the next best thing to do is to let the search engines find the exact information you need about that error code. When determining what caused an error it's important that you record as much information about it as possible. For example If you just received a error 14079 named, ERROR_SXS_MISSING_ASSEMBL Y_IDENTITY_ATTRIBUTE. You would record all the information about it, go to Yahoo, and put the name of the error code in quotes then hit enter. The first result may be a page from the Microsoft Developer Network which is a part 2 of a list of all possible error codes. This list was able to tell us more about the error code. It's called a side by side error code and it said that "The supplied assembly identity has one or more attribute names that contain characters not permitted in XML names." So now we know we have a XML filename with illegal characters, which is a result of bad programming, or from a user renaming the XML file. A lot of times you can just go to a site like www.pc-library.com which will scan your PC for different issues that might of caused the error. Theirs a lot of scans involved that just generally look for anything wrong, so it will take awhile, but in the end everything will most likely be resolved. Some of us though, don't like to be conventional, and like to spend all day determining what's wrong on our own. If that's the kind of thing you like to do then go for it.