Manage HoloLens updates
HoloLens uses Windows Update in the same manner as other Windows 10 devices. When an update is available, it's automatically downloaded and installed the next time that your device is plugged in and connected to the internet. This article describes how to manage updates in an enterprise or other managed environment. For information about how to manage updates to individual HoloLens devices, see Update HoloLens.
How to optimize HoloLens updates
While the process of applying updates to HoloLens devices is similar to other Windows 10 devices, the device itself is different in subtle ways. For example, just like a PC, HoloLens performs updates in three steps: find eligible updates (scan), fetch the latest eligible update (download & install), and apply that update (reboot). However, each of those steps can be optimized further specifically for HoloLens devices to ensure that updates occur seamlessly and as soon as possible.
Overall summary of best practices: The device should be plugged in and connected to the internet outside of configured Active Hours, usually overnight, to ensure an update can be applied. Go to Settings -> Update & Security -> Windows Update to see current Active Hour settings.
1. Scan
What happens during Scan
This is the first step of the update process where the device queries Windows Update for any applicable updates. An update scan automatically occurs in the background once every 22 hours and requires that the device is either actively in use or on standby but plugged in to ensure internet connectivity. For the update scan to succeed, the device must have internet connectivity. This scan happens automatically, although a user can manually start a scan from the Settings app. If the device was turned off during the last scheduled scan, then it will initiate a scan the next time it's plugged in.
Best practices for Scan
The two critical pieces for scan to succeed are power and internet connectivity. We suggest that when users end their session with HoloLens they return it to an area where it's plugged in overnight and that it still has internet connectivity in that area.
If your device is having issues scanning for updates, review the troubleshooting scanning section and ensure you don't have any hindering configurations.
2. Download & Install
What happens during Download & Install
Once the device has scanned and found an applicable update, it can begin downloading the update. Like scanning, a user can manually choose to start the download.
Best practices for Download & Install
If the best practices for scanning are followed, then the device should be plugged into power and have internet connectivity. These best practices are the same, and after the scan, if an update is found it will start the download.
3. Restart
What happens during Restart
This is the final stage of the update process, and the device has already found, downloaded and staged the update. The remaining step is a device restart to complete installation and boot into the updated operating system. It needs to restart to start the install process, which as a benefit of state separation, is an atomic step. By default, the device won't restart during active hours. When it's finished the device will boot into the sign-in screen and be finished updating!
Best practices for Restart
If the device is left plugged in overnight, it'll automatically completely installing the update and restart during the maintenance window. Once the download has been installed and staged for a restart internet connectivity isn't a requirement.
Restarting the device is necessary for successfully applying the update but it also breaks into user behavior. HoloLens offers IT administrators the following levels of control over when and how the device should be restarted:
- Configure different default active hours. If your devices are used at different times of day, or you'd like to change your active hours so the update process is started at a different time of day.
- Consider configuring an update schedule.
- Set Deadlines. If you want to ensure that a download update isn't delayed by a user either directly or indirectly, you can set a deadline to force the device to update. Check out the new deadline policies added in 21H2.
Manage updates automatically
Managing updates by using Windows Update for Business
Windows Holographic for Business can use Windows Update for Business to manage updates. All HoloLens 2 devices can use Windows Holographic for Business. Make sure that they use Windows Holographic for Business build 10.0.18362.1042 or a later build. If you have HoloLens (1st gen) devices, you have to upgrade them to Windows Holographic for Business in order to manage their updates.
Windows Update for Business connects HoloLens devices directly to the Windows Update service. By using Windows Update for Business, you can control multiple aspects of the update process—that is, which devices get which updates at what time. For example, you can roll out updates to a subset of devices for testing, then later roll out updates to the remaining devices. Or, you can define different update schedules for different types of updates.
Note
For HoloLens devices, you can automatically manage feature updates (released two times a year) and quality updates (released monthly or as required, including critical security updates). For more information about update types, see Types of updates managed by Windows Update for Business.
You can configure Windows Update for Business settings for HoloLens by using policies in a Mobile Device Management (MDM) solution such as Microsoft Intune.
Managing Windows Update for Business by using Microsoft Intune
For a detailed discussion about how to use Intune to configure Windows Update for Business, see Manage Windows 10 software updates in Intune. For more information about the specific Intune functionality that HoloLens supports, see Intune update management functions that HoloLens supports.
Important
Intune provides two policy types for managing updates: Windows 10 update ring and Windows 10 feature update. The Windows 10 feature update policy type is in public preview at this time and is not supported for HoloLens.
You can use Windows 10 update ring policies to manage HoloLens 2 updates.
Configure update policies for HoloLens 2 or HoloLens (1st gen)
This section describes the policies that you can use to manage updates for either HoloLens 2 or HoloLens (1st gen). For more information about the functionality that is available for HoloLens 2, see Plan and configure update rollouts for HoloLens 2.
Policy CSP - Update defines the policies that configure Windows Update for Business.
Note
For a list of specific policy configuration service providers (CSPs) that are supported by specific editions of HoloLens, see Policy CSPs supported by HoloLens devices.
Configure automatic checks for updates
You can use the Update/AllowAutoUpdate policy to manage automatic update behavior, such as scanning, downloading, and installing updates. For more information about the available settings for this policy, see Update/AllowAutoUpdate.
Note
In Microsoft Intune, you can use Automatic Update Behavior to change this policy. For more information, see Manage Windows 10 software updates in Intune.
Configure an update schedule
To configure how and when updates are applied, use the following policies:
- Update/ScheduledInstallDay
- Values: 0–7 (0 = every day, 1 = Sunday, 7 = Saturday)
- Default value: 0 (every day)
- Update/ScheduledInstallTime
- Values: 0–23 (0 = midnight, 23 = 11 PM)
- Default value: 3 AM
Configure active hours
Starting with Windows Holographic, version 20H2 an IT Admin can specify the active hours range for HoloLens 2 devices.
Active hours identify the period of time when you expect the device to be in use. Automatic restarts after an update will occur outside of the active hours. The specified range will be counted from the active hours start time. You can use MDM, as described in Configuring active hours with MDM. MDM uses the Update/ActiveHoursStart and Update/ActiveHoursEnd and Update/ActiveHoursMaxRange settings in the Policy CSP to configure active hours.
- Update/ActiveHoursEnd - This value sets the end time. There's a 12-hour maximum from start time.
- Supported values are 0-23, where 0 is 12 AM, 1 is 1 AM, etc.
- The default is 17 (5 PM).
- Update/ActiveHoursMaxRange - This value sets max number of active hours from start time.
- Supported values are 8-18.
- The default value is 18 (hours).
- Update/ActiveHoursStart - This value sets the start time. There's a 12-hour maximum from end time.
- Supported values are 0-23, where 0 is 12 AM, 1 is 1 AM, etc.
- The default value is 8 (8 AM).
For devices that run Windows 10, version 1607 only
You can use the following update policies to configure devices to get updates from Windows Server Update Service (WSUS), instead of from Windows Update:
Improved update restart detection and notifications
- Introduced in Windows Holographic, version 21H2.
Between active hours and install time policies, it's possible to avoid rebooting HoloLens devices when they are in use. However, it would also delay the adoption of updates if reboots don’t occur to complete the installation of a required update. We’ve now added policies to allow IT to enforce deadlines and required reboots and ensure that the installation of an update is completed in a timely manner. Users can be notified prior to the reboot being initiated and they can delay the reboot in accordance with IT policy.
The following update policies were added:
- Update/AutoRestartNotificationSchedule
- Update/AutoRestartRequiredNotificationDismissal
- Update/ConfigureDeadlineForFeatureUpdates
- Update/ConfigureDeadlineForQualityUpdates
- Update/ConfigureDeadlineGracePeriod
- Update/ConfigureDeadlineNoAutoReboot
- Update/ScheduleImminentRestartWarning
- Update/ScheduleRestartWarning
- Update/UpdateNotificationLevel
Plan and configure update rollouts for HoloLens 2
HoloLens 2 supports more update automation features than HoloLens (1st gen) does. This is especially true if you use Microsoft Intune to manage Windows Update for Business policies. These features make it easier for you to plan and implement update rollouts across your organization.
Plan the update strategy
Windows Updates for Business supports deferral policies. After Microsoft releases an update, you can use a deferral policy to define how long to wait before installing that update on devices. By associating subsets of your devices (also known as update rings) with different deferral policies, you can coordinate an update rollout strategy for your organization.
Tip
It is suggested that organizations also have a subset of test devices on the Insider Preview Builds, which allow for early validation of functionality in your environment prior to each monthly release.
For example, consider an organization that has 1,000 devices, and has to update the devices in five waves. The organization can create five update rings, as shown in the following table.
Group | Number of devices | Deferral (days) |
---|---|---|
Grp 1 (IT staff) | 5 | 0 |
Grp 2 (early adopters) | 50 | 60 |
Grp 3 (main 1) | 250 | 120 |
Grp 4 (main 2) | 300 | 150 |
Grp 5 (main 3) | 395 | 180 |
Here's how the rollout progresses over time to the whole organization.
Configure an update deferral policy
A deferral policy specifies the number of days between the date on which an update becomes available and the date on which the update is offered to a device.
You can configure different deferrals for feature updates and quality updates. The following table lists the specific policies to use for each type, and the maximum deferral for each.
Category | Policy | Maximum deferral |
---|---|---|
Feature updates | DeferFeatureUpdatesPeriodInDays | 365 days |
Quality updates | DeferQualityUpdatesPeriodInDays | 30 days |
Pause Updates via Device
If a user doesn't have access to MDM they can individually Pause updates for up to 35 days manually on a HoloLens 2 device on build Windows Holographic, version 2004 or later. Users can reach this setting by navigating to Settings > Update & Security > Advanced options scroll down to Pause updates and select the date until which they'll pause updates. Once a user reached the pause limit, the device will need to get new updates before they can pause again.
Starting with Windows Holographic, version 20H2, this pause updates function can be managed for HoloLens 2 devices:
- Update/SetDisablePauseUXAccess.
- 0 (default) – Enabled
- 1 – Disabled
Intune update management functions that HoloLens supports
You can use the following Intune update management functions to manage updates for HoloLens.
Create and Assign: These functions add a Windows 10 update ring to the list of update rings. For more information, see Create and assign update rings.
Pause: If you encounter a problem when you deploy a feature or quality update, you can pause the update for 35 days (starting from a specified date). This pause prevents other devices from installing the update until you resolve or mitigate the problem. If you pause a feature update, quality updates are still offered to devices to make sure that they stay secure. When an update type is paused, the Overview pane for that ring displays how many days remain before that update type resumes. After the specified time has passed, the pause automatically expires, and the update process resumes.
While the update ring is paused, you can select either of the following options:
- Extend: Extend the pause period for an update type for 35 days.
- Resume: Restore updates for that ring to active operation. You can pause the update ring again, if it's necessary.
Note
The Uninstall operation for update rings is not supported for HoloLens 2 devices.
Delivery Optimization Preview
Windows Holographic, version 21H1 has enabled an early preview for delivery optimization settings to reduce bandwidth consumption for downloads from multiple HoloLens devices. A fuller description of this functionality along with the recommended network configuration is available here: Delivery Optimization for Windows 10 updates.
The following settings are enabled as part of the management surface and can be configured from Intune:
- DOCacheHost
- DOCacheHostSource
- DODelayCacheServerFallbackBackground
- DODelayCacheServerFallbackForeground
- DODownloadMode
- DOMaxBackgroundDownloadBandwidth
- DOMaxForegroundDownloadBandwidth
- DOPercentageMaxBackgroundBandwidth
- DOPercentageMaxForegroundBandwidth
- DOSetHoursToLimitForegroundDownloadBandwidth
- DOSetHoursToLimitBackgroundDownloadBandwidth
A few caveats about this preview offering:
- HoloLens support is limited in this preview to OS updates only.
- Windows Holographic for Business only supports HTTP download modes and downloads from a Microsoft Connected Cache endpoint; peer-to-peer download modes and group assignments aren't supported for HoloLens devices at this time.
- HoloLens doesn't support deployment or delivery optimization for Windows Server Update Services endpoints.
- Troubleshooting will require either diagnostics on the Connected Cache server or collecting a trace on HoloLens via Settings > Update & Security > Troubleshooting > Windows Update.
Manually check for updates
Although HoloLens periodically checks for system updates, there may be circumstances in which you want to manually check.
To manually check for updates, go to Settings > Update & Security > Check for updates. If the Settings app indicates that your device is up to date, you have all the updates that are currently available.
Manually roll back an update
In some cases, you might want to revert to a previous version of the HoloLens software. The process for doing this depends on whether you're using HoloLens 2 or HoloLens (1st gen).
Revert to a previous version (HoloLens 2)
You can roll back updates and return to a previous version of HoloLens 2 by using the Advanced Recovery Companion to reset your HoloLens to the earlier version.
Note
Reverting to an earlier version deletes your personal files and settings.
To revert to a previous version of HoloLens 2, follow these steps:
- Make sure that you don't have any phones or Windows devices plugged in to your computer.
- On your computer, download the Advanced Recovery Companion from the Microsoft Store.
- Download the most recent HoloLens 2 release.
- After these downloads finish, open File explorer > Downloads, right-click the compressed (.zip) folder that you just downloaded, and then select Extract all > Extract to expand the file.
- Use a USB-A to USB-C cable to connect your HoloLens device to your computer. Even if you've been using other cables to connect your HoloLens, this kind of cable works best.
- The Advanced Recovery Companion automatically detects your HoloLens device. Select the Microsoft HoloLens tile.
- On the next screen, select Manual package selection, and then open the folder that you previously expanded.
- Select the installation (.ffu) file.
- Select Install software, and then follow the instructions.
Revert to a previous version (HoloLens (1st gen))
You can roll back updates and return to a previous version of HoloLens (1st gen) by using the Windows Device Recovery Tool (WDRT) to reset your HoloLens to the earlier version.
Note
Reverting to an earlier HoloLens version deletes your personal files and settings.
To revert to a previous version of HoloLens (1st gen), follow these steps:
- Make sure that you don't have any phones or Windows devices plugged into your computer.
- On your computer, download the Windows Device Recovery Tool (WDRT).
- Download the HoloLens Anniversary Update recovery package.
- After the downloads finish, open File explorer > Downloads, right-click the compressed (.zip) folder that you just downloaded, and then select Extract all > Extract to expand the file.
- Use the micro-USB cable that was provided together with your HoloLens device to connect your HoloLens device to your computer. Even if you've been using other cables to connect your HoloLens device, this one works best.
- The WDRT automatically detects your HoloLens device. Select the Microsoft HoloLens tile.
- On the next screen, select Manual package selection, and then open the folder that you previously expanded.
- Select the installation (.ffu) file.
- Select Install software, and then follow the instructions.
If WDRT doesn't detect your device
If WDRT doesn't detect your HoloLens device, try restarting your computer. If that doesn't work, select My device was not detected, select Microsoft HoloLens, and then follow the instructions.
Troubleshooting updates
Issue - My device didn't find an update when scanning
If your devices are having issues successfully scanning for updates entirely (verify using a manual scan when you know an update is pending) then check the following configurations.
- That you if you have a restrictive network in your organization, that you have allowed the endpoints for Windows Update.
- Your device has received a deferral policy,and is already on the latest eligible update as determined by policy.
- Your device has received a pause policy which will prevent scans from occurring while the policy is in effect.
- If your device at Intune uses Feature Updates for Windows 10 or Quality Updates for Windows 10, remove devices from being opted in these rings. These aren't supported for HoloLens devices.
Issue - My device has downloaded an update, but won't install it
Many of the troubleshooting steps for scanning also apply here. If you've already reviewed those you may have an OS install issue. If so, file an issue through feedback hub using the Enterprise Management -> Device category.