New
#1
I just followed this link, which said it was in the Microsoft News Center Press releases, and in the News Center there is nothing about it. Maybe it got pulled....
Press Releases | News Center
In a headline, with no body text, over at the Microsoft News Center, a press release is announcing that the Windows 10 Anniversary Update will be available on August 2nd. We’ve been expecting the update in late July, but this date is close. (updated to remove hasty calendar mangling)...
Read more: Windows 10 Anniversary update available August 2nd, says Microsoft press release headline
UPDATE: Windows 10 Anniversary Update Available August 2
I just followed this link, which said it was in the Microsoft News Center Press releases, and in the News Center there is nothing about it. Maybe it got pulled....
Press Releases | News Center
Oops, looks like Windows 10 Anniversary Update is arriving later than planned
SourceAccording to a headline in the company's News Center, "Microsoft announces Windows 10 anniversary update available Aug. 2". There’s no content to go with the story, but we were alerted, rather cryptically, earlier that Microsoft was set to make an announcement regarding the Anniversary Update, and it seems as if this could be what the announcement is about.
Last edited by Slartybart; 28 Jun 2016 at 12:19.
If true I'm glad that MS pushed back the release date. I don't mind waiting until MS feels that it's ready to release. MS and Windows 10 gets enough complaints.
All say pretty much the same thing:
Microsoft published a blog post earlier today that included only a headline,
"Microsoft announces Windows 10 Anniversary Update available Aug. 2,"
and then pulled the story moments later.
It's possible that Microsoft just got the date wrong, but, more likely than not, Microsoft seems to have just clicked the publish button earlier than it meant to.
Presumably, a formal announcement will come soon.
Maybe we the Insiders found a few bug that needs to be fixed and MS needed to push the date back to give them time to fix and test first.
Happens all the time... Business always rules deployment...which is not necessary wrong if IT confirms milestones have been met, but there is always some niggling bug that surfaces last minute.. the.decision then is go with the 80/20 rule or delay implementation... welcome to the wonderful world of development.
This is really bad news for me. sfc /scannow reports corrupt files and dism cant repair it so I was going to wait until 16th to format. I dont really want to format sooner if I can avoid it.
Lots of reasons for project creep
... the manager who signs off on the release doesn't get back from vacation until 1 August
... MS thought it wasn't a good idea to push the start (1607 begins - uh-oh hold the presses that makes it the 1608 release - new glossies / new websites ..... they'll never make the 2nd now) button to stop (free upgrade ends)
... some high ranking employee didn't like the colors and insisted they had to be changed.
... typos Microsoft is displayed as Mricosoft
... 160802 .... 16 divided by 8 = 2