Incident: Microsoft Surface RT tablets bricked after Windows RT 8.1 update.

Published Date: 2013-10-21

Postmortem Analysis
Timeline 1. The software failure incident of Microsoft Surface RT tablets bricking after updating to Windows RT 8.1 occurred on October 17, 2013, as mentioned in Article [22183].
System 1. Microsoft Surface RT tablets 2. Windows RT 8.1 operating system 3. ARM chips used in Windows RT tablets 4. Windows Store [22183]
Responsible Organization 1. Microsoft [22183]
Impacted Organization 1. Microsoft Surface RT tablet users [Article 22183] 2. Microsoft as a company [Article 22183]
Software Causes 1. Software issue that bricked Microsoft Surface RT tablets after updating to the new Windows RT 8.1 operating system [22183] 2. Incompatibility with ARM chips used in Windows RT tablets [22183]
Non-software Causes 1. Hardware compatibility issues with ARM chips used in Windows RT tablets [22183] 2. Boot drive corruption on the tablet [22183]
Impacts 1. Some Microsoft Surface RT tablets were bricked after updating to Windows RT 8.1, leading to the need for a fix [22183]. 2. Microsoft had to temporarily remove the Windows RT 8.1 update from the Windows Store [22183]. 3. Users had to resort to creating a bootable USB drive from another Windows computer to repair the boot drive on the affected tablets [22183]. 4. The update issues affected a limited number of Windows RT tablets using ARM chips, not full Windows 8 PCs with Intel chips [22183]. 5. Microsoft faced embarrassment and inconvenience due to the update issues, impacting the reputation of the Windows RT 8.1 operating system [22183].
Preventions 1. Thorough testing and quality assurance procedures before releasing the Windows RT 8.1 update could have potentially prevented the software failure incident [22183]. 2. Implementing a more robust rollback mechanism in case of issues arising post-update could have helped mitigate the impact of the incident [22183]. 3. Better communication and transparency from Microsoft regarding the potential risks and issues associated with the update could have prepared users and potentially reduced the number of affected devices [22183].
Fixes 1. Creating a bootable USB drive from another Windows computer and repairing the boot drive on the affected tablet [22183].
References 1. Microsoft Surface support engineer on a Microsoft community forum [22183]

Software Taxonomy of Faults

Category Option Rationale
Recurring one_organization (a) The software failure incident of bricking Microsoft Surface RT tablets after updating to Windows RT 8.1 is specific to Microsoft. This incident is not the first time Microsoft has faced issues with software updates causing problems for its devices. In this case, Microsoft had to temporarily remove the Windows RT 8.1 update from the Windows Store due to the issues faced by users of the Surface RT tablets [22183]. (b) The software failure incident of bricking Microsoft Surface RT tablets after updating to Windows RT 8.1 seems to be limited to Microsoft's devices running on ARM chips. There is no specific mention in the article about similar incidents happening at other organizations or with their products and services. Therefore, there is no evidence to suggest that this particular issue has occurred with devices from multiple organizations [22183].
Phase (Design/Operation) design (a) The software failure incident in the article is related to the design phase. Microsoft faced issues with the Windows RT 8.1 update that bricked some Microsoft Surface RT tablets after updating to the new operating system. The update was specifically for a limited number of Windows RT tablets, including the Microsoft Surface RT, Dell XPS 10, and Samsung ATIV Tab. The failure was due to issues introduced during the development and release of the Windows RT 8.1 update, leading to devices being unable to restart after the update [22183]. (b) The software failure incident in the article is not related to the operation phase or misuse of the system. The issue was specifically tied to the update process and the impact it had on the devices, rather than any operational errors or misuse by users.
Boundary (Internal/External) within_system (a) within_system: The software failure incident related to the Microsoft Surface RT tablets bricking after updating to Windows RT 8.1 was within the system. The issue was specifically affecting a limited number of Windows RT tablets using ARM chips, including the Microsoft Surface RT tablet, Dell XPS 10, and Samsung ATIV Tab. Microsoft had to temporarily remove the update from the Windows Store and work on a fix for the problem [22183]. (b) outside_system: There is no specific mention in the article about the software failure incident being caused by contributing factors originating from outside the system.
Nature (Human/Non-human) non-human_actions, human_actions (a) The software failure incident in this case was primarily due to non-human actions. The issue arose after users updated their Microsoft Surface RT tablets to the new Windows RT 8.1 operating system, which resulted in some devices being bricked and unable to restart. Microsoft had to temporarily remove the update from the Windows Store to address the problem. The update was limited to a small number of Windows RT tablets using ARM chips, and the issue was not caused by human actions but rather by a flaw in the update itself [22183]. (b) Human actions were involved in attempting to fix the software failure incident. One user posted a suggested fix for the problem, which involved creating a bootable USB drive from another Windows computer and then repairing the boot drive on the affected tablet. This indicates that users were actively trying to resolve the issue caused by the software failure incident [22183].
Dimension (Hardware/Software) hardware, software (a) The software failure incident related to hardware: - The incident involved Microsoft Surface RT tablets being bricked after updating to the new Windows RT 8.1 operating system, indicating a hardware-related issue [22183]. (b) The software failure incident related to software: - The failure was specifically related to the Windows RT 8.1 update causing the bricking of Microsoft Surface RT tablets, highlighting a software-related issue [22183].
Objective (Malicious/Non-malicious) non-malicious (a) The software failure incident described in the article is non-malicious. The issue with the Windows RT 8.1 update that bricked Microsoft Surface RT tablets was not caused by malicious intent but rather by a technical problem with the update itself. Microsoft acknowledged the problem and was working on a fix to resolve the situation as quickly as possible [22183].
Intent (Poor/Accidental Decisions) poor_decisions, accidental_decisions (a) The software failure incident related to the Microsoft Surface RT tablets bricking after updating to Windows RT 8.1 can be attributed to poor decisions made by Microsoft. The incident occurred because the update was released without proper testing, leading to devices being rendered unusable. Microsoft had to temporarily remove the update from the Windows Store, indicating a lack of thorough testing and quality control before the release [22183]. (b) The incident can also be linked to accidental decisions or unintended consequences. Users who updated their devices faced unexpected issues, forcing Microsoft to take immediate action to address the problem. The need for users to create a bootable USB drive from another Windows computer to fix the bricked tablets highlights the unintended consequences of the update [22183].
Capability (Incompetence/Accidental) development_incompetence (a) The software failure incident in Article 22183 can be attributed to development incompetence. Microsoft faced a significant issue with the Windows RT 8.1 update that bricked some Surface RT tablets. This incident led to Microsoft temporarily removing the update from the Windows Store. The update was limited to a small number of Windows RT tablets, and users had to resort to creating a bootable USB drive from another Windows computer to fix the problem. The fact that the update caused such a critical issue on a specific set of devices indicates a failure in the development process, possibly due to a lack of thorough testing or oversight [22183].
Duration temporary (a) The software failure incident described in the article is temporary. Microsoft had to temporarily remove the Windows RT 8.1 update from the Windows Store after some updated devices could not be restarted. A Microsoft Surface support engineer mentioned that they are working to resolve the situation as quickly as possible and apologized for any inconvenience. The incident is being actively investigated and steps are being taken to address the issue [22183].
Behaviour crash, other (a) crash: The software failure incident described in the article can be categorized as a crash. The update to Windows RT 8.1 caused some Microsoft Surface RT tablets to become bricked, rendering them unable to restart and essentially losing their state and failing to perform their intended functions [22183]. (b) omission: There is no specific mention of the software failure incident being related to the system omitting to perform its intended functions at an instance(s) in the provided article. (c) timing: The failure is not related to the system performing its intended functions correctly but too late or too early. (d) value: The software failure incident is not related to the system performing its intended functions incorrectly. (e) byzantine: The failure is not related to the system behaving erroneously with inconsistent responses and interactions. (f) other: The behavior of the software failure incident can be categorized as a crash, where the system lost its state and failed to perform its intended functions [22183].

IoT System Layer

Layer Option Rationale
Perception None None
Communication None None
Application None None

Other Details

Category Option Rationale
Consequence property, delay, non-human, theoretical_consequence (a) death: There is no mention of any deaths resulting from the software failure incident in the provided article [22183]. (b) harm: The article does not mention any physical harm caused to individuals due to the software failure incident [22183]. (c) basic: The incident did not impact people's access to food or shelter [22183]. (d) property: People's material goods, money, or data were impacted by the software failure incident as some Microsoft Surface RT tablets were bricked after updating to Windows RT 8.1, leading to inconvenience and potential loss of functionality [22183]. (e) delay: Users had to postpone using their Microsoft Surface RT tablets due to the software failure incident until a fix was provided by Microsoft [22183]. (f) non-human: Non-human entities, specifically Microsoft Surface RT tablets, were directly impacted by the software failure incident as they were bricked after the update to Windows RT 8.1 [22183]. (g) no_consequence: There were observed consequences of the software failure incident, such as bricked devices and inconvenience caused to users [22183]. (h) theoretical_consequence: The article discusses potential consequences of the software failure incident, such as the embarrassment for Microsoft and the impact on a limited number of Windows RT tablets, but does not mention any theoretical consequences that did not occur [22183]. (i) other: There are no other consequences mentioned in the article [22183].
Domain information (a) The software failure incident reported in the articles is related to the technology industry, specifically affecting Microsoft Surface RT tablets running the Windows RT 8.1 operating system [22183]. This incident impacted the production and distribution of information technology products. (m) The failed system is not related to any other industry mentioned in the options provided.

Sources

Back to List