PC is up to date, downloaded the anniversary update via windows update.
PC restarts and acts like its installing and it goes back to build 1511?
I tried downloading the manual installer and same thing, doesn't seem like anyone had this problem yet?
The manual installer capture below. (this is my 3rd try, 2 times with windows update and 1 time with the manual installer.)
It doesn't give me any errors so I don't know whats going on.
Thanks
Tried using the media creation tool and now getting.
0x80073b92 - 0x20009
It wouldn't be build 1511 but version 1511 being upgraded and updated to version 1607. If you are still running with last November's update and haven't been receiving regular updates you wouldn't have reached the 10586.494 version 1511 equal. You may have to consider either enabling the Get insider builds option to upgrade to one of the more recent builds first or simply plan a full clean install to get past the problem(s) being seen.
Here with the Insider 14385 the update simply didn't arrive already having one of the Redstone 1 builds running where the manual upgrade for the 14393.10 general update had to be performed manually. A second desktop already running the 14393.5 Insider build might also need a manual upgrade as well but still has involvement in the Insider Preview program. The second desktop continues to show itself as being updated while the build is still an Insider Preview release but not one seeing a fast expiration date being one of the Redstone 1 update builds.
To get the RS1 update to go on here over the 385 Insider build the windows.iso download by way of the updated just seen out Media Creation Tool note was mounted by a 3rd party freeware app(Virtual Clonedrive originally by Slystone now available at Redstone) where the upgrade to update took as well as the previous Insider builds had done so by way of the WU function.
Simply choosing the folder on a different partition or drive to store the ISO to as well as the free app you can mount and browse the iso file for starting up the setup.exe manually to work the update by upgrade to see if that will take. That would be one alternate to try to see if you can get past the error being seen before the last resort clean install action.
The differences between last fall's TH2 update and now this one are large enough to be cause for concern where seeing a newer Insider build go on now and then try the RS1 anniversary is the other dual upgrade option you can test. First be sure nothing such as your av software, firewall, or other 3rd party wares are in no way interfering with the update process.
Finally got it to go through, searched up the error and a few people said to remove any external drives and to disable your antivirus before the PC restarts. Did that and it finally went through.
Some av softwares and having external drives, devices plugged in especially when performing a clean install will raise havoc at times! I found that out fast last year when not able to even run any upgrade type of install here until unplugging the second OS drive to be made default host/boot once 10 was on along with two other internal drives. Since then however updates by upgrade of 10 between the Threshold 2 and Insider builds haven't seen any repeat of that initial problem.
So I might have to suspect that your av program was the culprit Nothing else being ruled out however. Here the manual mounting of the iso download to run the setup manually ended up seeing great results on two separate machines. Unlike upgrading from one version to anything newer where problems are common place MS seems to have worked out the previous issues as far as going about seeing newer builds applied in 10.
Personally, it was the fact that I have a second boot drive. In particular, one of my other drives has 8.1 on it. The moment I disabled the drive to install the update, it went without a hitch.
The reason for that is the 10 installer will get confused on just where to unpack the boot files and write the mbr info! When I was trying to upgrade a temp 7 install a year ago the boot loader went onto the first of the two storage drives and later found other files on the second storage drive explaining why the initial attempts failed.
Once 10 is on however the WU updates as well as simply mounting an iso image file never presented any additional problem since the boot sector on the correct drive was no longer the issue. The BT and WS folders are another item then seen by the 10 installer as present and end up being overwritten with the newer files. With a clean install however those are wiped in favor of the new.
I should also mention another item noting the larger then 8gb flash drives previously used for the 4 in 1 projects of combining both editions with both 32bit/64bit flavors worked on with Insider builds after being wiped clean failed to see new media created using the MC Tool. Apparently the tool won't recognize drives 8gb or larger for some reason? and saw an error message. The older iso program previously used on 10 now simply won't work besides wiping flash drives clean and made raw as well leaving a manual format with copy+paste and extraction from iso options later seeing the flash drives made bootable by other means.
