Windows Update Error 57A
A more recent error I encountered just today and took me no time to find out what could have gotten my Update not to install. Generally, Windows Update now creates these three digit error codes which are actually hexadecimal numbers as compared to previous versions of Windows Updates which generates 8-stringed hexadecimal errors. Although, the errors still account for the same decimal comparative. Error 57A and Error 1402 is of the same helix.
Troubleshooting errors for Windows Update does not required you to be a either a genius or a wizkid in any manner, it’s how you would need to use the resources in your system. I used several tools to be able to get into resolving this error: Calculator, Command Prompt, Event Viewer and Registry Editor.
Calculator: Get your Decimal comparative of the error. Change Calculator from Standard to Programmer in Windows 7 and Scientific in Vista or XP. Use Hexadecimal and input the code. Then transform this to Decimal by choosing the same in calculator. In this case 57A was 1402.
Command Prompt: Use Command Prompt to interpret the Hexadecimal error to a tangible interpretation. Type NET HELPMSG 1402 = Invalid Cursor Handle. This error is now similar to a “System Error 5” which is an “Access is Denied” error. To be more specific an Invalid Cursor Handle is an error for a Registry Entry not being able to be changed, removed, modified or patched by Windows Update.
Event Viewer: Now find the 1402 error code event for the Update being installed through Event Viewer. This should be under Windows Logs and then look under Applications. Find the Registry Key or Entry that Event Viewer should be pointing you to. Mine was at:
Error 1402. Setup cannot open the registry key
Registry Editor: Now this is where everything becomes intricate (which I did enjoy!). This requires patience in your part. But after several whacks at it you’ll get the hang of it. I’ll be as detailed as possible so that you won’t lose your way.
1. Open Registry Editor by going through Start Search on Vista or Windows 7. If you have XP go to RUN from the Start Button. Type REGEDIT the hit enter. The Registry Editor should open. You may have seen this Registry Editor Disclaimer several times now but I shall reiterate it:
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Windows. I will not guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.
2. Once in Registry Editor look for the registry key in question. Do you still have that Error 1402 from Event Viewer? We need to look for it now. Make sure you use the first part of that very long key. Why? you’ll find out later on. As for me it was A8CD4AD91379E0F3B85DCF71AC8684DA.
3. Now in Registry Editor look for EDIT. Click FIND. Now type in or paste that very long key, hit “Find Next” once your done. Registry Editor should find that key for you. Now everything below that key or what we refer to as SUBKEY, you’ll certainly encounter an error saying that you do not have access or permissions. This is now what’s causing the Update to fail and thus giving you the 57A error code.
4. We need to gain access to those keys, else the Update will continually fail. To gain access or permissions we need to perform necessary steps to have an Administrator account to gain FULL CONTROL.
a. Right click on the SUBKEY, ignore any errors.
b. Choose Properties. Wait for a window and then Hit “Add…”.
d. Find “Administrators” now by highlighting it and then hit OK. Wait we’re not yet done. Make sure that you select Full Control after adding Administrators.
e. Adding the Administrators as Full Control only gave you permissions for the key but not ownership. This is not enough. We need to be the Owner of this subkey. Hit “Advanced” and a bigger window should appear. Choose Owner now from among the tabs and select Administrators from the list appearing from under “Change owner to:”. Hit OK after highlighting Administrators from the list.
Coup de Grâce: Perform the installation of Windows Update
Never forget to apply the same steps for adding Permissions and Ownership of the SUBKEYS or else you will end with the same error since not all of the problematic keys have the necessary permissions to allow modification.