• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

AnandTech: Windows 10 Anniversary Update: The Road To Redstone

Eug

Lifer
AT: Windows 10 Anniversary Update: The Road To Redstone

I just checked my laptop. Apparently this Win 10 1511 laptop is still up to date, so the Anniversary Update isn't available for me yet (2016-08-02 10:30 ET).

I'll probably update this laptop right away, since it's not a mission critical machine. I made sure to create a restore point already, but others have mentioned that such a restore point is probably not so useful for an update this big.
 
Re-downloaded ISO from Microsoft using MediaCreationTools, it's still old ISO. Dated 4-27-16.
 
I'm looking forward to trying dark mode and the new Edge. I gave up on Edge a while back, but by the sounds of it, it might be worth trying again in the Anniversary Update. It will also be nice to have the ability to send as another email address in Mail. And hopefully the new Skype will be nice.

We need more info in the review about the features lost though, and how much more phoning home to mothership Microsoft there will be.
 
heh
1607-error.png
 
Use the manual updater. Only two of my pc's were able to get it through WU and the rest are getting it via the updater except for my laptop which for some reason cannot connect via the updater.
 
Last edited:
Last edited:
Just updated on another PC and Classicshell doesn't work anymore, seems Windows is intentionally blocking it.
 
Just updated on another PC and Classicshell doesn't work anymore, seems Windows is intentionally blocking it.

You have to allow classic shell to reconfigure itself to the new install. It told me that 8gadgetpack and my gadgets no longer worked but I let it repair itself and all is good. Classic shell updated to 4.3.0 a couple of days ago in preparation for the anniversary update.
 
Just updated on another PC and Classicshell doesn't work anymore, seems Windows is intentionally blocking it.

ClassicShell needs to be on the latest version (4.30) to be able to run on the latest Windows 10, build 14393.10.
 
OK thanks. Downloading now... although still at 0% on my machine.

Is it possible to download an ISO? Or a package? It would save time for my other machines.

ISO will be coming shortly, but the load on the MSDN servers is huge. You would be lucky to get 10Kb/sec.

I really hate that they don't stick up the ISOs first, and then do the rollout on windows update. 😡

BTW, here is a good changelog of all the new stuff. http://changewindows.org/build/14393/desktop
 
If you'll go back to my previous post you'll see the article link which states that the media creation tool will download 1607 starting today.
 
If you're wanting to save some bandwidth, get the .esd instead of the .iso file. The .esd file contains the exact same data as the .iso file, except that the .esd file is highly compressed. The .esd file is what Windows Update will normally download, then gets uncompressed locally by Windows. Each Windows build number's .esd file will require a unique decryption key in order to convert from .esd file (~2.6 Gb) to an .iso file (~4.0 Gb). A single decryption key works for all sub-versions of a Windows build number, such as: Windows 10 Pro US English, Windows 10 Home Brazil Portuguese, Windows 10 Corporate French, etc. All of the same build number use the same decryption key.
For download links for .esd files, see previous post.
 
Last edited:
If you'll go back to my previous post you'll see the article link which states that the media creation tool will download 1607 starting today.

It hasn't been updated as of 4PM EST, when I tried... that is why I said it should be shortly available.

If you're wanting to save some bandwidth, get the .esd instead of the .iso file. The .esd file contains the exact same data as the .iso file, except that the .esd file is highly compressed. The .esd file is what Windows Update will normally download, then gets uncompressed locally by Windows. Each .esd file will require a unique decryption key in order to convert from .esd file (~2.6 Gb) to an .iso file (~4.0 Gb).
For download links for .esd files, see previous post.

Yeah, I know that... but, was unsure of this site's policy on dealing with .esd files.

*edit, looks like at https://www.microsoft.com/en-us/software-download/windows10ISO/ it has 1607 up.
x64 (English) version SHA1 hash: 99fd8082a609997ae97a514dca22becf20420891
 
Last edited:
Just finished updating my main PC. First impressions:

-Yay! They de-coupled taskbar and titlebar colors so you can avoid the bleak whiteout that happens with the default theme without turning the taskbar into a funny color. Maybe next year they will introduce multiple colors to window titlebars, bringing the Win10 UI to the same standard as Windows 98.

-The "Dark" theme is a total disaster. It should be called the Pitch Black theme. Also it only affects UWP apps, so explorer windows are still white.

-It snuck in a new driver for my Wireless NIC which causes BSODs, so I had to manually downgrade that driver. It also tried to install the Razer Crapware for my DeathAdder mouse, which messes up mouse settings.

-Not much else new. Since Cortana is still not available in my country, none of the changes to it affect me.

Updating my Atom-powered 2in1 now, which is probably going to take quite a bit longer.
 
Last edited:
I've been having issues with the new upgrade assistance tool not working but just a few moments ago it connected on my laptop and tablet and began the upgrade process. The media creation tool and the ISO tried to clean install my laptop (which is a clean install) and wipe out my software so I tried the upgrade assistant again which worked.
 
Last edited:
Back
Top