New
#11
The MC Tool seen at that time replaced the MC Tool just seen for the Threshold 2 10586.494 some reporting 10586.499? while not listed among the builds released when researched any however at either of the MS Answers site Wiki threads for 10 builds. If you have previously downloaded and kept the MCTool you will want to rename either this one to RS1 or Redstone 1 Update MCTool.exe or the previous to TH2 or Threshold 2 MC Tool.exe to avoid any mixup between the two!
I have the older stashed away in a sub folder while this one sits at the root of a 10 ISO file folder I will be renaming for storing each. That will allow you to either redownload the older build for the same or other system if TH2 and not one of the Previews with a 6month later expired timeline. The 14366 builds for example still on a pair of VMs would expire on October 1st and have needed to either see the newer build or say good bye to VMs!![]()
I down loaded the MCT and created a ISO file. I then ran the MCT and selected update this pc now.
After several hours and reboots all I get displayed on the screen is the egg timer logo which will not go away and I cannot access any of my apps making the pc unusable. Is there any way that I can over come the problem? Walter
Hi there
easiest way is from Ms site itself Brinks tutorial seems the easiest
BACKUP old system first
How to get the Windows 10 Anniversary Update - Windows 10 Forums
Cheers
jimbo
If you didn't get into the Windows Insider Program it wouldn't make any sense trying to explain the pun intended there at all.
The first immediate online upgrade being an update at this time I never advise to anyone since it will either stall immediately or freezeup forcing a hard boot which should get you back up at least in Safe mode on the first startup. The download and save of the iso image file if not seeing an immediate usb key made up is how it works here where I either use another 3rd party iso program to write the flash drives or manually mount the download to run the upgrade manually. Tested on now both physical as well as on VMs the results have been reliable for each build tested.
Agreed! I've even added a few posts about the results from not expecting to see the RS1 update even arrive here due to having too new of builds running as well as the description from the manual option used here following the downloads. Rather then counting on the WU when builds are too close to each other or too different in contrast which might force a full clean install when not wanted I opted for the manual older type of method to get things done. It worked!![]()
That's good then! Clean installs of course will always take that extra time depending on how much was already on when going to put it all back on again. Presently I will simply be starting off going from the 14385 Insider to RS1 update here for a period of time before going that extra step. But the end results are generally worth it in the long run!
Still have to get to a 3rd desktop along with a 10 laptop and another pair of 8.1 laptops only just lately seeing the 10 upgrade take place. The last two may have already seen the update come in however while the 10 laptop hasn't been run now for nearly a month.
Garbage it is! It grows on you after so long!That's another reason for planning out a total wipe soon enough for the 7 side of the dual boot here as well as seeing a fresh RS1 update install.
Unfortunately I had to unpack the update's iso directly onto a couple of previously used for 10 flash drives that were already made bootable since the MC Tool and a 3rd party iso burning app both failed to write the downloaded isos to usb media. The MC Tool saw an error while the other older app simply made the flash drives raw requiring a new volume for each that was tried on. I suspect due to the Redstone 1 now being strictly RTM that explains the tighter security it now sees.