Download windows 10 1809 từ microsoft
If you downloaded an ISO file for Windows 10, the file is saved locally at the location you selected. If you have a third-party DVD burning program installed on your computer that you prefer to use for creating the installation DVD, that program might open by going to the location where the file is saved and double-clicking the ISO file, or right-click the ISO file, select Open with and choose your preferred DVD burning software. Show If you want to use the Windows Disk Image Burner to create an installation DVD, go to the location where the ISO file is saved. Right-click the ISO file and select Properties. On the General tab, click Change and select Windows Explorer for the program you would like to use to open ISO files and select Apply. Then right-click the ISO file and select Burn disc image. If you want to install Windows 10 directly from the ISO file without using a DVD or flash drive, you can do so by mounting the ISO file. This will perform an upgrade of your current operating system to Windows 10. To mount the ISO file:
Skip to main content This browser is no longer supported. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Windows 10, version 1809 and Windows Server 2019
In this articleFind information on known issues 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). Want the latest Windows release health updates? Follow @WindowsUpdate on Twitter. Current status as of May 11, 2021: As of May 11, 2021, all editions of Windows 10, version 1809 and Windows Server 2019 have reached end of servicing, except LTSC editions. Devices running these editions will no longer receive monthly security and quality updates containing protections from the latest security threats. As always, we recommend that you update your devices to the latest version of Windows 10 as soon as possible to ensure that you can take advantage of the latest features and advanced protections from the latest security threats. For information about servicing timelines and lifecycle, see the Windows 10 release information and Lifecycle FAQ - Windows. Known issuesThis table offers a summary of current active issues and those issues that have been resolved in the last 30 days.
Issue detailsNovember 2022Sign in failures and other issues related to Kerberos authentication
Updated November 18, 2022: Added update information for Windows Server 2008 R2 SP1. After installing updates released on November 8, 2022 or later on Windows Servers with the Domain Controller role, you might have issues with Kerberos authentication. This issue might affect any Kerberos authentication in your environment. Some scenarios which might be affected:
When this issue is encountered you might receive a Microsoft-Windows-Kerberos-Key-Distribution-Center Event ID 14 error event in the System section of Event Log on your Domain Controller with the below text. Note: affected events will have "the missing key has an ID of 1": While processing an AS request for target service Note: This issue is not an expected part of the security hardening for Netlogon and Kerberos starting with November 2022 security update. You will still need to follow the guidance in these articles even after this issue is resolved. Windows devices used at home by consumers or devices which are not part of a on premises domain are not affected by this issue. Azure Active Directory environments that are not hybrid and do not have any on premises Active Directory servers are not affected. Resolution: This issue was resolved in out-of-band updates released November 17, 2022 and November 18, 2022 for installation on all the Domain Controllers (DCs) in your environment. You do not need to install any update or make any changes to other servers or client devices in your environment to resolve this issue. If you used any workaround or mitigations for this issue, they are no longer needed, and we recommend you remove them. To get the standalone package for these out-of-band updates, search for the KB number in the Microsoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, see WSUS and the Catalog Site. For Configuration Manger instructions, see Import updates from the Microsoft Update Catalog. Note The below updates are not available from Windows Update and will not install automatically. Cumulative updates:
Note: You do not need to apply any previous update before installing these cumulative updates. If you have already installed updates released November 8, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above. Standalone Updates:
Note: If you are using security only updates for these versions of Windows Server, you only need to install these standalone updates for the month of November 2022. Security only updates are not cumulative, and you will also need to install all previous Security only updates to be fully up to date. Monthly rollup updates are cumulative and include security and all quality updates. If you are using Monthly rollup updates, you will need to install both the standalone updates listed above to resolve this issue, and install the Monthly rollups released November 8, 2022 to receive the quality updates for November 2022. If you have already installed updates released November 8, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above. Affected platforms:
Direct Access might be unable to reconnect after your device has connectivity issues
After installing KB5019966 or later updates, you might be unable to reconnect to Direct Access after temporarily losing network connectivity or transitioning between Wi-Fi networks or access points. Note: This issue should not affect other remote access solutions such as VPN (sometimes called Remote Access Server or RAS) and Always On VPN (AOVPN). Windows devices used at home by consumers or devices in organizations which are not using Direct Access to remotely access the organization's network resources are not affected. Workaround: You can mitigate this issue by restarting your Windows device. Next steps: We are working on a resolution and will provide an update in an upcoming release. Affected platforms:
October 2022Possible issues caused by Daylight Savings Time change in Jordan
On October 5, 2022, the Jordanian government made an official announcement ending the winter-time Daylight Saving Time (DST) time zone change. Starting at 12:00 a.m. Friday, October 28, 2022, the official time will not advance by an hour and will permanently shift to the UTC + 3 time zone. The impact of this change is as follows:
Symptoms if no update is installed and the workaround is not used on devices in the Jordan time zone on October 28, 2022 or later:
Workaround: You can mitigate this issue on devices in Jordan by doing either of the following on October 28, 2022, if an update is not available to resolve this issue for your version of Windows:
Important: We recommend using ONLY the above workaround to mitigate the issue with time created by the new Daylight Savings Time in Jordan. We do NOT recommend using any other workaround, as they can create inconsistent results and might create serious issues if done incorrectly. Resolution: This issue was resolved in KB5019966. Affected platforms:
Domain join processes may fail with error "0xaac (2732)"
Domain join operations might intentionally fail with error "0xaac (2732): NERR_AccountReuseBlockedByPolicy" and text "An account with the same name exists in Active Directory. Re-using the account was blocked by security policy." This issue originates with the October 2022 security updates ( KB5018419) which introduced some hardening changes enabled by default for domain join. Please see KB5020276 - Netjoin: Domain join hardening changes to understand the new designed behavior. Affected scenarios include some domain join or re-imaging operations where a computer account was created or pre-staged by a different identity than the identity used to join or re-join the computer to the domain. Home users of Windows are unlikely to experience this issue. Next steps: Please see KB5020276 to understand the designed behavior. We have added insights to this KB, and are evaluating whether optimizations can be made in a future Windows Update. This guidance will be updated once those changes have released. Affected platforms:
September 2022The September 2022 preview release is listed in Windows Server Update Services
IT administrators who utilize Windows Server Update Services (WSUS) might notice that the Windows September 2022 preview update, known as the 'C' release, is listed among the updates available from WSUS. This listing is an error. Preview updates are generally available for manual importing via the Microsoft Update Catalog and Windows Updates. This issue might also affect the installation of the September 2022 Cumulative Update Preview for .NET Framework, which is also generally available via Windows Update and Microsoft Update Catalog. For more information on .NET Framework September 2022 Cumulative Update Preview updates, see the KB articles listed on the .NET blog for the September 2022 Cumulative Update Preview. Home users of Windows are unlikely to experience this issue. WSUS is commonly utilized by technology administrators to deploy Microsoft product updates in managed environments. Workaround: The Windows September 2022 preview release was made available via Microsoft Update Catalog. We recommend IT administrators to use this release channel moving forward. Please note: In environments where WSUS is configured to auto-approve updates and also auto-decline superseded content, the Windows September 2022 Security update may subsequently be auto-declined and auto-expired from the client view. If this occurs, see the guidance for reinstating declined updates. Then run an update synchronization within Microsoft Endpoint Configuration Manager, or update management environments. Environments configured to only take security updates should not reflect these symptoms. Resolution: The Windows September 2022 preview releasewas removed from WSUS. We recommend IT administrators use the Microsoft Update Catalog to download and install updates in their environments. As always, we recommend the installation of the latest Windows security updates for all devices (the October 2022 security monthly release, KB5018419, or later). Affected platforms:
August 2022Update might fail to install and you might receive a 0x800f0922 error
When attempting to install KB5012170, it might fail to install, and you might receive an error 0x800f0922. Note: This issue only affects the Security update for Secure Boot DBX ( KB5012170) and does not affect the latest cumulative security updates, monthly rollups, or security only updates released on August 9, 2022. Workaround: This issue can be mitigated on some devices by updating the UEFI bios to the latest version before attempting to install KB5012170. Next steps: We are presently investigating and will provide an update in an upcoming release. Affected platforms:
February 2022Certain apps or devices might be unable to create Netlogon secure channel connections
After installing KB5009557 or any updates released January 11, 2022 and later on your domain controllers, scenarios which rely on Read-only domain controllers (RODCs) or synthetic RODC machine accounts might fail to establish a Netlogon secure channel. RODC accounts must have a linked and compliant KRBTGT account to successfully establish a secure channel. Affected applications or network appliances, such as Riverbed SteelHead WAN Optimizers, might have issues joining domains or limitations after joining a domain. Next Steps: Affected apps and network appliances will need an update from their developer or manufacturer to resolve this issue. Microsoft and Riverbed are presently investigating and will provide an update when more information is available. Affected platforms:
Apps that acquire or set Active Directory Forest Trust Information might have issues
After installing updates released January 11, 2022 or later, apps using Microsoft .NET Framework to acquire or set Active Directory Forest Trust Information might fail, close, or you might receive an error from the app or Windows. You might also receive an access violation (0xc0000005) error. Note for developers: Affected apps use the System.DirectoryServices API. Next Steps: This issue was resolved in the out-of-band update for the version of .NET Framework used by the app. Note: These out-of-band updates are not available from Windows Update and will not install automatically. To get the standalone package, search for the KB number for your version of Windows and .NET Framework in the Microsoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, see WSUS and the Catalog Site. For Configuration Manger instructions, see Import updates from the Microsoft Update Catalog. For instructions on how to install this update for your operating system, see the KB articles listed below:
Affected platforms:
December 2021Windows 10 Enterprise might not activate via KMS
After installing updates released April 22, 2021 or later on an affected version of Windows Server when used as Key Management Services (KMS) host, client devices running Windows 10 Enterprise LTSC 2019 and Windows 10 Enterprise LTSC 2016 might fail to activate. This issue only occurs when using a new Customer Support Volume License Key (CSVLK). Note: This does not affect activation of any other version or edition of Windows. Client devices attempting to activate that are affected by this issue might receive the error, "Error: 0xC004F074 The Software Licensing Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information." Event Log entries related to activation is another way to tell that you might be affected by this issue. Open Event Viewer on the client device that failed activation and go to Windows Logs, then Application. If you see only event ID 12288 (without a corresponding event ID 12289), this means that the KMS client was not able to reach the KMS host, the KMS host did not respond, or the client did not receive the response. For more information on these event ID, see Useful KMS client events - Event ID 12288 and Event ID 12289. Next steps: We are working on a resolution and will provide an update in an upcoming release. Affected platforms:
|