Microsoft Technology Licensing, LLC

Michael James Day

Abhinav Mishra

Mingbiao Fei

Derek Rivait

Christopher Scott Gouge

James Squires Masson

Alan B Back

Rainer Sigwald

Charles Keen

Michael Grier

Raj Jhanwar

David L Henrickson

Calin Negreanu

Vijayachandran Jayaseelan

James Aaron Holmes

James Andrew Bennett

Arunesh Chandra

Brian McNeill

Theodore C Van Zwol

Terrance James Dolan, Iv

Joseph Albert Robles, Iii

Theodore C VanZwol

A system and method for repairing corrupt software components of a computer system. Corrupt software is detected and repaired utilizing an automated component repair service. Repair files are downloaded from an external storage location and used to repair the corruption. The downloaded files are preferably the smallest amount of data necessary to repair the identified corruption. The process of repairing corrupt files is used in conjunction with a software updating service to resolve problems that occur when corrupt software is updated by allowing a corrupt component to be repaired and then uninstalled such that an updated component can be properly installed.

Method, system and device for validating repair files and repairing corrupt software

A software system, such as an operating system, that has multiple parts can be deployed to a computing device incrementally, rather than all at once. The software system self-adapts to the user's needs by installing and removing system extensions automatically without user intervention. A core part of the software system is deployed in the computing device, and system extensions are delivered to the computing device when needed. The software system is aware of the system extensions, so they appear to be part of the system, even though they have not yet been downloaded. The system extensions can be delivered to the computing system on demand or over time during idle times of the computing device. Unused system extensions can be removed from the computing device, and can be downloaded again when next needed.

Self-adapting software system

Migration of data relevant to, or associated with, one or more users from a prior operating system installation to a new operating system installation can be performed with reference to an archive of some or all of the data on a storage media made prior to the installation of a new operating system. Manifests associated with operating system components can be referenced to identify data to be transferred from those operating system components to new versions of those components. Independently generated manifests can also be referenced to migrate the files and data for one or more application programs, such as popular or commonly found application programs. User data and files to be migrated can be identified by loading registration database files from the offline operating system in the new operating system, or otherwise parsing a similar construct from the offline operating system.

Offline migration from prior operating system installation

A system and method are disclosed for creating and describing a configurable data set, configuring the data set and merging a resulting configured data set into a target data set. One or more configurable data elements are stored in a configurable data set that forms part of a configurable merge module. The configurable merge module also includes metadata concerning the configurable data. The metadata describes the data elements and how they can be configured and how to implement changes to the configurable data. Each configurable data element can be presented to the configurable merge module consumer through a user interface. The configurable merge module consumer can thus make configuration choices. Also provided is a transformation engine for customizing the configurable data based on configurable merge module consumer choices and a merge engine for inserting configured data into a target data set.

System and method for importing a configured data set into a target set

A componentization schema representing files from which an operating system or other software product is built. According to the schema, a component object represents one or more of the files. The component object has a manifest that identifies the component and specifies any dependencies between the component and other objects. Grouping objects according to the dependencies specified in manifests permits building the software product. A feature object defined by at least one component object represents a feature of the software product and a product object defined by at least one feature object represents the software product.

Software componentization for building a software product

Configuring software components(merge) with transformation component using configurable and non-configurable data elements

Growing community of inventors

Seattle, WA, United States of America

Michael James Day