One day, and for no apparent reason, my system was not installed in a package of an update. The strange thing was that the error was not documented, was not easily identifiable and not even the Microsoft support engineers could give me a solution. Is he will leave Windows with it this time?
For mystical reasons, a couple of weeks ago an update that promised to increase the compatibility and stability of my Windows Vista Business x 86 installation failed installation. The failure was not instant, Windows Update apparently installed the package, but restart when the system fails to complete the changes and Windows calling continually for the same update.
If it wasn't so perfectionist probably had forgotten the issue, but it bothered me greatly not to install, in particular, the following update package:
An update is available that improves the compatibility and reliability of Windows Vista
This update resolves some compatibility issues and reliability issues in Windows Vista. By applying this update, you can achieve better reliability and hardware compatibility in various scenarios.
Google, Google always
Always, the first thing is to search the network. This small premise could prevent billions of GB that are transferred on the Internet only by concept of questions asked by people who do not.
Although I consider myself a pretty good search engine, after a while I discovered that it would be impossible to specify the reason for my problem then the error code)80070003) that I gave the installer was quite generic and repeated in a thousand occasions for different update packages.
Even the same Updater offered a solution, but as I suspected, that solution was so generic as my same mistake and certainly not deterred my problem:
Filemon, Regmon?, no. Procmon
It is difficult to ignore the genius that Mark Russinovich and Bryce Cogswell showed to develop better diagnostic tools that exist on any platform. The merger of Filemon and Regmon in Procmon is without a doubt one of the tools that I use most is unthinkable not to use it in this case.
Needless to say that Filemon and Regmon does not run in Windows Vista, because anyone who want to know what will be tested it easily. In fact this limitation is totally artificial, because the idea is to empower Procmon. Anyway, if you need any of these programs in the new view, is thing small enhancements to the executable:
And in the application almost twin is the same:
The show is "task for the House".
I installed the update and before you restart the computer to apply the inapplicable changes active monitoring Process Monitor in conjunction with the startup of the operating system. In this way, I thought, that could get to the bone of the problem and find out the reason of why mysteriously failed process.
I was very wrong, monitoring of the operation was a daunting task. Nearly a million events recorded by Process Monitor not gave me a little laborious, and simple solution even filtering those data would not discover the background behind the problem. Interesting is the fact that in a couple of minutes, is easy to reach more than one quarter of a million registered in Windows Vista event when, in XP there can be moments in which even there is no activity of the system:
Resigned, temporarily, I decided to hide the update, waiting for the remote possibility that should appear and new updates to fail, can easily diagnose the unusual problem:
Taking advantage of my original license of Windows, I called Microsoft support. He had never before called and expected to get the exact answer from someone that had traveled to the future, read this article and was kind enough to tell me the procedures required to remedy the failed update is impossible.
After an endless ritual where I should provide my data and license numbers, I was transferred to the "team of engineers" where an expert would help me. The character of the support requested nearly two hours of instructions and questions some files and I reserved another hour of support to have time to review those files.
At this moment I understood that there would be no magic solution, however it did not precisely have the free time to design a solution. Interestingly Microsoft support call I discovered training should receive for letting the problem in a sort of limbo where user can almost come to think that your problem is solved when in the real world is not advanced to anything close to a solution. Something valuable is the "restoration" of everything related to which that expert sent me updates:
If by chance you came into this document by a similar problem, I recommend you truthfully that you run this script, restart and check if in your case it serves. The routine does not delete anything important, initializes only related updates, without deleting any update already applied to the system.
By the way, I did nothing in my case.
Get to work
All Windows users are spoiled everything. Down and install whatever, have several pairs of applications and unnecessary services, and are comfortable, very comfortable. Partly Microsoft deceives us making us believe that it is all very trivial and with a small problem (such as the failure of an update) we're aware that is not the case and probably fight hard for hours against something, how to install a network card, a video card or a modem were always the withheld payments for those who did not choose the freedom. Small enough cash in my opinion.
The obvious solution that comes to mind, is to simply replace the files modified by the update, so I install my current version of Windows in a virtual machine:
Now install the problematic update. With surprise and anger, I can see that the update installs perfectly, which reaffirms once more that the cause of the problem was probably one of my countless attempts at altering Windows, especially view which is much more delicate and sensitive in terms of permissions, alterations and those things which, by nature, tend to try to infect our system.
At this moment the update that I installed was not through Windows Update, I did it through a separate package (which only are changes to the files, something like a list of differences):
Important thing now is to find the differences between files. This process could be tedious, but it did not really need nothing more than copy lists of the following page: http://support.microsoft.com/kb/938194/en-us.
A little of Excel 2007copy the list and quickly created a routine that extracts the modified files:
Because taking the modified files, is save them in the same "backup" folder on my real computer and "inject" from a system console opened from a disk (the same installation disk allows this action):
The routine to "inject" into brute force our updates, does not require more than a change in the columns and is also trivial:
And in a couple of minutes, our system is up to date, by reason or force the patriotic slogan of my country as an amendment.
The icing on the cake
Yet the victory is not complete. When you restart Windows with the "updated" already copied files, Windows Update again ask the damn package. Clearly never detected changes in the files, the easiest way to complete the work is discovering how to cheat engine updates from the team.
We go back to the virtual machine, the logical thing would be to try to update the same independent package and see at what point the system responded "no, I do not need this update". When you run the update we received the expected warning:
As the update is not an executable, must debug to true engine update, particularly: "WindowsSystem32wusa.exe". Actually "debug" would take us a couple of minutes, the best is to use Process Monitor once again, focused now on "wusa.exe" and only in the events of registry and files. Now, I keep the list of events.
I return to execute the package now on my system (which supposedly need updating), again capturing the events of "wusa.exe". With any appropriate program)Araxis Filemerge, WinDiff(, among others), I take out the differences between the two catches of events and gender a records file ready to import into my system the "sick":
And the result is a success (and relaxation) total:
Nothing like keeping up-to-date equipment, right?