-AllowManagementOS $true
+Install-WindowsFeature -Name Hyper-V -IncludeManagementTools
+```
+
+When you are prompted to restart the computer, choose **Yes**. The computer might restart more than once.
+
+>Alternatively, you can install Hyper-V using the Control Panel in Windows under **Turn Windows features on or off** for a client operating system, or using Server Manager's **Add Roles and Features Wizard** on a server operating system, as shown below:
+
+ 
+
+ 
+
+If you choose to install Hyper-V using Server Manager, accept all default selections. Also be sure to install both items under **Role Administration Tools\Hyper-V Management Tools**.
+
+After installation is complete, open Hyper-V Manager by typing **virtmgmt.msc** at an elevated command prompt, or by typing **Hyper-V** in the Start menu search box.
+
+To read more about Hyper-V, see [Introduction to Hyper-V on Windows 10](https://docs.microsoft.com/virtualization/hyper-v-on-windows/about/) and [Hyper-V on Windows Server](https://docs.microsoft.com/windows-server/virtualization/hyper-v/hyper-v-on-windows-server).
+
+## Create a demo VM
+
+Now that Hyper-V is enabled, we need to create a VM running Windows 10. We can [create a VM](https://docs.microsoft.com/virtualization/hyper-v-on-windows/quick-start/create-virtual-machine) and [virtual network](https://docs.microsoft.com/virtualization/hyper-v-on-windows/quick-start/connect-to-network) using Hyper-V Manager, but it is simpler to use Windows PowerShell.
+
+To use Windows Powershell we just need to know two things:
+
+1. The location of the Windows 10 ISO file.
+ - In the example, we assume the location is **c:\iso\win10-eval.iso**.
+2. The name of the network interface that connects to the Internet.
+ - In the example, we use a Windows PowerShell command to determine this automatically.
+
+After we have set the ISO file location and determined the name of the appropriate network interface, we can install Windows 10.
+
+### Set ISO file location
+
+You can download an ISO file for an evaluation version of the latest release of Windows 10 Enterprise [here](https://www.microsoft.com/evalcenter/evaluate-windows-10-enterprise).
+- When asked to select a platform, choose **64 bit**.
+
+After you download this file, the name will be extremely long (ex: 17763.107.101029-1455.rs5_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us.iso).
+
+1. So that it is easier to type and remember, rename the file to **win10-eval.iso**.
+2. Create a directory on your computer named **c:\iso** and move the **win10-eval.iso** file there, so the path to the file is **c:\iso\win10-eval.iso**.
+3. If you wish to use a different name and location for the file, you must modify the Windows PowerShell commands below to use your custom name and directory.
+
+### Determine network adapter name
+
+The Get-NetAdaper cmdlet is used below to automatically find the network adapter that is most likely to be the one you use to connect to the Internet. You should test this command first by running the following at an elevated Windows PowerShell prompt:
+
+```powershell
+(Get-NetAdapter |?{$_.Status -eq "Up" -and !$_.Virtual}).Name
+```
+
+The output of this command should be the name of the network interface you use to connect to the Internet. Verify that this is the correct interface name. If it is not the correct interface name, you'll need to edit the first command below to use your network interface name.
+
+For example, if the command above displays Ethernet but you wish to use Ethernet2, then the first command below would be New-VMSwitch -Name AutopilotExternal -AllowManagementOS $true -NetAdapterName **Ethernet2**.
+
+### Use Windows PowerShell to create the demo VM
+
+All VM data will be created under the current path in your PowerShell prompt. Consider navigating into a new folder before running the following commands.
+
+>[!IMPORTANT]
+>**VM switch**: a VM switch is how Hyper-V connects VMs to a network.
If you have previously enabled Hyper-V and your Internet-connected network interface is already bound to a VM switch, then the PowerShell commands below will fail. In this case, you can either delete the existing VM switch (so that the commands below can create one), or you can reuse this VM switch by skipping the first command below and either modifying the second command to replace the switch name **AutopilotExternal** with the name of your switch, or by renaming your existing switch to "AutopilotExternal."
If you have never created an external VM switch before, then just run the commands below.
+
+```powershell
+New-VMSwitch -Name AutopilotExternal -AllowManagementOS $true -NetAdapterName (Get-NetAdapter |?{$_.Status -eq "Up" -and !$_.Virtual}).Name
New-VM -Name WindowsAutopilot -MemoryStartupBytes 2GB -BootDevice VHD -NewVHDPath .\VMs\WindowsAutopilot.vhdx -Path .\VMData -NewVHDSizeBytes 80GB -Generation 2 -Switch AutopilotExternal
-Add-VMDvdDrive -Path -VMName WindowsAutopilot
+Add-VMDvdDrive -Path c:\iso\win10-eval.iso -VMName WindowsAutopilot
Start-VM -VMName WindowsAutopilot
```
->[!IMPORTANT]
->Make sure to replace <*Name of Network Adapter with internet access*> and <*Path to Windows 10 ISO*> with the appropriate values.
->Additionally, note that all Virtual Machine related data will be created under the current path in your PowerShell prompt. Consider navigating into a new folder before running the above.
+After entering these commands, connect to the VM that you just created and wait for a prompt to press a key and boot from the DVD. You can connect to the VM by double-clicking it in Hyper-V Manager.
+
+See the sample output below. In this sample, the VM is created under the **c:\autopilot** directory and the vmconnect.exe command is used (which is only available on Windows Server). If you installed Hyper-V on Windows 10, use Hyper-V Manager to connect to your VM.
+
+
+PS C:\autopilot> dir c:\iso
+
+
+ Directory: C:\iso
+
+
+Mode LastWriteTime Length Name
+---- ------------- ------ ----
+-a---- 3/12/2019 2:46 PM 4627343360 win10-eval.iso
+
+PS C:\autopilot> (Get-NetAdapter |?{$_.Status -eq "Up" -and !$_.Virtual}).Name
+Ethernet
+PS C:\autopilot> New-VMSwitch -Name AutopilotExternal -AllowManagementOS $true -NetAdapterName (Get-NetAdapter |?{$_.Status -eq "Up" -and !$_.Virtual}).Name
+
+Name SwitchType NetAdapterInterfaceDescription
+---- ---------- ------------------------------
+AutopilotExternal External Intel(R) Ethernet Connection (2) I218-LM
+
+PS C:\autopilot> New-VM -Name WindowsAutopilot -MemoryStartupBytes 2GB -BootDevice VHD -NewVHDPath .\VMs\WindowsAutopilot.vhdx -Path .\VMData -NewVHDSizeBytes 80GB -Generation 2 -Switch AutopilotExternal
+
+Name State CPUUsage(%) MemoryAssigned(M) Uptime Status Version
+---- ----- ----------- ----------------- ------ ------ -------
+WindowsAutopilot Off 0 0 00:00:00 Operating normally 8.0
+
+PS C:\autopilot> Add-VMDvdDrive -Path c:\iso\win10-eval.iso -VMName WindowsAutopilot
+PS C:\autopilot> Start-VM -VMName WindowsAutopilot
+PS C:\autopilot> vmconnect.exe localhost WindowsAutopilot
+PS C:\autopilot> dir
+
+ Directory: C:\autopilot
+
+Mode LastWriteTime Length Name
+---- ------------- ------ ----
+d----- 3/12/2019 3:15 PM VMData
+d----- 3/12/2019 3:42 PM VMs
+
+PS C:\autopilot>
+
### Install Windows 10
-Now that the Virtual Machine was created and started, open **Hyper-V Manager** and connect to the **WindowsAutopilot** Virtual Machine.
-Make sure the Virtual Machine booted from the installation media you've provided and complete the Windows installation process.
+Ensure the VM booted from the installation ISO, click **Next** then click **Install now** and complete the Windows installation process. See the following examples:
-Once the installation is complete, create a checkpoint. You will create multiple checkpoints throughout this process, which you can later use to go through the process again.
+ 
+ 
+ 
+ 
+ 
+ 
+
+>After the VM restarts, during OOBE, it’s fine to select **Set up for personal use** or **Domain join instead** and then choose an offline account on the **Sign in** screen. This will offer the fastest way to the desktop. For example:
+
+ 
+
+Once the installation is complete, sign in and verify that you are at the Windows 10 desktop, then create your first Hyper-V checkpoint. Checkpoints are used to restore the VM to a previous state. You will create multiple checkpoints throughout this lab, which can be used later to go through the process again.
+
+ 
+
+To create your first checkpoint, open an elevated Windows PowerShell prompt on the computer running Hyper-V (not on the VM) and run the following:
-To create the checkpoint, open a PowerShell prompt **as an administrator** and run the following:
```powershell
Checkpoint-VM -Name WindowsAutopilot -SnapshotName "Finished Windows install"
```
-## Capture your Virtual Machine's hardware ID
+Click on the **WindowsAutopilot** VM in Hyper-V Manager and verify that you see **Finished Windows Install** listed in the Checkpoints pane.
-On the newly created Virtual Machine, open a PowerShell prompt **as an administrator** and run the following:
-```powershell
-md c:\HWID
-Set-Location c:\HWID
-Set-ExecutionPolicy Unrestricted
-Install-Script -Name Get-WindowsAutopilotInfo
-Get-WindowsAutopilotInfo.ps1 -OutputFile AutopilotHWID.csv
-```
+## Capture the hardware ID
+
+>NOTE: Normally, the Device ID is captured by the OEM as they run the OA3 Tool on each device in the factory. The OEM then submits the 4K HH created by the OA3 Tool to Microsoft by submitting it with a Computer Build Report (CBR). For purposes of this lab, you are acting as the OEM (capturing the 4K HH), but you’re not going to use the OA3 Tool to capture the full 4K HH for various reasons (you’d have to install the OA3 tool, your device couldn’t have a volume license version of Windows, it’s a more complicated process than using a PS script, etc.). Instead, you’ll simulate running the OA3 tool by running a PowerShell script, which captures the device 4K HH just like the OA3 tool.
+
+Follow these steps to run the PS script:
+
+1. Open an elevated Windows PowerShell prompt and run the following commands. These commands are the same regardless of whether you are using a VM or a physical device:
+
+ ```powershell
+ md c:\HWID
+ Set-Location c:\HWID
+ Set-ExecutionPolicy -Scope Process -ExecutionPolicy Unrestricted -Force
+ Install-Script -Name Get-WindowsAutopilotInfo -Force
+ $env:Path += ";C:\Program Files\WindowsPowerShell\Scripts"
+ Get-WindowsAutopilotInfo.ps1 -OutputFile AutopilotHWID.csv
+ ```
+
+When you are prompted to install the NuGet package, choose **Yes**.
+
+See the sample output below.
+
+
+PS C:\> md c:\HWID
+
+ Directory: C:\
+
+Mode LastWriteTime Length Name
+---- ------------- ------ ----
+d----- 3/14/2019 11:33 AM HWID
+
+PS C:\> Set-Location c:\HWID
+PS C:\HWID> Set-ExecutionPolicy -Scope Process -ExecutionPolicy Unrestricted -Force
+PS C:\HWID> Install-Script -Name Get-WindowsAutopilotInfo -Force
+
+NuGet provider is required to continue
+PowerShellGet requires NuGet provider version '2.8.5.201' or newer to interact with NuGet-based repositories. The NuGet
+ provider must be available in 'C:\Program Files\PackageManagement\ProviderAssemblies' or
+'C:\Users\user1\AppData\Local\PackageManagement\ProviderAssemblies'. You can also install the NuGet provider by running
+ 'Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force'. Do you want PowerShellGet to install and
+import the NuGet provider now?
+[Y] Yes [N] No [S] Suspend [?] Help (default is "Y"): Y
+PS C:\HWID> $env:Path += ";C:\Program Files\WindowsPowerShell\Scripts"
+PS C:\HWID> Get-WindowsAutopilotInfo.ps1 -OutputFile AutopilotHWID.csv
+PS C:\HWID> dir
+
+ Directory: C:\HWID
+
+Mode LastWriteTime Length Name
+---- ------------- ------ ----
+-a---- 3/14/2019 11:33 AM 8184 AutopilotHWID.csv
+
+PS C:\HWID>
+
+
+Verify that there is an **AutopilotHWID.csv** file in the **c:\HWID** directory that is about 8 KB in size. This file contains the complete 4K HH.
+
+**Note**: Although the .csv extension might be associated with Microsoft Excel, you cannot view the file properly by double-clicking it. To correctly parse the comma delimiters and view the file in Excel, you must use the **Data** > **From Text/CSV** function in Excel to import the appropriate data columns. You don't need to view the file in Excel unless you are curious. The file format will be validated when it is imported into Autopilot. An example of the data in this file is shown below.
+
+
+
+You will need to upload this data into Intune to register your device for Autopilot, so it needs to be transferred to the computer you will use to access the Azure portal. If you are using a physical device instead of a VM, you can copy the file to a USB stick. If you’re using a VM, you can right-click the AutopilotHWID.csv file and copy it, then right-click and paste the file to your desktop (outside the VM).
+
+If you have trouble copying and pasting the file, just view the contents in Notepad on the VM and copy the text into Notepad outside the VM. Do not use another text editor to do this.
>[!NOTE]
->Accept all prompts while running the above cmdlets.
+>When copying and pasting to or from VMs, avoid clicking other things with your mouse cursor between the copy and paste process as this can empty or overwrite the clipboard and require that you start over. Go directly from copy to paste.
-### Mount the Virtual Hard Drive (VHD)
+## Reset the VM back to Out-Of-Box-Experience (OOBE)
-To gain access to the AutopilotHWID.csv that contains the hardware ID, stop the Virtual Machine to unlock the Virtual Hard Drive.
-
-To do that, on your device (**not** on the Virtual Machine), open a PowerShell prompt **as an administrator** and run the following:
-```powershell
-Stop-VM -VMName WindowsAutopilot
-```
-
-Once the Virtual Machine has stopped, create a checkpoint:
-```powershell
-Checkpoint-VM -Name WindowsAutopilot -SnapshotName "HWID captured"
-```
-
-With the checkpoint created, continue to mount the VHD:
-```powershell
-Mount-VHD -path (Get-VMHardDiskDrive -VMName WindowsAutopilot).Path
-```
-
-Once mounted, navigate to the new drive and copy **AutopilotHWID.csv** to a location on your device.
-
-Before you proceed, unmount the VHD to unlock it and start the Virtual Machine:
-```powershell
-Dismount-VHD -path (Get-VMHardDiskDrive -VMName WindowsAutopilot).Path
-Start-VM -VMName WindowsAutopilot
-```
-
-## Reset Virtual Machine back to Out-Of-Box-Experience (OOBE)
-
-With the hardware ID captured, prepare your Virtual Machine for Windows Autopilot deployment by resetting it back to OOBE.
+With the hardware ID captured in a file, prepare your Virtual Machine for Windows Autopilot deployment by resetting it back to OOBE.
On the Virtual Machine, go to **Settings > Update & Security > Recovery** and click on **Get started** under **Reset this PC**.
Select **Remove everything** and **Just remove my files**. Finally, click on **Reset**.
-Resetting your Virtual Machine can take a while. Proceed to the next steps while your Virtual Machine is resetting.
+Resetting the VM or device can take a while. Proceed to the next step (verify subscription level) during the reset process.
+## Verify subscription level
+
+For this lab, you need an AAD Premium subscription. You can tell if you have a Premium subscription by navigating to the [MDM enrollment configuration](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Mobility) blade. See the following example:
+
+**Azure Active Directory** > **Mobility (MDM and MAM)** > **Microsoft Intune**
+
+
+
+If the configuration blade shown above does not appear, it’s likely that you don’t have a **Premium** subscription. Auto-enrollment is a feature only available in AAD Premium.
+
+To convert your Intune trial account to a free Premium trial account, navigate to **Azure Active Directory** > **Licenses** > **All products** > **Try / Buy** and select **Free trial** for Azure AD Premium, or EMS E5.
+
+
+
## Configure company branding
->[!IMPORTANT]
->If you already have company branding configured in Azure Active Directory, you can skip this step.
-
-Navigate to [Company branding in Azure Active Directory](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/LoginTenantBranding).
+If you already have company branding configured in Azure Active Directory, you can skip this step.
>[!IMPORTANT]
>Make sure to sign-in with a Global Administrator account.
-Click on **Configure** and configure any type of company branding you'd like to see during the OOBE.
+Navigate to [Company branding in Azure Active Directory](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/LoginTenantBranding), click on **Configure** and configure any type of company branding you'd like to see during the OOBE.
-
+
-Once finished, click **Save**.
+When you are finished, click **Save**.
>[!NOTE]
>Changes to company branding can take up to 30 minutes to apply.
-
## Configure Microsoft Intune auto-enrollment
->[!IMPORTANT]
->If you already have MDM auto-enrollment configured in Azure Active Directory, you can skip this step.
+If you already have MDM auto-enrollment configured in Azure Active Directory, you can skip this step.
-Navigate to [Mobility (MDM and MAM) in Azure Active Directory](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Mobility) and select **Microsoft Intune**.
+Open [Mobility (MDM and MAM) in Azure Active Directory](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Mobility) and select **Microsoft Intune**. If you do not see Microsoft Intune, click **Add application** and choose **Intune**.
For the purposes of this demo, select **All** under the **MDM user scope** and click **Save**.
-
+
-## Register your Virtual Machine to your organization
+## Register your VM
-Navigate to [Microsoft Store for Business device management](https://businessstore.microsoft.com/en-us/manage/devices). Click on **Add devices** and select the **AutopilotHWID.csv** you've saved earlier. A message will appear indicating your request is being processed. Wait a few moments before refreshing to see your Virtual Machine added.
+Your VM (or device) can be registered either via Intune or Microsoft Store for Business (MSfB). Both processes are shown here, but only pick one for purposes of this lab. We highly recommend using Intune rather than MSfB.
-
+### Autopilot registration using Intune
+
+1. In Intune in the Azure portal, choose **Device enrollment** > **Windows enrollment** > **Devices** > **Import**.
+
+ 
+
+ >[!NOTE]
+ >If menu items like **Windows enrollment** are not active for you, then look to the far-right blade in the UI. You might need to provide Intune configuration privileges in a challenge window that appeared.
+
+2. Under **Add Windows Autopilot devices** in the far right pane, browse to the **AutopilotHWID.csv** file you previously copied to your local computer. The file should contain the serial number and 4K HH of your VM (or device). It’s okay if other fields (Windows Product ID) are left blank.
+
+ 
+
+ You should receive confirmation that the file is formatted correctly before uploading it, as shown above.
+
+3. Click **Import** and wait until the import process completes. This can take up to 15 minutes.
+
+4. Click **Sync** to sync the device you just registered. Wait a few moments before refreshing to verify your VM or device has been added. See the following example.
+
+ 
+
+### Autopilot registration using MSfB
+
+>[!IMPORTANT]
+>If you've already registered your VM (or device) using Intune, then skip this step.
+
+Optional: see the following video for an overview of the process.
+
+
+
+> [!video https://www.youtube.com/embed/IpLIZU_j7Z0]
+
+First, you need a MSfB account. You can use the same one you created above for Intune, or follow [these instructions](https://docs.microsoft.com/en-us/microsoft-store/windows-store-for-business-overview) to create a new one.
+
+Next, sign in to [Microsoft Store for Business](https://businessstore.microsoft.com/en-us/store) using your test account by clicking **Sign in** in the upper-right-corner of the main page.
+
+Select **Manage** from the top menu, then click the **Windows Autopilot Deployment Program** link under the **Devices** card. See the following example:
+
+
+
+Click the **Add devices** link to upload your CSV file. A message will appear indicating your request is being processed. Wait a few moments before refreshing to see your new device has been added.
+
+
## Create and assign a Windows Autopilot deployment profile
-Navigate to [Windows enrollment in Microsoft Intune](https://portal.azure.com/#blade/Microsoft_Intune_Enrollment/OverviewBlade/windowsEnrollment).
+>[!IMPORTANT]
+>Autopilot profiles can be created and assigned to your registered VM or device either through Intune or MSfB. Both processes are shown here, but only pick one for purposes of this lab:
-Make sure to sync the device you've just registered, by clicking on **Devices** under **Windows Autopilot Deployment Program (Preview)** and selecting **Sync**. Wait a few moments before refreshing to see your Virtual Machine added.
+Pick one:
+- [Create profiles using Intune](#create-a-windows-autopilot-deployment-profile-using-intune)
+- [Create profiles using MSfB](#create-a-windows-autopilot-deployment-profile-using-msfb)
-
+### Create a Windows Autopilot deployment profile using Intune
-### Create a Windows Autopilot deployment profile
+>[!NOTE]
+>Even if you registered your device in MSfB, it will still appear in Intune, though you might have to **sync** and then **refresh** your device list first:
-Click on **Deployment profiles** under **Windows Autopilot Deployment Program (Preview)** and select **Create profile**.
+
-
+>The example above lists both a physical device and a VM. Your list should only include only one of these.
-In the **Create profile** blade, set the name to **Autopilot Intune Demo**, click on **Out-of-box experience (OOBE)** and configure the following:
-| Setting name | Value |
+To create a Windows Autopilot profile, select **Device enrollment** > **Windows enrollment** > **Deployment profiles**
+
+
+
+Click on **Create profile**.
+
+
+
+On the **Create profile** blade, use the following values:
+
+| Setting | Value |
|---|---|
-|Privacy Settings|Hide|
-|End user license agreement (EULA)|Hide|
-|User account type|Standard|
+| Name | Autopilot Lab profile |
+| Description | blank |
+| Convert all targeted devices to Autopilot | No |
+| Deployment mode | User-driven |
+| Join to Azure AD as | Azure AD joined |
-Click on **Save** and **Create**.
+Click on **Out-of-box experience (OOBE)** and configure the following settings:
-
+| Setting | Value |
+|---|---|
+| EULA | Hide |
+| Privacy Settings | Hide |
+| Hide change account options | Hide |
+| User account type | Standard |
+| Apply device name template | No |
-### Assign a Windows Autopilot deployment profile
+See the following example:
-With the deployment profile created, go back to **Devices** under **Windows Autopilot Deployment Program (Preview)** and select your Virtual Machine. Click on **Assign profile** and in the **Assign Profile** blade select **Autopilot Intune Demo** under the **Autopilot profile**. Click on **Assign**.
+
-
+Click on **OK** and then click on **Create**.
-Wait a few minutes for all changes to apply.
+>If you want to add an app to your profile via Intune, the OPTIONAL steps for doing so can be found in [Appendix B: Adding apps to your profile](#appendix-b-adding-apps-to-your-profile).
+
+#### Assign the profile
+
+Profiles can only be assigned to Groups, so first you must create a group that contains the devices to which the profile should be applied. This guide will provide simple instructions to assign a profile, for more detailed instructions, see [Create an Autopilot device group](https://docs.microsoft.com/intune/enrollment-autopilot#create-an-autopilot-device-group) and [Assign an Autopilot deployment profile to a device group](https://docs.microsoft.com/en-us/intune/enrollment-autopilot#assign-an-autopilot-deployment-profile-to-a-device-group), as optional reading.
+
+To create a Group, open the Azure Portal and select **Azure Active Directory** > **Groups** > **All groups**:
+
+
+
+Select New group from the Groups blade to open the new groups UI. Select the “Security” group type, name the group, and select the “Assigned” membership type:
+
+Before clicking **Create**, expand the **Members** panel, click your device's serial number (it will then appear under **Selected members**) and then click **Select** to add that device to this group.
+
+
+
+Now click **Create** to finish creating the new group.
+
+Click on **All groups** and click **Refresh** to verify that your new group has been successfully created.
+
+With a group created containing your device, you can now go back and assign your profile to that group. Navigate back to the Intune page in the Azure portal (one way is to type **Intune** in the top banner search bar and select **Intune** from the results).
+
+From Intune, select **Device enrollment** > **Windows enrollment** > **Deployment Profiles** to open the profile blade. Click on the name of the profile you previously created (Autopilot Lab profile) to open the details blade for that profile:
+
+
+
+Under **Manage**, click **Assignments**, and then with the **Include** tab highlighted, expand the **Select groups** blade and click **AP Lab Group 1** (the group will appear under **Selected members**).
+
+
+
+Click **Select** and then click **Save**.
+
+
+
+It’s also possible to assign specific users to a profile, but we will not cover this scenario in the lab. For more detailed information, see [Enroll Windows devices in Intune by using Windows Autopilot](https://docs.microsoft.com/intune/enrollment-autopilot).
+
+### Create a Windows Autopilot deployment profile using MSfB
+
+If you have already created and assigned a profile via Intune by using the steps immediately above, then skip this section.
+
+A [video](https://www.youtube.com/watch?v=IpLIZU_j7Z0) is available that covers the steps required to create and assign profiles in MSfB. These steps are also summarized below.
+
+First, sign in to the [Microsoft Store for Business](https://businessstore.microsoft.com/manage/dashboard) using the Intune account you initially created for this lab.
+
+Click **Manage** from the top menu, then click **Devices** from the left navigation tree.
+
+
+
+Click the **Windows Autopilot Deployment Program** link in the **Devices** tile.
+
+To CREATE the profile:
+
+Select your device from the **Devices** list:
+
+
+
+On the Autopilot deployment dropdown menu, select **Create new profile**:
+
+
+
+Name the profile, choose your desired settings, and then click **Create**:
+
+
+
+The new profile is added to the Autopilot deployment list.
+
+To ASSIGN the profile:
+
+To assign (or reassign) the profile to a device, select the checkboxes next to the device you registered for this lab, then select the profile you want to assign from the **Autopilot deployment** dropdown menu as shown:
+
+
+
+Confirm the profile was successfully assigned to the intended device by checking the contents of the **Profile** column:
+
+
+
+>[!IMPORTANT]
+>The new profile will only be applied if the device has not been started, and gone through OOBE. Settings from a different profile can't be applied when another profile has been applied. Windows would need to be reinstalled on the device for the second profile to be applied to the device.
## See Windows Autopilot in action
-By now, your Virtual Machine should be back to OOBE. Make sure to wait at least 30 minutes from the time you've [configured company branding](#configure-company-branding)
-, otherwise those changes might not show up.
+If you shut down your VM after the last reset, it’s time to start it back up again, so it can progress through the Autopilot OOBE experience but do not attempt to start your device again until the **PROFILE STATUS** for your device in Intune has changed from **Not assigned** to **Assigning** and finally **Assigned**:
+
+
+
+Also, make sure to wait at least 30 minutes from the time you've [configured company branding](#configure-company-branding), otherwise these changes might not show up.
+
+>[!TIP]
+>If you reset your device previously after collecting the 4K HH info, and then let it restart back to the first OOBE screen, then you might need to restart the device again to ensure the device is recognized as an Autopilot device and displays the Autopilot OOBE experience you’re expecting. If you do not see the Autopilot OOBE experience, then reset the device again (Settings > Update & Security > Recovery and click on Get started. Under Reset this PC, select Remove everything and Just remove my files. Click on Reset).
+
+- Ensure your device has an internet connection.
+- Turn on the device
+- Verify that the appropriate OOBE screens (with appropriate Company Branding) appear. You should see the region selection screen, the keyboard selection screen, and the second keyboard selection screen (which you can skip).
+
+
+
+Soon after reaching the desktop, the device should show up in Intune as an **enabled** Autopilot device. Go into the Intune Azure portal, and select **Devices > All devices**, then **Refresh** the data to verify that your device has changed from disabled to enabled, and the name of the device is updated.
+
+
Once you select a language and a keyboard layout, your company branded sign-in screen should appear. Provide your Azure Active Directory credentials and you're all done.
-
+Windows Autopilot will now take over to automatically join your device into Azure Active Directory and enroll it to Microsoft Intune. Use the checkpoints you've created to go through this process again with different settings.
-Windows Autopilot will now take over to automatically join your Virtual Machine into Azure Active Directory and enroll it to Microsoft Intune. Use the checkpoints you've created to go through this process again with different settings.
+## Remove devices from Autopilot
+To use the device (or VM) for other purposes after completion of this lab, you will need to remove (deregister) it from Autopilot via either Intune or MSfB, and then reset it. Instructions for deregistering devices can be found [here](https://docs.microsoft.com/en-us/intune/enrollment-autopilot#create-an-autopilot-device-group) and [here](https://docs.microsoft.com/en-us/intune/devices-wipe#delete-devices-from-the-azure-active-directory-portal) and below.
+
+### Delete (deregister) Autopilot device
+
+You need to delete (or retire, or factory reset) the device from Intune before deregistering the device from Autopilot. To delete the device from Intune (not Azure Active Directory), log into your Intune Azure portal, then navigate to **Intune > Devices > All Devices**. Select the checkbox next to the device you want to delete, then click the Delete button along the top menu.
+
+
+
+Click **X** when challenged to complete the operation:
+
+
+
+This will remove the device from Intune management, and it will disappear from **Intune > Devices > All devices**. But this does not yet deregister the device from Autopilot, so the device should still appear under **Intune > Device Enrollment > Windows Enrollment > Windows Autopilot Deployment Program > Devices**.
+
+
+
+The **Intune > Devices > All Devices** list and the **Intune > Device Enrollment > Windows Enrollment > Windows Autopilot Deployment Program > Devices** list mean different things and are two completely separate datastores. The former (All devices) is the list of devices currently enrolled into Intune. Note: A device will only appear in the All devices list once it has booted. The latter (Windows Autopilot Deployment Program > Devices) is the list of devices currently registered from that Intune account into the Autopilot program - which may or may not be enrolled to Intune.
+
+To remove the device from the Autopilot program, select the device and click Delete.
+
+
+
+A warning message appears reminding you to first remove the device from Intune, which we previously did.
+
+
+
+At this point, your device has been unenrolled from Intune and also deregistered from Autopilot. After several minutes, click the **Sync** button, followed by the **Refresh** button to confirm the device is no longer listed in the Autopilot program:
+
+
+
+Once the device no longer appears, you are free to reuse it for other purposes.
+
+If you also (optionally) want to remove your device from AAD, navigate to **Azure Active Directory > Devices > All Devices**, select your device, and click the delete button:
+
+
+
+## Appendix A: Verify support for Hyper-V
+
+Starting with Windows 8, the host computer’s microprocessor must support second level address translation (SLAT) to install Hyper-V. See [Hyper-V: List of SLAT-Capable CPUs for Hosts](https://social.technet.microsoft.com/wiki/contents/articles/1401.hyper-v-list-of-slat-capable-cpus-for-hosts.aspx) for more information.
+
+To verify your computer supports SLAT, open an administrator command prompt, type **systeminfo**, press ENTER, scroll down, and review the section displayed at the bottom of the output, next to Hyper-V Requirements. See the following example:
+
+
+C:\>systeminfo
+
+...
+Hyper-V Requirements: VM Monitor Mode Extensions: Yes
+ Virtualization Enabled In Firmware: Yes
+ Second Level Address Translation: Yes
+ Data Execution Prevention Available: Yes
+
+
+In this example, the computer supports SLAT and Hyper-V.
+
+>If one or more requirements are evaluated as **No** then the computer does not support installing Hyper-V. However, if only the virtualization setting is incompatible, you might be able to enable virtualization in the BIOS and change the **Virtualization Enabled In Firmware** setting from **No** to **Yes**. The location of this setting will depend on the manufacturer and BIOS version, but is typically found associated with the BIOS security settings.
+
+You can also identify Hyper-V support using [tools](https://blogs.msdn.microsoft.com/taylorb/2008/06/19/hyper-v-will-my-computer-run-hyper-v-detecting-intel-vt-and-amd-v/) provided by the processor manufacturer, the [msinfo32](https://technet.microsoft.com/library/cc731397.aspx) tool, or you can download the [coreinfo](https://technet.microsoft.com/sysinternals/cc835722) utility and run it, as shown in the following example:
+
+
+C:\>coreinfo -v
+
+Coreinfo v3.31 - Dump information on system CPU and memory topology
+Copyright (C) 2008-2014 Mark Russinovich
+Sysinternals - www.sysinternals.com
+
+Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
+Intel64 Family 6 Model 42 Stepping 7, GenuineIntel
+Microcode signature: 0000001B
+HYPERVISOR - Hypervisor is present
+VMX * Supports Intel hardware-assisted virtualization
+EPT * Supports Intel extended page tables (SLAT)
+
+
+Note: A 64-bit operating system is required to run Hyper-V.
+
+## Appendix B: Adding apps to your profile
+
+### Add a Win32 app
+
+#### Prepare the app for Intune
+
+Before we can pull an application into Intune to make it part of our AP profile, we need to “package” the application for delivery using the [IntuneWinAppUtil.exe command-line tool](https://github.com/Microsoft/Intune-Win32-App-Packaging-Tool). After downloading the tool, gather the following three bits of information to use the tool:
+
+1. The source folder for your application
+2. The name of the setup executable file
+3. The output folder for the new file
+
+For the purposes of this lab, we’ll use the Notepad++ tool as our Win32 app.
+
+Download the Notepad++ msi package [here](https://www.hass.de/content/notepad-msi-package-enterprise-deployment-available) and then opy the file to a known location, such as C:\Notepad++msi.
+
+Run the IntuneWinAppUtil tool, supplying answers to the three questions, for example:
+
+
+
+After the tool finishes running, you should have an .intunewin file in the Output folder, which you can now upload into Intune using the following steps.
+
+#### Create app in Intune
+
+Log into the Azure portal and select **Intune**.
+
+Navigate to **Intune > Clients apps > Apps**, and then click the **Add** button to create a new app package.
+
+
+
+Under **App Type**, select **Windows app (Win32)**:
+
+
+
+On the **App package file** blade, browse to the **npp.7.6.3.installer.x64.intunewin** file in your output folder, open it, then click **OK**:
+
+
+
+On the **App Information Configure** blade, provide a friendly name, description, and publisher, such as:
+
+
+
+On the **Program Configuration** blade, supply the install and uninstall commands:
+
+Install: msiexec /i "npp.7.6.3.installer.x64.msi" /q
+Uninstall: msiexec /x "{F188A506-C3C6-4411-BE3A-DA5BF1EA6737}" /q
+
+NOTE: Likely, you do not have to write the install and uninstall commands yourself because the [IntuneWinAppUtil.exe command-line tool](https://github.com/Microsoft/Intune-Win32-App-Packaging-Tool) automatically generated them when it converted the .msi file into a .intunewin file.
+
+
+
+Simply using an install command like “notepad++.exe /S” will not actually install Notepad++; it will only launch the app. To actually install the program, we need to use the .msi file instead. Notepad++ doesn’t actually have an .msi version of their program, but we got an .msi version from a [third party provider](https://www.hass.de/content/notepad-msi-package-enterprise-deployment-available).
+
+Click **OK** to save your input and activate the **Requirements** blade.
+
+On the **Requirements Configuration** blade, specify the **OS architecture** and the **Minimum OS version**:
+
+
+
+Next, configure the **Detection rules**. For our purposes, we will select manual format:
+
+
+
+Click **Add** to define the rule properties. For **Rule type**, select **MSI**, which will automatically import the right MSI product code into the rule:
+
+
+
+Click **OK** twice to save, as you back out to the main **Add app** blade again for the final configuration.
+
+**Return codes**: For our purposes, leave the return codes at their default values:
+
+
+
+Click **OK** to exit.
+
+You may skip configuring the final **Scope (Tags)** blade.
+
+Click the **Add** button to finalize and save your app package.
+
+Once the indicator message says the addition has completed.
+
+
+
+You will be able to find your app in your app list:
+
+
+
+#### Assign the app to your Intune profile
+
+**NOTE**: The following steps only work if you previously [created a GROUP in Intune and assigned a profile to it](#assign-the-profile). If you have not done that, please return to the main part of the lab and complete those steps before returning here.
+
+In the **Intune > Client Apps > Apps** pane, select the app package you already created to reveal its properties blade. Then click **Assignments** from the menu:
+
+
+
+Select **Add Group** to open the **Add group** pane that is related to the app.
+
+For our purposes, select *8Required** from the **Assignment type** dropdown menu:
+
+>**Available for enrolled devices** means users install the app from the Company Portal app or Company Portal website.
+
+Select **Included Groups** and assign the groups you previously created that will use this app:
+
+
+
+
+
+In the **Select groups** pane, click the **Select** button.
+
+In the **Assign group** pane, select **OK**.
+
+In the **Add group** pane, select **OK**.
+
+In the app **Assignments** pane, select **Save**.
+
+
+
+At this point, you have completed steps to add a Win32 app to Intune.
+
+For more information on adding adds to Intune, see [Intune Standalone - Win32 app management](https://docs.microsoft.com/en-us/intune/apps-win32-app-management).
+
+### Add Office 365
+
+#### Create app in Intune
+
+Log into the Azure portal and select **Intune**.
+
+Navigate to **Intune > Clients apps > Apps**, and then click the **Add** button to create a new app package.
+
+
+
+Under **App Type**, select **Office 365 Suite > Windows 10**:
+
+
+
+Under the **Configure App Suite** pane, select the Office apps you want to install. For the purposes of this labe we have only selected Excel:
+
+
+
+Click **OK**.
+
+In the **App Suite Information** pane, enter a unique suite name, and a suitable description.
+
+>Enter the name of the app suite as it is displayed in the company portal. Make sure that all suite names that you use are unique. If the same app suite name exists twice, only one of the apps is displayed to users in the company portal.
+
+
+
+Click **OK**.
+
+In the **App Suite Settings** pane, select **Monthly** for the **Update channel** (any selection would be fine for the purposes of this lab). Also select **Yes** for **Automatically accept the app end user license agreement**:
+
+
+
+Click **OK** and then click **Add**.
+
+#### Assign the app to your Intune profile
+
+**NOTE**: The following steps only work if you previously [created a GROUP in Intune and assigned a profile to it](#assign-the-profile). If you have not done that, please return to the main part of the lab and complete those steps before returning here.
+
+In the **Intune > Client Apps > Apps** pane, select the Office package you already created to reveal its properties blade. Then click **Assignments** from the menu:
+
+
+
+Select **Add Group** to open the **Add group** pane that is related to the app.
+
+For our purposes, select **Required** from the **Assignment type** dropdown menu:
+
+>**Available for enrolled devices** means users install the app from the Company Portal app or Company Portal website.
+
+Select **Included Groups** and assign the groups you previously created that will use this app:
+
+
+
+
+
+In the **Select groups** pane, click the **Select** button.
+
+In the **Assign group** pane, select **OK**.
+
+In the **Add group** pane, select **OK**.
+
+In the app **Assignments** pane, select **Save**.
+
+
+
+At this point, you have completed steps to add Office to Intune.
+
+For more information on adding Office apps to Intune, see [Assign Office 365 apps to Windows 10 devices with Microsoft Intune](https://docs.microsoft.com/en-us/intune/apps-add-office365).
+
+If you installed both the win32 app (Notepad++) and Office (just Excel) per the instructions in this lab, your VM will show them in the apps list, although it could take several minutes to populate:
+
+
+
+## Glossary
+
+
+| OEM | Original Equipment Manufacturer |
+| CSV | Comma Separated Values |
+| MPC | Microsoft Partner Center |
+| CSP | Cloud Solution Provider |
+| MSfB | Microsoft Store for Business |
+| AAD | Azure Active Directory |
+| 4K HH | 4K Hardware Hash |
+| CBR | Computer Build Report |
+| EC | Enterprise Commerce (server) |
+| DDS | Device Directory Service |
+| OOBE | Out of the Box Experience |
+| VM | Virtual Machine |
+
diff --git a/windows/deployment/windows-autopilot/images/aad-lic1.png b/windows/deployment/windows-autopilot/images/aad-lic1.png
new file mode 100644
index 0000000000..569d601066
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/aad-lic1.png differ
diff --git a/windows/deployment/windows-autopilot/images/all-groups.png b/windows/deployment/windows-autopilot/images/all-groups.png
new file mode 100644
index 0000000000..6ae904ed62
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/all-groups.png differ
diff --git a/windows/deployment/windows-autopilot/images/app01.png b/windows/deployment/windows-autopilot/images/app01.png
new file mode 100644
index 0000000000..f551c5ca68
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app01.png differ
diff --git a/windows/deployment/windows-autopilot/images/app02.png b/windows/deployment/windows-autopilot/images/app02.png
new file mode 100644
index 0000000000..e5036043cc
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app02.png differ
diff --git a/windows/deployment/windows-autopilot/images/app03.png b/windows/deployment/windows-autopilot/images/app03.png
new file mode 100644
index 0000000000..63ef76b3f8
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app03.png differ
diff --git a/windows/deployment/windows-autopilot/images/app04.png b/windows/deployment/windows-autopilot/images/app04.png
new file mode 100644
index 0000000000..bd307c4a46
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app04.png differ
diff --git a/windows/deployment/windows-autopilot/images/app05.png b/windows/deployment/windows-autopilot/images/app05.png
new file mode 100644
index 0000000000..83861dcd51
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app05.png differ
diff --git a/windows/deployment/windows-autopilot/images/app06.png b/windows/deployment/windows-autopilot/images/app06.png
new file mode 100644
index 0000000000..9563e0514c
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app06.png differ
diff --git a/windows/deployment/windows-autopilot/images/app07.png b/windows/deployment/windows-autopilot/images/app07.png
new file mode 100644
index 0000000000..59025e69fa
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app07.png differ
diff --git a/windows/deployment/windows-autopilot/images/app08.png b/windows/deployment/windows-autopilot/images/app08.png
new file mode 100644
index 0000000000..cea5edfc57
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app08.png differ
diff --git a/windows/deployment/windows-autopilot/images/app09.png b/windows/deployment/windows-autopilot/images/app09.png
new file mode 100644
index 0000000000..250c85dd8a
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app09.png differ
diff --git a/windows/deployment/windows-autopilot/images/app10.png b/windows/deployment/windows-autopilot/images/app10.png
new file mode 100644
index 0000000000..8d5af2ece1
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app10.png differ
diff --git a/windows/deployment/windows-autopilot/images/app11.png b/windows/deployment/windows-autopilot/images/app11.png
new file mode 100644
index 0000000000..9ca5bc10eb
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app11.png differ
diff --git a/windows/deployment/windows-autopilot/images/app12.png b/windows/deployment/windows-autopilot/images/app12.png
new file mode 100644
index 0000000000..3f82bf78a9
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app12.png differ
diff --git a/windows/deployment/windows-autopilot/images/app13.png b/windows/deployment/windows-autopilot/images/app13.png
new file mode 100644
index 0000000000..2b499f4ec2
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app13.png differ
diff --git a/windows/deployment/windows-autopilot/images/app14.png b/windows/deployment/windows-autopilot/images/app14.png
new file mode 100644
index 0000000000..e809db6134
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app14.png differ
diff --git a/windows/deployment/windows-autopilot/images/app15.png b/windows/deployment/windows-autopilot/images/app15.png
new file mode 100644
index 0000000000..b85a96bf9e
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app15.png differ
diff --git a/windows/deployment/windows-autopilot/images/app16.png b/windows/deployment/windows-autopilot/images/app16.png
new file mode 100644
index 0000000000..f22f74a091
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app16.png differ
diff --git a/windows/deployment/windows-autopilot/images/app17.png b/windows/deployment/windows-autopilot/images/app17.png
new file mode 100644
index 0000000000..5adfc9218f
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app17.png differ
diff --git a/windows/deployment/windows-autopilot/images/app18.png b/windows/deployment/windows-autopilot/images/app18.png
new file mode 100644
index 0000000000..24c4b9f331
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app18.png differ
diff --git a/windows/deployment/windows-autopilot/images/app19.png b/windows/deployment/windows-autopilot/images/app19.png
new file mode 100644
index 0000000000..281ba9fb40
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app19.png differ
diff --git a/windows/deployment/windows-autopilot/images/app20.png b/windows/deployment/windows-autopilot/images/app20.png
new file mode 100644
index 0000000000..a5a066b45e
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app20.png differ
diff --git a/windows/deployment/windows-autopilot/images/app21.png b/windows/deployment/windows-autopilot/images/app21.png
new file mode 100644
index 0000000000..d2e23f2db4
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app21.png differ
diff --git a/windows/deployment/windows-autopilot/images/app22.png b/windows/deployment/windows-autopilot/images/app22.png
new file mode 100644
index 0000000000..4541a69204
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app22.png differ
diff --git a/windows/deployment/windows-autopilot/images/app23.png b/windows/deployment/windows-autopilot/images/app23.png
new file mode 100644
index 0000000000..19b951c653
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app23.png differ
diff --git a/windows/deployment/windows-autopilot/images/app24.png b/windows/deployment/windows-autopilot/images/app24.png
new file mode 100644
index 0000000000..aa77e4083f
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app24.png differ
diff --git a/windows/deployment/windows-autopilot/images/app25.png b/windows/deployment/windows-autopilot/images/app25.png
new file mode 100644
index 0000000000..544d1ae37a
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app25.png differ
diff --git a/windows/deployment/windows-autopilot/images/app26.png b/windows/deployment/windows-autopilot/images/app26.png
new file mode 100644
index 0000000000..e210faa31b
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/app26.png differ
diff --git a/windows/deployment/windows-autopilot/images/autopilot-aad-mdm.png b/windows/deployment/windows-autopilot/images/autopilot-aad-mdm.png
new file mode 100644
index 0000000000..1533f68c7c
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/autopilot-aad-mdm.png differ
diff --git a/windows/deployment/windows-autopilot/images/branding.png b/windows/deployment/windows-autopilot/images/branding.png
new file mode 100644
index 0000000000..46dd37bc4a
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/branding.png differ
diff --git a/windows/deployment/windows-autopilot/images/create-profile.png b/windows/deployment/windows-autopilot/images/create-profile.png
new file mode 100644
index 0000000000..52f087721d
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/create-profile.png differ
diff --git a/windows/deployment/windows-autopilot/images/delete-device1.png b/windows/deployment/windows-autopilot/images/delete-device1.png
new file mode 100644
index 0000000000..e73f929fbd
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/delete-device1.png differ
diff --git a/windows/deployment/windows-autopilot/images/delete-device2.png b/windows/deployment/windows-autopilot/images/delete-device2.png
new file mode 100644
index 0000000000..ed764ac1ed
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/delete-device2.png differ
diff --git a/windows/deployment/windows-autopilot/images/delete-device3.png b/windows/deployment/windows-autopilot/images/delete-device3.png
new file mode 100644
index 0000000000..a2daa1c39a
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/delete-device3.png differ
diff --git a/windows/deployment/windows-autopilot/images/delete-device4.png b/windows/deployment/windows-autopilot/images/delete-device4.png
new file mode 100644
index 0000000000..c0119fbc39
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/delete-device4.png differ
diff --git a/windows/deployment/windows-autopilot/images/delete-device5.png b/windows/deployment/windows-autopilot/images/delete-device5.png
new file mode 100644
index 0000000000..33b539d33c
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/delete-device5.png differ
diff --git a/windows/deployment/windows-autopilot/images/delete-device6.png b/windows/deployment/windows-autopilot/images/delete-device6.png
new file mode 100644
index 0000000000..23cbcb7c44
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/delete-device6.png differ
diff --git a/windows/deployment/windows-autopilot/images/delete-device7.png b/windows/deployment/windows-autopilot/images/delete-device7.png
new file mode 100644
index 0000000000..dcdeee5205
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/delete-device7.png differ
diff --git a/windows/deployment/windows-autopilot/images/deployment-profiles.png b/windows/deployment/windows-autopilot/images/deployment-profiles.png
new file mode 100644
index 0000000000..7888da55d1
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/deployment-profiles.png differ
diff --git a/windows/deployment/windows-autopilot/images/deployment-profiles2.png b/windows/deployment/windows-autopilot/images/deployment-profiles2.png
new file mode 100644
index 0000000000..6ff9fbb89e
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/deployment-profiles2.png differ
diff --git a/windows/deployment/windows-autopilot/images/device-import.png b/windows/deployment/windows-autopilot/images/device-import.png
new file mode 100644
index 0000000000..3be4cff996
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/device-import.png differ
diff --git a/windows/deployment/windows-autopilot/images/device-status.png b/windows/deployment/windows-autopilot/images/device-status.png
new file mode 100644
index 0000000000..5a78973ce5
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/device-status.png differ
diff --git a/windows/deployment/windows-autopilot/images/enabled-device.png b/windows/deployment/windows-autopilot/images/enabled-device.png
new file mode 100644
index 0000000000..96dc935309
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/enabled-device.png differ
diff --git a/windows/deployment/windows-autopilot/images/hwid-csv.png b/windows/deployment/windows-autopilot/images/hwid-csv.png
new file mode 100644
index 0000000000..ac177e0b5a
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/hwid-csv.png differ
diff --git a/windows/deployment/windows-autopilot/images/hwid.png b/windows/deployment/windows-autopilot/images/hwid.png
new file mode 100644
index 0000000000..fcc73fa0b0
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/hwid.png differ
diff --git a/windows/deployment/windows-autopilot/images/import-vm.png b/windows/deployment/windows-autopilot/images/import-vm.png
new file mode 100644
index 0000000000..5fb97cda5d
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/import-vm.png differ
diff --git a/windows/deployment/windows-autopilot/images/include-group.png b/windows/deployment/windows-autopilot/images/include-group.png
new file mode 100644
index 0000000000..fb7bca7efa
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/include-group.png differ
diff --git a/windows/deployment/windows-autopilot/images/include-group2.png b/windows/deployment/windows-autopilot/images/include-group2.png
new file mode 100644
index 0000000000..585d006bac
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/include-group2.png differ
diff --git a/windows/deployment/windows-autopilot/images/intune-devices.png b/windows/deployment/windows-autopilot/images/intune-devices.png
new file mode 100644
index 0000000000..bc29c76511
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/intune-devices.png differ
diff --git a/windows/deployment/windows-autopilot/images/mdm-intune.png b/windows/deployment/windows-autopilot/images/mdm-intune.png
new file mode 100644
index 0000000000..db9b144fad
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/mdm-intune.png differ
diff --git a/windows/deployment/windows-autopilot/images/mdm-intune2.png b/windows/deployment/windows-autopilot/images/mdm-intune2.png
new file mode 100644
index 0000000000..d464863f37
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/mdm-intune2.png differ
diff --git a/windows/deployment/windows-autopilot/images/msfb-assign1.png b/windows/deployment/windows-autopilot/images/msfb-assign1.png
new file mode 100644
index 0000000000..c1e8e27e21
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/msfb-assign1.png differ
diff --git a/windows/deployment/windows-autopilot/images/msfb-assign2.png b/windows/deployment/windows-autopilot/images/msfb-assign2.png
new file mode 100644
index 0000000000..fd3be16853
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/msfb-assign2.png differ
diff --git a/windows/deployment/windows-autopilot/images/msfb-create1.png b/windows/deployment/windows-autopilot/images/msfb-create1.png
new file mode 100644
index 0000000000..f76aa82991
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/msfb-create1.png differ
diff --git a/windows/deployment/windows-autopilot/images/msfb-create2.png b/windows/deployment/windows-autopilot/images/msfb-create2.png
new file mode 100644
index 0000000000..ec6c260fcd
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/msfb-create2.png differ
diff --git a/windows/deployment/windows-autopilot/images/msfb-create3.png b/windows/deployment/windows-autopilot/images/msfb-create3.png
new file mode 100644
index 0000000000..a6241fb5ea
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/msfb-create3.png differ
diff --git a/windows/deployment/windows-autopilot/images/msfb-device.png b/windows/deployment/windows-autopilot/images/msfb-device.png
new file mode 100644
index 0000000000..d338056013
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/msfb-device.png differ
diff --git a/windows/deployment/windows-autopilot/images/msfb-manage.png b/windows/deployment/windows-autopilot/images/msfb-manage.png
new file mode 100644
index 0000000000..9bf684d844
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/msfb-manage.png differ
diff --git a/windows/deployment/windows-autopilot/images/msfb-manage2.png b/windows/deployment/windows-autopilot/images/msfb-manage2.png
new file mode 100644
index 0000000000..406aaf5948
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/msfb-manage2.png differ
diff --git a/windows/deployment/windows-autopilot/images/msfb-manage3.png b/windows/deployment/windows-autopilot/images/msfb-manage3.png
new file mode 100644
index 0000000000..bf5fb1ccf9
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/msfb-manage3.png differ
diff --git a/windows/deployment/windows-autopilot/images/msfb.png b/windows/deployment/windows-autopilot/images/msfb.png
new file mode 100644
index 0000000000..af937c2c5f
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/msfb.png differ
diff --git a/windows/deployment/windows-autopilot/images/new-group.png b/windows/deployment/windows-autopilot/images/new-group.png
new file mode 100644
index 0000000000..c18c1865f6
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/new-group.png differ
diff --git a/windows/deployment/windows-autopilot/images/profile.png b/windows/deployment/windows-autopilot/images/profile.png
new file mode 100644
index 0000000000..40cf26bee2
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/profile.png differ
diff --git a/windows/deployment/windows-autopilot/images/winsetup1.png b/windows/deployment/windows-autopilot/images/winsetup1.png
new file mode 100644
index 0000000000..c8048256c4
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/winsetup1.png differ
diff --git a/windows/deployment/windows-autopilot/images/winsetup2.png b/windows/deployment/windows-autopilot/images/winsetup2.png
new file mode 100644
index 0000000000..43db844334
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/winsetup2.png differ
diff --git a/windows/deployment/windows-autopilot/images/winsetup3.png b/windows/deployment/windows-autopilot/images/winsetup3.png
new file mode 100644
index 0000000000..dbea3969de
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/winsetup3.png differ
diff --git a/windows/deployment/windows-autopilot/images/winsetup4.png b/windows/deployment/windows-autopilot/images/winsetup4.png
new file mode 100644
index 0000000000..1121b1dff5
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/winsetup4.png differ
diff --git a/windows/deployment/windows-autopilot/images/winsetup5.png b/windows/deployment/windows-autopilot/images/winsetup5.png
new file mode 100644
index 0000000000..2757253097
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/winsetup5.png differ
diff --git a/windows/deployment/windows-autopilot/images/winsetup6.png b/windows/deployment/windows-autopilot/images/winsetup6.png
new file mode 100644
index 0000000000..e91843e1ff
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/winsetup6.png differ
diff --git a/windows/deployment/windows-autopilot/images/winsetup7.png b/windows/deployment/windows-autopilot/images/winsetup7.png
new file mode 100644
index 0000000000..dadf85485e
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/winsetup7.png differ
diff --git a/windows/deployment/windows-autopilot/images/winsetup8.png b/windows/deployment/windows-autopilot/images/winsetup8.png
new file mode 100644
index 0000000000..9d7a499db0
Binary files /dev/null and b/windows/deployment/windows-autopilot/images/winsetup8.png differ
diff --git a/windows/hub/TOC.md b/windows/hub/TOC.md
index 1883594880..a811ff7119 100644
--- a/windows/hub/TOC.md
+++ b/windows/hub/TOC.md
@@ -1,6 +1,6 @@
# [Windows 10 and Windows 10 Mobile](index.md)
## [What's new](/windows/whats-new)
-## [Release information](release-information.md)
+## [Release information](/windows/release-information)
## [Deployment](/windows/deployment)
## [Configuration](/windows/configuration)
## [Client management](/windows/client-management)
diff --git a/windows/hub/release-information.md b/windows/hub/release-information.md
deleted file mode 100644
index 2aa38be1de..0000000000
--- a/windows/hub/release-information.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: Windows 10 - release information
-description: Learn release information for Windows 10 releases
-keywords: ["Windows 10", "Windows 10 October 2018 Update"]
-ms.prod: w10
-layout: LandingPage
-ms.topic: landing-page
-ms.mktglfcycl: deploy
-ms.sitesec: library
-author: lizap
-ms.author: elizapo
-ms.localizationpriority: high
----
-# Windows 10 release information
-
-Feature updates for Windows 10 are released twice a year, targeting March and September, via the Semi-Annual Channel (SAC) and will be serviced with monthly quality updates for 18 months from the date of the release. We recommend that you begin deployment of each SAC release immediately to devices selected for early adoption and ramp up to full deployment at your discretion. This will enable you to gain access to new features, experiences, and integrated security as soon as possible.
-
-Starting with Windows 10, version 1809, feature updates for Windows 10 Enterprise and Education editions with a targeted release month of September will be serviced for 30 months from their release date. For information about servicing timelines, see the [Windows lifecycle fact sheet](https://support.microsoft.com/help/13853).
-
->[!NOTE]
->If you are not using Windows Update for Business today, the "Semi-Annual Channel (Targeted)" servicing option has no impact on when your devices will be updated. It merely reflects a milestone for the semi-annual release, the period of time during which Microsoft recommends that your IT team make the release available to specific, "targeted" devices for the purpose of validating and generating data in order to get to a broad deployment decision. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-Update-for-Business-and-the-retirement-of-SAC-T/ba-p/339523).
-
-
-
-
-
diff --git a/windows/release-information/TOC.md b/windows/release-information/TOC.md
new file mode 100644
index 0000000000..e924832067
--- /dev/null
+++ b/windows/release-information/TOC.md
@@ -0,0 +1,19 @@
+# [Windows 10 release information](index.md)
+## [Message center](windows-message-center.yml)
+## [Version 1809 and Windows Server 2019](status-windows-10-1809-and-windows-server-2019.yml)
+### [Resolved issues](resolved-issues-windows-10-1809-and-windows-server-2019.yml)
+## [Version 1803](status-windows-10-1803.yml)
+### [Resolved issues](resolved-issues-windows-10-1803.yml)
+## [Version 1709](status-windows-10-1709.yml)
+### [Resolved issues](resolved-issues-windows-10-1709.yml)
+## [Version 1703](status-windows-10-1703.yml)
+### [Resolved issues](resolved-issues-windows-10-1703.yml)
+## [Version 1607 and Windows Server 2016](status-windows-10-1607-and-windows-server-2016.yml)
+### [Resolved issues](resolved-issues-windows-10-1607.yml)
+## [Version 1507](status-windows-10-1507.yml)
+### [Resolved issues](resolved-issues-windows-10-1507.yml)
+## Previous versions
+### [Windows 8.1 and Windows Server 2012 R2](status-windows-8.1-and-windows-server-2012-r2.yml)
+####[Resolved issues](resolved-issues-windows-8.1-and-windows-server-2012-r2.yml)
+### [Windows 7 and Windows Server 2008 R2](status-windows-7-and-windows-server-2008-r2-sp1.yml)
+####[Resolved issues](resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml)
\ No newline at end of file
diff --git a/windows/release-information/TOC.yml b/windows/release-information/TOC.yml
deleted file mode 100644
index b5ef71ac32..0000000000
--- a/windows/release-information/TOC.yml
+++ /dev/null
@@ -1,2 +0,0 @@
-- name: Index
- href: index.md
\ No newline at end of file
diff --git a/windows/release-information/index.md b/windows/release-information/index.md
index 45697f0cda..2aa38be1de 100644
--- a/windows/release-information/index.md
+++ b/windows/release-information/index.md
@@ -1,3 +1,30 @@
-# Welcome to release-information!
+---
+title: Windows 10 - release information
+description: Learn release information for Windows 10 releases
+keywords: ["Windows 10", "Windows 10 October 2018 Update"]
+ms.prod: w10
+layout: LandingPage
+ms.topic: landing-page
+ms.mktglfcycl: deploy
+ms.sitesec: library
+author: lizap
+ms.author: elizapo
+ms.localizationpriority: high
+---
+# Windows 10 release information
+
+Feature updates for Windows 10 are released twice a year, targeting March and September, via the Semi-Annual Channel (SAC) and will be serviced with monthly quality updates for 18 months from the date of the release. We recommend that you begin deployment of each SAC release immediately to devices selected for early adoption and ramp up to full deployment at your discretion. This will enable you to gain access to new features, experiences, and integrated security as soon as possible.
+
+Starting with Windows 10, version 1809, feature updates for Windows 10 Enterprise and Education editions with a targeted release month of September will be serviced for 30 months from their release date. For information about servicing timelines, see the [Windows lifecycle fact sheet](https://support.microsoft.com/help/13853).
+
+>[!NOTE]
+>If you are not using Windows Update for Business today, the "Semi-Annual Channel (Targeted)" servicing option has no impact on when your devices will be updated. It merely reflects a milestone for the semi-annual release, the period of time during which Microsoft recommends that your IT team make the release available to specific, "targeted" devices for the purpose of validating and generating data in order to get to a broad deployment decision. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-Update-for-Business-and-the-retirement-of-SAC-T/ba-p/339523).
+
+
+
+
-test
diff --git a/windows/release-information/resolved-issues-windows-10-1507.yml b/windows/release-information/resolved-issues-windows-10-1507.yml
new file mode 100644
index 0000000000..a630e7184b
--- /dev/null
+++ b/windows/release-information/resolved-issues-windows-10-1507.yml
@@ -0,0 +1,103 @@
+### YamlMime:YamlDocument
+
+documentType: LandingData
+title: Resolved issues in Windows 10, version 1507
+metadata:
+ document_id:
+ title: Resolved issues in Windows 10, version 1507
+ description: Resolved issues in Windows 10, version 1507
+ keywords: ["Resolved issues in Windows 10", "Windows 10", "Windows 10, version 1507"]
+ ms.localizationpriority: high
+ author: greg-lindsay
+ ms.author: greglin
+ manager: dougkim
+ ms.topic: article
+ ms.devlang: na
+
+sections:
+- items:
+ - type: markdown
+ text: "
+ See a list of known issues that have been resolved for Windows 10, version 1507 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page.
+
+ "
+- items:
+ - type: markdown
+ text: "
+
+ "
+
+- title: Resolved issues
+- items:
+ - type: markdown
+ text: "
+ | Summary | Affected build | Status | Date resolved |
+ MSXML6 may cause applications to stop responding
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
See details > | OS Build 10240.18094
January 08, 2019
KB4480962 | Resolved
KB4493475 | April 09, 2019 10:00 AM PT |
+ Custom URI schemes may not start corresponding application
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.
See details > | OS Build 10240.18158
March 12, 2019
KB4489872 | Resolved
KB4493475 | April 09, 2019 10:00 AM PT |
+ Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.
See details > | OS Build 10240.18132
February 12, 2019
KB4487018 | Resolved
KB4489872 | March 12, 2019 10:00 AM PT |
+ Error 1309 when installing/uninstalling MSI or MSP files
Users may receive \"Error 1309\" while installing or uninstalling certain types of MSI and MSP files.
See details > | OS Build 10240.18132
February 12, 2019
KB4487018 | Resolved
KB4489872 | March 12, 2019 10:00 AM PT |
+ First character of Japanese era name not recognized
The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.
See details > | OS Build 10240.18132
February 12, 2019
KB4487018 | Resolved
KB4489872 | March 12, 2019 10:00 AM PT |
+ Internet Explorer may fail to load images
Internet Explorer may fail to load images with a backslash (\\) in their relative source path.
See details > | OS Build 10240.18132
February 12, 2019
KB4487018 | Resolved
KB4491101 | February 21, 2019 02:00 PM PT |
+ Applications using Microsoft Jet database fail to open
Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if column names are greater than 32 characters.
See details > | OS Build 10240.18094
January 08, 2019
KB4480962 | Resolved
KB4487018 | February 12, 2019 10:00 AM PT |
+ Unable to access hotspots with third-party applications
Third-party applications may have difficulty authenticating hotspots.
See details > | OS Build 10240.18094
January 08, 2019
KB4480962 | Resolved
KB4487018 | February 12, 2019 10:00 AM PT |
+ Unable to use Seek bar in Windows Media Player
Users may not be able to use the Seek bar in Windows Media Player when playing specific files.
See details > | OS Build 10240.18005
October 09, 2018
KB4462922 | Resolved
KB4471323 | December 11, 2018 10:00 AM PT |
+ Guest VMs running Unicast NLB fail to respond after restart
All guest virtual machines running Unicast NLB fail to respond to NLB requests after the virtual machines restart.
See details > | OS Build 10240.17976
September 11, 2018
KB4457132 | Resolved
KB4462922 | October 09, 2018 10:00 AM PT |
+
+ "
+
+- title: Issue Details
+- items:
+ - type: markdown
+ text: "
+
+
+ "
+- title: March 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Custom URI schemes may not start corresponding applicationAfter installing KB4489872, Custom URI Schemes for Application Protocol handlers may not start the corresponding application for local intranet and trusted sites on Internet Explorer.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue was resolved in KB4493475.
Back to top | OS Build 10240.18158
March 12, 2019
KB4489872 | Resolved
KB4493475 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+
+ "
+
+- title: February 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ | Applications using Microsoft Jet database and Access 95 file format stop working Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4489872.
Back to top | OS Build 10240.18132
February 12, 2019
KB4487018 | Resolved
KB4489872 | Resolved:
March 12, 2019 10:00 AM PT
Opened:
February 12, 2019 10:00 AM PT |
+ Error 1309 when installing/uninstalling MSI or MSP filesAfter installing KB4487018, users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue is resolved in KB4489872.
Back to top | OS Build 10240.18132
February 12, 2019
KB4487018 | Resolved
KB4489872 | Resolved:
March 12, 2019 10:00 AM PT
Opened:
February 12, 2019 10:00 AM PT |
+ First character of Japanese era name not recognizedAfter installing KB4487018, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4489872.
Back to top | OS Build 10240.18132
February 12, 2019
KB4487018 | Resolved
KB4489872 | Resolved:
March 12, 2019 10:00 AM PT
Opened:
February 12, 2019 10:00 AM PT |
+ Internet Explorer may fail to load imagesAfter installing KB4487018, Internet Explorer may fail to load images with a backslash (\\) in their relative source path.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4491101.
Back to top | OS Build 10240.18132
February 12, 2019
KB4487018 | Resolved
KB4491101 | Resolved:
February 21, 2019 02:00 PM PT
Opened:
February 12, 2019 10:00 AM PT |
+
+ "
+
+- title: January 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ MSXML6 may cause applications to stop responding After installing KB4480962, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue was resolved in KB4493475.
Back to top | OS Build 10240.18094
January 08, 2019
KB4480962 | Resolved
KB4493475 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ | Applications using Microsoft Jet database fail to open Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if the database has column names greater than 32 characters. The database will fail to open with the error, \"Unrecognized Database Format\".
Affected platforms: - Client: Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487018.
Back to top | OS Build 10240.18094
January 08, 2019
KB4480962 | Resolved
KB4487018 | Resolved:
February 12, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ Unable to access hotspots with third-party applicationsAfter installing KB4480962, third-party applications may have difficulty authenticating hotspots.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue is resolved in KB4487018.
Back to top | OS Build 10240.18094
January 08, 2019
KB4480962 | Resolved
KB4487018 | Resolved:
February 12, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+
+ "
+
+- title: October 2018
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Unable to use Seek bar in Windows Media PlayerAfter installing KB4462922, users may not be able to use the Seek Bar in Windows Media Player when playing specific files. This issue does not affect normal playback.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4471323.
Back to top | OS Build 10240.18005
October 09, 2018
KB4462922 | Resolved
KB4471323 | Resolved:
December 11, 2018 10:00 AM PT
Opened:
October 09, 2018 10:00 AM PT |
+
+ "
+
+- title: September 2018
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ | Guest VMs running Unicast NLB fail to respond after restart All guest virtual machines running Unicast NLB fail to respond to NLB requests after the virtual machines restart.
Affected platforms: - Client: Windows 10, version 1803; Windows 10, version 1507
- Server: Windows Server, version 1803
Resolution: This issue is resolved in KB4462922.
Back to top | OS Build 10240.17976
September 11, 2018
KB4457132 | Resolved
KB4462922 | Resolved:
October 09, 2018 10:00 AM PT
Opened:
September 11, 2018 10:00 AM PT |
+
+ "
diff --git a/windows/release-information/resolved-issues-windows-10-1607.yml b/windows/release-information/resolved-issues-windows-10-1607.yml
new file mode 100644
index 0000000000..12c94040bc
--- /dev/null
+++ b/windows/release-information/resolved-issues-windows-10-1607.yml
@@ -0,0 +1,131 @@
+### YamlMime:YamlDocument
+
+documentType: LandingData
+title: Resolved issues in Windows 10, version 1607 and Windows Server 2016
+metadata:
+ document_id:
+ title: Resolved issues in Windows 10, version 1607 and Windows Server 2016
+ description: Resolved issues in Windows 10, version 1607
+ keywords: ["Resolved issues in Windows 10", "Windows 10", "Windows 10, version 1607"]
+ ms.localizationpriority: high
+ author: greg-lindsay
+ ms.author: greglin
+ manager: dougkim
+ ms.topic: article
+ ms.devlang: na
+
+sections:
+- items:
+ - type: markdown
+ text: "
+ See a list of known issues that have been resolved for Windows 10, version 1607 and Windows Server 2016 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page.
+
+ "
+- items:
+ - type: markdown
+ text: "
+
+ "
+
+- title: Resolved issues
+- items:
+ - type: markdown
+ text: "
+ | Summary | Affected build | Status | Date resolved |
+ End-user-defined characters (EUDC) cause blue screen at startup
If you enable per font end-user-defined characters (EUDC), the system will stop working and a blue screen may appear at startup.
See details > | OS Build 14393.2879
March 19, 2019
KB4489889 | Resolved
KB4493470 | April 09, 2019 10:00 AM PT |
+ Internet Explorer 11 authentication issue with multiple concurrent logons
Internet Explorer 11 users may encounter issues if two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine.
See details > | OS Build 14393.2724
January 08, 2019
KB4480961 | Resolved
KB4493470 | April 09, 2019 10:00 AM PT |
+ MSXML6 may cause applications to stop responding
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
See details > | OS Build 14393.2724
January 08, 2019
KB4480961 | Resolved
KB4493470 | April 09, 2019 10:00 AM PT |
+ Issue hosting multiple terminal server sessions and a user logs off on Windows Server
In some cases, Windows Server will stop working and restart when hosting multiple terminal server sessions and a user logs off.
See details > | OS Build 14393.2828
February 19, 2019
KB4487006 | Resolved
KB4489882 | March 12, 2019 10:00 AM PT |
+ Error 1309 when installing/uninstalling MSI or MSP files
Users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.
See details > | OS Build 14393.2791
February 12, 2019
KB4487026 | Resolved
KB4489882 | March 12, 2019 10:00 AM PT |
+ Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.
See details > | OS Build 14393.2791
February 12, 2019
KB4487026 | Resolved
KB4487006 | February 19, 2019 02:00 PM PT |
+ First character of the Japanese era name not recognized as an abbreviation
The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.
See details > | OS Build 14393.2759
January 17, 2019
KB4480977 | Resolved
KB4487006 | February 19, 2019 02:00 PM PT |
+ Internet Explorer may fail to load images
Internet Explorer may fail to load images with a backslash (\\) in their relative source path.
See details > | OS Build 14393.2791
February 12, 2019
KB4487026 | Resolved
KB4487006 | February 19, 2019 02:00 PM PT |
+ Applications using Microsoft Jet database fail to open
Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if column names are greater than 32 characters.
See details > | OS Build 14393.2724
January 08, 2019
KB4480961 | Resolved
KB4487026 | February 12, 2019 10:00 AM PT |
+ Instant search in Microsoft Outlook fails on Windows Server 2016
Instant search in Microsoft Outlook clients fail with the error, \"Outlook cannot perform the search\" on Windows Server 2016.
See details > | OS Build 14393.2639
November 27, 2018
KB4467684 | Resolved
KB4487026 | February 12, 2019 10:00 AM PT |
+ SqlConnection instantiation exception on .NET 4.6 and later
Instantiation of SqlConnection can throw an exception after certain updates have been installed.
See details > | OS Build 14393.2457
August 30, 2018
KB4343884 | Resolved
KB4480977 | January 17, 2019 02:00 PM PT |
+ Unable to access hotspots with third-party applications
Third-party applications may have difficulty authenticating hotspots.
See details > | OS Build 14393.2724
January 08, 2019
KB4480961 | Resolved
KB4480977 | January 17, 2019 02:00 PM PT |
+ System becomes unresponsive when end-user-defined characters (EUDC) are used
When features related to end-user-defined characters (EUDC) are used, the entire system may become unresponsive.
See details > | OS Build 14393.2639
November 27, 2018
KB4467684 | Resolved
KB4471321 | December 11, 2018 10:00 AM PT |
+ Unable to use Seek bar in Windows Media Player
Users may not be able to use the Seek bar in Windows Media Player when playing specific files.
See details > | OS Build 14393.2551
October 09, 2018
KB4462917 | Resolved
KB4471321 | December 11, 2018 10:00 AM PT |
+ Issues with install and activation of Key Management Service (KMS) (CSVLK) host keys
Installation and client activation of Windows Server 2019 and 1809 LTSC Key Management Service (KMS) (CSVLK) host keys do not work as expected.
See details > | OS Build 14393.2457
August 30, 2018
KB4343884 | Resolved
KB4467684 | November 27, 2018 10:00 AM PT |
+ Promotions that create non-root domains fail with optional features enabled
Windows Server 2016 promotions that create non-root domains fail in forests in which optional features like Active Directory recycle have been enabled.
See details > | OS Build 14393.2515
September 20, 2018
KB4457127 | Resolved
KB4467684 | November 27, 2018 10:00 AM PT |
+
+ "
+
+- title: Issue Details
+- items:
+ - type: markdown
+ text: "
+
+
+ "
+- title: March 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ | End-user-defined characters (EUDC) cause blue screen at startup If you enable per font end-user-defined characters (EUDC), the system will stop working and a blue screen may appear at startup. This is not a common setting in non-Asian regions.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016
Resolution: This issue was resolved in KB4493470.
Back to top | OS Build 14393.2879
March 19, 2019
KB4489889 | Resolved
KB4493470 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 19, 2019 10:00 AM PT |
+
+ "
+
+- title: February 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ | Issue hosting multiple terminal server sessions and a user logs off on Windows Server In some cases, Windows Server will stop working and restart when hosting multiple terminal server sessions and a user logs off. The faulting driver is win32kbase.sys.
Affected platforms: - Client: Windows 10 Enterprise LTSC 2016
- Server: Windows Server 2016
Resolution: This issue is resolved in KB4489882.
Back to top | OS Build 14393.2828
February 19, 2019
KB4487006 | Resolved
KB4489882 | Resolved:
March 12, 2019 10:00 AM PT
Opened:
February 19, 2019 02:00 PM PT |
+ Error 1309 when installing/uninstalling MSI or MSP filesAfter installing KB4487026, users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue is resolved in KB4489882.
Back to top | OS Build 14393.2791
February 12, 2019
KB4487026 | Resolved
KB4489882 | Resolved:
March 12, 2019 10:00 AM PT
Opened:
February 12, 2019 10:00 AM PT |
+ | Applications using Microsoft Jet database and Access 95 file format stop working Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487006.
Back to top | OS Build 14393.2791
February 12, 2019
KB4487026 | Resolved
KB4487006 | Resolved:
February 19, 2019 02:00 PM PT
Opened:
February 12, 2019 10:00 AM PT |
+ Internet Explorer may fail to load imagesAfter installing KB4487026, Internet Explorer may fail to load images with a backslash (\\) in their relative source path.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487006.
Back to top | OS Build 14393.2791
February 12, 2019
KB4487026 | Resolved
KB4487006 | Resolved:
February 19, 2019 02:00 PM PT
Opened:
February 12, 2019 10:00 AM PT |
+
+ "
+
+- title: January 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Internet Explorer 11 authentication issue with multiple concurrent logonsAfter installing KB4480961, Internet Explorer 11 and other applications that use WININET.DLL may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to:
- Cache size and location show zero or empty.
- Keyboard shortcuts may not work properly.
- Webpages may intermittently fail to load or render correctly.
- Issues with credential prompts.
- Issues when downloading files.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue was resolved in KB4493470.
Back to top | OS Build 14393.2724
January 08, 2019
KB4480961 | Resolved
KB4493470 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ MSXML6 may cause applications to stop responding After installing KB4480961, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue was resolved in KB4493470.
Back to top | OS Build 14393.2724
January 08, 2019
KB4480961 | Resolved
KB4493470 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ First character of the Japanese era name not recognized as an abbreviationAfter installing KB4480977, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487006.
Back to top | OS Build 14393.2759
January 17, 2019
KB4480977 | Resolved
KB4487006 | Resolved:
February 19, 2019 02:00 PM PT
Opened:
January 17, 2019 02:00 PM PT |
+ | Applications using Microsoft Jet database fail to open Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if the database has column names greater than 32 characters. The database will fail to open with the error, “Unrecognized Database Format”.
Affected platforms: - Client: Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487026.
Back to top | OS Build 14393.2724
January 08, 2019
KB4480961 | Resolved
KB4487026 | Resolved:
February 12, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ Unable to access hotspots with third-party applicationsAfter installing KB4480961, third-party applications may have difficulty authenticating hotspots.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue is resolved in KB4480977.
Back to top | OS Build 14393.2724
January 08, 2019
KB4480961 | Resolved
KB4480977 | Resolved:
January 17, 2019 02:00 PM PT
Opened:
January 08, 2019 10:00 AM PT |
+
+ "
+
+- title: November 2018
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Instant search in Microsoft Outlook fails on Windows Server 2016After installing KB4467684 on Windows Server 2016, instant search in Microsoft Outlook clients fail with the error, \"Outlook cannot perform the search\".
Affected platforms: - Client: Windows 10 Enterprise LTSC 2016
- Server: Windows Server 2016
Resolution: This issue is resolved in KB4487026.
Back to top | OS Build 14393.2639
November 27, 2018
KB4467684 | Resolved
KB4487026 | Resolved:
February 12, 2019 10:00 AM PT
Opened:
November 27, 2018 10:00 AM PT |
+ | System becomes unresponsive when end-user-defined characters (EUDC) are used When features related to end-user-defined characters (EUDC) are used, the entire system may become unresponsive.
Affected platforms: - Client: Windows 10 Enterprise LTSC 2016
- Server: Windows Server 2016
Resolution: This issue is resolved in KB4471321.
Back to top | OS Build 14393.2639
November 27, 2018
KB4467684 | Resolved
KB4471321 | Resolved:
December 11, 2018 10:00 AM PT
Opened:
November 27, 2018 10:00 AM PT |
+
+ "
+
+- title: October 2018
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Unable to use Seek bar in Windows Media PlayerAfter installing KB4462917, users may not be able to use the Seek Bar in Windows Media Player when playing specific files. This issue does not affect normal playback.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4471321.
Back to top | OS Build 14393.2551
October 09, 2018
KB4462917 | Resolved
KB4471321 | Resolved:
December 11, 2018 10:00 AM PT
Opened:
October 09, 2018 10:00 AM PT |
+
+ "
+
+- title: September 2018
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Promotions that create non-root domains fail with optional features enabledAfter installing KB4457127, Windows Server 2016 promotions that create non-root domains fail in forests in which optional features like Active Directory recycle have been enabled. The error is, “The replication operation encountered a database error.”
Affected platforms: - Client: Windows 10 Enterprise LTSC 2016
- Server: Windows Server 2016
Resolution: This issue is resolved in KB4467684.
Back to top | OS Build 14393.2515
September 20, 2018
KB4457127 | Resolved
KB4467684 | Resolved:
November 27, 2018 10:00 AM PT
Opened:
September 20, 2018 10:00 AM PT |
+
+ "
+
+- title: August 2018
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ | SqlConnection instantiation exception on .NET 4.6 and later
For more information about this issue, see the following article in the Microsoft Knowledge Base: 4470809, SqlConnection instantiation exception on .NET 4.6 and later after August-September 2018 .NET Framework updates.
Affected platforms: - Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016
- Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016
Resolution: This issue is resolved in KB4480977.
Back to top | OS Build 14393.2457
August 30, 2018
KB4343884 | Resolved
KB4480977 | Resolved:
January 17, 2019 02:00 PM PT
Opened:
August 30, 2018 05:00 PM PT |
+ Issues with install and activation of Key Management Service (KMS) (CSVLK) host keysAfter installing KB4343884, installation and client activation of Windows Server 2019 and Windows 10 Enterprise 2019 LTSC Key Management Service (KMS) CSVLK host keys do not work as expected.
Affected platforms: - Client: Windows 10 Enterprise LTSC 2016
- Server: Windows Server 2016
Resolution: This issue is resolved in KB4467684.
Back to top | OS Build 14393.2457
August 30, 2018
KB4343884 | Resolved
KB4467684 | Resolved:
November 27, 2018 10:00 AM PT
Opened:
August 30, 2018 05:00 PM PT |
+
+ "
diff --git a/windows/release-information/resolved-issues-windows-10-1703.yml b/windows/release-information/resolved-issues-windows-10-1703.yml
new file mode 100644
index 0000000000..d8009fe5de
--- /dev/null
+++ b/windows/release-information/resolved-issues-windows-10-1703.yml
@@ -0,0 +1,109 @@
+### YamlMime:YamlDocument
+
+documentType: LandingData
+title: Resolved issues in Windows 10, version 1703
+metadata:
+ document_id:
+ title: Resolved issues in Windows 10, version 1703
+ description: Resolved issues in Windows 10, version 1703
+ keywords: ["Resolved issues in Windows 10", "Windows 10", "Windows 10, version 1703"]
+ ms.localizationpriority: high
+ author: greg-lindsay
+ ms.author: greglin
+ manager: dougkim
+ ms.topic: article
+ ms.devlang: na
+
+sections:
+- items:
+ - type: markdown
+ text: "
+ See a list of known issues that have been resolved for Windows 10, version 1703 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page.
+
+ "
+- items:
+ - type: markdown
+ text: "
+
+ "
+
+- title: Resolved issues
+- items:
+ - type: markdown
+ text: "
+ | Summary | Affected build | Status | Date resolved |
+ End-user-defined characters (EUDC) may cause blue screen at startup
If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup.
See details > | OS Build 15063.1716
March 19, 2019
KB4489888 | Resolved
KB4493474 | April 09, 2019 10:00 AM PT |
+ MSXML6 may cause applications to stop responding
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
See details > | OS Build 15063.1563
January 08, 2019
KB4480973 | Resolved
KB4493474 | April 09, 2019 10:00 AM PT |
+ Error 1309 when installing/uninstalling MSI or MSP files
Users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.
See details > | OS Build 15063.1659
February 19, 2019
KB4487011 | Resolved
KB4489871 | March 12, 2019 10:00 AM PT |
+ First character of the Japanese era name not recognized as an abbreviation
The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.
See details > | OS Build 15063.1596
January 15, 2019
KB4480959 | Resolved
KB4487011 | February 19, 2019 02:00 PM PT |
+ Internet Explorer may fail to load images
Internet Explorer may fail to load images with a backslash (\\) in their relative source path.
See details > | OS Build 15063.1631
February 12, 2019
KB4487020 | Resolved
KB4487011 | February 19, 2019 02:00 PM PT |
+ Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.
See details > | OS Build 15063.1631
February 12, 2019
KB4487020 | Resolved
KB4487011 | February 19, 2019 10:00 AM PT |
+ Applications using Microsoft Jet database fail to open
Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if column names are greater than 32 characters.
See details > | OS Build 15063.1563
January 08, 2019
KB4480973 | Resolved
KB4487020 | February 12, 2019 10:00 AM PT |
+ Webpages become unresponsive in Microsoft Edge
Microsoft Edge users report difficulty browsing and loading webpages.
See details > | OS Build 15063.1563
January 08, 2019
KB4480973 | Resolved
KB4487020 | February 12, 2019 10:00 AM PT |
+ SqlConnection instantiation exception on .NET 4.6 and later
Instantiation of SqlConnection can throw an exception after certain updates have been installed.
See details > | OS Build 15063.1292
August 30, 2018
KB4343889 | Resolved
KB4480959 | January 15, 2019 10:00 AM PT |
+ Unable to access hotspots with third-party applications
Third-party applications may have difficulty authenticating hotspots.
See details > | OS Build 15063.1563
January 08, 2019
KB4480973 | Resolved
KB4480959 | January 15, 2019 10:00 AM PT |
+ Unable to use Seek bar in Windows Media Player
Users may not be able to use the Seek bar in Windows Media Player when playing specific files.
See details > | OS Build 15063.1387
October 09, 2018
KB4462937 | Resolved
KB4471327 | December 11, 2018 10:00 AM PT |
+ LongonUI.exe stops working intermittently
LongonUI.exe stops working intermittently.
See details > | OS Build 15063.1387
October 09, 2018
KB4462937 | Resolved
KB4467699 | November 27, 2018 10:00 AM PT |
+ Error message beginning with “Hosted by…” when launching Microsoft Edge
Some users may encounter an error message beginning with “Hosted by…” when launching Microsoft Edge.
See details > | OS Build 15063.1387
October 09, 2018
KB4462937 | Resolved
KB4462939 | October 18, 2018 10:00 AM PT |
+
+ "
+
+- title: Issue Details
+- items:
+ - type: markdown
+ text: "
+
+
+ "
+- title: March 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ | End-user-defined characters (EUDC) may cause blue screen at startup If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup. This is not a common setting in non-Asian regions.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016
Resolution: This issue was resolved in KB4493474.
Back to top | OS Build 15063.1716
March 19, 2019
KB4489888 | Resolved
KB4493474 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 19, 2019 10:00 AM PT |
+
+ "
+
+- title: February 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Error 1309 when installing/uninstalling MSI or MSP filesAfter installing KB4487011, users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue is resolved in KB4489871.
Back to top | OS Build 15063.1659
February 19, 2019
KB4487011 | Resolved
KB4489871 | Resolved:
March 12, 2019 10:00 AM PT
Opened:
February 19, 2019 02:00 PM PT |
+ Internet Explorer may fail to load imagesAfter installing KB4487020, Internet Explorer may fail to load images with a backslash (\\) in their relative source path.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487011.
Back to top | OS Build 15063.1631
February 12, 2019
KB4487020 | Resolved
KB4487011 | Resolved:
February 19, 2019 02:00 PM PT
Opened:
February 12, 2019 10:00 AM PT |
+ | Applications using Microsoft Jet database and Access 95 file format stop working Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487011.
Back to top | OS Build 15063.1631
February 12, 2019
KB4487020 | Resolved
KB4487011 | Resolved:
February 19, 2019 02:00 PM PT
Opened:
February 12, 2019 10:00 AM PT |
+
+ "
+
+- title: January 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ MSXML6 may cause applications to stop responding After installing KB4480973, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue was resolved in KB4493474.
Back to top | OS Build 15063.1563
January 08, 2019
KB4480973 | Resolved
KB4493474 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ First character of the Japanese era name not recognized as an abbreviationAfter installing KB4480959, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487011.
Back to top | OS Build 15063.1596
January 15, 2019
KB4480959 | Resolved
KB4487011 | Resolved:
February 19, 2019 02:00 PM PT
Opened:
January 15, 2019 10:00 AM PT |
+ | Applications using Microsoft Jet database fail to open Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if the database has column names greater than 32 characters. The database will fail to open with the error, “Unrecognized Database Format”.
Affected platforms: - Client: Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487020.
Back to top | OS Build 15063.1563
January 08, 2019
KB4480973 | Resolved
KB4487020 | Resolved:
February 12, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ Webpages become unresponsive in Microsoft EdgeAfter installing KB4480973, some Microsoft Edge users report that they:
• Cannot load webpages using a local IP address. • Cannot load webpages on the Internet using a VPN connection.
Browsing fails or the webpage may become unresponsive.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709
Resolution: This issue is resolved in KB4487020.
Back to top | OS Build 15063.1563
January 08, 2019
KB4480973 | Resolved
KB4487020 | Resolved:
February 12, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ Unable to access hotspots with third-party applicationsAfter installing KB4480973, third-party applications may have difficulty authenticating hotspots.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue is resolved in KB4480959.
Back to top | OS Build 15063.1563
January 08, 2019
KB4480973 | Resolved
KB4480959 | Resolved:
January 15, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+
+ "
+
+- title: October 2018
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Unable to use Seek bar in Windows Media PlayerAfter installing KB4462937, users may not be able to use the Seek Bar in Windows Media Player when playing specific files. This issue does not affect normal playback.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4471327.
Back to top | OS Build 15063.1387
October 09, 2018
KB4462937 | Resolved
KB4471327 | Resolved:
December 11, 2018 10:00 AM PT
Opened:
October 09, 2018 10:00 AM PT |
+ LongonUI.exe stops working intermittentlyAfter installing KB4462937, LogonUI.exe stops working intermittently.
Affected platforms:
Resolution: This issue is resolved in KB4467699.
Back to top | OS Build 15063.1387
October 09, 2018
KB4462937 | Resolved
KB4467699 | Resolved:
November 27, 2018 10:00 AM PT
Opened:
October 09, 2018 10:00 AM PT |
+ Error message beginning with “Hosted by…” when launching Microsoft EdgeAfter installing KB4462937, some users may see a dialog box with a non-applicable message beginning with the words “Hosted by...” when first starting Microsoft Edge.
This dialog will only appear once if they have turned on “Block only third-party cookies” in Microsoft Edge and applied certain language packs before installing this update.
Affected platforms: - Client: Windows 10, version 1709; Windows 10, version 1703
- Server: Windows Server, version 1709
Resolution: This issue is resolved in KB4462939.
Back to top | OS Build 15063.1387
October 09, 2018
KB4462937 | Resolved
KB4462939 | Resolved:
October 18, 2018 10:00 AM PT
Opened:
October 09, 2018 10:00 AM PT |
+
+ "
+
+- title: August 2018
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ | SqlConnection instantiation exception on .NET 4.6 and later
For more information about this issue, see the following article in the Microsoft Knowledge Base: 4470809 SqlConnection instantiation exception on .NET 4.6 and later after August-September 2018 .NET Framework updates.
Affected platforms: - Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016
- Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016
Resolution: This issue is resolved in KB4480959.
Back to top | OS Build 15063.1292
August 30, 2018
KB4343889 | Resolved
KB4480959 | Resolved:
January 15, 2019 10:00 AM PT
Opened:
August 30, 2018 05:00 PM PT |
+
+ "
diff --git a/windows/release-information/resolved-issues-windows-10-1709.yml b/windows/release-information/resolved-issues-windows-10-1709.yml
new file mode 100644
index 0000000000..3c1728302f
--- /dev/null
+++ b/windows/release-information/resolved-issues-windows-10-1709.yml
@@ -0,0 +1,109 @@
+### YamlMime:YamlDocument
+
+documentType: LandingData
+title: Resolved issues in Windows 10, version 1709 and Windows Server, vesion 1709
+metadata:
+ document_id:
+ title: Resolved issues in Windows 10, version 1709 and Windows Server, vesion 1709
+ description: Resolved issues in Windows 10, version 1709 and Windows Server 1709
+ keywords: ["Resolved issues in Windows 10", "Windows 10", "Windows 10, version 1709"]
+ ms.localizationpriority: high
+ author: greg-lindsay
+ ms.author: greglin
+ manager: dougkim
+ ms.topic: article
+ ms.devlang: na
+
+sections:
+- items:
+ - type: markdown
+ text: "
+ See a list of known issues that have been resolved for Windows 10, version 1709 and Windows Server, version 1709 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page.
+
+ "
+- items:
+ - type: markdown
+ text: "
+
+ "
+
+- title: Resolved issues
+- items:
+ - type: markdown
+ text: "
+ | Summary | Affected build | Status | Date resolved |
+ End-user-defined characters (EUDC) may cause blue screen at startup
If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup.
See details > | OS Build 16299.1059
March 19, 2019
KB4489890 | Resolved
KB4493441 | April 09, 2019 10:00 AM PT |
+ MSXML6 causes applications to stop responding if an exception was thrown
MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
See details > | OS Build 16299.904
January 08, 2019
KB4480978 | Resolved
KB4493441 | April 09, 2019 10:00 AM PT |
+ Stop error when attempting to start SSH from WSL
A stop error occurs when attempting to start the Secure Shell client program from Windows Subsystem for Linux with agent forwarding enabled using a command line switch (ssh –A) or
See details > | OS Build 16299.1029
March 12, 2019
KB4489886 | Resolved
KB4493441 | April 09, 2019 10:00 AM PT |
+ Error 1309 when installing/uninstalling MSI or MSP files
Users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.
See details > | OS Build 16299.967
February 12, 2019
KB4486996 | Resolved
KB4489886 | March 12, 2019 10:00 AM PT |
+ Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.
See details > | OS Build 16299.967
February 12, 2019
KB4486996 | Resolved
KB4487021 | February 19, 2019 02:00 PM PT |
+ First character of the Japanese era name not recognized as an abbreviation
The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.
See details > | OS Build 16299.936
January 15, 2019
KB4480967 | Resolved
KB4487021 | February 19, 2019 02:00 PM PT |
+ Internet Explorer may fail to load images
Internet Explorer may fail to load images with a backslash (\\) in their relative source path.
See details > | OS Build 16299.967
February 12, 2019
KB4486996 | Resolved
KB4487021 | February 19, 2019 02:00 PM PT |
+ Applications using Microsoft Jet database fail to open
Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if column names are greater than 32 characters.
See details > | OS Build 16299.904
January 08, 2019
KB4480978 | Resolved
KB4486996 | February 12, 2019 10:00 AM PT |
+ Webpages become unresponsive in Microsoft Edge
Microsoft Edge users report difficulty browsing and loading webpages.
See details > | OS Build 16299.904
January 08, 2019
KB4480978 | Resolved
KB4486996 | February 12, 2019 10:00 AM PT |
+ SqlConnection instantiation exception on .NET 4.6 and later
Instantiation of SqlConnection can throw an exception after certain updates have been installed.
See details > | OS Build 16299.637
August 30, 2018
KB4343893 | Resolved
KB4480967 | January 15, 2019 10:00 AM PT |
+ Unable to access hotspots with third-party applications
Third-party applications may have difficulty authenticating hotspots.
See details > | OS Build 16299.904
January 08, 2019
KB4480978 | Resolved
KB4480967 | January 15, 2019 10:00 AM PT |
+ Unable to use Seek bar in Windows Media Player
Users may not be able to use the Seek bar in Windows Media Player when playing specific files.
See details > | OS Build 16299.726
October 09, 2018
KB4462918 | Resolved
KB4471329 | December 11, 2018 10:00 AM PT |
+ Error message beginning with “Hosted by…” when launching Microsoft Edge
Some users may encounter an error message beginning with “Hosted by…” when launching Microsoft Edge.
See details > | OS Build 16299.726
October 09, 2018
KB4462918 | Resolved
KB4462932 | October 18, 2018 10:00 AM PT |
+
+ "
+
+- title: Issue Details
+- items:
+ - type: markdown
+ text: "
+
+
+ "
+- title: March 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ | End-user-defined characters (EUDC) may cause blue screen at startup If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup. This is not a common setting in non-Asian regions.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016
Resolution: This issue is resolved in KB4493441.
Back to top | OS Build 16299.1059
March 19, 2019
KB4489890 | Resolved
KB4493441 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 19, 2019 10:00 AM PT |
+ Stop error when attempting to start SSH from WSLAfter applying KB4489886, a stop error occurs when attempting to start the Secure Shell (SSH) client program from Windows Subsystem for Linux (WSL) with agent forwarding enabled using a command line switch (ssh –A) or a configuration setting.
Affected platforms: - Client: Windows 10, version 1803; Windows 10, version 1709
- Server: Windows Server, version 1803; Windows Server, version 1709
Resolution: This issue is resolved in KB4493441.
Back to top | OS Build 16299.1029
March 12, 2019
KB4489886 | Resolved
KB4493441 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+
+ "
+
+- title: February 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Error 1309 when installing/uninstalling MSI or MSP filesAfter installing KB4486996, users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue is resolved in KB4489886.
Back to top | OS Build 16299.967
February 12, 2019
KB4486996 | Resolved
KB4489886 | Resolved:
March 12, 2019 10:00 AM PT
Opened:
February 12, 2019 10:00 AM PT |
+ | Applications using Microsoft Jet database and Access 95 file format stop working Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487021.
Back to top | OS Build 16299.967
February 12, 2019
KB4486996 | Resolved
KB4487021 | Resolved:
February 19, 2019 02:00 PM PT
Opened:
February 12, 2019 10:00 AM PT |
+ Internet Explorer may fail to load imagesAfter installing KB4486996, Internet Explorer may fail to load images with a backslash (\\) in their relative source path.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487021.
Back to top | OS Build 16299.967
February 12, 2019
KB4486996 | Resolved
KB4487021 | Resolved:
February 19, 2019 02:00 PM PT
Opened:
February 12, 2019 10:00 AM PT |
+
+ "
+
+- title: January 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ MSXML6 causes applications to stop responding if an exception was thrownAfter installing KB4480978, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue is resolved in KB4493441.
Back to top | OS Build 16299.904
January 08, 2019
KB4480978 | Resolved
KB4493441 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ First character of the Japanese era name not recognized as an abbreviationAfter installing KB4480967, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487021.
Back to top | OS Build 16299.936
January 15, 2019
KB4480967 | Resolved
KB4487021 | Resolved:
February 19, 2019 02:00 PM PT
Opened:
January 15, 2019 10:00 AM PT |
+ | Applications using Microsoft Jet database fail to open Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if the database has column names greater than 32 characters. The database will fail to open with the error, “Unrecognized Database Format.”
Affected platforms: - Client: Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4486996.
Back to top | OS Build 16299.904
January 08, 2019
KB4480978 | Resolved
KB4486996 | Resolved:
February 12, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ Webpages become unresponsive in Microsoft EdgeAfter installing KB4480978, some Microsoft Edge users report that they:
• Cannot load webpages using a local IP address. • Cannot load webpages on the Internet using a VPN connection.
Browsing fails or the webpage may become unresponsive.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709
Resolution: This issue is resolved in KB4486996.
Back to top | OS Build 16299.904
January 08, 2019
KB4480978 | Resolved
KB4486996 | Resolved:
February 12, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ Unable to access hotspots with third-party applicationsAfter installing KB4480978, third-party applications may have difficulty authenticating hotspots.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue is resolved in KB4480967.
Back to top | OS Build 16299.904
January 08, 2019
KB4480978 | Resolved
KB4480967 | Resolved:
January 15, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+
+ "
+
+- title: October 2018
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Unable to use Seek bar in Windows Media PlayerAfter installing KB4462918, users may not be able to use the Seek Bar in Windows Media Player when playing specific files. This issue does not affect normal playback.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4471329.
Back to top | OS Build 16299.726
October 09, 2018
KB4462918 | Resolved
KB4471329 | Resolved:
December 11, 2018 10:00 AM PT
Opened:
October 09, 2018 10:00 AM PT |
+ Error message beginning with “Hosted by…” when launching Microsoft EdgeAfter installing KB4462918, some users may see a dialog box with a non-applicable message beginning with the words “Hosted by...” when first starting Microsoft Edge.
This dialog will only appear once if they have turned on “Block only third-party cookies” in Microsoft Edge and applied certain language packs before installing this update.
Affected platforms: - Client: Windows 10, version 1709; Windows 10, version 1703
- Server: Windows Server, version 1709
Resolution: This issue is resolved in KB4462932.
Back to top | OS Build 16299.726
October 09, 2018
KB4462918 | Resolved
KB4462932 | Resolved:
October 18, 2018 10:00 AM PT
Opened:
October 09, 2018 10:00 AM PT |
+
+ "
+
+- title: August 2018
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ | SqlConnection instantiation exception on .NET 4.6 and later
For more information about this issue, see the following article in the Microsoft Knowledge Base: 4470809 SqlConnection instantiation exception on .NET 4.6 and later after August-September 2018 .NET Framework updates.
Affected platforms: - Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016
- Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016
Resolution: This issue is resolved in KB4480967.
Back to top | OS Build 16299.637
August 30, 2018
KB4343893 | Resolved
KB4480967 | Resolved:
January 15, 2019 10:00 AM PT
Opened:
August 30, 2018 05:00 PM PT |
+
+ "
diff --git a/windows/release-information/resolved-issues-windows-10-1803.yml b/windows/release-information/resolved-issues-windows-10-1803.yml
new file mode 100644
index 0000000000..7dca69d3a4
--- /dev/null
+++ b/windows/release-information/resolved-issues-windows-10-1803.yml
@@ -0,0 +1,143 @@
+### YamlMime:YamlDocument
+
+documentType: LandingData
+title: Resolved issues in Windows 10, version 1803
+metadata:
+ document_id:
+ title: Resolved issues in Windows 10, version 1803
+ description: Resolved issues in Windows 10, version 1803
+ keywords: ["Resolved issues in Windows 10", "Windows 10", "Windows 10, version 1803"]
+ ms.localizationpriority: high
+ author: greg-lindsay
+ ms.author: greglin
+ manager: dougkim
+ ms.topic: article
+ ms.devlang: na
+
+sections:
+- items:
+ - type: markdown
+ text: "
+ See a list of known issues that have been resolved for Windows 10, version 1803 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page.
+
+ "
+- items:
+ - type: markdown
+ text: "
+
+ "
+
+- title: Resolved issues
+- items:
+ - type: markdown
+ text: "
+ | Summary | Affected build | Status | Date resolved |
+ End-user-defined characters (EUDC) may cause blue screen at startup
If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup.
See details > | OS Build 17134.677
March 19, 2019
KB4489894 | Resolved
KB4493464 | April 09, 2019 10:00 AM PT |
+ MSXML6 may cause applications to stop responding
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
See details > | OS Build 17134.523
January 08, 2019
KB4480966 | Resolved
KB4493464 | April 09, 2019 10:00 AM PT |
+ Stop error when attempting to start SSH from WSL
A stop error occurs when attempting to start Secure Shell from Windows Subsystem for Linux with agent forwarding using a command line switch (ssh –A) or a configuration setting.
See details > | OS Build 17134.648
March 12, 2019
KB4489868 | Resolved
KB4493464 | April 09, 2019 10:00 AM PT |
+ Error 1309 when installing/uninstalling MSI or MSP files
Users may receive \"Error 1309\" while installing or uninstalling certain types of MSI and MSP files.
See details > | OS Build 17134.590
February 12, 2019
KB4487017 | Resolved
KB4489868 | March 12, 2019 10:00 AM PT |
+ Cannot pin a web link on the Start menu or the taskbar
Some users cannot pin a web link on the Start menu or the taskbar.
See details > | OS Build 17134.471
December 11, 2018
KB4471324 | Resolved
KB4487029 | February 19, 2019 02:00 PM PT |
+ First character of Japanese era name not recognized
The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.
See details > | OS Build 17134.556
January 15, 2019
KB4480976 | Resolved
KB4487029 | February 19, 2019 02:00 PM PT |
+ Internet Explorer may fail to load images
Internet Explorer may fail to load images with a backslash (\\) in their relative source path.
See details > | OS Build 17134.590
February 12, 2019
KB4487017 | Resolved
KB4487029 | February 19, 2019 02:00 PM PT |
+ Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.
See details > | OS Build 17134.523
January 08, 2019
KB4480966 | Resolved
KB4487017 | February 12, 2019 10:00 AM PT |
+ Webpages become unresponsive in Microsoft Edge
Microsoft Edge users report difficulty browsing and loading webpages.
See details > | OS Build 17134.523
January 08, 2019
KB4480966 | Resolved
KB4487017 | February 12, 2019 10:00 AM PT |
+ SqlConnection instantiation exception on .NET 4.6 and later
After you install the August Preview of Quality Rollup or the September 11, 2018 .NET Framework update, instantiation of SqlConnection can throw an exception.
See details > | OS Build 17134.285
September 11, 2018
KB4457128 | Resolved
KB4480976 | January 15, 2019 10:00 AM PT |
+ Unable to access hotspots with third-party applications
Third-party applications may have difficulty authenticating hotspots.
See details > | OS Build 17134.523
January 08, 2019
KB4480966 | Resolved
KB4480976 | January 15, 2019 10:00 AM PT |
+ Blue or black screen with \"System thread exception not handled\" error
Some users may get a blue or black screen with the error code, “System thread exception not handled.”
See details > | OS Build 17134.441
November 27, 2018
KB4467682 | Resolved
KB4471324 | December 11, 2018 10:00 AM PT |
+ Custom Start menu layouts display incorrectly
Custom Start menu layouts may display incorrectly.
See details > | OS Build 17134.441
November 27, 2018
KB4467682 | Resolved
KB4471324 | December 11, 2018 10:00 AM PT |
+ Unable to use Seek bar in Windows Media Player
Users may not be able to use the Seek Bar in Windows Media Player when playing specific files.
See details > | OS Build 17134.345
October 09, 2018
KB4462919 | Resolved
KB4471324 | December 11, 2018 10:00 AM PT |
+ Users cannot set Win32 program defaults
Some users cannot set Win32 program defaults for certain app and file type combinations.
See details > | OS Build 17134.320
September 26, 2018
KB4458469 | Resolved
KB4467682 | November 27, 2018 10:00 AM PT |
+ Developer Tools (F12) fail to start in Microsoft Edge
Developer Tools (F12) may fail to start in Microsoft Edge.
See details > | OS Build 17134.376
October 24, 2018
KB4462933 | Resolved
KB4467702 | November 13, 2018 10:00 AM PT |
+ Guest VMs running Unicast NLB fail to respond after restart
All guest virtual machines running Unicast NLB fail to respond to NLB requests after the virtual machines restart.
See details > | OS Build 17134.285
September 11, 2018
KB4457128 | Resolved
KB4458469 | September 20, 2018 10:00 AM PT |
+ Microsoft Intune takes a long time to deliver user profiles
Windows no longer recognizes the Personal Information exchange (PFX) certificate used for Wi-Fi or VPN authentication, causing delays in Microsoft Intune delivering user profiles.
See details > | OS Build 17134.191
July 24, 2018
KB4340917 | Resolved
KB4464218 | September 17, 2018 10:00 AM PT |
+
+ "
+
+- title: Issue Details
+- items:
+ - type: markdown
+ text: "
+
+
+ "
+- title: March 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ | End-user-defined characters (EUDC) may cause blue screen at startup If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup. This is not a common setting in non-Asian regions.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016
Resolution: This issue was resolved in KB4493464.
Back to top | OS Build 17134.677
March 19, 2019
KB4489894 | Resolved
KB4493464 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 19, 2019 10:00 AM PT |
+ Stop error when attempting to start SSH from WSLAfter applying KB4489868, a stop error occurs when attempting to start the Secure Shell (SSH) client program from Windows Subsystem for Linux (WSL) with agent forwarding enabled using a command line switch (ssh -A) or a configuration setting.
Affected platforms: - Client: Windows 10, version 1803; Windows 10, version 1709
- Server: Windows Server, version 1803; Windows Server, version 1709
Resolution: This issue was resolved in KB4493464.
Back to top | OS Build 17134.648
March 12, 2019
KB4489868 | Resolved
KB4493464 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+
+ "
+
+- title: February 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Error 1309 when installing/uninstalling MSI or MSP filesAfter installing KB4487017, users may received \"Error 1309\" while installing or uninstalling certain types of MSI and MSP files.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue is resolved in KB4489868.
Back to top | OS Build 17134.590
February 12, 2019
KB4487017 | Resolved
KB4489868 | Resolved:
March 12, 2019 10:00 AM PT
Opened:
February 12, 2019 10:00 AM PT |
+ Internet Explorer may fail to load imagesAfter installing KB4487017, Internet Explorer may fail to load images with a backslash (\\) in their relative source path.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487029.
Back to top | OS Build 17134.590
February 12, 2019
KB4487017 | Resolved
KB4487029 | Resolved:
February 19, 2019 02:00 PM PT
Opened:
February 12, 2019 10:00 AM PT |
+
+ "
+
+- title: January 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ MSXML6 may cause applications to stop responding After installing KB4480966, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue was resolved in KB4493464.
Back to top | OS Build 17134.523
January 08, 2019
KB4480966 | Resolved
KB4493464 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ First character of Japanese era name not recognizedAfter installing KB4480976, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487029.
Back to top | OS Build 17134.556
January 15, 2019
KB4480976 | Resolved
KB4487029 | Resolved:
February 19, 2019 02:00 PM PT
Opened:
January 15, 2019 10:00 AM PT |
+ | Applications using Microsoft Jet database and Access 95 file format stop working Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487017.
Back to top | OS Build 17134.523
January 08, 2019
KB4480966 | Resolved
KB4487017 | Resolved:
February 12, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ Webpages become unresponsive in Microsoft EdgeAfter installing KB4480966, some Microsoft Edge users report that they:
- Cannot load webpages using a local IP address.
- Cannot load webpages on the Internet using a VPN connection.
Browsing fails or the webpage may become unresponsive.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709
Resolution: This issue is resolved in KB4487017.
Back to top | OS Build 17134.523
January 08, 2019
KB4480966 | Resolved
KB4487017 | Resolved:
February 12, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ Unable to access hotspots with third-party applicationsAfter installing KB4480966, third-party applications may have difficulty authenticating hotspots.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue is resolved in KB4480976.
Back to top | OS Build 17134.523
January 08, 2019
KB4480966 | Resolved
KB4480976 | Resolved:
January 15, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+
+ "
+
+- title: December 2018
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Cannot pin a web link on the Start menu or the taskbarAfter installing KB4471324, some users cannot pin a web link on the Start menu or the taskbar.
Affected platforms: - Client: Windows 10, version 1803
- Server: Windows Server, version 1803
Resolution: This issue is resolved in KB4487029.
Back to top | OS Build 17134.471
December 11, 2018
KB4471324 | Resolved
KB4487029 | Resolved:
February 19, 2019 02:00 PM PT
Opened:
December 11, 2018 10:00 AM PT |
+
+ "
+
+- title: November 2018
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Blue or black screen with \"System thread exception not handled\" errorAfter installing KB4467682, an optional update, some users may get a blue or black screen with the error code, \"System thread exception not handled.\"
Affected platforms: - Client: Windows 10, version 1803
- Server: Windows Server, version 1803
Resolution: This issue is resolved in KB4471324.
Back to top | OS Build 17134.441
November 27, 2018
KB4467682 | Resolved
KB4471324 | Resolved:
December 11, 2018 10:00 AM PT
Opened:
November 27, 2018 10:00 AM PT |
+ Custom Start menu layouts display incorrectlyAfter installing KB4467682, custom Start menu layouts may display incorrectly.
Affected platforms: - Client: Windows 10, version 1803
- Server: Windows Server, version 1803
Resolution: This issue is resolved in KB4471324.
Back to top | OS Build 17134.441
November 27, 2018
KB4467682 | Resolved
KB4471324 | Resolved:
December 11, 2018 10:00 AM PT
Opened:
November 27, 2018 10:00 AM PT |
+
+ "
+
+- title: October 2018
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Unable to use Seek bar in Windows Media PlayerAfter installing KB4462919, users may not be able to use the Seek bar in Windows Media Player when playing specific files. This issue does not affect normal playback.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4471324.
Back to top | OS Build 17134.345
October 09, 2018
KB4462919 | Resolved
KB4471324 | Resolved:
December 11, 2018 10:00 AM PT
Opened:
October 09, 2018 10:00 AM PT |
+ | Developer Tools (F12) fail to start in Microsoft Edge Developer Tools (F12) may fail to start in Microsoft Edge.
Affected platforms: - Client: Windows 10, version 1803
- Server: Windows Server, version 1803
Resolution: This issue is resolved in KB4467702.
Back to top | OS Build 17134.376
October 24, 2018
KB4462933 | Resolved
KB4467702 | Resolved:
November 13, 2018 10:00 AM PT
Opened:
October 24, 2018 02:00 PM PT |
+
+ "
+
+- title: September 2018
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ | SqlConnection instantiation exception on .NET 4.6 and later
For more information about this issue, see the following article in the Microsoft Knowledge Base: 4470809, SqlConnection instantiation exception on .NET 4.6 and later after August-September 2018 .NET Framework updates.
Affected platforms: - Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016
- Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016
Resolution: This issue is resolved in KB4480976.
Back to top | OS Build 17134.285
September 11, 2018
KB4457128 | Resolved
KB4480976 | Resolved:
January 15, 2019 10:00 AM PT
Opened:
September 11, 2018 10:00 AM PT |
+ Users cannot set Win32 program defaultsAfter installing KB4458469, some users cannot set Win32 program defaults for certain app and file type combinations using the Open with... command or Settings > Apps > Default apps. In some cases, Microsoft Notepad or other Win32 programs cannot be set as the default.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803
Resolution: This issue is resolved in KB4467682.
Back to top | OS Build 17134.320
September 26, 2018
KB4458469 | Resolved
KB4467682 | Resolved:
November 27, 2018 10:00 AM PT
Opened:
September 26, 2018 02:00 PM PT |
+ | Guest VMs running Unicast NLB fail to respond after restart All guest virtual machines running Unicast NLB fail to respond to NLB requests after the virtual machines restart.
Affected platforms: - Client: Windows 10, version 1803; Windows 10, version 1507
- Server: Windows Server, version 1803
Resolution: This issue is resolved in KB4458469.
Back to top | OS Build 17134.285
September 11, 2018
KB4457128 | Resolved
KB4458469 | Resolved:
September 20, 2018 10:00 AM PT
Opened:
September 11, 2018 10:00 AM PT |
+
+ "
+
+- title: July 2018
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Microsoft Intune takes a long time to deliver user profilesAfter installing KB4457128, Windows no longer recognizes the Personal Information exchange (PFX) certificate that's used for authenticating to a Wi-Fi or VPN connection. As a result, Microsoft Intune takes a long time to deliver user profiles because it doesn't recognize that the required certificate is on the device.
Affected platforms: - Client: Windows 10, version 1803
- Server: Windows Server, version 1803
Resolution: This issue is resolved in KB4464218.
Back to top | OS Build 17134.191
July 24, 2018
KB4340917 | Resolved
KB4464218 | Resolved:
September 17, 2018 10:00 AM PT
Opened:
July 24, 2018 10:00 AM PT |
+
+ "
diff --git a/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml b/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml
new file mode 100644
index 0000000000..777084433a
--- /dev/null
+++ b/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml
@@ -0,0 +1,143 @@
+### YamlMime:YamlDocument
+
+documentType: LandingData
+title: Resolved issues in Windows 10, version 1809 and Windows Server 2019
+metadata:
+ document_id:
+ title: Resolved issues in Windows 10, version 1809 and Windows Server 2019
+ description: Resolved issues in Windows 10, version 1809 or Windows Server 2019
+ keywords: ["Resolved issues in Windows 10", "Windows 10", "Windows 10 1809"]
+ ms.localizationpriority: high
+ author: greg-lindsay
+ ms.author: greglin
+ manager: dougkim
+ ms.topic: article
+ ms.devlang: na
+
+sections:
+- items:
+ - type: markdown
+ text: "
+ See a list of known issues that have been resolved for Windows 10, version 1809 and Windows Server 2019 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page.
+
+ "
+- items:
+ - type: markdown
+ text: "
+
+ "
+
+- title: Resolved issues
+- items:
+ - type: markdown
+ text: "
+ | Summary | Affected build | Status | Date resolved |
+ End-user-defined characters (EUDC) may cause blue screen at startup
If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup.
See details > | OS Build 17763.404
April 02, 2019
KB4490481 | Resolved
KB4493509 | April 09, 2019 10:00 AM PT |
+ Internet Explorer 11 authentication issue with multiple concurrent logons
Internet Explorer 11 users may encounter issues if two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine.
See details > | OS Build 17763.253
January 08, 2019
KB4480116 | Resolved
KB4493509 | April 09, 2019 10:00 AM PT |
+ MSXML6 may cause applications to stop responding
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
See details > | OS Build 17763.253
January 08, 2019
KB4480116 | Resolved
KB4493509 | April 09, 2019 10:00 AM PT |
+ Apps may stop working after selecting an audio output device other than the default
Users with multiple audio devices that select an audio output device different from the \"Default Audio Device\" may find certain applications stop working unexpectedly.
See details > | OS Build 17763.348
March 01, 2019
KB4482887 | Resolved
KB4490481 | April 02, 2019 10:00 AM PT |
+ Error 1309 when installing/uninstalling MSI or MSP files
Users may receive \"Error 1309\" while installing or uninstalling certain types of MSI and MSP files.
See details > | OS Build 17763.316
February 12, 2019
KB4487044 | Resolved
KB4489899 | March 12, 2019 10:00 AM PT |
+ Global DNS outage affects Windows Update customers
Windows Update customers were recently affected by a network infrastructure event caused by an external DNS service provider's global outage.
See details > |
| Resolved
| March 08, 2019 11:15 AM PT |
+ Internet Explorer may fail to load images
Internet Explorer may fail to load images with a backslash (\\) in their relative source path.
See details > | OS Build 17763.316
February 12, 2019
KB4487044 | Resolved
KB4482887 | March 01, 2019 10:00 AM PT |
+ Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 9 file format may randomly stop working.
See details > | OS Build 17763.316
February 12, 2019
KB4487044 | Resolved
KB4482887 | March 01, 2019 10:00 AM PT |
+ First character of the Japanese era name not recognized
The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.
See details > | OS Build 17763.316
February 12, 2019
KB4487044 | Resolved
KB4482887 | March 01, 2019 10:00 AM PT |
+ Shared albums may not sync with iCloud for Windows
Upgrade block: Apple has identified an incompatibility with iCloud for Windows (version 7.7.0.27) where users may experience issues updating or synching Shared Albums.
See details > | OS Build 17763.134
November 13, 2018
KB4467708 | Resolved
KB4482887 | March 01, 2019 10:00 AM PT |
+ Intel Audio Display (intcdaud.sys) notification during Windows 10 Setup
Upgrade block: Users may see an Intel Audio Display (intcdaud.sys) notification during setup for devices with certain Intel Display Audio Drivers.
See details > | OS Build 17763.134
November 13, 2018
KB4467708 | Resolved
KB4482887 | March 01, 2019 10:00 AM PT |
+ F5 VPN clients losing network connectivity
Upgrade block: After updating to Window 10, version 1809, F5 VPN clients may lose network connectivity when the VPN service is in a split tunnel configuration.
See details > | OS Build 17763.134
November 13, 2018
KB4467708 | Resolved
KB4482887 | March 01, 2019 10:00 AM PT |
+ Webpages become unresponsive in Microsoft Edge
Microsoft Edge users report difficulty browsing and loading webpages.
See details > | OS Build 17763.253
January 08, 2019
KB4480116 | Resolved
KB4487044 | February 12, 2019 10:00 AM PT |
+ Issues with lock screen and Microsoft Edge tabs for certain AMD Radeon video cards
Upgrade block: Devices utilizing AMD Radeon HD2000 or HD4000 series video cards may experience issues with the lock screen and Microsoft Edge tabs.
See details > | OS Build 17763.134
November 13, 2018
KB4467708 | Resolved
KB4487044 | February 12, 2019 10:00 AM PT |
+ Trend Micro OfficeScan and Worry-Free Business Security AV software not compatible
Upgrade block: Microsoft and Trend Micro identified a compatibility issue with the Trend Micro business endpoint security solutions OfficeScan and Worry-Free Business Security.
See details > | OS Build 17763.134
November 13, 2018
KB4467708 | Resolved
| February 01, 2019 09:00 AM PT |
+ Unable to access hotspots with third-party applications
Third-party applications may have difficulty authenticating hotspots.
See details > | OS Build 17763.253
January 08, 2019
KB4480116 | Resolved
KB4476976 | January 22, 2019 02:00 PM PT |
+ Unable to use Seek bar in Windows Media Player
Users may not be able to use the Seek bar in Windows Media Player when playing specific files.
See details > | OS Build 17763.55
October 09, 2018
KB4464330 | Resolved
KB4471332 | December 11, 2018 10:00 AM PT |
+ Audio stops working after installing Intel audio driver
Upgrade block: Windows 10 audio stops working after installing Intel Smart Sound Technology driver (version 09.21.00.3755).
See details > | OS Build 17763.134
November 13, 2018
KB4467708 | Resolved
KB4468550 | December 07, 2018 10:00 AM PT |
+ Office apps (32-bit) unable to use 'Save As…' function
Upgrade block: Devices using Morphisec Protector (or other application that uses the Morphisec SDK) may be unable to save documents when using 32-bit Microsoft Office apps.
See details > | OS Build 17763.134
November 13, 2018
KB4467708 | Resolved
| December 06, 2018 12:00 PM PT |
+ Users cannot set Win32 program defaults
Some users cannot set Win32 program defaults for certain app and file type combinations.
See details > | OS Build 17763.55
October 09, 2018
KB4464330 | Resolved
KB4469342 | December 05, 2018 02:00 PM PT |
+ Mapped drives fail to reconnect after login
Upgrade block: Mapped drives may fail to reconnect after booting and logging on to a Windows device.
See details > | OS Build 17763.134
November 13, 2018
KB4467708 | Resolved
KB4469342 | December 05, 2018 02:00 PM PT |
+ Microsoft Edge may crash or hang while playing video
Following an nVidia driver update, Microsoft Edge may crash or hang while playing video.
See details > | OS Build 17763.165
December 05, 2018
KB4469342 | Resolved
| November 29, 2018 10:03 AM PT |
+
+ "
+
+- title: Issue Details
+- items:
+ - type: markdown
+ text: "
+
+
+ "
+- title: April 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ | End-user-defined characters (EUDC) may cause blue screen at startup If you enable per font end-user-defined characters (EUDC), the system will stop working and a blue screen may appear at startup. This is not a common setting in non-Asian regions.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016
Workaround: To avoid this issue, don't enable per font EUDC. As an alternative, you can edit the registry to mitigate this issue; for more information, see KB4496149.
Resolved: This issue was resolved in KB4493509.
Back to top | OS Build 17763.404
April 02, 2019
KB4490481 | Resolved
KB4493509 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
April 02, 2019 10:00 AM PT |
+
+ "
+
+- title: March 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Apps may stop working after selecting an audio output device other than the defaultAfter installing KB4482887 on machines that have multiple audio devices, applications that provide advanced options for internal or external audio output devices may stop working unexpectedly. This issue occurs for users that select an audio output device different from the \"Default Audio Device\". Examples of applications that may stop working include:
- Windows Media Player
- Realtek HD Audio Manager
- Sound Blaster Control Panel
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
- Server: Windows Server, version 1809; Windows Server 2019
Workaround: As a temporary solution, select the \"Default Audio Device\" in the options provided by the application; please refer to the application's user manual for details. For example, to set the Default Audio Device in Windows Media Player:
- Open Windows Media Player > Tools > Options > Devices.
- Select the device and choose Properties.
- On the next dialog, from the drop-down menu under Select the Audio Device, choose Default Audio Device from the list.
You can then send audio from the application to the audio device you want in the per-application audio settings found under Settings > System > Sound > App Volume and device preferences.
Resolved: This issue was resolved in KB4490481.
Back to top | OS Build 17763.348
March 01, 2019
KB4482887 | Resolved
KB4490481 | Resolved:
April 02, 2019 10:00 AM PT
Opened:
March 01, 2019 10:00 AM PT |
+
+ "
+
+- title: February 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Error 1309 when installing/uninstalling MSI or MSP filesAfter installing KB4487044, users may receive \"Error 1309\" while installing or uninstalling certain types of MSI and MSP files.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue is resolved in KB4489899.
Back to top | OS Build 17763.316
February 12, 2019
KB4487044 | Resolved
KB4489899 | Resolved:
March 12, 2019 10:00 AM PT
Opened:
February 12, 2019 10:00 AM PT |
+ Internet Explorer may fail to load imagesAfter installing KB4487044, Internet Explorer may fail to load images with a backslash (\\) in their relative source path.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4482887.
Back to top | OS Build 17763.316
February 12, 2019
KB4487044 | Resolved
KB4482887 | Resolved:
March 01, 2019 10:00 AM PT
Opened:
February 12, 2019 10:00 AM PT |
+ | Applications using Microsoft Jet database and Access 95 file format stop working Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4482887.
Back to top | OS Build 17763.316
February 12, 2019
KB4487044 | Resolved
KB4482887 | Resolved:
March 01, 2019 10:00 AM PT
Opened:
February 12, 2019 10:00 AM PT |
+ First character of the Japanese era name not recognizedAfter installing KB4487044, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4482887.
Back to top | OS Build 17763.316
February 12, 2019
KB4487044 | Resolved
KB4482887 | Resolved:
March 01, 2019 10:00 AM PT
Opened:
February 12, 2019 10:00 AM PT |
+
+ "
+
+- title: January 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Internet Explorer 11 authentication issue with multiple concurrent logonsAfter installing the February 12, 2019 update ( KB4487044), Internet Explorer 11 and other applications that use WININET.DLL may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to: - Cache size and location show zero or empty.
- Keyboard shortcuts may not work properly.
- Webpages may intermittently fail to load or render correctly.
- Issues with credential prompts.
- Issues when downloading files.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolved: This issue was resolved in KB4493509.
Back to top | OS Build 17763.253
January 08, 2019
KB4480116 | Resolved
KB4493509 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ MSXML6 may cause applications to stop responding After installing KB4480116, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode(). The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolved: This issue was resolved in KB4493509.
Back to top | OS Build 17763.253
January 08, 2019
KB4480116 | Resolved
KB4493509 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ | Global DNS outage affects Windows Update customers Windows Update customers were affected by a network infrastructure event on January 29, 2019 (21:00 UTC), caused by an external DNS service provider's global outage. A software update to the external provider's DNS servers resulted in the distribution of corrupted DNS records that affected connectivity to the Windows Update service. The DNS records were restored by January 30, 2019 (00:10 UTC), and the majority of local Internet Service Providers (ISP) have refreshed their DNS servers and customer services have been restored. Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
- Server: Windows Server, version 1809; Windows Server 2019
While this was not an issue with Microsoft's services, we take any service disruption for our customers seriously. We will work with partners to better understand this so we can provide higher quality service in the future even across diverse global network providers. If you are still unable to connect to Windows Update services due to this problem, please contact your local ISP or network administrator. You can also refer to our new KB4493784 for more information to determine if your network is affected, and to provide your local ISP or network administrator with additional information to assist you.
Back to top |
| Resolved
| Resolved:
March 08, 2019 11:15 AM PT
Opened:
January 29, 2019 02:00 PM PT |
+ Webpages become unresponsive in Microsoft EdgeAfter installing KB4480116, some Microsoft Edge users report that they:
- Cannot load webpages using a local IP address.
- Cannot load webpages on the Internet using a VPN connection.
Browsing fails or the webpage may become unresponsive.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709
Resolution: This issue is resolved in KB4487044.
Back to top | OS Build 17763.253
January 08, 2019
KB4480116 | Resolved
KB4487044 | Resolved:
February 12, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ Unable to access hotspots with third-party applicationsAfter installing KB4480116, third-party applications may have difficulty authenticating hotspots.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue is resolved in KB4476976.
Back to top | OS Build 17763.253
January 08, 2019
KB4480116 | Resolved
KB4476976 | Resolved:
January 22, 2019 02:00 PM PT
Opened:
January 08, 2019 10:00 AM PT |
+
+ "
+
+- title: December 2018
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ | Microsoft Edge may crash or hang while playing video nVidia has notified Microsoft of an issue where Microsoft Edge may crash or hang while playing video. This issue occurs following an nVidia driver update.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
- Server: Windows Server, version 1809; Windows Server 2019
Resolution: nVidia has released an updated driver to address this issue. Please follow the instructions found in nVidia's support article.
Back to top | OS Build 17763.165
December 05, 2018
KB4469342 | Resolved
| Resolved:
November 29, 2018 10:03 AM PT
Opened:
December 05, 2018 02:00 PM PT |
+
+ "
+
+- title: November 2018
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ | Shared albums may not sync with iCloud for Windows Upgrade block: Users who attempt to install iCloud for Windows (version 7.7.0.27) will see a message displayed that this version iCloud for Windows isn't supported and the install will fail.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
- Server: Windows Server, version 1809; Windows Server 2019
To ensure a seamless experience, Microsoft is blocking devices with iCloud for Windows (version 7.7.0.27) software installed from being offered Window 10, version 1809 until this issue has been resolved.
We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool from the Microsoft software download website until this issue is resolved. Resolution: Apple has released an updated version of iCloud for Windows (version 7.8.1) that resolves compatibility issues encountered when updating or synching Shared Albums after updating to Windows 10, version 1809. We recommend that you update your iCloud for Windows to version 7.8.1 when prompted before attempting to upgrade to Windows 10, version 1809. You can also manually download the latest version of iCloud for Windows by visiting https://support.apple.com/en-us/HT204283.
Back to top | OS Build 17763.134
November 13, 2018
KB4467708 | Resolved
KB4482887 | Resolved:
March 01, 2019 10:00 AM PT
Opened:
November 13, 2018 10:00 AM PT |
+ | Intel Audio Display (intcdaud.sys) notification during Windows 10 Setup Upgrade block: Microsoft and Intel have identified a compatibility issue with a range of Intel Display Audio device drivers (intcdaud.sys, versions 10.25.0.3 - 10.25.0.8) that may result in excessive processor demand and reduced battery life. As a result, the update process to the Windows 10 October 2018 Update (Windows 10, version 1809) will fail and affected devices will automatically revert to the previous working configuration.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
- Server: Windows Server, version 1809; Windows Server 2019
If you see a \"What needs your attention\" notification during installation of the October 2018 Update, you have one of these affected drivers on your system. On the notification, click Back to remain on your current version of Windows 10. To ensure a seamless experience, we are blocking devices from being offered the October 2018 Update until updated Intel device drivers are installed on your current operating system. We recommend that you do not attempt to manually update to Windows 10, version 1809, using the Update Now button or the Media Creation Tool from the Microsoft Software Download Center until newer Intel device drivers are available with the update. You can either wait for newer drivers to be installed automatically through Windows Update or check with your computer manufacturer for the latest device driver software availability and installation procedures. For more information about this issue, see Intel's customer support guidance. Resolution: This issue was resolved in KB4482887 and the upgrade block removed.
Back to top | OS Build 17763.134
November 13, 2018
KB4467708 | Resolved
KB4482887 | Resolved:
March 01, 2019 10:00 AM PT
Opened:
November 13, 2018 10:00 AM PT |
+ | F5 VPN clients losing network connectivity Upgrade block: After updating to Window 10, version 1809, F5 VPN clients may lose network connectivity when the VPN service is in a split tunnel configuration.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
- Server: Windows Server, version 1809; Windows Server 2019
Resolution: This issue was resolved in KB4482887 and the upgrade block removed.
Back to top | OS Build 17763.134
November 13, 2018
KB4467708 | Resolved
KB4482887 | Resolved:
March 01, 2019 10:00 AM PT
Opened:
November 13, 2018 10:00 AM PT |
+ | Issues with lock screen and Microsoft Edge tabs for certain AMD Radeon video cards Note: AMD no longer supports Radeon HD2000 and HD4000 series graphic processor units (GPUs). Upgrade block: After updating to Window 10, version 1809, Microsoft Edge tabs may stop working when a device is configured with AMD Radeon HD2000 or HD4000 series video cards. Customers may get the following error code: \"INVALID_POINTER_READ_c0000005_atidxx64.dll\". Some users may also experience performance issues with the lock screen or the ShellExperienceHost. (The lock screen hosts widgets, and the ShellExperienceHost is responsible for assorted shell functionality.)
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
- Server: Windows Server, version 1809; Windows Server 2019
Resolution: This issue was resolved in KB4487044, and the block was removed.
Back to top | OS Build 17763.134
November 13, 2018
KB4467708 | Resolved
KB4487044 | Resolved:
February 12, 2019 10:00 AM PT
Opened:
November 13, 2018 10:00 AM PT |
+ | Trend Micro OfficeScan and Worry-Free Business Security AV software not compatible Upgrade block: Microsoft and Trend Micro have identified a compatibility issue with Trend Micro's OfficeScan and Worry-Free Business Security software when attempting to update to Windows 10, version 1809.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
- Server: Windows Server, version 1809; Windows Server 2019
Once you have updated your version of Trend Micro's OfficeScan or Worry-Free Business Security software, you will be offered Windows 10, version 1809 automatically.
Back to top | OS Build 17763.134
November 13, 2018
KB4467708 | Resolved
| Resolved:
February 01, 2019 09:00 AM PT
Opened:
November 13, 2018 10:00 AM PT |
+ | Audio stops working after installing Intel audio driver Upgrade block: Intel unintentionally released version 9.21.00.3755 of the Intel Smart Sound Technology (ISST) Driver through Windows Update and inadvertently offered it to a range of devices running Window 10, version 1709, 1803, and 1809. If a device contained a compatible audio driver, the new driver overrode it and caused audio to stop working.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
- Server: Windows Server, version 1809; Windows Server 2019
Resolution: This issue was resolved in KB4468550 and the upgrade block removed.
Back to top | OS Build 17763.134
November 13, 2018
KB4467708 | Resolved
KB4468550 | Resolved:
December 07, 2018 10:00 AM PT
Opened:
November 13, 2018 10:00 AM PT |
+ | Office apps (32-bit) unable to use 'Save As…' function Upgrade block: Microsoft and Morphisec have identified an issue on devices that have installed Morphisec Protector or another application that uses the Morphisec Software Development Kit (SDK) including Cisco AMP for Endpoints. These applications may impact customers' ability to use the 'Save As.'dialog when saving documents in 32-bit versions of Microsoft Office applications. Saving of files is not impacted.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
- Server: Windows Server, version 1809; Windows Server 2019
Resolution: Morphisec and Cisco have released updated versions of their applications to address this issue. We recommend customers update to these minimum versions before attempting to attempting to upgrade to Windows 10, version 1809:
- Morphisec Protector version 2.4.8
- Cisco AMP for Endpoints version 6.2.3.10814
An upgrade block remains in place for earlier versions of the applications than those listed above.
Back to top | OS Build 17763.134
November 13, 2018
KB4467708 | Resolved
| Resolved:
December 06, 2018 12:00 PM PT
Opened:
November 13, 2018 10:00 AM PT |
+ | Mapped drives fail to reconnect after login Upgrade block: Network drives may fail to reconnect after booting and logging on to a Windows device. Symptoms include: - In Windows Explorer, a red X appears on the mapped network drives.
- Mapped network drives show as Unavailable when you run the net use command from a command prompt.
- In the notification area, a notification displays the following message, \"Could not reconnect all network drives.\"
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
- Server: Windows Server, version 1809; Windows Server 2019
Resolution: This issue was resolved in KB4469342 and the upgrade block removed.
Back to top | OS Build 17763.134
November 13, 2018
KB4467708 | Resolved
KB4469342 | Resolved:
December 05, 2018 02:00 PM PT
Opened:
November 13, 2018 10:00 AM PT |
+
+ "
+
+- title: October 2018
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Unable to use Seek bar in Windows Media PlayerAfter installing KB4464330, users may not be able to use the Seek bar in Windows Media Player when playing specific files. This issue does not affect normal playback.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4471332.
Back to top | OS Build 17763.55
October 09, 2018
KB4464330 | Resolved
KB4471332 | Resolved:
December 11, 2018 10:00 AM PT
Opened:
October 09, 2018 10:00 AM PT |
+ Users cannot set Win32 program defaults After installing KB4464330, some users cannot set Win32 program defaults for certain app and file type combinations using the Open with... command or Settings > Apps > Default apps. In some cases, Microsoft Notepad or other Win32 programs cannot be set as the default.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803
Resolution: This issue is resolved in KB4469342.
Back to top | OS Build 17763.55
October 09, 2018
KB4464330 | Resolved
KB4469342 | Resolved:
December 05, 2018 02:00 PM PT
Opened:
October 09, 2018 10:00 AM PT |
+
+ "
diff --git a/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml b/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml
new file mode 100644
index 0000000000..784833bce6
--- /dev/null
+++ b/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml
@@ -0,0 +1,107 @@
+### YamlMime:YamlDocument
+
+documentType: LandingData
+title: Resolved issues in Windows 7 and Windows Server 2008 R2 SP1
+metadata:
+ document_id:
+ title: Resolved issues in Windows 7 and Windows Server 2008 R2 SP1
+ description: Resolved issues in Windows 7 and Windows Server 2008 R2 SP1
+ keywords: ["Resolved issues in Windows 7", "Windows 7", "Windows Server 2008 R2 SP1"]
+ ms.localizationpriority: high
+ author: greg-lindsay
+ ms.author: greglin
+ manager: dougkim
+ ms.topic: article
+ ms.devlang: na
+
+sections:
+- items:
+ - type: markdown
+ text: "
+ See a list of known issues that have been resolved for Windows 7 and Windows Server 2008 R2 SP1 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page.
+
+ "
+- items:
+ - type: markdown
+ text: "
+
+ "
+
+- title: Resolved issues
+- items:
+ - type: markdown
+ text: "
+ | Summary | Affected build | Status | Date resolved |
+ Virtual machines fail to restore.
Virtual machines (VMs) may fail to restore successfully if the VM has been saved and restored once before.
See details > | January 08, 2019
KB4480970 | Resolved
KB4490511 | April 21, 2019 12:00 AM PT |
+ Local Administrators unable to remotely access shares.
Local users who are part of the local Administrators group may not be able to remotely access shares on Windows Server 2008 R2 and Windows 7 machines.
See details > | January 08, 2019
KB4480970 | Resolved
KB4487345 | April 20, 2019 11:53 PM PT |
+ Internet Explorer 11 authentication issue with multiple concurrent logons.
Internet Explorer 11 users may encounter issues if two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine.
See details > | January 08, 2019
KB4480970 | Resolved
KB4493472 | April 09, 2019 10:00 AM PT |
+ Custom URI schemes may not start corresponding application.
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.
See details > | March 12, 2019
KB4489878 | Resolved
KB4493472 | April 09, 2019 10:00 AM PT |
+ NETDOM.EXE fails to run.
NETDOM.EXE fails to run and the error, “The command failed to complete successfully.” appears on screen.
See details > | March 12, 2019
KB4489878 | Resolved
KB4493472 | April 09, 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 09, 2019 10:00 AM PT |
+ Event Viewer may not show some event descriptions for network interface cards.
The Event Viewer may not show some event descriptions for network interface cards (NIC).
See details > | October 18, 2018
KB4462927 | Resolved
KB4489878 | March 12, 2019 10:00 AM PT |
+ First character of the Japanese era name not recognized as an abbreviation.
The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.
See details > | January 17, 2019
KB4480955 | Resolved
KB4486565 | February 19, 2019 02:00 PM PT |
+ Internet Explorer may fail to load images.
Internet Explorer may fail to load images with a backslash (\\) in their relative source path.
See details > | February 12, 2019
KB4486563 | Resolved
KB4486565 | February 19, 2019 02:00 PM PT |
+ Applications using Microsoft Jet database and Access 95 file format stop working.
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.
See details > | February 12, 2019
KB4486563 | Resolved
KB4486565 | February 19, 2019 02:00 PM PT |
+ Applications using Microsoft Jet database fail to open.
Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if column names are greater than 32 characters.
See details > | January 08, 2019
KB4480970 | Resolved
KB4486563 | February 12, 2019 10:00 AM PT |
+ Unable to use Seek bar in Windows Media Player
Users may not be able to use the Seek bar in Windows Media Player when playing specific files.
See details > | October 09, 2018
KB4462923 | Resolved
KB4471318 | December 11, 2018 10:00 AM PT |
+
+ "
+
+- title: Issue Details
+- items:
+ - type: markdown
+ text: "
+
+
+ "
+- title: April 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Devices may not respond at login or Welcome screen if running certain Avast software.Microsoft and Avast have identified an issue on devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software after you install KB4493472 and restart. Devices may become unresponsive at the login or Welcome screen. Additionally, you may be unable to log in or log in after an extended period of time.
Affected platforms: - Client: Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: Avast has released emergency updates to address this issue. For more information and AV update schedule, see the Avast support KB article.
Back to top | April 09, 2019
KB4493472 | Resolved
| Resolved:
April 09, 2019 10:00 AM PT
Opened:
April 09, 2019 10:00 AM PT |
+
+ "
+
+- title: March 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Custom URI schemes may not start corresponding application.After installing KB4489878, custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites on Internet Explorer.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4493472.
Back to top | March 12, 2019
KB4489878 | Resolved
KB4493472 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+ NETDOM.EXE fails to run.After installing KB4489878, NETDOM.EXE fails to run, and the on-screen error, “The command failed to complete successfully.” appears.
Affected platforms: - Client: Windows 7, Service Pack 1
- Server: Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4493472.
Back to top | March 12, 2019
KB4489878 | Resolved
KB4493472 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+
+ "
+
+- title: February 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Internet Explorer may fail to load images.After installing KB4486563, Internet Explorer may fail to load images with a backslash (\\) in their relative source path.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4486565.
Back to top | February 12, 2019
KB4486563 | Resolved
KB4486565 | Resolved:
February 19, 2019 02:00 PM PT
Opened:
February 12, 2019 10:00 AM PT |
+ | Applications using Microsoft Jet database and Access 95 file format stop working. Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4486565.
Back to top | February 12, 2019
KB4486563 | Resolved
KB4486565 | Resolved:
February 19, 2019 02:00 PM PT
Opened:
February 12, 2019 10:00 AM PT |
+
+ "
+
+- title: January 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Virtual machines fail to restore.After installing KB4480970, virtual machines (VM) may fail to restore successfully if the VM has been saved and restored once before. The error message is, “Failed to restore the virtual machine state: Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine. (0xC0370027).”
This affects AMD Bulldozer Family 15h, AMD Jaguar Family 16h, and AMD Puma Family 16h (second generation) microarchitectures.
Affected platforms: - Client: Windows 7, Service Pack 1
- Server: Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4490511.
Back to top | January 08, 2019
KB4480970 | Resolved
KB4490511 | Resolved:
February 19, 2019 02:00 PM PT
Opened:
January 08, 2019 10:00 AM PT |
+ Local Administrators unable to remotely access shares.Local users who are part of the local Administrators group may not be able to remotely access shares on Windows Server 2008 R2 and Windows 7 machines after installing KB4480970. This does not affect domain accounts in the local Administrators group. Affected platforms: - Client: Windows 7, Service Pack 1
- Server: Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487345.
Back to top | January 08, 2019
KB4480970 | Resolved
KB4487345 | Resolved:
January 11, 2019 02:00 PM PT
Opened:
January 08, 2019 10:00 AM PT |
+ Internet Explorer 11 authentication issue with multiple concurrent logons.After installing KB4480970, Internet Explorer 11 and other applications that use WININET.DLL may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to:
- Cache size and location show zero or empty.
- Keyboard shortcuts may not work properly.
- Webpages may intermittently fail to load or render correctly.
- Issues with credential prompts.
- Issues when downloading files.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4493472.
Back to top | January 08, 2019
KB4480970 | Resolved
KB4493472 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ First character of the Japanese era name not recognized as an abbreviation.After installing KB4480955, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4486565.
Back to top | January 17, 2019
KB4480955 | Resolved
KB4486565 | Resolved:
February 19, 2019 02:00 PM PT
Opened:
January 17, 2019 10:00 AM PT |
+ | Applications using Microsoft Jet database fail to open. Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if the database has column names greater than 32 characters. The database will fail to open with the error, “Unrecognized Database Format”.
Affected Platforms: - Client: Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4486563.
Back to top | January 08, 2019
KB4480970 | Resolved
KB4486563 | Resolved:
February 12, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+
+ "
+
+- title: October 2018
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Event Viewer may not show some event descriptions for network interface cards.After installing KB4462927, the Event Viewer may not show some event descriptions for network interface cards (NICs).
Affected Platforms: - Client: Windows 7, Service Pack 1
- Server: Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4489878.
Back to top | October 18, 2018
KB4462927 | Resolved
KB4489878 | Resolved:
March 12, 2019 10:00 AM PT
Opened:
October 18, 2018 10:00 AM PT |
+ Unable to use Seek bar in Windows Media PlayerAfter installing KB4462923, users may not be able to use the Seek Bar in Windows Media Player when playing specific files. This issue does not affect normal playback.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1.
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4471318.
Back to top | October 09, 2018
KB4462923 | Resolved
KB4471318 | Resolved:
December 11, 2018 10:00 AM PT
Opened:
October 09, 2018 10:00 AM PT |
+
+ "
diff --git a/windows/release-information/resolved-issues-windows-8.1-and-windows-server-2012-r2.yml b/windows/release-information/resolved-issues-windows-8.1-and-windows-server-2012-r2.yml
new file mode 100644
index 0000000000..01cef4fef3
--- /dev/null
+++ b/windows/release-information/resolved-issues-windows-8.1-and-windows-server-2012-r2.yml
@@ -0,0 +1,109 @@
+### YamlMime:YamlDocument
+
+documentType: LandingData
+title: Resolved issues in Windows 7 and Windows Server 2008 R2 SP1
+metadata:
+ document_id:
+ title: Resolved issues in Windows 7 and Windows Server 2008 R2 SP1
+ description: Resolved issues in Windows 8.1 and Windows Server 2012 R2
+ keywords: ["Resolved issues in Windows 7", "Windows 7", "Windows Server 2012 R2"]
+ ms.localizationpriority: high
+ author: greg-lindsay
+ ms.author: greglin
+ manager: dougkim
+ ms.topic: article
+ ms.devlang: na
+
+sections:
+- items:
+ - type: markdown
+ text: "
+ See a list of known issues that have been resolved for Windows 8.1 and Windows Server 2012 R2 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page.
+
+ "
+- items:
+ - type: markdown
+ text: "
+
+ "
+
+- title: Resolved issues
+- items:
+ - type: markdown
+ text: "
+ | Summary | Affected build | Status | Date resolved |
+ Internet Explorer 11 authentication issue with multiple concurrent logons
Internet Explorer 11 users may encounter issues if two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine.
See details > | January 08, 2019
KB4480963 | Resolved
KB4493446 | April 09, 2019 10:00 AM PT |
+ MSXML6 may cause applications to stop responding.
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
See details > | January 08, 2019
KB4480963 | Resolved
KB4493446 | April 09, 2019 10:00 AM PT |
+ Custom URI schemes may not start corresponding application
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.
See details > | March 12, 2019
KB4489881 | Resolved
KB4493446 | April 09, 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
KB4493446 | Resolved
| April 09, 2019 10:00 AM PT |
+ Embedded objects may display incorrectly
Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly.
See details > | February 12, 2019
KB4487000 | Resolved
KB4493446 | April 09, 2019 10:00 AM PT |
+ Devices with winsock kernel client may receive error
Devices with a winsock kernel client may receive D1, FC, and other errors.
See details > | March 12, 2019
KB4489881 | Resolved
KB4489893 | March 19, 2019 10:00 AM PT |
+ Error 1309 when installing/uninstalling MSI or MSP files
Users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.
See details > | February 19, 2019
KB4487016 | Resolved
KB4489881 | March 12, 2019 10:00 AM PT |
+ First character of the Japanese era name not recognized as an abbreviation
The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.
See details > | January 15, 2019
KB4480969 | Resolved
KB4487016 | February 19, 2019 02:00 PM PT |
+ Internet Explorer may fail to load images
Internet Explorer may fail to load images with a backslash (\\) in their relative source path.
See details > | February 12, 2019
KB4487000 | Resolved
KB4487016 | February 19, 2019 02:00 PM PT |
+ Virtual machines fail to restore
Virtual machines (VMs) may fail to restore successfully if the VM has been saved and restored once before.
See details > | January 08, 2019
KB4480963 | Resolved
KB4490512 | February 19, 2019 10:00 AM PT |
+ Applications using Microsoft Jet database fail to open
Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if column names are greater than 32 characters.
See details > | January 08, 2019
KB4480963 | Resolved
KB4487000 | February 12, 2019 10:00 AM PT |
+ Unable to access hotspots with third-party applications
Third-party applications may have difficulty authenticating hotspots.
See details > | January 08, 2019
KB4480963 | Resolved
KB4480969 | January 15, 2019 10:00 AM PT |
+ Unable to use Seek bar in Windows Media Player
Users may not be able to use the Seek bar in Windows Media Player when playing specific files.
See details > | October 09, 2018
KB4462926 | Resolved
KB4471320 | December 11, 2018 10:00 AM PT |
+
+ "
+
+- title: Issue Details
+- items:
+ - type: markdown
+ text: "
+
+
+ "
+- title: April 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Devices may not respond at login or Welcome screen if running certain Avast softwareMicrosoft and Avast have identified an issue on devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software after you install KB4493446 and restart. Devices may become unresponsive at the login or Welcome screen. Additionally, you may be unable to log in or log in after an extended period of time.
Affected platforms: - Client: Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: Avast has released emergency updates to address this issue. For more information and AV update schedule, see the Avast support KB article.
Back to top | April 09, 2019
KB4493446 | Resolved
| Resolved:
April 09, 2019 10:00 AM PT
Opened:
April 09, 2019 10:00 AM PT |
+
+ "
+
+- title: March 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Custom URI schemes may not start corresponding applicationAfter installing KB4489881, 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: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4493446.
Back to top | March 12, 2019
KB4489881 | Resolved
KB4493446 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+ Devices with winsock kernel client may receive errorAfter installing KB4489881, devices with a winsock kernel client may receive D1, FC, and other errors. Additionally, systems that run the Skype for Business or Lync Server Edge Transport role may be affected by this issue.
Affected platforms: - Client: Windows 8.1
- Server: Windows Server 2012 R2
Resolution: This issue is resolved in KB4489893.
Back to top | March 12, 2019
KB4489881 | Resolved
KB4489893 | Resolved:
March 19, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+
+ "
+
+- title: February 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ | Embedded objects may display incorrectly Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly.
For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color.
Affected platforms: - Client: Windows 8.1
- Server: Windows Server 2012 R2
Resolution: This issue is resolved in KB4493446.
Back to top | February 12, 2019
KB4487000 | Resolved
KB4493446 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
February 12, 2019 10:00 AM PT |
+ Error 1309 when installing/uninstalling MSI or MSP filesAfter installing KB4487016, users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue is resolved in KB4489881.
Back to top | February 19, 2019
KB4487016 | Resolved
KB4489881 | Resolved:
March 12, 2019 10:00 AM PT
Opened:
February 19, 2019 02:00 PM PT |
+ Internet Explorer may fail to load imagesAfter installing KB4487000, Internet Explorer may fail to load images with a backslash (\\) in their relative source path.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487016.
Back to top | February 12, 2019
KB4487000 | Resolved
KB4487016 | Resolved:
February 19, 2019 02:00 PM PT
Opened:
February 12, 2019 10:00 AM PT |
+
+ "
+
+- title: January 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Internet Explorer 11 authentication issue with multiple concurrent logonsAfter installing KB4480963, Internet Explorer 11 and other applications that use WININET.DLL may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to:
- Cache size and location show zero or empty.
- Keyboard shortcuts may not work properly.
- Webpages may intermittently fail to load or render correctly.
- Issues with credential prompts.
- Issues when downloading files.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4493446.
Back to top | January 08, 2019
KB4480963 | Resolved
KB4493446 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ MSXML6 may cause applications to stop responding.After installing KB4480963, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.
Resolution: This issue is resolved in KB4493446.
Back to top | January 08, 2019
KB4480963 | Resolved
KB4493446 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ First character of the Japanese era name not recognized as an abbreviationAfter installing KB4480969, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487016.
Back to top | January 15, 2019
KB4480969 | Resolved
KB4487016 | Resolved:
February 19, 2019 02:00 PM PT
Opened:
January 15, 2019 10:00 AM PT |
+ Virtual machines fail to restoreAfter installing KB4480963, virtual machines (VM) may fail to restore successfully if the VM has been saved and restored once before. The error message is, “Failed to restore the virtual machine state: Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine. (0xC0370027).”
This affects AMD Bulldozer Family 15h, AMD Jaguar Family 16h, and AMD Puma Family 16h (second generation) microarchitectures.
Resolution: This issue is resolved in KB4490512.
Back to top | January 08, 2019
KB4480963 | Resolved
KB4490512 | Resolved:
February 19, 2019 02:00 PM PT
Opened:
January 08, 2019 10:00 AM PT |
+ | Applications using Microsoft Jet database fail to open Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if the database has column names greater than 32 characters. The database will fail to open with the error, “Unrecognized Database Format”.
Affected platforms: - Client: Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487000.
Back to top | January 08, 2019
KB4480963 | Resolved
KB4487000 | Resolved:
February 12, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ Unable to access hotspots with third-party applicationsAfter installing KB4480963, third-party applications may have difficulty authenticating hotspots.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue is resolved in KB4480969.
Back to top | January 08, 2019
KB4480963 | Resolved
KB4480969 | Resolved:
January 15, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+
+ "
+
+- title: October 2018
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Unable to use Seek bar in Windows Media PlayerAfter installing KB4462926, users may not be able to use the Seek Bar in Windows Media Player when playing specific files. This issue does not affect normal playback.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4471320.
Back to top | October 09, 2018
KB4462926 | Resolved
KB4471320 | Resolved:
December 11, 2018 10:00 AM PT
Opened:
October 09, 2018 10:00 AM PT |
+
+ "
diff --git a/windows/release-information/status-windows-10-1507.yml b/windows/release-information/status-windows-10-1507.yml
new file mode 100644
index 0000000000..b951fd389b
--- /dev/null
+++ b/windows/release-information/status-windows-10-1507.yml
@@ -0,0 +1,91 @@
+### YamlMime:YamlDocument
+
+documentType: LandingData
+title: Windows 10, version 1507
+metadata:
+ document_id:
+ title: Windows 10, version 1507
+ description: View annoucements and review known issues and fixes for Windows 10 version 1507
+ keywords: Windows 10, issues, fixes, announcements, Windows Server, advisories
+ ms.localizationpriority: high
+ author: greg-lindsay
+ ms.author: greglin
+ manager: dougkim
+ ms.topic: article
+ ms.devlang: na
+
+sections:
+- items:
+ - type: markdown
+ text: "
+ Find information on known issues for Windows 10, version 1507. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s).
+
+ "
+
+- items:
+ - type: list
+ style: cards
+ className: cardsM
+ columns: 3
+ items:
+
+ - href: https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-version-1809-designated-for-broad-deployment/ba-p/389540
+ html: Read the announcement >
+ image:
+ src: https://docs.microsoft.com//media/common/i_deploy.svg
+ title: Windows 10, version 1809 designated for broad deployment
+ - href: https://blogs.windows.com/windowsexperience/2019/04/04/improving-the-windows-10-update-experience-with-control-quality-and-transparency
+ html: Find out more >
+ image:
+ src: https://docs.microsoft.com/media/common/i_whats-new.svg
+ title: Improvements to the Windows 10 update experience are coming
+ - href: https://blogs.windows.com/windowsexperience/2019/03/06/data-insights-and-listening-to-improve-the-customer-experience
+ html: Learn about our approach >
+ image:
+ src: https://docs.microsoft.com/media/common/i_investigate.svg
+ title: How do we measure and improve the quality of Windows?
+- items:
+ - type: markdown
+ text: "
+
+ "
+- items:
+ - type: markdown
+ text: "
+
+ "
+
+- title: Known issues
+- items:
+ - type: markdown
+ text: "
+ | Summary | Affected build | Status | Last updated |
+ MSXML6 may cause applications to stop responding
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
See details > | OS Build 10240.18094
January 08, 2019
KB4480962 | Resolved
KB4493475 | April 09, 2019 10:00 AM PT |
+ Custom URI schemes may not start corresponding application
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.
See details > | OS Build 10240.18158
March 12, 2019
KB4489872 | Resolved
KB4493475 | April 09, 2019 10:00 AM PT |
+
+ "
+
+- title: Issue Details
+- items:
+ - type: markdown
+ text: "
+
+
+ "
+- title: March 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Custom URI schemes may not start corresponding applicationAfter installing KB4489872, Custom URI Schemes for Application Protocol handlers may not start the corresponding application for local intranet and trusted sites on Internet Explorer.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue was resolved in KB4493475.
Back to top | OS Build 10240.18158
March 12, 2019
KB4489872 | Resolved
KB4493475 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+
+ "
+
+- title: January 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ MSXML6 may cause applications to stop responding After installing KB4480962, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue was resolved in KB4493475.
Back to top | OS Build 10240.18094
January 08, 2019
KB4480962 | Resolved
KB4493475 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+
+ "
diff --git a/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml b/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml
new file mode 100644
index 0000000000..9c6bd050d3
--- /dev/null
+++ b/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml
@@ -0,0 +1,111 @@
+### YamlMime:YamlDocument
+
+documentType: LandingData
+title: Windows 10, version 1607 and Windows Server 2016
+metadata:
+ document_id:
+ title: Windows 10, version 1607 and Windows Server 2016
+ description: View annoucements and review known issues and fixes for Windows 10 version 1607 and Windows Server 2016
+ keywords: Windows 10, issues, fixes, announcements, Windows Server, advisories
+ ms.localizationpriority: high
+ author: greg-lindsay
+ ms.author: greglin
+ manager: dougkim
+ ms.topic: article
+ ms.devlang: na
+
+sections:
+- items:
+ - type: markdown
+ text: "
+ Find information on known issues for Windows 10, version 1607 and Windows Server 2016. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s).
+
+ "
+
+- items:
+ - type: list
+ style: cards
+ className: cardsM
+ columns: 3
+ items:
+
+ - href: https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-version-1809-designated-for-broad-deployment/ba-p/389540
+ html: Read the announcement >
+ image:
+ src: https://docs.microsoft.com//media/common/i_deploy.svg
+ title: Windows 10, version 1809 designated for broad deployment
+ - href: https://blogs.windows.com/windowsexperience/2019/04/04/improving-the-windows-10-update-experience-with-control-quality-and-transparency
+ html: Find out more >
+ image:
+ src: https://docs.microsoft.com/media/common/i_whats-new.svg
+ title: Improvements to the Windows 10 update experience are coming
+ - href: https://blogs.windows.com/windowsexperience/2019/03/06/data-insights-and-listening-to-improve-the-customer-experience
+ html: Learn about our approach >
+ image:
+ src: https://docs.microsoft.com/media/common/i_investigate.svg
+ title: How do we measure and improve the quality of Windows?
+- items:
+ - type: markdown
+ text: "
+
+ "
+- items:
+ - type: markdown
+ text: "
+
+ "
+
+- title: Known issues
+- items:
+ - type: markdown
+ text: "
+ | Summary | Affected build | Status | Last updated |
+ End-user-defined characters (EUDC) cause blue screen at startup
If you enable per font end-user-defined characters (EUDC), the system will stop working and a blue screen may appear at startup.
See details > | OS Build 14393.2879
March 19, 2019
KB4489889 | Resolved
KB4493470 | April 09, 2019 10:00 AM PT |
+ Internet Explorer 11 authentication issue with multiple concurrent logons
Internet Explorer 11 users may encounter issues if two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine.
See details > | OS Build 14393.2724
January 08, 2019
KB4480961 | Resolved
KB4493470 | April 09, 2019 10:00 AM PT |
+ MSXML6 may cause applications to stop responding
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
See details > | OS Build 14393.2724
January 08, 2019
KB4480961 | Resolved
KB4493470 | April 09, 2019 10:00 AM PT |
+ Cluster service may fail if the minimum password length is set to greater than 14
The cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the Group Policy “Minimum Password Length” is configured with greater than 14 characters.
See details > | OS Build 14393.2639
November 27, 2018
KB4467684 | Mitigated
| March 19, 2019 10:00 AM PT |
+ Custom URI schemes may not start corresponding application
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.
See details > | OS Build 14393.2848
March 12, 2019
KB4489882 | Mitigated
| March 19, 2019 10:00 AM PT |
+ Issue using PXE to start a device from WDS
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.
See details > | OS Build 14393.2848
March 12, 2019
KB4489882 | Mitigated
| March 19, 2019 10:00 AM PT |
+ SCVMM cannot enumerate and manage logical switches deployed on the host
For hosts managed by System Center Virtual Machine Manager (VMM), VMM cannot enumerate and manage logical switches deployed on the host.
See details > | OS Build 14393.2639
November 27, 2018
KB4467684 | Mitigated
| March 19, 2019 10:00 AM PT |
+ Windows may not start on certain Lenovo and Fujitsu laptops with less than 8GB of RAM
Windows may fail to start on certain Lenovo and Fujitsu laptops that have less than 8 GB of RAM.
See details > | OS Build 14393.2608
November 13, 2018
KB4467691 | Mitigated
| February 19, 2019 10:00 AM PT |
+
+ "
+
+- title: Issue Details
+- items:
+ - type: markdown
+ text: "
+
+
+ "
+- title: March 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ | End-user-defined characters (EUDC) cause blue screen at startup If you enable per font end-user-defined characters (EUDC), the system will stop working and a blue screen may appear at startup. This is not a common setting in non-Asian regions.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016
Resolution: This issue was resolved in KB4493470.
Back to top | OS Build 14393.2879
March 19, 2019
KB4489889 | Resolved
KB4493470 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 19, 2019 10:00 AM PT |
+ Custom URI schemes may not start corresponding applicationAfter 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: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Workaround: Right-click the URL link to open it in a new window or tab, or enable Protected Mode in Internet Explorer for local intranet and trusted sites
- Go to Tools > Internet options > Security.
- Within Select a zone to view or change security settings, select Local intranet and then select Enable Protected Mode.
- Select Trusted sites and then select Enable Protected Mode.
- Select OK.
You must restart the browser after making these changes.
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:
March 19, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+ Issue using PXE to start a device from WDSAfter 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: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10 Enterprise LTSC 2016; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server 2016; Windows Server 2012 R2
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:
1. Open Windows Deployment Services from Windows Administrative Tools. 2. Expand Servers and right-click a WDS server. 3. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab.
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:
March 19, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+
+ "
+
+- title: January 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Internet Explorer 11 authentication issue with multiple concurrent logonsAfter installing KB4480961, Internet Explorer 11 and other applications that use WININET.DLL may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to:
- Cache size and location show zero or empty.
- Keyboard shortcuts may not work properly.
- Webpages may intermittently fail to load or render correctly.
- Issues with credential prompts.
- Issues when downloading files.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue was resolved in KB4493470.
Back to top | OS Build 14393.2724
January 08, 2019
KB4480961 | Resolved
KB4493470 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ MSXML6 may cause applications to stop responding After installing KB4480961, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue was resolved in KB4493470.
Back to top | OS Build 14393.2724
January 08, 2019
KB4480961 | Resolved
KB4493470 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+
+ "
+
+- title: November 2018
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Cluster service may fail if the minimum password length is set to greater than 14After installing KB4467684, the cluster service may fail to start with the error \"2245 (NERR_PasswordTooShort)\" if the Group Policy \"Minimum Password Length\" is configured with greater than 14 characters.
Affected platforms: - Client: Windows 10 Enterprise LTSC 2016
- Server: Windows Server 2016
Workaround: Set the domain default \"Minimum Password Length\" policy to less than or equal to 14 characters.
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.
Back to top | OS Build 14393.2639
November 27, 2018
KB4467684 | Mitigated
| Last updated:
March 19, 2019 10:00 AM PT
Opened:
November 27, 2018 10:00 AM PT |
+ SCVMM cannot enumerate and manage logical switches deployed on the hostFor hosts managed by System Center Virtual Machine Manager (VMM), VMM cannot enumerate and manage logical switches deployed on the host after installing KB4467684.
Additionally, if you do not follow the best practices, a stop error may occur in vfpext.sys on the hosts.
Affected platforms: - Client: Windows 10 Enterprise LTSC 2016
- Server: Windows Server 2016
Workaround: Run mofcomp on the following mof files on the affected host:
- Scvmmswitchportsettings.mof
- VMMDHCPSvr.mof
Follow the best practices while patching to avoid a stop error in vfpext.sys in an SDN v2 environment (NC managed hosts).
Back to top | OS Build 14393.2639
November 27, 2018
KB4467684 | Mitigated
| Last updated:
March 19, 2019 10:00 AM PT
Opened:
November 27, 2018 10:00 AM PT |
+ Windows may not start on certain Lenovo and Fujitsu laptops with less than 8GB of RAMAfter installing KB4467691, Windows may fail to start on certain Lenovo and Fujitsu laptops that have less than 8 GB of RAM.
Affected platforms: - Client: Windows 10 Enterprise LTSC 2016
- Server: Windows Server 2016
Workaround: Restart the affected machine using the Unified Extensible Firmware Interface (UEFI). Disable Secure Boot and then restart.
If BitLocker is enabled on your machine, you may have to go through BitLocker recovery after Secure Boot has been disabled.
Next steps: Lenovo and Fujitsu are aware of this issue. Please contact your OEM to ask if there is a firmware update available for your device.
Back to top | OS Build 14393.2608
November 13, 2018
KB4467691 | Mitigated
| Last updated:
February 19, 2019 10:00 AM PT
Opened:
November 13, 2018 10:00 AM PT |
+
+ "
diff --git a/windows/release-information/status-windows-10-1703.yml b/windows/release-information/status-windows-10-1703.yml
new file mode 100644
index 0000000000..932378b491
--- /dev/null
+++ b/windows/release-information/status-windows-10-1703.yml
@@ -0,0 +1,93 @@
+### YamlMime:YamlDocument
+
+documentType: LandingData
+title: Windows 10, version 1703
+metadata:
+ document_id:
+ title: Windows 10, version 1703
+ description: View annoucements and review known issues and fixes for Windows 10 version 1703
+ keywords: Windows 10, issues, fixes, announcements, Windows Server, advisories
+ ms.localizationpriority: high
+ author: greg-lindsay
+ ms.author: greglin
+ manager: dougkim
+ ms.topic: article
+ ms.devlang: na
+
+sections:
+- items:
+ - type: markdown
+ text: "
+ Find information on known issues for Windows 10, version 1703. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s).
+
+ "
+
+- items:
+ - type: list
+ style: cards
+ className: cardsM
+ columns: 3
+ items:
+
+ - href: https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-version-1809-designated-for-broad-deployment/ba-p/389540
+ html: Read the announcement >
+ image:
+ src: https://docs.microsoft.com//media/common/i_deploy.svg
+ title: Windows 10, version 1809 designated for broad deployment
+ - href: https://blogs.windows.com/windowsexperience/2019/04/04/improving-the-windows-10-update-experience-with-control-quality-and-transparency
+ html: Find out more >
+ image:
+ src: https://docs.microsoft.com/media/common/i_whats-new.svg
+ title: Improvements to the Windows 10 update experience are coming
+ - href: https://blogs.windows.com/windowsexperience/2019/03/06/data-insights-and-listening-to-improve-the-customer-experience
+ html: Learn about our approach >
+ image:
+ src: https://docs.microsoft.com/media/common/i_investigate.svg
+ title: How do we measure and improve the quality of Windows?
+- items:
+ - type: markdown
+ text: "
+
+ "
+- items:
+ - type: markdown
+ text: "
+
+ "
+
+- title: Known issues
+- items:
+ - type: markdown
+ text: "
+ | Summary | Affected build | Status | Last updated |
+ End-user-defined characters (EUDC) may cause blue screen at startup
If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup.
See details > | OS Build 15063.1716
March 19, 2019
KB4489888 | Resolved
KB4493474 | April 09, 2019 10:00 AM PT |
+ MSXML6 may cause applications to stop responding
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
See details > | OS Build 15063.1563
January 08, 2019
KB4480973 | Resolved
KB4493474 | April 09, 2019 10:00 AM PT |
+ Custom URI schemes may not start corresponding application
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.
See details > | OS Build 15063.1689
March 12, 2019
KB4489871 | Mitigated
| March 19, 2019 10:00 AM PT |
+
+ "
+
+- title: Issue Details
+- items:
+ - type: markdown
+ text: "
+
+
+ "
+- title: March 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ | End-user-defined characters (EUDC) may cause blue screen at startup If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup. This is not a common setting in non-Asian regions.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016
Resolution: This issue was resolved in KB4493474.
Back to top | OS Build 15063.1716
March 19, 2019
KB4489888 | Resolved
KB4493474 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 19, 2019 10:00 AM PT |
+ Custom URI schemes may not start corresponding applicationAfter 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: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Workaround: Right-click the URL link to open it in a new window or tab, or enable Protected Mode in Internet Explorer for local intranet and trusted sites
1. Go to Tools > Internet options > Security. 2. Within Select a zone to view or change security settings, select Local intranet and then select Enable Protected Mode. 3. Select Trusted sites and then select Enable Protected Mode. 4. Select OK.
You must restart the browser after making these changes.
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.
Back to top | OS Build 15063.1689
March 12, 2019
KB4489871 | Mitigated
| Last updated:
March 19, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+
+ "
+
+- title: January 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ MSXML6 may cause applications to stop responding After installing KB4480973, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue was resolved in KB4493474.
Back to top | OS Build 15063.1563
January 08, 2019
KB4480973 | Resolved
KB4493474 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+
+ "
diff --git a/windows/release-information/status-windows-10-1709.yml b/windows/release-information/status-windows-10-1709.yml
new file mode 100644
index 0000000000..dde03d0798
--- /dev/null
+++ b/windows/release-information/status-windows-10-1709.yml
@@ -0,0 +1,95 @@
+### YamlMime:YamlDocument
+
+documentType: LandingData
+title: Windows 10, version 1709 and Windows Server, version 1709
+metadata:
+ document_id:
+ title: Windows 10, version 1709 and Windows Server, version 1709
+ description: View annoucements and review known issues and fixes for Windows 10 version 1709 and Windows Server 1709
+ keywords: Windows 10, issues, fixes, announcements, Windows Server, advisories
+ ms.localizationpriority: high
+ author: greg-lindsay
+ ms.author: greglin
+ manager: dougkim
+ ms.topic: article
+ ms.devlang: na
+
+sections:
+- items:
+ - type: markdown
+ text: "
+ Find information on known issues for Windows 10, version 1709 and Windows Server, version 1709. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s).
+
+ "
+
+- items:
+ - type: list
+ style: cards
+ className: cardsM
+ columns: 3
+ items:
+
+ - href: https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-version-1809-designated-for-broad-deployment/ba-p/389540
+ html: Read the announcement >
+ image:
+ src: https://docs.microsoft.com//media/common/i_deploy.svg
+ title: Windows 10, version 1809 designated for broad deployment
+ - href: https://blogs.windows.com/windowsexperience/2019/04/04/improving-the-windows-10-update-experience-with-control-quality-and-transparency
+ html: Find out more >
+ image:
+ src: https://docs.microsoft.com/media/common/i_whats-new.svg
+ title: Improvements to the Windows 10 update experience are coming
+ - href: https://blogs.windows.com/windowsexperience/2019/03/06/data-insights-and-listening-to-improve-the-customer-experience
+ html: Learn about our approach >
+ image:
+ src: https://docs.microsoft.com/media/common/i_investigate.svg
+ title: How do we measure and improve the quality of Windows?
+- items:
+ - type: markdown
+ text: "
+
+ "
+- items:
+ - type: markdown
+ text: "
+
+ "
+
+- title: Known issues
+- items:
+ - type: markdown
+ text: "
+ | Summary | Affected build | Status | Last updated |
+ End-user-defined characters (EUDC) may cause blue screen at startup
If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup.
See details > | OS Build 16299.1059
March 19, 2019
KB4489890 | Resolved
KB4493441 | April 09, 2019 10:00 AM PT |
+ MSXML6 causes applications to stop responding if an exception was thrown
MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
See details > | OS Build 16299.904
January 08, 2019
KB4480978 | Resolved
KB4493441 | April 09, 2019 10:00 AM PT |
+ Stop error when attempting to start SSH from WSL
A stop error occurs when attempting to start the Secure Shell client program from Windows Subsystem for Linux with agent forwarding enabled using a command line switch (ssh –A) or
See details > | OS Build 16299.1029
March 12, 2019
KB4489886 | Resolved
KB4493441 | April 09, 2019 10:00 AM PT |
+ Custom URI schemes may not start corresponding application
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.
See details > | OS Build 16299.1029
March 12, 2019
KB4489886 | Mitigated
| March 19, 2019 10:00 AM PT |
+
+ "
+
+- title: Issue Details
+- items:
+ - type: markdown
+ text: "
+
+
+ "
+- title: March 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ | End-user-defined characters (EUDC) may cause blue screen at startup If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup. This is not a common setting in non-Asian regions.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016
Resolution: This issue is resolved in KB4493441.
Back to top | OS Build 16299.1059
March 19, 2019
KB4489890 | Resolved
KB4493441 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 19, 2019 10:00 AM PT |
+ Stop error when attempting to start SSH from WSLAfter applying KB4489886, a stop error occurs when attempting to start the Secure Shell (SSH) client program from Windows Subsystem for Linux (WSL) with agent forwarding enabled using a command line switch (ssh –A) or a configuration setting.
Affected platforms: - Client: Windows 10, version 1803; Windows 10, version 1709
- Server: Windows Server, version 1803; Windows Server, version 1709
Resolution: This issue is resolved in KB4493441.
Back to top | OS Build 16299.1029
March 12, 2019
KB4489886 | Resolved
KB4493441 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+ Custom URI schemes may not start corresponding applicationAfter 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: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Workaround: Right-click the URL link to open it in a new window or tab, or enable Protected Mode in Internet Explorer for local intranet and trusted sites
1. Go to Tools > Internet options > Security. 2. Within Select a zone to view or change security settings, select Local intranet and then select Enable Protected Mode. 3. Select Trusted sites and then select Enable Protected Mode. 4. Select OK.
You must restart the browser after making these changes.
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.
Back to top | OS Build 16299.1029
March 12, 2019
KB4489886 | Mitigated
| Last updated:
March 19, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+
+ "
+
+- title: January 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ MSXML6 causes applications to stop responding if an exception was thrownAfter installing KB4480978, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue is resolved in KB4493441.
Back to top | OS Build 16299.904
January 08, 2019
KB4480978 | Resolved
KB4493441 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+
+ "
diff --git a/windows/release-information/status-windows-10-1803.yml b/windows/release-information/status-windows-10-1803.yml
new file mode 100644
index 0000000000..5470f7dfec
--- /dev/null
+++ b/windows/release-information/status-windows-10-1803.yml
@@ -0,0 +1,97 @@
+### YamlMime:YamlDocument
+
+documentType: LandingData
+title: Windows 10, version 1803
+metadata:
+ document_id:
+ title: Windows 10, version 1803
+ description: View annoucements and review known issues and fixes for Windows 10 version 1803
+ keywords: Windows 10, issues, fixes, announcements, Windows Server, advisories
+ ms.localizationpriority: high
+ author: greg-lindsay
+ ms.author: greglin
+ manager: dougkim
+ ms.topic: article
+ ms.devlang: na
+
+sections:
+- items:
+ - type: markdown
+ text: "
+ Find information on known issues for Windows 10, version 1803. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s).
+
+ "
+
+- items:
+ - type: list
+ style: cards
+ className: cardsM
+ columns: 3
+ items:
+
+ - href: https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-version-1809-designated-for-broad-deployment/ba-p/389540
+ html: Read the announcement >
+ image:
+ src: https://docs.microsoft.com//media/common/i_deploy.svg
+ title: Windows 10, version 1809 designated for broad deployment
+ - href: https://blogs.windows.com/windowsexperience/2019/04/04/improving-the-windows-10-update-experience-with-control-quality-and-transparency
+ html: Find out more >
+ image:
+ src: https://docs.microsoft.com/media/common/i_whats-new.svg
+ title: Improvements to the Windows 10 update experience are coming
+ - href: https://blogs.windows.com/windowsexperience/2019/03/06/data-insights-and-listening-to-improve-the-customer-experience
+ html: Learn about our approach >
+ image:
+ src: https://docs.microsoft.com/media/common/i_investigate.svg
+ title: How do we measure and improve the quality of Windows?
+- items:
+ - type: markdown
+ text: "
+
+ "
+- items:
+ - type: markdown
+ text: "
+
+ "
+
+- title: Known issues
+- items:
+ - type: markdown
+ text: "
+ | Summary | Affected build | Status | Last updated |
+ End-user-defined characters (EUDC) may cause blue screen at startup
If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup.
See details > | OS Build 17134.677
March 19, 2019
KB4489894 | Resolved
KB4493464 | April 09, 2019 10:00 AM PT |
+ MSXML6 may cause applications to stop responding
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
See details > | OS Build 17134.523
January 08, 2019
KB4480966 | Resolved
KB4493464 | April 09, 2019 10:00 AM PT |
+ Stop error when attempting to start SSH from WSL
A stop error occurs when attempting to start Secure Shell from Windows Subsystem for Linux with agent forwarding using a command line switch (ssh –A) or a configuration setting.
See details > | OS Build 17134.648
March 12, 2019
KB4489868 | Resolved
KB4493464 | April 09, 2019 10:00 AM PT |
+ Custom URI schemes may not start corresponding application
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.
See details > | OS Build 17134.648
March 12, 2019
KB4489868 | Mitigated
| March 19, 2019 10:00 AM PT |
+ Issue using PXE to start a device from WDS
Using PXE to start a device from a WDS server configured to use Variable Window Extension may cause the connection to the WDS server to terminate prematurely.
See details > | OS Build 17134.648
March 12, 2019
KB4489868 | Mitigated
| March 19, 2019 10:00 AM PT |
+
+ "
+
+- title: Issue Details
+- items:
+ - type: markdown
+ text: "
+
+
+ "
+- title: March 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ | End-user-defined characters (EUDC) may cause blue screen at startup If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup. This is not a common setting in non-Asian regions.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016
Resolution: This issue was resolved in KB4493464.
Back to top | OS Build 17134.677
March 19, 2019
KB4489894 | Resolved
KB4493464 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 19, 2019 10:00 AM PT |
+ Stop error when attempting to start SSH from WSLAfter applying KB4489868, a stop error occurs when attempting to start the Secure Shell (SSH) client program from Windows Subsystem for Linux (WSL) with agent forwarding enabled using a command line switch (ssh -A) or a configuration setting.
Affected platforms: - Client: Windows 10, version 1803; Windows 10, version 1709
- Server: Windows Server, version 1803; Windows Server, version 1709
Resolution: This issue was resolved in KB4493464.
Back to top | OS Build 17134.648
March 12, 2019
KB4489868 | Resolved
KB4493464 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+ Custom URI schemes may not start corresponding applicationAfter 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: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Workaround: Right-click the URL link to open it in a new window or tab, or enable Protected Mode in Internet Explorer for local intranet and trusted sites - Go to Tools > Internet options > Security
- Within Select a zone to view or change security settings, select Local intranet and then select Enable Protected Mode.
- Select Trusted sites and then select Enable Protected Mode.
- Select OK.
You must restart the browser after making these changes. 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:
March 19, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+ Issue using PXE to start a device from WDSAfter 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: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10 Enterprise LTSC 2016; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server 2016; Windows Server 2012 R2
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: - Open Windows Deployment Services from Windows Administrative Tools.
- Expand Servers and right-click a WDS server.
- Open its properties and clear the?Enable Variable Window Extension?box on the TFTP tab.
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:
March 19, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+
+ "
+
+- title: January 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ MSXML6 may cause applications to stop responding After installing KB4480966, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue was resolved in KB4493464.
Back to top | OS Build 17134.523
January 08, 2019
KB4480966 | Resolved
KB4493464 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+
+ "
diff --git a/windows/release-information/status-windows-10-1809-and-windows-server-2019.yml b/windows/release-information/status-windows-10-1809-and-windows-server-2019.yml
new file mode 100644
index 0000000000..3ddeef1489
--- /dev/null
+++ b/windows/release-information/status-windows-10-1809-and-windows-server-2019.yml
@@ -0,0 +1,123 @@
+### YamlMime:YamlDocument
+
+documentType: LandingData
+title: Windows 10, version 1809 and Windows Server 2019
+metadata:
+ document_id:
+ title: Windows 10, version 1809 and Windows Server 2019
+ description: View annoucements and review known issues and fixes for Windows 10 version 1809 and Windows Server 2019
+ keywords: Windows 10, issues, fixes, announcements, Windows Server, advisories
+ ms.localizationpriority: high
+ author: greg-lindsay
+ ms.author: greglin
+ manager: dougkim
+ ms.topic: article
+ ms.devlang: na
+
+sections:
+- items:
+ - type: markdown
+ text: "
+ Find information on known issues and the status of the rollout for Windows 10, version 1809 and Windows Server 2019. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s).
+
+
+Current status:
+ Windows 10, version 1809 is designated for broad deployment and available for any user who manually selects “Check for updates” via Windows Update. The recommended servicing status is Semi-Annual Channel.
+ |
+
+ "
+
+- items:
+ - type: list
+ style: cards
+ className: cardsM
+ columns: 3
+ items:
+
+ - href: https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-version-1809-designated-for-broad-deployment/ba-p/389540
+ html: Read the announcement >
+ image:
+ src: https://docs.microsoft.com//media/common/i_deploy.svg
+ title: Windows 10, version 1809 designated for broad deployment
+ - href: https://blogs.windows.com/windowsexperience/2019/04/04/improving-the-windows-10-update-experience-with-control-quality-and-transparency
+ html: Find out more >
+ image:
+ src: https://docs.microsoft.com/media/common/i_whats-new.svg
+ title: Improvements to the Windows 10 update experience are coming
+ - href: https://blogs.windows.com/windowsexperience/2019/03/06/data-insights-and-listening-to-improve-the-customer-experience
+ html: Learn about our approach >
+ image:
+ src: https://docs.microsoft.com/media/common/i_investigate.svg
+ title: How do we measure and improve the quality of Windows?
+- items:
+ - type: markdown
+ text: "
+
+ "
+- items:
+ - type: markdown
+ text: "
+
+ "
+
+- title: Known issues
+- items:
+ - type: markdown
+ text: "
+ | Summary | Affected build | Status | Last updated |
+ End-user-defined characters (EUDC) may cause blue screen at startup
If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup.
See details > | OS Build 17763.404
April 02, 2019
KB4490481 | Resolved
KB4493509 | April 09, 2019 10:00 AM PT |
+ Internet Explorer 11 authentication issue with multiple concurrent logons
Internet Explorer 11 users may encounter issues if two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine.
See details > | OS Build 17763.253
January 08, 2019
KB4480116 | Resolved
KB4493509 | April 09, 2019 10:00 AM PT |
+ MSXML6 may cause applications to stop responding
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
See details > | OS Build 17763.253
January 08, 2019
KB4480116 | Resolved
KB4493509 | April 09, 2019 10:00 AM PT |
+ Apps may stop working after selecting an audio output device other than the default
Users with multiple audio devices that select an audio output device different from the \"Default Audio Device\" may find certain applications stop working unexpectedly.
See details > | OS Build 17763.348
March 01, 2019
KB4482887 | Resolved
KB4490481 | April 02, 2019 10:00 AM PT |
+ Custom URI schemes may not start corresponding application
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.
See details > | OS Build 17763.379
March 12, 2019
KB4489899 | Mitigated
| April 02, 2019 10:00 AM PT |
+ Issue using PXE to start a device from WDS
Using PXE to start a device from a WDS server configured to use Variable Window Extension may cause the connection to the WDS server to terminate prematurely.
See details > | OS Build 17763.379
March 12, 2019
KB4489899 | Mitigated
| April 02, 2019 10:00 AM PT |
+ Audio not working on monitors or TV connected to a PC via HDMI, USB, or DisplayPort
Upgrade block: Microsoft has identified issues with certain new Intel display drivers, which accidentally turn on unsupported features in Windows.
See details > | OS Build 17763.134
November 13, 2018
KB4467708 | Mitigated
| March 15, 2019 12:00 PM PT |
+
+ "
+
+- title: Issue Details
+- items:
+ - type: markdown
+ text: "
+
+
+ "
+- title: April 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ | End-user-defined characters (EUDC) may cause blue screen at startup If you enable per font end-user-defined characters (EUDC), the system will stop working and a blue screen may appear at startup. This is not a common setting in non-Asian regions.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016
Workaround: To avoid this issue, don't enable per font EUDC. As an alternative, you can edit the registry to mitigate this issue; for more information, see KB4496149.
Resolved: This issue was resolved in KB4493509.
Back to top | OS Build 17763.404
April 02, 2019
KB4490481 | Resolved
KB4493509 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
April 02, 2019 10:00 AM PT |
+
+ "
+
+- title: March 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Apps may stop working after selecting an audio output device other than the defaultAfter installing KB4482887 on machines that have multiple audio devices, applications that provide advanced options for internal or external audio output devices may stop working unexpectedly. This issue occurs for users that select an audio output device different from the \"Default Audio Device\". Examples of applications that may stop working include:
- Windows Media Player
- Realtek HD Audio Manager
- Sound Blaster Control Panel
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
- Server: Windows Server, version 1809; Windows Server 2019
Workaround: As a temporary solution, select the \"Default Audio Device\" in the options provided by the application; please refer to the application's user manual for details. For example, to set the Default Audio Device in Windows Media Player:
- Open Windows Media Player > Tools > Options > Devices.
- Select the device and choose Properties.
- On the next dialog, from the drop-down menu under Select the Audio Device, choose Default Audio Device from the list.
You can then send audio from the application to the audio device you want in the per-application audio settings found under Settings > System > Sound > App Volume and device preferences.
Resolved: This issue was resolved in KB4490481.
Back to top | OS Build 17763.348
March 01, 2019
KB4482887 | Resolved
KB4490481 | Resolved:
April 02, 2019 10:00 AM PT
Opened:
March 01, 2019 10:00 AM PT |
+ Custom URI schemes may not start corresponding applicationAfter installing KB4489899, 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: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Workaround: Right-click the URL link to open it in a new window or tab, or enable Protected Mode in Internet Explorer for local intranet and trusted sites - Go to Tools > Internet options > Security.
- Within Select a zone to view of change security settings, select Local intranet and then select Enable Protected Mode.
- Select Trusted Sites and then select Enable Protected Mode.
- Select OK.
You must restart the browser after making these changes. Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.
Back to top | OS Build 17763.379
March 12, 2019
KB4489899 | Mitigated
| Last updated:
April 02, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+ Issue using PXE to start a device from WDSAfter installing KB4489899, 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: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10 Enterprise LTSC 2016; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server 2016; Windows Server 2012 R2
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: - Open Windows Deployment Services from Windows Administrative Tools.
- Expand Servers and right-click a WDS server.
- Open its properties and clear the Enable Variable Window Extension box on the TFTP tab.
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 17763.379
March 12, 2019
KB4489899 | Mitigated
| Last updated:
April 02, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+
+ "
+
+- title: January 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Internet Explorer 11 authentication issue with multiple concurrent logonsAfter installing the February 12, 2019 update ( KB4487044), Internet Explorer 11 and other applications that use WININET.DLL may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to: - Cache size and location show zero or empty.
- Keyboard shortcuts may not work properly.
- Webpages may intermittently fail to load or render correctly.
- Issues with credential prompts.
- Issues when downloading files.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolved: This issue was resolved in KB4493509.
Back to top | OS Build 17763.253
January 08, 2019
KB4480116 | Resolved
KB4493509 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ MSXML6 may cause applications to stop responding After installing KB4480116, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode(). The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolved: This issue was resolved in KB4493509.
Back to top | OS Build 17763.253
January 08, 2019
KB4480116 | Resolved
KB4493509 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+
+ "
+
+- title: November 2018
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ | Audio not working on monitors or TV connected to a PC via HDMI, USB, or DisplayPort Upgrade block: Microsoft has identified issues with certain new Intel display drivers. Intel inadvertently released versions of its display driver (versions 24.20.100.6344, 24.20.100.6345) to OEMs that accidentally turned on unsupported features in Windows. As a result, after updating to Windows 10, version 1809, audio playback from a monitor or television connected to a PC via HDMI, USB-C, or a DisplayPort may not function correctly on devices with these drivers.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
- Server: Windows Server, version 1809; Windows Server 2019
Next steps: Intel has released updated drivers to OEM device manufacturers. OEMs need to make the updated driver available via Windows Update.
Note: This Intel display driver issue is different from the Intel Smart Sound Technology driver (version 09.21.00.3755) audio issue previously documented.
Back to top | OS Build 17763.134
November 13, 2018
KB4467708 | Mitigated
| Last updated:
March 15, 2019 12:00 PM PT
Opened:
November 13, 2018 10:00 AM PT |
+
+ "
diff --git a/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml b/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml
new file mode 100644
index 0000000000..3545bba81f
--- /dev/null
+++ b/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml
@@ -0,0 +1,115 @@
+### YamlMime:YamlDocument
+
+documentType: LandingData
+title: Windows 7 and Windows Server 2008 R2 SP1
+metadata:
+ document_id:
+ title: Windows 7 and Windows Server 2008 R2 SP1
+ description: View annoucements and review known issues and fixes for Windows 7 and Windows Server 2008 R2 SP1
+ keywords: Windows 10, issues, fixes, announcements, Windows Server, advisories
+ ms.localizationpriority: high
+ author: greg-lindsay
+ ms.author: greglin
+ manager: dougkim
+ ms.topic: article
+ ms.devlang: na
+
+sections:
+- items:
+ - type: markdown
+ text: "
+ Find information on known issues for Windows 7 and Windows Server 2008 R2 SP1. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s).
+
+ "
+
+- items:
+ - type: list
+ style: cards
+ className: cardsM
+ columns: 3
+ items:
+
+ - href: https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-version-1809-designated-for-broad-deployment/ba-p/389540
+ html: Read the announcement >
+ image:
+ src: https://docs.microsoft.com//media/common/i_deploy.svg
+ title: Windows 10, version 1809 designated for broad deployment
+ - href: https://blogs.windows.com/windowsexperience/2019/04/04/improving-the-windows-10-update-experience-with-control-quality-and-transparency
+ html: Find out more >
+ image:
+ src: https://docs.microsoft.com/media/common/i_whats-new.svg
+ title: Improvements to the Windows 10 update experience are coming
+ - href: https://blogs.windows.com/windowsexperience/2019/03/06/data-insights-and-listening-to-improve-the-customer-experience
+ html: Learn about our approach >
+ image:
+ src: https://docs.microsoft.com/media/common/i_investigate.svg
+ title: How do we measure and improve the quality of Windows?
+- items:
+ - type: markdown
+ text: "
+
+ "
+- items:
+ - type: markdown
+ text: "
+
+ "
+
+- title: Known issues
+- items:
+ - type: markdown
+ text: "
+ | Summary | Affected build | Status | Last updated |
+ Virtual machines fail to restore.
Virtual machines (VMs) may fail to restore successfully if the VM has been saved and restored once before.
See details > | January 08, 2019
KB4480970 | Resolved
KB4490511 | April 21, 2019 12:00 AM PT |
+ Local Administrators unable to remotely access shares.
Local users who are part of the local Administrators group may not be able to remotely access shares on Windows Server 2008 R2 and Windows 7 machines.
See details > | January 08, 2019
KB4480970 | Resolved
KB4487345 | April 20, 2019 11:53 PM PT |
+ Internet Explorer 11 authentication issue with multiple concurrent logons.
Internet Explorer 11 users may encounter issues if two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine.
See details > | January 08, 2019
KB4480970 | Resolved
KB4493472 | April 09, 2019 10:00 AM PT |
+ Custom URI schemes may not start corresponding application.
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.
See details > | March 12, 2019
KB4489878 | Resolved
KB4493472 | April 09, 2019 10:00 AM PT |
+ NETDOM.EXE fails to run.
NETDOM.EXE fails to run and the error, “The command failed to complete successfully.” appears on screen.
See details > | March 12, 2019
KB4489878 | Resolved
KB4493472 | April 09, 2019 10:00 AM 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 | Mitigated
| April 09, 2019 10:00 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 | Mitigated
| April 09, 2019 10:00 AM 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 | Investigating
| April 09, 2019 10:00 AM PT |
+ System may be unresponsive after restart if ArcaBit antivirus software installed.
Devices with ArcaBit antivirus software installed may become unresponsive upon restart.
See details > | April 09, 2019
KB4493472 | Mitigated
| April 09, 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 09, 2019 10:00 AM PT |
+
+ "
+
+- title: Issue Details
+- items:
+ - type: markdown
+ text: "
+
+
+ "
+- title: April 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ System unresponsive after restart if Sophos Endpoint Protection installed.Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing KB4493472.
Microsoft has temporarily blocked devices from receiving this update if the Sophos Endpoint is installed until a solution is available.
Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.
Back to top | April 09, 2019
KB4493472 | Mitigated
| Last updated:
April 09, 2019 10:00 AM PT
Opened:
April 09, 2019 10:00 AM PT |
+ System may be unresponsive after restart if Avira antivirus software installed.Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493472.
Microsoft has temporarily blocked devices from receiving this update if Avira antivirus software is installed.
Next steps: We are presently investigating this issue with Avira and will provide an update when available.
Back to top | April 09, 2019
KB4493472 | Investigating
| Last updated:
April 09, 2019 10:00 AM PT
Opened:
April 09, 2019 10:00 AM PT |
+ System may be unresponsive after restart if ArcaBit antivirus software installed.Microsoft and ArcaBit have identified an issue on devices with ArcaBit antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493472.
Microsoft has temporarily blocked devices from receiving this update if ArcaBit antivirus software is installed.
ArcaBit has released an update to address this issue. For more information, see the Arcabit support article.
Back to top | April 09, 2019
KB4493472 | Mitigated
| Last updated:
April 09, 2019 10:00 AM PT
Opened:
April 09, 2019 10:00 AM PT |
+ Devices may not respond at login or Welcome screen if running certain Avast software.Microsoft and Avast have identified an issue on devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software after you install KB4493472 and restart. Devices may become unresponsive at the login or Welcome screen. Additionally, you may be unable to log in or log in after an extended period of time.
Affected platforms: - Client: Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: Avast has released emergency updates to address this issue. For more information and AV update schedule, see the Avast support KB article.
Back to top | April 09, 2019
KB4493472 | Resolved
| Resolved:
April 09, 2019 10:00 AM PT
Opened:
April 09, 2019 10:00 AM PT |
+
+ "
+
+- title: March 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Custom URI schemes may not start corresponding application.After installing KB4489878, custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites on Internet Explorer.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4493472.
Back to top | March 12, 2019
KB4489878 | Resolved
KB4493472 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+ NETDOM.EXE fails to run.After installing KB4489878, NETDOM.EXE fails to run, and the on-screen error, “The command failed to complete successfully.” appears.
Affected platforms: - Client: Windows 7, Service Pack 1
- Server: Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4493472.
Back to top | March 12, 2019
KB4489878 | Resolved
KB4493472 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+ Authentication may fail for services after the Kerberos ticket expires.After installing KB4489878, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). For example, the SQL server service fails.
Workaround: To mitigate this issue, use one of the following options:
- Option 1: Purge the Kerberos tickets on the application server. After the Kerberos ticket expires, the issue will occur again, and you must purge the tickets again.
- Option 2: If purging does not mitigate the issue, restart the application; for example, restart the Internet Information Services (IIS) app pool associated with the SQL server.
- Option 3: Use constrained delegation.
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.
Back to top | March 12, 2019
KB4489878 | Mitigated
| Last updated:
April 09, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+
+ "
+
+- title: January 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Virtual machines fail to restore.After installing KB4480970, virtual machines (VM) may fail to restore successfully if the VM has been saved and restored once before. The error message is, “Failed to restore the virtual machine state: Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine. (0xC0370027).”
This affects AMD Bulldozer Family 15h, AMD Jaguar Family 16h, and AMD Puma Family 16h (second generation) microarchitectures.
Affected platforms: - Client: Windows 7, Service Pack 1
- Server: Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4490511.
Back to top | January 08, 2019
KB4480970 | Resolved
KB4490511 | Resolved:
February 19, 2019 02:00 PM PT
Opened:
January 08, 2019 10:00 AM PT |
+ Local Administrators unable to remotely access shares.Local users who are part of the local Administrators group may not be able to remotely access shares on Windows Server 2008 R2 and Windows 7 machines after installing KB4480970. This does not affect domain accounts in the local Administrators group. Affected platforms: - Client: Windows 7, Service Pack 1
- Server: Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487345.
Back to top | January 08, 2019
KB4480970 | Resolved
KB4487345 | Resolved:
January 11, 2019 02:00 PM PT
Opened:
January 08, 2019 10:00 AM PT |
+ Internet Explorer 11 authentication issue with multiple concurrent logons.After installing KB4480970, Internet Explorer 11 and other applications that use WININET.DLL may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to:
- Cache size and location show zero or empty.
- Keyboard shortcuts may not work properly.
- Webpages may intermittently fail to load or render correctly.
- Issues with credential prompts.
- Issues when downloading files.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4493472.
Back to top | January 08, 2019
KB4480970 | Resolved
KB4493472 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+
+ "
diff --git a/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml b/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml
new file mode 100644
index 0000000000..07b6ceef12
--- /dev/null
+++ b/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml
@@ -0,0 +1,123 @@
+### YamlMime:YamlDocument
+
+documentType: LandingData
+title: Windows 8.1 and Windows Server 2012 R2
+metadata:
+ document_id:
+ title: Windows 8.1 and Windows Server 2012 R2
+ description: View annoucements and review known issues and fixes for Windows 8.1 and Windows Server 2012 R2
+ keywords: Windows 10, issues, fixes, announcements, Windows Server, advisories
+ ms.localizationpriority: high
+ author: greg-lindsay
+ ms.author: greglin
+ manager: dougkim
+ ms.topic: article
+ ms.devlang: na
+
+sections:
+- items:
+ - type: markdown
+ text: "
+ Find information on known issues for Windows 8.1 and Windows Server 2012 R2. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s).
+
+ "
+
+- items:
+ - type: list
+ style: cards
+ className: cardsM
+ columns: 3
+ items:
+
+ - href: https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-version-1809-designated-for-broad-deployment/ba-p/389540
+ html: Read the announcement >
+ image:
+ src: https://docs.microsoft.com//media/common/i_deploy.svg
+ title: Windows 10, version 1809 designated for broad deployment
+ - href: https://blogs.windows.com/windowsexperience/2019/04/04/improving-the-windows-10-update-experience-with-control-quality-and-transparency
+ html: Find out more >
+ image:
+ src: https://docs.microsoft.com/media/common/i_whats-new.svg
+ title: Improvements to the Windows 10 update experience are coming
+ - href: https://blogs.windows.com/windowsexperience/2019/03/06/data-insights-and-listening-to-improve-the-customer-experience
+ html: Learn about our approach >
+ image:
+ src: https://docs.microsoft.com/media/common/i_investigate.svg
+ title: How do we measure and improve the quality of Windows?
+- items:
+ - type: markdown
+ text: "
+
+ "
+- items:
+ - type: markdown
+ text: "
+
+ "
+
+- title: Known issues
+- items:
+ - type: markdown
+ text: "
+ | Summary | Affected build | Status | Last updated |
+ Internet Explorer 11 authentication issue with multiple concurrent logons
Internet Explorer 11 users may encounter issues if two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine.
See details > | January 08, 2019
KB4480963 | Resolved
KB4493446 | April 09, 2019 10:00 AM PT |
+ MSXML6 may cause applications to stop responding.
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
See details > | January 08, 2019
KB4480963 | Resolved
KB4493446 | April 09, 2019 10:00 AM PT |
+ Custom URI schemes may not start corresponding application
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.
See details > | March 12, 2019
KB4489881 | Resolved
KB4493446 | April 09, 2019 10:00 AM PT |
+ Issue using PXE to start a device from WDS
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.
See details > | March 12, 2019
KB4489881 | Mitigated
| April 09, 2019 10:00 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
KB4493446 | Mitigated
| April 09, 2019 10:00 AM 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
KB4493446 | Investigating
| April 09, 2019 10:00 AM PT |
+ System may be unresponsive after restart if ArcaBit antivirus software installed
Devices with ArcaBit antivirus software installed may become unresponsive upon restart.
See details > | April 09, 2019
KB4493446 | Mitigated
| April 09, 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
KB4493446 | Resolved
| April 09, 2019 10:00 AM PT |
+ Certain operations performed on on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”.
See details > | April 09, 2019
KB4493446 | Mitigated
| April 09, 2019 10:00 AM PT |
+ Embedded objects may display incorrectly
Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly.
See details > | February 12, 2019
KB4487000 | Resolved
KB4493446 | April 09, 2019 10:00 AM PT |
+
+ "
+
+- title: Issue Details
+- items:
+ - type: markdown
+ text: "
+
+
+ "
+- title: April 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ System unresponsive after restart if Sophos Endpoint Protection installedMicrosoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing KB4493446.
Microsoft has temporarily blocked devices from receiving this update if the Sophos Endpoint is installed until a solution is available.
Affected platforms: - Client: Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1
Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.
Back to top | April 09, 2019
KB4493446 | Mitigated
| Last updated:
April 09, 2019 10:00 AM PT
Opened:
April 09, 2019 10:00 AM PT |
+ System may be unresponsive after restart if Avira antivirus software installedMicrosoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493446.
Microsoft has temporarily blocked devices from receiving this update if Avira antivirus software is installed.
Affected platforms: - Client: Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1
Next steps: We are presently investigating this issue with Avira and will provide an update when available.
Back to top | April 09, 2019
KB4493446 | Investigating
| Last updated:
April 09, 2019 10:00 AM PT
Opened:
April 09, 2019 10:00 AM PT |
+ System may be unresponsive after restart if ArcaBit antivirus software installedMicrosoft and ArcaBit have identified an issue on devices with ArcaBit antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493446.
Microsoft has temporarily blocked devices from receiving this update if ArcaBit antivirus software is installed.
Affected platforms: - Client: Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1
Back to top | April 09, 2019
KB4493446 | Mitigated
| Last updated:
April 09, 2019 10:00 AM PT
Opened:
April 09, 2019 10:00 AM PT |
+ Devices may not respond at login or Welcome screen if running certain Avast softwareMicrosoft and Avast have identified an issue on devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software after you install KB4493446 and restart. Devices may become unresponsive at the login or Welcome screen. Additionally, you may be unable to log in or log in after an extended period of time.
Affected platforms: - Client: Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: Avast has released emergency updates to address this issue. For more information and AV update schedule, see the Avast support KB article.
Back to top | April 09, 2019
KB4493446 | Resolved
| Resolved:
April 09, 2019 10:00 AM PT
Opened:
April 09, 2019 10:00 AM PT |
+ | Certain operations performed on on a Cluster Shared Volume may fail Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Affected platforms: - Client: Windows 8.1
- Server: Windows Server 2012 R2
Workaround: Do one of the following:
- Perform the operation from a process that has administrator privilege.
- Perform the operation from a node that doesn’t have CSV ownership.
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.
Back to top | April 09, 2019
KB4493446 | Mitigated
| Last updated:
April 09, 2019 10:00 AM PT
Opened:
April 09, 2019 10:00 AM PT |
+
+ "
+
+- title: March 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Custom URI schemes may not start corresponding applicationAfter installing KB4489881, 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: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4493446.
Back to top | March 12, 2019
KB4489881 | Resolved
KB4493446 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+ Issue using PXE to start a device from WDSAfter installing KB4489881, 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: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10 Enterprise LTSC 2016; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server 2016; Windows Server 2012 R2
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:
1. Open Windows Deployment Services from Windows Administrative Tools. 2. Expand Servers and right-click a WDS server. 3. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab.
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 | March 12, 2019
KB4489881 | Mitigated
| Last updated:
April 09, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+
+ "
+
+- title: February 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ | Embedded objects may display incorrectly Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly.
For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color.
Affected platforms: - Client: Windows 8.1
- Server: Windows Server 2012 R2
Resolution: This issue is resolved in KB4493446.
Back to top | February 12, 2019
KB4487000 | Resolved
KB4493446 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
February 12, 2019 10:00 AM PT |
+
+ "
+
+- title: January 2019
+- items:
+ - type: markdown
+ text: "
+ | Details | Affected build | Status | History |
+ Internet Explorer 11 authentication issue with multiple concurrent logonsAfter installing KB4480963, Internet Explorer 11 and other applications that use WININET.DLL may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to:
- Cache size and location show zero or empty.
- Keyboard shortcuts may not work properly.
- Webpages may intermittently fail to load or render correctly.
- Issues with credential prompts.
- Issues when downloading files.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4493446.
Back to top | January 08, 2019
KB4480963 | Resolved
KB4493446 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ MSXML6 may cause applications to stop responding.After installing KB4480963, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.
Resolution: This issue is resolved in KB4493446.
Back to top | January 08, 2019
KB4480963 | Resolved
KB4493446 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+
+ "
diff --git a/windows/release-information/windows-message-center.yml b/windows/release-information/windows-message-center.yml
new file mode 100644
index 0000000000..3c85070b12
--- /dev/null
+++ b/windows/release-information/windows-message-center.yml
@@ -0,0 +1,94 @@
+### YamlMime:YamlDocument
+
+documentType: LandingData
+title: Windows 10 message center
+metadata:
+ document_id:
+ title: Windows 10 message center
+ description: Windows 10 message center
+ keywords: Windows 10, issues, fixes, announcements, Windows Server, advisories
+ ms.localizationpriority: high
+ author: greg-lindsay
+ ms.author: greglin
+ manager: dougkim
+ ms.topic: article
+ ms.devlang: na
+
+sections:
+
+- items:
+ - type: list
+ style: cards
+ className: cardsM
+ columns: 2
+ items:
+
+ - href: https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-version-1809-designated-for-broad-deployment/ba-p/389540
+ html: Read the announcement >
+ image:
+ src: https://docs.microsoft.com//media/common/i_deploy.svg
+ title: Windows 10, version 1809 designated for broad deployment
+ - href: https://blogs.windows.com/windowsexperience/2019/04/04/improving-the-windows-10-update-experience-with-control-quality-and-transparency
+ html: Find out more >
+ image:
+ src: https://docs.microsoft.com/media/common/i_whats-new.svg
+ title: Improvements to the Windows 10 update experience are coming
+ - href: https://blogs.windows.com/windowsexperience/2019/03/06/data-insights-and-listening-to-improve-the-customer-experience
+ html: Learn about our approach >
+ image:
+ src: https://docs.microsoft.com/media/common/i_investigate.svg
+ title: How do we measure and improve the quality of Windows?
+ - href: https://docs.microsoft.com/windows/windows-10/release-information
+ html: Visit the Windows 10 release information page >
+ image:
+ src: https://docs.microsoft.com/media/common/i_download-monitor.svg
+ title: Find a list of currently supported versions and previous releases
+
+- title: Recent announcements
+- items:
+ - type: markdown
+ text: "
+ | Message | Date |
+
+ The benefits of Windows 10 Dynamic Update
Dynamic Update can help organizations and end users alike ensure that their Windows 10 devices have the latest feature update content (as part of an in-place upgrade)—and preserve precious features on demand (FODs) and language packs (LPs) that may have been previously installed.
+
+Find out which components are updated by Dynamic Update, how Dynamic Update is initiated, and how to enable or disable it. | April 17, 2019 11: 26 AM PT |
+ Improvements to the Windows 10 update experience are coming
Find out about the changes coming to the Windows update process that will improve the experience, offer users more control, and improve the quality of Windows updates. | April 04, 2019 09: 00 AM PT |
+ Take action: review your Windows Update for Business deferral values
If devices under your management are still running Windows 10 Pro or Windows 10 Pro for Workstations, version 1709, your devices will reach end of service on April 9, 2019 if you have configured both of the following Windows Update for Business policies:
+
+- Branch readiness is configured as Semi-Annual Channel (SAC)
+- Feature update deferral is configured as 274 days or more
+
+In order avoid this, you need to set your feature update deferral policy to 273 days or less. | April 03, 2019 05: 47 PM PT |
+ Find a list of currently supported versions and previous releases
Every Windows product has a lifecycle. The lifecycle begins when a product is released and ends when it is no longer serviced or supported. Knowing key dates in this lifecycle helps you make informed decisions about when to update, upgrade, or make other changes to your software. Check out the updated Windows 10 release information page for a list of current versions by servicing option as well as end of service dates. | March 28, 2019 02: 00 PM PT |
+ Windows 10, version 1809 designated for broad deployment
Based on the data and the feedback we’ve received from consumers, OEMs, ISVs, partners, and commercial customers, Windows 10, version 1809 has transitioned to broad deployment. With this, the Windows 10 release information page will now reflect Semi-Annual Channel (SAC) for version 1809. | March 28, 2019 10: 00 AM PT |
+ How do we measure and improve the quality of Windows?
We rely heavily on feedback and data to detect and fix potential issues before we release new updates to the general population. Explore some of the practices we’ve developed during the last few years to measure and improve the quality of Windows. | March 06, 2019 10: 23 AM PT |
+ Data, insights and listening to improve the customer experience
Measuring the quality of Windows is a complex undertaking that requires gathering a variety of diagnostic signals from millions of devices within the Windows ecosystem. In addition to rigorous internal testing, we rely heavily on the feedback provided through diagnostic data to detect and fix problems before we release new updates of Windows to the general population, and to monitor the impact of those updates after each release.
+
+Get insight into some of the practices we employ to measure and improve the quality of Windows. | March 06, 2019 10: 23 AM PT |
+ Getting to know the Windows update history pages
Windows Update customers were affected by a network infrastructure event on January 29, 2019 (21:00 UTC), caused by an external DNS service provider’s global outage. A software update to the external provider’s DNS servers resulted in the distribution of corrupted DNS records that affected connectivity to the Windows Update service. The DNS records were restored by January 30, 2019 (00:10 UTC), and the majority of local Internet Service Providers (ISP) have refreshed their DNS servers and customer services have been restored.
+
+While this was not an issue with Microsoft’s services, we take any service disruption for our customers seriously. We will work with partners to better understand this so we can provide higher quality service in the future even across diverse global network providers.
+
+If you are still unable to connect to Windows Update services due to this problem, please contact your local ISP or network administrator. You can also refer to our new KB4493784 for more information to determine if your network is affected, and to provide your local ISP or network administrator with additional information to assist you. | February 21, 2019 06: 37 PM PT |
+ Share your feedback: Windows update history
We read every comment you leave on our update history pages, and are always looking to improve these pages and the monthly knowledge base (KB) articles that accompany each monthly update. Take our survey and let us know how we can improve our transparency further and make these more compelling and useful to you and your organization. | February 21, 2019 12: 00 PM PT |
+ Plan for change: Windows Update for Business and the retirement of SAC-T
Beginning with Windows 10, version 1903 (the next feature update for Windows 10), the Windows 10 release information page will no longer list SAC-T information for version 1903 and future feature updates. Instead, you will find a single entry for each new SAC release. In addition, if you are using Windows Update for Business, you will see new UI and behavior to reflect that there is only one release date for each SAC release. If you use System Center Configuration Manager, Windows Server Update Services (WSUS), or other management tools, there will now only be one feature update published to WSUS, and this will occur at the time of release. Learn how this change will affect Windows Business for Update customers. | February 14, 2019 12: 00 PM PT |
+ Champs corner: Classifying Windows updates in common deployment tools
If you utilize automated update deployment tools, such as Windows Server Update Services (WSUS) or System Center Configuration Manager, you likely use automatic rules to streamline the approval and deployment of Windows updates. Using the correct update classification is, therefore, an important component of your organization’s device update process. Explore the options available and how to approach it in a WSUS or Configuration Manager environment. | February 05, 2019 10: 34 AM PT |
+ Global DNS outage affecting Windows Update customers
Windows Update customers were affected by a network infrastructure event on January 29, 2019 (21:00 UTC), caused by an external DNS service provider’s global outage. A software update to the external provider’s DNS servers resulted in the distribution of corrupted DNS records that affected connectivity to the Windows Update service. The DNS records were restored by January 30, 2019 (00:10 UTC), and the majority of local Internet Service Providers (ISP) have refreshed their DNS servers and customer services have been restored.
+
+While this was not an issue with Microsoft’s services, we take any service disruption for our customers seriously. We will work with partners to better understand this so we can provide higher quality service in the future even across diverse global network providers.
+
+If you are still unable to connect to Windows Update services due to this problem, please contact your local ISP or network administrator. You can also refer to our new KB4493784 for more information to determine if your network is affected, and to provide your local ISP or network administrator with additional information to assist you. | January 29, 2019 04: 15 PM PT |
+ Application compatibility in the Windows ecosystem
Our application ecosystem is incredibly diverse, encompassing tens of millions of applications (apps) with numerous versions, languages, architectures, services and configuration options. While our ecosystem is complex, our vision is simple. All apps on Windows devices should just work! Explore the various programs and technologies we use to improve application compatibility. | January 15, 2019 10: 00 AM PT |
+ Modern desktop servicing: the year in review
2018 was a pivotal year for the modern desktop and the servicing transformation journey we have been taking with you and your organization. In this post, John Wilcox takes a look back and recaps the progress that has been made, highlighting significant events, and provideing nsight into what 2019 has in store. | December 19, 2018 02: 20 PM PT |
+ Driver quality in the Windows ecosystem
Ensuring Windows 10 works great with all the devices and accessories our customers use is a top priority. We work closely with this broad mix of partners to test new drivers, monitor health characteristics over time, and make Windows and our ecosystem more resilient architecturally. Our goal is to ensure that all the updates and drivers we deliver to non-Insider populations are validated and at production quality (including monthly optional releases) before pushing drivers broadly to all. Explore the driver distribution chain and learn how we measure driver quality and prevent conflicts. | December 19, 2018 10: 04 AM PT |
+ Introducing the Modern Desktop podcast series
In this new podcast series, we'll explore the good, the bad, and, yes, the ugly of servicing and delivery for Windows 10 and Office 365 ProPlus. We'll talk about modern desktop management through Enterprise Mobility, security, and cloud-attached and co-managed environments. Listen to the first episode, in which we discuss monthly quality updates fpr Windows 10, the Microsoft 365 Stay Current pilot program, and interview a real customer to see how they ingest monthly updates in their organization. | December 18, 2018 01: 00 PM PT |
+ Measuring Delivery Optimization and its impact to your network
If you've familiarized yourself with the configuration options for Delivery Optimization in Windows 10, and have started to configure the settings you feel will be the best fit for your organization’s network topology, now is the time to see how well those settings are working. This article provides tips on how evaluate performance at the device level or organization level. | December 13, 2018 03: 48 PM PT |
+ Windows monthly security and quality updates overview
Today’s global cybersecurity threats are both dynamic and sophisticated, and new vulnerabilities are discovered almost every day. We focus on protecting customers from these security threats by providing security updates on a timely basis and with high quality. Find out how how we deliver these critical updates on a massive scale as a key component of our ongoing Windows as a service effort. | December 10, 2018 10: 00 AM PT |
+ LTSC: What is it, and when should it be used?
With the Semi-Annual Channel, devices receive two feature updates per year, and benefit from the best performance, user experience, security, and stability. This servicing option continues to be our recommendation for managing Windows 10 updates; however, we acknowledge that certain devices and use cases (e.g. medical systems and industrial process controllers) dictate that functionality and features don’t change over time. Find out how we designed the Long-Term Servicing Channel (LTSC) with these types of use cases in mind, and what is offered through the LTSC. | November 29, 2018 07: 02 PM PT |
+ Plan for change: Local Experience Packs: What are they and when should you use them?
When we released Windows 10, version 1803, we introduced Local Experience Packs (LXPs), which are modern language packs delivered through the Microsoft Store or Microsoft Store for Business. Learn about the biggest advantage to LXPs, and the retirement of legacy language packs (lp.cab) for all Language Interface Packs (LIP). | November 14, 2018 11: 10 AM PT |
+ Windows 10 Quality approach for a complex ecosystem
While our measurements of quality show improving trends on aggregate for each successive Windows 10 release, if a single customer experiences an issue with any of our updates, we take it seriously. In this blog post, Windows CVP Mike Fortin shares an overview of how we work to continuously improve the quality of Windows and our Windows as a service approach. This blog will be the first in a series of more in-depth explanations of the work we do to deliver quality in our Windows releases. | November 13, 2018 10: 00 AM PT |
+ Windows 10, version 1809 rollout resumes; now available on VLSC
Today we are resuming the rollout of the latest Windows 10 feature update—Windows 10, version 1809—via the Software Download Center (via Update Assistant or the Media Creation Tool), Windows Server Update Services (WSUS), and Windows Update for Business. Windows 10, version 1809 is also now available on the Volume Licensing Service Center (VLSC). | November 13, 2018 10: 00 AM PT |
+ Express updates for Windows Server 2016 re-enabled for November 2018 update
Starting with the November 13, 2018 Update Tuesday release, Windows will again publish Express updates for Windows Server 2016. That means that system administrators for WSUS and System Center Configuration Manager will once again see two packages for the Windows Server 2016 update: a Full update and an Express update. Read this article for more details. | November 12, 2018 03: 00 PM PT |
+
+ "
diff --git a/windows/security/information-protection/bitlocker/prepare-your-organization-for-bitlocker-planning-and-policies.md b/windows/security/information-protection/bitlocker/prepare-your-organization-for-bitlocker-planning-and-policies.md
index 86ebe29111..72fd992131 100644
--- a/windows/security/information-protection/bitlocker/prepare-your-organization-for-bitlocker-planning-and-policies.md
+++ b/windows/security/information-protection/bitlocker/prepare-your-organization-for-bitlocker-planning-and-policies.md
@@ -13,7 +13,7 @@ manager: dansimp
audience: ITPro
ms.collection: M365-security-compliance
ms.topic: conceptual
-ms.date: 04/17/2019
+ms.date: 04/24/2019
---
# Prepare your organization for BitLocker: Planning and policies
@@ -201,8 +201,8 @@ However, you cannot use recovery passwords generated on a system in FIPS mode fo
## More information
-- [Trusted Platform Module](/windows/security/hardware-protection/tpm/trusted-platform-module-overview.md)
-- [TPM Group Policy settings](/windows/security/hardware-protection/tpm/trusted-platform-module-services-group-policy-settings.md)
+- [Trusted Platform Module](https://docs.microsoft.com/windows/security/information-protection/tpm/trusted-platform-module-top-node)
+- [TPM Group Policy settings](https://docs.microsoft.com/windows/security/information-protection/tpm/trusted-platform-module-services-group-policy-settings)
- [BitLocker frequently asked questions (FAQ)](bitlocker-frequently-asked-questions.md)
- [BitLocker](bitlocker-overview.md)
- [BitLocker Group Policy settings](bitlocker-group-policy-settings.md)