Applies ToWindows 10 Enterprise LTSC 2021 Windows 10 IoT Enterprise LTSC 2021 Windows 10, version 22H2, all editions
Version:
OS Builds 19044.4894 and 19045.4894
Highlights
-
This update addresses security issues for your Windows operating system.
Improvements
Note To view the list of addressed issues, click or tap the OS name to expand the collapsible section.
Important: Use EKB KB5015684 to update to Windows 10, version 22H2.
This security update includes quality improvements. Key changes include:
-
This build includes all the improvements from the supported Windows 10, version 21H2 editions.
-
No additional issues are documented for this release.
Important: Use EKB KB5003791 to update to Windows 10, version 21H2 on supported editions.
This security update includes quality improvements that were a part of update KB5041582 (released August 27, 2024). Below is a summary of the key issues that this update addresses when you install this KB. If there are new features, it lists them as well. The bold text within the brackets indicates the item or area of the change we are documenting.
-
[Windows Installer] When it repairs an application, the User Account Control (UAC) does not prompt for your credentials. After you install this update, the UAC will prompt for them. Because of this, you must update your automation scripts. Application owners must add the Shield icon. It indicates that the process requires full administrator access. To turn off the UAC prompt, set the HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer\DisableLUAInRepair registry value to 1. The changes in this update might affect automatic Windows Installer repairs; see Application Resiliency: Unlock the Hidden Features of Windows Installer.
-
[Dual boot of Windows and Linux (known issue)] Linux might fail to start up when you turn on dual-boot setup for Windows and Linux on your device. The error message is, “Verifying shim SBAT data failed: Security Policy Violation. Something has gone seriously wrong: SBAT self-check failed: Security Policy Violation.” See the full guidance in CVE-2022-2601 and CVE-2023-40547.
If you installed earlier updates, only the new updates contained in this package will be downloaded and installed on your device.
For more information about security vulnerabilities, please refer to the new Security Update Guide website and the September 2024 Security Updates.
Windows 10 servicing stack update (KB5043935) — 19044.4892 and 19045.4892
This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. Servicing stack updates (SSU) ensure that you have a robust and reliable servicing stack so that your devices can receive and install Microsoft updates.
Symptom |
Workaround |
---|---|
After installing this update, you might be unable to change your user account profile picture. When attempting to change a profile picture by selecting the button Start> Settings > Account > Your info and, under Create your picture, clicking on Browse for one, you might receive an error message with error code 0x80070520. |
After further investigation, we concluded this issue has very limited or no impact for this Windows version. If you encounter this issue on your device, please contact Windows support for help |
After installing this security update, you might face issues with booting Linux if you have enabled the dual-boot setup for Windows and Linux in your device. Resulting from this issue, your device might fail to boot Linux and show the error message “Verifying shim SBAT data failed: Security Policy Violation. Something has gone seriously wrong: SBAT self-check failed: Security Policy Violation.” The August 2024 Windows security update applies a Secure Boot Advanced Targeting (SBAT) setting to devices that run Windows to block old, vulnerable boot managers. This SBAT update will not be applied to devices where dual booting is detected. On some devices, the dual-boot detection did not detect some customized methods of dual-booting and applied the SBAT value when it should not have been applied. |
Please refer to the workaround mentioned in Windows release health site for this issue. |
After installing this update, you might experience a black screen when you login to Azure Virtual Desktop (AVD). You might also notice that you are unable to log out of your account and the black screen persists even after disconnecting and reconnecting to AVD. Resulting from this issue, the application event log in Event viewer will show an application error with Event ID:1000 indicating a fault with the application ‘svchost.exe_AppXSvc’. Please note that AppX Deployment Service (AppxSvc) being in an invalid state could also cause other symptoms like the Start Menu to close unexpectedly due to registration issues. |
This issue is resolved by installing the Windows updates released October 22, 2024 (KB5045594) or later updates and by applying one of the options mentioned in the Resolution section in KB5048864. Note that you need to perform both actions to resolve the issue. |
After installing this update, or subsequent updates, a small subset of Azure Virtual Desktop customers using multi-session hosts (AVD) may experience the following issues:
This issue is caused by a deadlock in the interactions between the Azure Active Directory (AAD) broker and the underlying AppX deployment service(AppxSvc) and Background tasks infrastructure service. You are more likely to experience this issue if you are using FSLogix user profile containers on multi-session environments. FSLogix is a Microsoft tool that helps manage and speed up user profiles on computers, especially in virtual environments like remote desktops. |
This issue is resolved by installing the Windows updates released October 22, 2024 (KB5045594) or later updates and by applying one of the options mentioned in the Resolution section in KB5048864. Note that you need to perform both actions to resolve the issue. |
How to get this update
Before you install this update
Microsoft now combines the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). For general information about SSUs, see Servicing stack updates and Servicing Stack Updates (SSU): Frequently Asked Questions.
Prerequisite:
Based on your installation scenario, choose one of the following:
-
For offline OS image servicing:
If your image does not have the July 25, 2023 (KB5028244) or later LCU, you must install the special standalone October 13, 2023 SSU (KB5031539) before installing this update.
-
For Windows Server Update Services (WSUS) deployment or when installing the standalone package from Microsoft Update Catalog:
If your devices do not have the May 11, 2021 (KB5003173) or later LCU, you must install the special standalone August 10, 2021 SSU (KB5005260) before installing this update.
Install this update
To install this update, use one of the following Windows and Microsoft release channels.
Available |
Next Step |
Yes |
None. This update will be downloaded and installed automatically from Windows Update and Microsoft Update. |
If you want to remove the LCU
To remove the LCU after installing the combined SSU and LCU package, use the DISM/Remove-Package command line option with the LCU package name as the argument. You can find the package name by using this command: DISM /online /get-packages.
Running Windows Update Standalone Installer (wusa.exe) with the /uninstall switch on the combined package will not work because the combined package contains the SSU. You cannot remove the SSU from the system after installation.
File information
For a list of the files that are provided in this update, download the file information for cumulative update 5043064.
For a list of the files that are provided in the servicing stack update, download the file information for the SSU (KB5043935) — versions 19044.4892 and 19045.4892.
Need more help?
Want more options?
Explore subscription benefits, browse training courses, learn how to secure your device, and more.
Soft
Интерфейс: Русский
Лекарство: на рабочем столе
Сборка сделана на основе оригинальных образов Windows 10 MSDN. Были интегрированы обновления по 14 мая 2024 года, а также интегрирован SmartFix 2.4.8 и Microsoft DaRT.
Применён Mod. С правом выбора install.wim. В процессе установки можно предварительно настроить Windows 10 выставив нужные чекбоксы.
Системные требования:
• ОЗУ: 4 ГБ для системы 64-разрядной системы
• Место на жестком диске: 40 ГБ для 64-разрядной ОС
• Процессор не менее 2 ГГц или SoC из за «Microsoft Store»
• Видеоадаптер: DirectX 9/10 или более поздняя версия с драйвером WDDM 1.0
• Экран: 1280 x 720
Описание:
Особенности сборки:
— Интегрированы обновления по 14 мая 2024 года;
— Панель управления в контекстном меню.
— Внесены косметические изменения.
— Интегрирован .Net Framework 4.8.1;
— Включен .Net Framework 3.5 (включая 2.0 и 3.0);
— Интегрирован Visual C++ 2005-2022 (Upd 03.03.2023);
— Интегрирован DirectX 9c (Upd June 2010);
— Интегрирован Games Pack (Collection Microsoft);
— Интегрирован SmartFix 2.4.8, Microsoft DaRT в winre.wim и boot.wim;
— Интегрирован Yandex браузер;
— Системы не были в режиме аудита.
Список редакций windows доступных для установки:
Windows 10 Домашняя x64
Windows 10 Домашняя с одним языком x64
Windows 10 Pro x64
Windows 10 Pro для общеобразовательных учреждений x64
Windows 10 Pro с одним языком x64
Windows 10 Pro для рабочих станций x64
Windows 10 для общеобразовательных учреждений x64
Windows 10 Enterprise для виртуальных рабочих столов x64
Windows 10 Enterprise x64
Windows 10 IoT Enterprise x64
Windows 10 Enterprise 2021 LTSC x64
Windows 10 IoT Enterprise 2021 LTSC x64
Горячие клавиши:
F1 — помощь и смена разрешения.
Ctrl+Shift+Esc — диспетчер задач.
Shift+F10 — командная строка (хоткеи для cmd хоть и есть, но её не вызвать до инициализации и запуска setup.exe, теперь можно когда угодно.)
Tab — переключение между основным окном и нижней панелью.
Written By
published
October 18, 2022
Hello Windows Insiders, today we are releasing Windows 10 21H2 Build 19044.2192 (KB5018482) to the Release Preview Channel for those Insiders who are on Windows 10, version 21H2.
This update includes the following improvements:
- We fixed an issue that affects Distributed Component Object Model (DCOM) authentication hardening. We will automatically raise the authentication level for all non-anonymous activation requests from DCOM clients to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY. This occurs if the authentication level is below Packet Integrity.
- We fixed a DCOM issue that affects the Remote Procedure Call Service (rpcss.exe). We raise the authentication level to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY instead of RPC_C_AUTHN_LEVEL_CONNECT if RPC_C_AUTHN_LEVEL_NONE is specified.
- We fixed an issue that causes an OS upgrade to stop responding, and then it fails.
- We fixed an issue that affects the Microsoft Azure Active Directory (AAD) Application Proxy connector. It cannot retrieve a Kerberos ticket on behalf of the user. The error message is, “The handle specified is invalid (0x80090301).”
- We fixed an issue that affects the font of three Chinese characters. When you format these characters as bold, the width size is wrong.
- We fixed an issue that affects Microsoft Direct3D 9 games. The graphics hardware stops working if the hardware does not have a native Direct3D 9 driver.
- We fixed graphical issues in games that use Microsoft D3D9 on some platforms.
- We fixed an issue that affects Microsoft Edge when it is in IE Mode. The titles of pop-up windows and tabs are wrong.
- We fixed an issue that affects Microsoft Edge IE mode. It stops you from opening webpages. This occurs when you enable Windows Defender Application Guard (WDAG) and you do not configure Network Isolation policies.
- We fixed an issue that might cause an application to stop responding. This might occur when the input queue overflows.
- We fixed an issue that affects input method editors (IME) from Microsoft and third parties. They stop working when you close the IME window. This occurs if the IME uses Windows Text Services Framework (TSF) 1.0.
- We fixed an issue that affects the lasso tool in a graphics editing program.
- We fixed an issue that affects Miracast advertisements. This issue occurs on Surface Hub devices under certain conditions.
- We fixed an issue that affects some drivers. They use more power when you play hardware-protected digital rights management (DRM) content.
- We fixed an issue that affects .msi files. Windows Defender Application Control (WDAC) will ignore them when you disable script enforcement.
- We fixed an issue that affects a remote desktop virtual desktop infrastructure (VDI) scenario. The session might use the wrong time zone.
Thanks,
The Windows Insider Program Team
- Microsoft pushes Windows 10 build 19044.1147 as the first official preview of version 21H2.
- The update brings a slew of fixes, but you won’t find any new features.
- The company outlines the changes expected to arrive with the update.
- And confirms that Windows 10 21H2 will be a minor update delivered as a cumulative update.
- The same changes are also available for version 21H1 as build 19043.1147.
Microsoft is now releasing Windows 10 build 19044.1147 (KB5004296) in the Release Preview Channel of the Windows Insider Program. This marks the first preview of the next feature update for Windows 10, and it’s only available for devices that were automatically moved from the Beta Channel to the Release Preview Channel as a result of not being compatible with Windows 11.
Although build 19044.1147 doesn’t introduce any new significant changes, it brings a slew of fixes for File Explorer, network, and storage. Also, the update KB5004296 further disables Timeline, fixes a memory leak, and more.
The same update KB5004296 with the exact same changes is also available for version 21H1. However, in this flight, the update will bump the version number to 19043.1147, and it’s available through the Release Preview Channel. If your device was previously in the Beta Channel and then moved to the Release Preview Channel automatically, you won’t receive this update. Also, these changes are expected to start rolling out to user with the next cumulative update for Windows 10 21H1.
According to the company’s announcement, these are all the changes in the latest flight of version 21H2:
- Fixed a problem with “searchindexer.” After you sign out, “searchindexerd” continues to hold handles to the per-user search database in the profile path, “C:\Users\username\AppData\Roaming\Microsoft\Search\Data\Applications\\”. As a result, “searchindexer” stops working and duplicate profile names are created.
- Addressed a problem that prevents gaming services from opening certain games for desktop users.
- Fixed a problem that prevents you from entering text using the Input Method Editor (IME). This might occur, for example, after startup if you have set the power options to shut down a laptop by closing its lid.
- We changed the functionality for uploading new activity into Timeline. If you sync your activity history across your devices using your Microsoft account (MSA), you cannot upload new activity into the Timeline. You can still use Timeline and see your activity history (information about recent apps, websites, and files) on your local device. This does not affect Azure Active Directory (AAD) accounts. To view web history, Microsoft Edge and other browsers provide the option to view recent web activities. You can also view recently used files using Microsoft OneDrive and Microsoft Office.
- Addressed a problem that might cause the File Explorer window to lose focus when you are mapping a network drive.
- Fixed a problem that causes File Explorer to stop working after reaching 99% completion when you are deleting many files on a mapped network drive.
- We fixed a timing issue in the Group Policy Registry Telemetry that causes Group Policy extension processing to fail.
- Addressed a problem that repeatedly rebuilds the Windows Filtering Platform (WFP) filters. This issue occurs when a device is enrolled in a mobile device management (MDM) service and “MDMWinsOverGP” is set.
- Fixed a problem with an MDM service that fails to correctly apply certain junk mail rules.
- Addressed a problem that always reports the update build revision (UBR) as zero (0) on a device during enrollment to an MDM service.
- Fixed a problem that causes the enrollment of the Elliptic Curve Digital Signature Algorithm (ECDSA) certificate to fail with the error, “0x80090027 NTE_INVALID_PARAMETER.” This issue occurs when the Trusted Platform Module (TPM) provider (the Microsoft Software Key Storage Provider) stores the key.
- Addressed a problem with auditing events 4624 and 5142 that display the wrong event template when Dutch is the display language.
- Fixed a problem that causes System Integrity to leak memory.
- Addressed a problem that plays the sound for selecting something in a game loudly when you press the trigger button on a game controller.
- Fixed a problem that prevents power plans and Game Mode from working as expected. This results in lower frame rates and reduced performance while gaming.
- Addressed a problem in which “Network Internal Access” appears on the taskbar network icon on systems that access the internet from certain domains.
- Fixed a problem in which the Network Connectivity Status Indicator (NCSI) fails to detect internet connectivity after you connect to a virtual private network (VPN).
- Addressed a problem that causes printing to stop or prints the wrong output. This issue occurs when you print using a USB connection after updating to Windows 10, version 2004 or later.
- We fixed a rare issue that might degrade performance in applications that call Gdiplus.dll!GdipMeasureString in a tight loop with a new font on each call. This issue occurs after installing Windows updates released on and after February 2021.
- Fixed a problem that incorrectly routes some audio channels when streaming using certain fixed channel layouts.
- Addressed a problem that always displays devices that RemoteFX USB redirects as “Remote Desktop Generic USB Device” instead of the actual device name.
- Fixed a problem in which Set-RDSessionCollectionConfiguration does not set the “camerastoredirect:s:value” custom property.
- We fixed a Local Security Authority Subsystem Service (LSASS) domain controller memory leak that is reported in Privileged Access Management (PAM) deployments.
- Addressed a problem that prevents you from accessing a network drive that maps to a Distributed File System (DFS) root after you sign out.
- Fixed a problem that prevents you from reconnecting to mapped network drives after you sign in and displays an access denied error. This issue occurs if you use the net use /deep option to create multiple drive mappings to different paths on the same encrypted file share.
- Addressed a problem that prevents access to files on a Server Message Block (SMB) share when you enable Access Enabled Enumeration (ABE).
- Fixed a problem that prevents the Windows Server service from starting if SrvComment is greater than 128 characters.
- Addressed a problem in the Windows Network File System (NFS) client that might prevent you from renaming a file after mounting an NFS share. This issue occurs if you rename the file using File Explorer but does not occur if you rename the file using the command line.
- Fixed a problem with an unhandled Open File dialog critical exception. As a result, Microsoft Foundation Class (MFC) applications might close unexpectedly.
- Addressed a problem in which the Storage Sense page in Settings might incorrectly report the size of some storage devices that use the GUID Partition Table (GPT). The affected devices will incorrectly report in Storage Sense that the size is twice as large as the size reported in File Explorer. Note: This issue does not affect storage devices that use a master boot record (MBR).
Alongside these improvements, the company has also announced that version 21H2 will be a small update delivered as a cumulative update with a “scoped set of features focused on productivity and security, prioritized to meet our customers’ needs based on feedback,” some of which will include:
- Adding WPA3 H2E standards support to wireless security.
- Windows Hello for Business supports simplified passwordless deployment models.
- GPU compute support in the Windows Subsystem for Linux (WSL) and Azure IoT Edge for Linux on Windows (EFLOW) deployments for machine learning and other workflows.
However, these changes are still not implemented in the latest preview of Windows 10.
Download Windows 10 19044.1147
The 19044.1147 preview is available immediately through the Dev Channel, and it will install automatically. However, you can always get it manually from Settings > Update & security > Windows Update and clicking the Check for updates button.
Why You Can Trust Pureinfotech
The author combines expert insights with user-centric guidance, rigorously researching and testing to ensure you receive trustworthy, easy-to-follow tech guides. Review the publishing process.
- About
- Blog
- Projects
- Help
-
Donate
Donate icon
An illustration of a heart shape - Contact
- Jobs
- Volunteer
- People
Item Preview
There Is No Preview Available For This Item
This item does not appear to have any files that can be experienced on Archive.org.
Please download files in this item to interact with them on your computer.
Show all files
software
Windows. 10. Pro. 19044.2130
Windows 10 Pro 21H2 Build 19044.2130 October 2022
- Addeddate
- 2022-12-18 04:55:37
- Identifier
- windows.-10.-pro.-19044.2130
- Scanner
- Internet Archive HTML5 Uploader 1.7.0
comment
Reviews
(1)
There is 1 review for this item. .
1,165
Views
2
Favorites
1
Review
DOWNLOAD OPTIONS
Uploaded by
samsami2
on
SIMILAR ITEMS (based on metadata)