Update for Windows RT 8.1 (KB3097667) Power BI. Transform data into actionable insights with dashboards and reports. Jun 03, 2019 Remove Windows 8.1 RT Update 3. To remove the update from your Surface, uninstall it in Control Panel. Heres how: Go to Start, and select Control Panel Programs View installed updates. In the search box in the upper-right corner, enter kb3033055. Select Update for Microsoft Windows (KB3033055) Uninstall. We understand that you're having issues with your Surface RT not able download updates and allow anything to be downloaded from the Windows Store app. This usually happens when there is an issue with the Windows Update components. You can try the suggested troubleshooting step below to resolve the issue. I recently bought a Surface RT from Ebay. While it installs updates up to kb2919394, it finds no updates after this point. Also, once it reaches this point it will not allow me to install apps from the windows app store. Am I missing something, as I cannot verify if that last update is the one causing the issue. KB2919442 is a prerequisite for Windows 8.1 Update and should be installed before attempting to install KB2919355 Additional Information Other critical security updates are available: To find the latest security updates for you, visit Windows Update and click Express Install.
Microsoft will not be releasing full updates of its new Windows 10 operating system for any of its Surface devices running Windows RT or Windows RT 8.1.
However, the company has confirmed that it is working on a limited update for Surface devices using Windows RT, which hit the market in 2012, along with Windows 8.
'We are working on an update for [Windows RT] Surface, which will have some of the functionality of Windows 10,' the company told CNET in a statement. 'More information to come.'
![]()
The software giant had already indicated that some editions of Windows would not be included in the free Windows 10 update it announced on Wednesday, which the company said on January 21 would be made free for users running Windows 7, 8.1, and Phone 8.1 on their devices.
'It is our intent that most of these devices will qualify, but some hardware/software requirements apply and feature availability may vary by device,' the company said in the fine print underpinning the offer on its website. 'Some editions are excluded: Windows 7 Enterprise, Windows 8/8.1 Enterprise, and Windows RT/RT 8.1.'
Given that Windows RT and RT 8.1 were designed for power economising devices sporting 32-bit ARM architecture, and never had the same functionality -- to many users' frustration -- as full-blown Windows 8 and 8.1, it comes as little surprise that the RT versions of the operating system should be left out of the latest update loop.
In fact, a week before Microsoft's big Windows 10 reveal on January 21, the company released firmware updates for all three models of its Intel-powered Surface Pro series, but neither of the ARM-based Surface tablets -- the Surface 2 or Surface RT -- received any new updates this month.
![]()
Microsoft's Windows 10 event on Wednesday saw the company not only offer its Windows 10 upgrade free for a year to qualifying users currently running Windows 7, 8.12, and Phone 8; it also revealed its HoloLens holographic goggle offering and its accompanying HoloStudio for developers.
It also demonstrated new universal applications that Microsoft is building and plans to include as a built-in part of Windows 10 on phones, tablets, and PCs, including new People, Music, Maps, Photos, Calendar, and Outlook applications.
Related Topics:Microsoft Enterprise Software Windows 10 PCs ReviewsApplies to
In addition to the traditional deployment method of reimaging devices, administrators that want to upgrade Surface devices that are running Windows 8.1 or Windows 10 have the option of deploying upgrades. By performing an upgrade deployment, Windows 10 can be applied to devices without removing users, apps, or configuration. The users of the deployed devices can simply continue using the devices with the same apps and settings that they used prior to the upgrade. The process described in this article shows how to perform a Windows 10 upgrade deployment to Surface devices.
If you are not already familiar with the deployment of Windows or the Microsoft deployment tools and technologies, you should read Deploy Windows 10 to Surface devices with MDT and familiarize yourself with the traditional deployment method before you proceed.
The upgrade conceptWindows 8 Rt Update 3
When you use the factory installation media to install Windows on a device, you are presented with two options or installation paths to install Windows on that device. The first of these installation paths – clean installation – allows you to apply a factory image of Windows to that device, including all default settings. The second of these installation paths – upgrade – allows you to apply Windows to the device but retains the device’s users, apps, and settings.
When you perform a Windows deployment using traditional deployment methods, you follow an installation path that is very similar to a clean installation. The primary difference between the clean installation and the traditional deployment method of reimaging is that with reimaging, you can apply an image that includes customizations. Microsoft deployment technologies, such as the Microsoft Deployment Toolkit (MDT), expand the capabilities of the reimaging process by modifying the image during deployment. For example, MDT is able to inject drivers for a specific hardware configuration during deployment, and with pre and post imaging scripts to perform a number of tasks, such as the installation of applications.
For versions of Windows prior to Windows 10, if you wanted to install a new version of Windows on your devices and preserve the configuration of those systems, you had to perform additional steps during your deployment. For example, if you wanted to keep the data of users on the device, you had to back up user data with the User State Migration Tool (USMT) prior to the deployment and restore that data after the deployment had completed.
Introduced with Windows 10 and MDT 2013 Update 1, you can use the upgrade installation path directly with Microsoft deployment technologies such as the Microsoft Deployment Toolkit (MDT). With an upgrade deployment you can use the same deployment technologies and process, but you can preserve users settings, and applications of the existing environment on the device.
Deployment tools and resources
Performing an upgrade deployment of Windows 10 requires the same tools and resources that are required for a traditional reimaging deployment. You can read about the tools required, including detailed explanations and installation instructions, in Deploy Windows 10 to Surface devices with MDT. To proceed with the upgrade deployment described in this article, you will need the following tools installed and configured:
You will also need to have available the following resources:
Prepare the upgrade deployment
Before you begin the process described in this section, you need to have installed and configured the deployment tools outlined in the previous Deployment tools and resources section. For instructions on how to install and configure the deployment tools, see the Install the deployment tools section in the Deploy Windows 10 to Surface devices with MDT article. You will also have needed to create a deployment share with MDT, described in the section Create a Deployment Share in the aforementioned article.
Windows 8 Rt TabletsImport Windows 10 installation files
Windows 10 installation files only need to be imported if you have not already done so in the deployment share. To import Windows 10 installation files, follow the steps described in the Import Windows installation files section in the Deploy Windows 10 to Surface devices with MDT article.
Import Surface drivers
In the import process example shown in the Deploy Windows 10 to Surface devices with MDT article, drivers for Surface Pro 4 were imported for Windows 10. To perform an upgrade deployment of Windows 10 to Surface Pro 3, drivers for Surface Pro 3 must also be imported. To import the Surface drivers for Surface Pro 3, follow these steps:
Import applications
Installation of applications in an upgrade deployment is not always necessary because the applications from the previous environment will remain on the device. (For example, in the Deploy Windows 10 to Surface devices with MDT article, the deployment includes Office 365 which is not required in an upgrade deployment where the user is already using Office 365 on the device.)
There are still some circumstances where you will want to deploy an application, even during an upgrade deployment. For example, you may have Surface Pro 3 devices on which you would like to add the Surface app. To deploy the Surface app in an upgrade scenario use the same process as you would for a traditional deployment. See the Deploy Surface app with Microsoft Store for Business article for instructions on how to add the Surface app to an MDT task sequence.
Create the upgrade task sequence
After you have all of the resources in place to perform the deployment (including the installation files, Surface drivers, and application files), the next step is to create the upgrade task sequence. This task sequence is a series of steps that will be performed on the device being upgraded that applies the new Windows environment, compatible drivers, and any applications you have specified.
Create the upgrade task sequence with the following process:
After the task sequence is created, you can modify some additional settings to provide additional automation of the task sequence and require less interaction during deployment. Follow these steps to modify the task sequence:
Steps 11 through 15 are very important to the deployment of Surface devices. These steps instruct the task sequence to install only drivers that are organized into the correct folder using the organization for drivers from the Import Surface drivers section.
Deployment share rules
To automate the upgrade process, the rules of the MDT deployment share need to be modified to suppress prompts for information from the user. Unlike a traditional deployment, Bootstrap.ini does not need to be modified because the deployment process is not started from boot media. Similarly, boot media does not need to be imported into WDS because it will not be booted over the network with PXE.
To modify the deployment share rules and suppress the Windows Deployment Wizard prompts for information, copy and paste the following text into the text box on the Rules tab of your deployment share properties:
For more information about the rules configured by this text, see the Configure deployment share rules section in the Deploy Windows 10 to Surface devices with MDT article.
Update deployment share
To update the deployment share, right-click the deployment share in the Deployment Workbench and click Update Deployment Share, then proceed through the Update Deployment Share Wizard. See the Update and import updated MDT boot media section of the Deploy Windows 10 to Surface devices with MDT article for detailed steps.
Run the upgrade deploymentWindows 8 Rt Download
Unlike a traditional deployment, the upgrade task sequence must be launched from within the Windows environment that will be upgraded. This requires that a user on the device to be upgraded navigate to the deployment share over the network and launch a script, LiteTouch.vbs. This script is the same script that displays the Windows Deployment Wizard in Windows PE in a traditional deployment. In this scenario, Litetouch.vbs will run within Windows. To perform the upgrade task sequence and deploy the upgrade to Windows 10 follow these steps:
Windows 8 Rt Upgrade
The task sequence will automatically install the drivers for Surface Pro 3 and the Surface app, and will perform any outstanding Windows Updates. When it completes, it will log out and be ready for the user to log on with the credentials they have always used for this device.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |