diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index 6fa361d6e9..cddcf257b4 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -14968,7 +14968,7 @@ "redirect_document_id": true }, { -"source_path": "windows/hub/windows-10-landing.yml", +"source_path": "windows/windows-10/windows-10-landing.yml", "redirect_url": "/windows/hub/windows-10", "redirect_document_id": true }, diff --git a/.vscode/settings.json b/.vscode/settings.json new file mode 100644 index 0000000000..e7f59d08ec --- /dev/null +++ b/.vscode/settings.json @@ -0,0 +1,7 @@ +{ + "cSpell.words": [ + "kovter", + "kovter's", + "poshspy" + ] +} \ No newline at end of file diff --git a/browsers/internet-explorer/ie11-deploy-guide/set-up-enterprise-mode-portal.md b/browsers/internet-explorer/ie11-deploy-guide/set-up-enterprise-mode-portal.md index c6c5cf099e..83ca5233e3 100644 --- a/browsers/internet-explorer/ie11-deploy-guide/set-up-enterprise-mode-portal.md +++ b/browsers/internet-explorer/ie11-deploy-guide/set-up-enterprise-mode-portal.md @@ -45,8 +45,8 @@ You must download the deployment folder (**EMIEWebPortal/**), which includes all 6. Go back up a directory, open the solution file **EMIEWebPortal.sln** in Visual Studio, open **Web.config** from **EMIEWebPortal/** folder, and replace MSIT-LOB-COMPAT with your server name hosting your database, replace LOBMerged with your database name, and build the entire solution. - >[!Note] - >Step 3 of this topic provides the steps to create your database. + >[!Note] + >Step 3 of this topic provides the steps to create your database. 7. Copy the contents of the **EMIEWebPortal/** folder to a dedicated folder on your file system. For example, _D:\EMIEWebApp_. In a later step, you'll designate this folder as your website in the IIS Manager. diff --git a/devices/hololens/TOC.md b/devices/hololens/TOC.md index 6b1c835350..5d0635344e 100644 --- a/devices/hololens/TOC.md +++ b/devices/hololens/TOC.md @@ -1,17 +1,24 @@ # [Microsoft HoloLens](index.md) -## [What's new in Microsoft HoloLens](hololens-whats-new.md) -## [HoloLens in the enterprise: requirements and FAQ](hololens-requirements.md) -## [Insider preview for Microsoft HoloLens](hololens-insider.md) -## [Set up HoloLens](hololens-setup.md) +# [What's new in HoloLens](hololens-whats-new.md) +# [HoloLens in the enterprise: requirements and FAQ](hololens-requirements.md) +# [Set up HoloLens](hololens-setup.md) + +# Device Management +## [Unlock Windows Holographic for Business features](hololens-upgrade-enterprise.md) ## [Install localized version of HoloLens](hololens-install-localized.md) -## [Unlock Windows Holographic for Business features](hololens-upgrade-enterprise.md) +## [Configure HoloLens using a provisioning package](hololens-provisioning.md) ## [Enroll HoloLens in MDM](hololens-enroll-mdm.md) ## [Manage updates to HoloLens](hololens-updates.md) -## [Set up HoloLens in kiosk mode](hololens-kiosk.md) -## [Share HoloLens with multiple people](hololens-multiple-users.md) -## [Configure HoloLens using a provisioning package](hololens-provisioning.md) -## [Install apps on HoloLens](hololens-install-apps.md) -## [Enable Bitlocker device encryption for HoloLens](hololens-encryption.md) ## [Restore HoloLens 2 using Advanced Recovery Companion](hololens-recovery.md) + +# Application Management +## [Install apps on HoloLens](hololens-install-apps.md) +## [Share HoloLens with multiple people](hololens-multiple-users.md) + +# User/Access Management +## [Set up single application access](hololens-kiosk.md) +## [Enable Bitlocker device encryption for HoloLens](hololens-encryption.md) ## [How HoloLens stores data for spaces](hololens-spaces.md) -## [Change history for Microsoft HoloLens documentation](change-history-hololens.md) \ No newline at end of file + +# [Insider preview for Microsoft HoloLens](hololens-insider.md) +# [Change history for Microsoft HoloLens documentation](change-history-hololens.md) \ No newline at end of file diff --git a/devices/surface-hub/create-a-device-account-using-office-365.md b/devices/surface-hub/create-a-device-account-using-office-365.md index 2d52e698c0..85be497437 100644 --- a/devices/surface-hub/create-a-device-account-using-office-365.md +++ b/devices/surface-hub/create-a-device-account-using-office-365.md @@ -217,6 +217,8 @@ In order to enable Skype for Business, your environment will need to meet the fo ## Create a device account using the Exchange Admin Center +>[!NOTE] +>This method will only work if you are syncing from an on-premises Active Directory. You can use the Exchange Admin Center to create a device account: diff --git a/windows/client-management/advanced-troubleshooting-boot-problems.md b/windows/client-management/advanced-troubleshooting-boot-problems.md index 101ca103bc..b80840d43d 100644 --- a/windows/client-management/advanced-troubleshooting-boot-problems.md +++ b/windows/client-management/advanced-troubleshooting-boot-problems.md @@ -385,6 +385,6 @@ If the dump file shows an error that is related to a driver (for example, window 1. Start WinRE, and open a Command Prompt window. 2. Start a text editor, such as Notepad. - 3. Navigate to C\Windows\System32\Config\. + 3. Navigate to C:\Windows\System32\Config\. 4. Rename the all five hives by appending ".old" to the name. 5. Copy all the hives from the Regback folder, paste them in the Config folder, and then try to start the computer in Normal mode. diff --git a/windows/client-management/mdm/TOC.md b/windows/client-management/mdm/TOC.md index 3e6ae32cb4..54ce71766b 100644 --- a/windows/client-management/mdm/TOC.md +++ b/windows/client-management/mdm/TOC.md @@ -245,6 +245,7 @@ #### [RestrictedGroups](policy-csp-restrictedgroups.md) #### [Search](policy-csp-search.md) #### [Security](policy-csp-security.md) +#### [ServiceControlManager](policy-csp-servicecontrolmanager.md) #### [Settings](policy-csp-settings.md) #### [SmartScreen](policy-csp-smartscreen.md) #### [Speech](policy-csp-speech.md) diff --git a/windows/client-management/mdm/configuration-service-provider-reference.md b/windows/client-management/mdm/configuration-service-provider-reference.md index e90f12b931..b5fe65544d 100644 --- a/windows/client-management/mdm/configuration-service-provider-reference.md +++ b/windows/client-management/mdm/configuration-service-provider-reference.md @@ -941,7 +941,7 @@ Additional lists:
Home | +Pro | +Business | +Enterprise | +Education | +Mobile | +Mobile Enterprise | +
---|---|---|---|---|---|---|
![]() |
+ ![]() |
+ ![]() |
+ ![]() |
+ ![]() |
+ + | + |
Microsoft uses diagnostic data to: keep Windows secure and up to date, troubleshoot problems, and make product improvements as described in more detail below. Regardless of level selected, the device will be just as secure and will operate normally. This data is collected by Microsoft and stored with one or more unique identifiers that can help us recognize an individual user on an individual device, and understand the device's service issues and use patterns.
Diagnostic data is categorized into four levels:
Cortana is Microsoft’s personal digital assistant, which helps busy people get things done, even while they’re at work. Cortana on Windows is available in [certain regions and languages](https://support.microsoft.com/instantanswers/557b5e0e-0eb0-44db-87d6-5e5db6f9c5b0/cortana-s-regions-and-languages). Cortana learns from certain data about the user, such as location, searches, calendar, contacts, voice input, speech patterns, email, content and communication history from text messages. In Microsoft Edge, Cortana uses browsing history. The user is in control of how much data is shared.
Cortana has powerful configuration options, specifically optimized for a business. By signing in with an Azure Active Directory (Azure AD) account, enterprise users can give Cortana access to their enterprise/work identity, while getting all the functionality Cortana provides to them outside of work.
Summary | Originating update | Status | Date resolved |
Update not showing as applicable through WSUS or SCCM or when manually installed Update not showing as applicable through WSUS or SCCM or when manually installed See details > | OS Build 14393.2969 May 14, 2019 KB4494440 | Resolved KB4498947 | May 14, 2019 10:00 AM PT |
Unable to access some gov.uk websites gov.uk websites that don’t support “HSTS” may not be accessible See details > | OS Build 14393.2969 May 14, 2019 KB4494440 | Resolved KB4505052 | May 19, 2019 02:00 PM PT |
Layout and cell size of Excel sheets may change when using MS UI Gothic When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. See details > | OS Build 14393.2941 April 25, 2019 KB4493473 | Resolved KB4494440 | May 14, 2019 10:00 AM PT |
Zone transfers over TCP may fail Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail. See details > | OS Build 14393.2941 April 25, 2019 KB4493473 | Resolved KB4494440 | May 14, 2019 10:00 AM PT |
Details | Originating update | Status | History |
Update not showing as applicable through WSUS or SCCM or when manually installed KB4494440 or later updates may not show as applicable through WSUS or SCCM to the affected platforms. When manually installing the standalone update from Microsoft Update Catalog, it may fail to install with the error, \"The update is not applicable to your computer.\" Affected platforms:
Resolution: The servicing stack update (SSU) (KB4498947) must be installed before installing the latest cumulative update (LCU). The LCU will not be reported as applicable until the SSU is installed. For more information, see Servicing stack updates. Back to top | OS Build 14393.2969 May 14, 2019 KB4494440 | Resolved KB4498947 | Resolved: May 14, 2019 10:00 AM PT Opened: May 24, 2019 04:20 PM PT |
Unable to access some gov.uk websites After installing the May 14, 2019 update, some gov.uk websites that don’t support HTTP Strict Transport Security (HSTS) may not be accessible through Internet Explorer 11 or Microsoft Edge. Affected platforms:
Resolution: We have released an \"optional, out-of-band\" update for Windows 10 (KB4505052) to resolve this issue. If you are affected, we recommend you apply this update by installing KB4505052 from Windows Update and then restarting your device. This update will not be applied automatically. To download and install this update, go to Settings > Update & Security > Windows Update and select Check for updates. To get the standalone package for KB4505052, search for it in the Microsoft Update Catalog. Back to top | OS Build 14393.2969 May 14, 2019 KB4494440 | Resolved KB4505052 | Resolved: May 19, 2019 02:00 PM PT Opened: May 16, 2019 01:57 PM PT |
Layout and cell size of Excel sheets may change when using MS UI Gothic When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic. Affected platforms:
Resolution: This issue has been resolved. Back to top | OS Build 14393.2941 April 25, 2019 KB4493473 | Resolved KB4494440 | Resolved: May 14, 2019 10:00 AM PT Opened: May 10, 2019 10:35 AM PT |
Details | Originating update | Status | History |
Devices running Windows Server 2016 with Hyper-V seeing Bitlocker error 0xC0210000 Some devices running Windows Server 2016 with Hyper-V enabled may enter Bitlocker recovery mode and receive an error, \"0xC0210000\" after installing KB4494440 and restarting. Note Windows 10, version 1607 may also be affected when Bitlocker and Hyper-V are both enabled. Affected platforms:
Workaround: If your device is already in this state, you can successfully start Windows after suspending Bitlocker from the Windows Recovery Environment (WinRE) using the following steps:
Note The workaround needs to be followed on every system restart unless Bitlocker is suspended before restarting. To prevent this issue, execute the following command to temporarily suspend Bitlocker just before restarting the system: Manage-bde -protectors -disable c: -rc 1 Note This command will suspend Bitlocker for 1 restart of the device (-rc 1 option only works inside OS and does not work from recovery environment). Next steps: Microsoft is presently investigating this issue and will provide an update when available. Back to top | OS Build 14393.2969 May 14, 2019 KB4494440 | Mitigated | Last updated: May 23, 2019 09:57 AM PT Opened: May 21, 2019 08:50 AM PT |
Update not showing as applicable through WSUS or SCCM or when manually installed KB4494440 or later updates may not show as applicable through WSUS or SCCM to the affected platforms. When manually installing the standalone update from Microsoft Update Catalog, it may fail to install with the error, \"The update is not applicable to your computer.\" Affected platforms:
Resolution: The servicing stack update (SSU) (KB4498947) must be installed before installing the latest cumulative update (LCU). The LCU will not be reported as applicable until the SSU is installed. For more information, see Servicing stack updates. Back to top | OS Build 14393.2969 May 14, 2019 KB4494440 | Resolved KB4498947 | Resolved: May 14, 2019 10:00 AM PT Opened: May 24, 2019 04:20 PM PT |
Unable to access some gov.uk websites After installing the May 14, 2019 update, some gov.uk websites that don’t support HTTP Strict Transport Security (HSTS) may not be accessible through Internet Explorer 11 or Microsoft Edge. Affected platforms:
Resolution: We have released an \"optional, out-of-band\" update for Windows 10 (KB4505052) to resolve this issue. If you are affected, we recommend you apply this update by installing KB4505052 from Windows Update and then restarting your device. This update will not be applied automatically. To download and install this update, go to Settings > Update & Security > Windows Update and select Check for updates. To get the standalone package for KB4505052, search for it in the Microsoft Update Catalog. Back to top | OS Build 14393.2969 May 14, 2019 KB4494440 | Resolved KB4505052 | Resolved: May 19, 2019 02:00 PM PT Opened: May 16, 2019 01:57 PM PT |
Layout and cell size of Excel sheets may change when using MS UI Gothic When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic. Affected platforms:
Resolution: This issue has been resolved. Back to top | OS Build 14393.2941 April 25, 2019 KB4493473 | Resolved KB4494440 | Resolved: May 14, 2019 10:00 AM PT Opened: May 10, 2019 10:35 AM PT |
Details | Originating update | Status | History |
Issue using PXE to start a device from WDS After installing KB4489882, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension. Affected platforms:
Workaround: To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI to make the following adjustment:
Option 3: Set the following registry value to 0: HKLM\\System\\CurrentControlSet\\Services\\WDSServer\\Providers\\WDSTFTP\\EnableVariableWindowExtension Restart the WDSServer service after disabling the Variable Window Extension. Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 14393.2848 March 12, 2019 KB4489882 | Mitigated | Last updated: April 25, 2019 02:00 PM PT Opened: March 12, 2019 10:00 AM PT |
Custom URI schemes may not start corresponding application After installing KB4489882, Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites security zones on Internet Explorer. Affected platforms:
Resolution: This issue is resolved in KB4493473. Back to top | OS Build 14393.2848 March 12, 2019 KB4489882 | Resolved KB4493473 | Resolved: April 25, 2019 02:00 PM PT Opened: March 12, 2019 10:00 AM PT |
Details | Originating update | Status | History |
Custom URI schemes may not start corresponding application After installing KB4489871, custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites security zones on Internet Explorer. Affected platforms:
Resolution: This issue is resolved in KB4493436. Back to top | OS Build 15063.1689 March 12, 2019 KB4489871 | Resolved KB4493436 | Resolved: April 25, 2019 02:00 PM PT Opened: March 12, 2019 10:00 AM PT |
Details | Originating update | Status | History |
Custom URI schemes may not start corresponding application After installing KB4489886, custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites security zones on Internet Explorer. Affected platforms:
Resolution: This issue is resolved in KB4493440. Back to top | OS Build 16299.1029 March 12, 2019 KB4489886 | Resolved KB4493440 | Resolved: April 25, 2019 02:00 PM PT Opened: March 12, 2019 10:00 AM PT |
Details | Originating update | Status | History |
Issue using PXE to start a device from WDS After installing KB4489868, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension. Affected platforms:
Workaround: To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI to make the following adjustment:
Option 3: Set the following registry value to 0: HKLM\\System\\CurrentControlSet\\Services\\WDSServer\\Providers\\WDSTFTP\\EnableVariableWindowExtension Restart the WDSServer service after disabling the Variable Window Extension. Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 17134.648 March 12, 2019 KB4489868 | Mitigated | Last updated: April 25, 2019 02:00 PM PT Opened: March 12, 2019 10:00 AM PT |
Custom URI schemes may not start corresponding application After installing KB4489868, custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites security zones on Internet Explorer. Affected platforms:
Resolution: This issue is resolved in KB4493437. Back to top | OS Build 17134.648 March 12, 2019 KB4489868 | Resolved KB4493437 | Resolved: April 25, 2019 02:00 PM PT Opened: March 12, 2019 10:00 AM PT |
Summary | Originating update | Status | Last updated |
Windows Sandbox may fail to start with error code “0x80070002” Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language was changed between updates See details > | OS Build 18362.116 May 20, 2019 KB4505057 | Acknowledged | May 24, 2019 04:20 PM PT |
Loss of functionality in Dynabook Smartphone Link app After updating to Windows 10, version 1903, you may experience a loss of functionality when using the Dynabook Smartphone Link application. See details > | OS Build 18362.116 May 20, 2019 KB4505057 | Investigating | May 24, 2019 03:10 PM PT |
Display brightness may not respond to adjustments Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Investigating | May 21, 2019 04:47 PM PT |
Audio not working with Dolby Atmos headphones and home theater Users may experience audio loss with Dolby Atmos headphones or Dolby Atmos home theater. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Investigating | May 21, 2019 07:17 AM PT |
Duplicate folders and documents showing in user profile directory If known folders (e.g. Desktop, Documents, or Pictures folders) are redirected, an empty folder with that same name may be created. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Investigating | May 21, 2019 07:16 AM PT |
Gamma ramps, color profiles, and night light settings do not apply in some cases Microsoft has identified some scenarios where gamma ramps, color profiles and night light settings may stop working. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | May 24, 2019 11:02 AM PT |
AMD RAID driver incompatibility Installation process may stop when trying to install Windows 10, version 1903 update on computers that run certain versions of AMD RAID drivers. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | May 23, 2019 09:28 AM PT |
Error attempting to update with external USB device or memory card attached PCs with an external USB device or SD memory card attached may get error: \"This PC can't be upgraded to Windows 10.\" See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | May 21, 2019 04:49 PM PT |
Unable to discover or connect to Bluetooth devices Microsoft has identified compatibility issues with some versions of Realtek and Qualcomm Bluetooth radio drivers. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | May 21, 2019 04:48 PM PT |
Night light settings do not apply in some cases Microsoft has identified some scenarios where night light settings may stop working. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | May 21, 2019 04:48 PM PT |
Intel Audio displays an intcdaud.sys notification Microsoft and Intel have identified an issue with a range of Intel Display Audio device drivers that may result in battery drain. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | May 21, 2019 04:47 PM PT |
Cannot launch Camera app Microsoft and Intel have identified an issue affecting Intel RealSense SR300 or Intel RealSense S200 camera apps. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | May 21, 2019 04:47 PM PT |
Intermittent loss of Wi-Fi connectivity Some older devices may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | May 21, 2019 04:46 PM PT |
Details | Originating update | Status | History |
Windows Sandbox may fail to start with error code “0x80070002” Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903. Affected platforms:
Next steps: We are working on a resolution and estimate a solution will be available in late June. Back to top | OS Build 18362.116 May 20, 2019 KB4505057 | Acknowledged | Last updated: May 24, 2019 04:20 PM PT Opened: May 24, 2019 04:20 PM PT |
Loss of functionality in Dynabook Smartphone Link app Some users may experience a loss of functionality after updating to Windows 10, version 1903 when using the Dynabook Smartphone Link application on Windows devices. Loss of functionality may affect the display of phone numbers in the Call menu and the ability to answer phone calls on the Windows PC. To safeguard your update experience, we have applied a compatibility hold on devices with Dynabook Smartphone Link from being offered Windows 10, version 1903, until this issue is resolved. Affected platforms:
Next steps: Microsoft and Dynabook are working on a resolution; the Dynabook Smartphone Link application may have a loss of functionality until this issue is resolved. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Back to top | OS Build 18362.116 May 20, 2019 KB4505057 | Investigating | Last updated: May 24, 2019 03:10 PM PT Opened: May 24, 2019 03:10 PM PT |
Display brightness may not respond to adjustments Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers. After updating to Window 10, version 1903, brightness settings may sometime appear as if changes applied took effect, yet the actual display brightness doesn't change. To safeguard your update experience, we have applied a compatibility hold on devices with certain Intel drivers from being offered Windows 10, version 1903, until this issue is resolved. Affected platforms:
Workaround: Restart your device to apply changes to brightness. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Next steps: We are working on a resolution that will be made available in upcoming release. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Investigating | Last updated: May 21, 2019 04:47 PM PT Opened: May 21, 2019 07:56 AM PT |
Audio not working with Dolby Atmos headphones and home theater After updating to Windows 10, version 1903, you may experience loss of audio with Dolby Atmos for home theater (free extension) or Dolby Atmos for headphones (paid extension) acquired through the Microsoft Store due to a licensing configuration error. This occurs due to an issue with a Microsoft Store licensing component, where license holders are not able to connect to the Dolby Access app and enable Dolby Atmos extensions. To safeguard your update experience, we have applied protective hold on devices from being offered Windows 10, version 1903 until this issue is resolved. This configuration error will not result in loss of access for the acquired license once the problem is resolved. Affected platforms:
Next steps: We are working on a resolution for Microsoft Store and estimate a solution will be available in mid-June. Note We recommend you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Investigating | Last updated: May 21, 2019 07:17 AM PT Opened: May 21, 2019 07:16 AM PT |
Duplicate folders and documents showing in user profile directory If you have redirected known folders (e.g. Desktop, Documents, or Pictures folders) you may see an empty folder with the same name in your %userprofile% directories after updating to Windows 10, version 1903. This may occur if known folders were redirected when you chose to back up your content to OneDrive using the OneDrive wizard, or if you chose to back up your content during the Windows Out-of-Box-Experience (OOBE). This may also occur if you redirected your known folders manually through the Properties dialog box in File Explorer. This issue does not cause any user files to be deleted and a solution is in progress. To safeguard your update experience, we have applied a quality hold on devices with redirected known folders from being offered Windows 10, version 1903, until this issue is resolved. Affected platforms:
Next steps: Microsoft is working on a resolution and estimates a solution will be available in late May. Note We recommend that you do not attempt to manually update to Windows 10, version 1903 using the Update now button or the Media Creation Tool until this issue has been resolved. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Investigating | Last updated: May 21, 2019 07:16 AM PT Opened: May 21, 2019 07:16 AM PT |
Gamma ramps, color profiles, and night light settings do not apply in some cases Microsoft has identified some scenarios where gamma ramps, color profiles and night light settings may stop working. Microsoft has identified some scenarios where night light settings may stop working, for example:
Affected platforms:
Workaround: If you find that your night light has stopped working, try turning the night light off and on, or restarting your computer. For other color setting issues, restart your computer to correct the issue. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Next steps: We are working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | Last updated: May 24, 2019 11:02 AM PT Opened: May 21, 2019 07:28 AM PT |
AMD RAID driver incompatibility Microsoft and AMD have identified an incompatibility with AMD RAID driver versions earlier than 9.2.0.105. When you attempt to install the Windows 10, version 1903 update on a Windows 10-based computer with an affected driver version, the installation process stops and you get a message like the following: AMD Ryzen™ or AMD Ryzen™ Threadripper™ configured in SATA or NVMe RAID mode. “A driver is installed that causes stability problems on Windows. This driver will be disabled. Check with your software/driver provider for an updated version that runs on this version of Windows.” To safeguard your update experience, we have applied a compatibility hold on devices with these AMD drivers from being offered Windows 10, version 1903, until this issue is resolved. Affected platforms:
Workaround: To resolve this issue, download the latest AMD RAID drivers directly from AMD at https://www.amd.com/en/support/chipsets/amd-socket-tr4/x399. The drivers must be version 9.2.0.105 or later. Install the drivers on the affected computer, and then restart the installation process for the Windows 10, version 1903 feature update. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until a new driver has been installed and the Windows 10, version 1903 feature update has been automatically offered to you. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | Last updated: May 23, 2019 09:28 AM PT Opened: May 21, 2019 07:12 AM PT |
Error attempting to update with external USB device or memory card attached If you have an external USB device or SD memory card attached when installing Windows 10, version 1903, you may get an error message stating \"This PC can't be upgraded to Windows 10.\" This is caused by inappropriate drive reassignment during installation. Sample scenario: An update to Windows 10, version 1903 is attempted on a computer that has a thumb drive inserted into its USB port. Before the update, the thumb drive is mounted in the system as drive G based on the existing drive configuration. After the feature update is installed; however, the device is reassigned a different drive letter (e.g., drive H). Note The drive reassignment is not limited to removable drives. Internal hard drives may also be affected. To safeguard your update experience, we have applied a hold on devices with an external USB device or SD memory card attached from being offered Windows 10, version 1903 until this issue is resolved. Affected platforms:
Workaround: To work around this issue, remove all external media, such as USB devices and SD cards, from your computer and restart installation of the Windows 10, version 1903 feature update. The update should then proceed normally. Note If you need to keep your external device, SD memory card, or other devices attached to your computer while updating, we recommend that you do not attempt to manually update to Windows 10, version 1903 using the Update now button or the Media Creation Tool until this issue has been resolved. Next steps: Microsoft is working on a resolution and estimate a solution will be available in late May. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | Last updated: May 21, 2019 04:49 PM PT Opened: May 21, 2019 07:38 AM PT |
Unable to discover or connect to Bluetooth devices Microsoft has identified compatibility issues with some driver versions for Bluetooth radios made by Realtek and Qualcomm. To safeguard your update experience, we have applied a compatibility hold on devices with affected driver versions for Realtek or Qualcomm Bluetooth radios from being offered Windows 10, version 1903 or Windows Server, version 1903 until the driver has been updated. Affected platforms:
Workaround: Check with your device manufacturer (OEM) to see if an updated driver is available and install it.
Note Until an updated driver has been installed, we recommend you do not attempt to manually update using the Update now button or the Media Creation Tool. Next steps: Microsoft is working with Realtek and Qualcomm to release new drivers for all affected system via Windows Update. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | Last updated: May 21, 2019 04:48 PM PT Opened: May 21, 2019 07:29 AM PT |
Night light settings do not apply in some cases Microsoft has identified some scenarios where night light settings may stop working, for example:
Affected platforms:
Workaround: If you find that your night light settings have stopped working, try turning the night light on and off, or restart your computer. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Next steps: We are working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | Last updated: May 21, 2019 04:48 PM PT Opened: May 21, 2019 07:28 AM PT |
Intel Audio displays an intcdaud.sys notification Microsoft and Intel have identified an issue with a range of Intel Display Audio device drivers that may result in higher than normal battery drain. If you see an intcdaud.sys notification or “What needs your attention” notification when trying to update to Windows 10, version 1903, you have an affected Intel Audio Display device driver installed on your machine (intcdaud.sys, versions 10.25.0.3 through 10.25.0.8). To safeguard your update experience, we have applied a compatibility hold on devices with drivers from being offered Windows 10, version 1903 until updated device drivers have been installed. Affected platforms:
Workaround: On the “What needs your attention\" notification, click the Back button to remain on your current version of Windows 10. (Do not click Confirm as this will proceed with the update and you may experience compatibility issues.) Affected devices will automatically revert to the previous working configuration. For more information, see Intel's customer support guidance and the Microsoft knowledge base article KB4465877. Note We recommend you do not attempt to update your devices until newer device drivers are installed. Next steps: You can opt to wait for newer drivers to be installed automatically through Windows Update or check with the computer manufacturer for the latest device driver software availability and installation procedures. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | Last updated: May 21, 2019 04:47 PM PT Opened: May 21, 2019 07:22 AM PT |
Cannot launch Camera app Microsoft and Intel have identified an issue affecting Intel RealSense SR300 and Intel RealSense S200 cameras when using the Camera app. After updating to the Windows 10 May 2019 Update and launching the Camera app, you may get an error message stating: \"Close other apps, error code: 0XA00F4243.” To safeguard your update experience, we have applied a protective hold on machines with Intel RealSense SR300 or Intel RealSense S200 cameras installed from being offered Windows 10, version 1903, until this issue is resolved. Affected platforms:
Workaround: To temporarily resolve this issue, perform one of the following:
or
or
Note This workaround will only resolve the issue until your next system restart. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Next steps: We are working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | Last updated: May 21, 2019 04:47 PM PT Opened: May 21, 2019 07:20 AM PT |
Intermittent loss of Wi-Fi connectivity Some older computers may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver. An updated Wi-Fi driver should be available from your device manufacturer (OEM). To safeguard your upgrade experience, we have applied a hold on devices with this Qualcomm driver from being offered Windows 10, version 1903, until the updated driver is installed. Affected platforms:
Workaround: Download and install an updated Wi-Fi driver from your device manufacturer (OEM). Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until a new driver has been installed and the Windows 10, version 1903 feature update has been automatically offered to you. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | Last updated: May 21, 2019 04:46 PM PT Opened: May 21, 2019 07:13 AM PT |
System unresponsive after restart if Sophos Endpoint Protection installed Devices with Sophos Endpoint Protection installed and managed by Sophos Central or Sophos Enterprise Console (SEC) may become unresponsive upon restart. See details > | April 09, 2019 KB4493472 | Resolved | May 14, 2019 01:22 PM PT |
System may be unresponsive after restart if Avira antivirus software installed Devices with Avira antivirus software installed may become unresponsive upon restart. See details > | April 09, 2019 KB4493472 | Resolved | May 14, 2019 01:21 PM PT |
Authentication may fail for services after the Kerberos ticket expires Authentication may fail for services that require unconstrained delegation after the Kerberos ticket expires. See details > | March 12, 2019 KB4489878 | Resolved KB4499164 | May 14, 2019 10:00 AM PT |
Devices may not respond at login or Welcome screen if running certain Avast software Devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software may become unresponsive after restart. See details > | April 09, 2019 KB4493472 | Resolved | April 25, 2019 02:00 PM PT |
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-5-7 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights |
-None |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-5-11 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=System,cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights |
-[Access this computer from the network](/windows/device-security/security-policy-settings/access-this-computer-from-the-network): SeNetworkLogonRight -[Add workstations to domain](/windows/device-security/security-policy-settings/add-workstations-to-domain): SeMachineAccountPrivilege -[Bypass traverse checking](/windows/device-security/security-policy-settings/bypass-traverse-checking): SeChangeNotifyPrivilege |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-5-3 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights |
-None |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-3-1 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights |
-None |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-3-0 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights |
-None |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-5-1 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights |
-None |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-5-64-21 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights |
-None |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-5-9 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights Assignment |
-[Access this computer from the network](/windows/device-security/security-policy-settings/access-this-computer-from-the-network): SeNetworkLogonRight -[Allow log on locally](/windows/device-security/security-policy-settings/allow-log-on-locally): SeInteractiveLogonRight |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-1-0 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights |
-[Access this computer from the network](/windows/device-security/security-policy-settings/access-this-computer-from-the-network): SeNetworkLogonRight -[Act as part of the operating system](/windows/device-security/security-policy-settings/act-as-part-of-the-operating-system): SeTcbPrivilege -[Bypass traverse checking](/windows/device-security/security-policy-settings/bypass-traverse-checking): SeChangeNotifyPrivilege |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-5-4 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights |
-None |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-5-19 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default user rights |
-[Adjust memory quotas for a process](/windows/device-security/security-policy-settings/adjust-memory-quotas-for-a-process): SeIncreaseQuotaPrivilege -[Bypass traverse checking](/windows/device-security/security-policy-settings/bypass-traverse-checking): SeChangeNotifyPrivilege -[Change the system time](/windows/device-security/security-policy-settings/change-the-system-time): SeSystemtimePrivilege -[Change the time zone](/windows/device-security/security-policy-settings/change-the-time-zone): SeTimeZonePrivilege -[Create global objects](/windows/device-security/security-policy-settings/create-global-objects): SeCreateGlobalPrivilege -[Generate security audits](/windows/device-security/security-policy-settings/generate-security-audits): SeAuditPrivilege -[Impersonate a client after authentication](/windows/device-security/security-policy-settings/impersonate-a-client-after-authentication): SeImpersonatePrivilege -[Replace a process level token](/windows/device-security/security-policy-settings/replace-a-process-level-token): SeAssignPrimaryTokenPrivilege |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-5-18 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights |
-None |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-5-2 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights |
-None |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-5-20 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights |
-[Adjust memory quotas for a process](/windows/device-security/security-policy-settings/adjust-memory-quotas-for-a-process): SeIncreaseQuotaPrivilege -[Bypass traverse checking](/windows/device-security/security-policy-settings/bypass-traverse-checking): SeChangeNotifyPrivilege -[Create global objects](/windows/device-security/security-policy-settings/create-global-objects): SeCreateGlobalPrivilege -[Generate security audits](/windows/device-security/security-policy-settings/generate-security-audits): SeAuditPrivilege -[Impersonate a client after authentication](/windows/device-security/security-policy-settings/impersonate-a-client-after-authentication): SeImpersonatePrivilege -[Restore files and directories](/windows/device-security/security-policy-settings/restore-files-and-directories): SeRestorePrivilege -[Replace a process level token](/windows/device-security/security-policy-settings/replace-a-process-level-token): SeAssignPrimaryTokenPrivilege |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-5-64-10 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights |
-None |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-5-1000 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights |
-None |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-5-10 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights |
-None |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-5-14 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights |
-None |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-5-12 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights |
-None |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-5-64-14 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights |
-None |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-5-6 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights |
-[Create global objects](/windows/device-security/security-policy-settings/create-global-objects): SeCreateGlobalPrivilege -[Impersonate a client after authentication](/windows/device-security/security-policy-settings/impersonate-a-client-after-authentication): SeImpersonatePrivilege |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-5-13 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights |
-None |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-S-1-5-15 |
-
Object Class |
-Foreign Security Principal |
-
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights |
-None |
-
Attribute | -Value | -
---|---|
Well-Known SID/RID |
-- |
Object Class |
-- |
Default Location in Active Directory |
-cn=WellKnown Security Principals, cn=Configuration, dc=<forestRootDomain> |
-
Default User Rights |
-[Bypass traverse checking](/windows/device-security/security-policy-settings/bypass-traverse-checking): SeChangeNotifyPrivilege -[Increase a process working set](/windows/device-security/security-policy-settings/increase-a-process-working-set): SeIncreaseWorkingSetPrivilege |
-