Microsoft has recently released the next version of Windows 10, dubbed as Anniversary Update it has a slew of features that make it more efficient and appealing to Users with its new features. I will not be enumerating any of the new features since this is not a review of Windows 10’s Anniversary Update, instead this is more of how to resolve errors that is plaguing users that updated. If you want to see the new features of version 1607 or the Anniversary Update here’s a site that you may want to go to: How-To-Geek: Windows 10 Anniversary Update
I was compelled to write this post due to the fact that I had a first hand experience on my system that went through the update. Soon after and for the next four days of that , I had to resolve the issue one by one with little to none of any online resource that can figure out what was going on. Going through Safemode was the only thing that can save you from the freezing and BSODs. So was it a driver? Is it a Windows Component? Or was it something else? Honestly, it was a combination of sorts.
There has been numerous errors for Microsoft/Windows Updates that are mostly affected by errors within the registry. All throughout the history of installing and patching updates for Windows we may infrequently bump into some corners where we can’t install some or even everything!
Most errors commonly happen when there’s an error accessing keys within the registry. Some people will find it difficult just trying to read through a log file where we can find the error being caused by the installation. Windows will often prompt or give you an error message that’s also as elusive as trying to find the failure point.
I have featured numerous error codes that within this blog that has helped most in overcoming installation errors such as error 57A, 1402, 80073712, .Net Framework, 646, FF0B, 0x80070715, 0x8004FF0B, 0x8024402C, etc., you can walk around the Crimson Spectrum blog just to see how much we have covered such errors. The most intriguing are 643 and hexadecimal ending at “5”.
In a larger perspective, Registry errors or Permission errors are due to some “lock down” on the key itself. At times, the keys could lose their specific Security Descriptor and Access Control List (ACL) Architecture – TechNet Library. Often this can be caused by improper use of Registry Cleaners that may either remove, delete or nullify access into a certain key or object that it may see as unusable. Personally, through my own tests I have seen and also used on test machines how registry cleaners can be either effective or become a catalyst to disaster. Also, a Malware infection may have added Registry permissions to certain keys to deny access to system tools or allow access for it exclusively to certain keys relevant for propagating itself and stealing information.
The method below to help you overcome Registry Permission Errors has been used for .Net Framework installation errors in the past and present but is also successful in resolving errors for installation issues of MSI (Windows Installer) based applications such is what’s being used by Microsoft/Windows Updates , more about this through Aaron Stebner’s WebLog.
I am providing a tool for download once you install SubInACL. This is my own version which will create a Restore Point before the tool executes giving you an option to revert all of the changes after the tool executes.
Download and install SubInACL, do not change the default installation path.
Download the file which is a Command Script –> Reset-ACL.cmd
Save the zipped file and extract the application inside. Once extracted “Run as Administrator”.
Before running the file, make sure that there are currently no other programs or applications running. Also, do not use the system while the script is running. This will ensure that the execution for default permissions in the Registry will go smoothly.
Note: The file may take several minutes to complete. Take heed though, this small script will reset Permission entries within the Registry. If you have any custom configurations, these may be removed and you will need to add it again i.e. User and Group settings in the Registry. For more information: Using the Command Line to Edit Multiple Subdirectory Permissions
It has been a long standing issue that Windows Update, Microsoft Update and MSE could not update through a Proxy Server or Proxy Address use. This is not exactly the case. Windows Update, Microsoft Update and MSE “can” update through a Proxy Server or address. It’s the proper configuration and use on how to allow WU/MU or MSE to pass through a Proxy.
There are two definite Microsoft KB Articles that has fueled my research on how to Update Windows and MSE through a Proxy (Server/Address). See the links of KB Articles below:
Here are the steps I have provided to allow WU/MU and MSE to update using either a Proxy Server or a Proxy Address in the MSE Forums and several other Microsoft Answers site forums:
On Vista/Windows 7:
1. Go to START, All Programs, Accessories, and right click on Command Prompt.
2. Click and choose “Run As Administrator”.
3. In the Command Prompt window, enter: NETSH WINHTTP SET PROXY (Number and Proxy Server)
Example: NETSH WINHTTP SET PROXY 188.8.131.52:8080
or: NETSH WINHTTP SET PROXY MYPROXY.NET:8080
On XP (SP2/SP3):
1. Open Command Prompt by going through Start>RUN
2. In the RUN box, delete anything inside and then type CMD. Hit ENTER.
3. In the Command Prompt window type the syntax: PROXYCFG -P (Number and Proxy Server)
Example: PROXYCFG -P 184.108.40.206:8080
OR: PROXYCFG -P MYPROXY.NET:8080
4. Hit ENTER after typing your proxy server or address.
Let’s use Internet Explorer.
1. Let’s configure Internet Options for Internet Explorer:
a. In Vista/Windows 7, type INETCPL.CPL from the Start Search in the Start Menu then hit Enter.
b. In XP (SP2/SP3), look and open RUN from the Start Menu and type INETCPL.CPL then click OK.
2. A window should come up then jump to the Connections tab. On the Connections tab hit LAN Settings menu box:
3. In the resulting windows add your Proxy Server or Proxy Address under the Proxy Server menu by clicking on the check box. Hit OK and then Apply, OK again to close the Internet Properties window.