|
Microsoft cloud and Azure services hosted on the West Coast of the US went down for hours on Thursday when network connectivity failed. Although services running entirely within Microsoft's West US cloud region were unaffected, any traffic entering or leaving the facilities was affected.
Microsoft has now published a Preliminary Post Incident Review (PIR) of the incident, reporting that connectivity was lost for five hours between 14.44 UTC (7.44 a.m. Pacific Time) and 19.41 UTC on July 23. The problem was caused when a set of IP routes was removed in error while isolating a device for routine maintenance.
Before starting the maintenance work, Microsoft checked that at least one of the two redundant paths to the facility remained operational. When it came to starting the work, however, automated systems included some additional devices in the perimeter to be isolated, and removing some IP routes that had not been included in the initial assessment.
Customers discovered the problems very quickly, and engineers identified the issue within the first hour and started to reconnect services. Microsoft said the disruption had been caused by some "recent fiber maintenance activity".
To minimize the risk of disruption from such errors in the future, Microsoft advised organizations handling mission-critical data to consider a multi-region approach.
The Azure outage was the second significant one to hit Microsoft this year. In February,
|
|
If you're unaware, the Media Creation Tool is a super-simple way to download a small program from Microsoft and bake it onto a USB drive that can then be used to install a copy of Windows on a PC. It's an excellent method for installing fresh and starting from scratch, especially if you need to do so for another computer, say, in aid of family tech support. The Media Creation Tool has been around in various flavors for years, and it's periodically updated as a separate piece of software… and the latest update has broken it for some users on Windows 10.
That's according to Microsoft itself, who filed it as a bug on October 10th (that's 11 days after the tool was updated). According to the official "Known Issues" page for Windows (spotted by Windows Latest), Windows 10 machines on the 22H2 release are seeing the tool "close unexpectedly, displaying no error message."
The fact that this was an update to the tool that immediately preceded the self-imposed deadline that Microsoft set for a Windows 11 upgrade is u
|
|
