{"family":"windowsserver","family_label":"Windows Server","build":"20348.288","base":"20348","tag":"2022","kb":"KB5006699","kb_url":"https://support.microsoft.com/help/5006699","kb_title":"October 12, 2021—KB5006699 (OS Build 20348.288)","release_date":"2021-10-12","update_type":"2021-10 B","update_type_label":"Security update (Patch Tuesday)","servicing":"LTSC","ms_known_issues":[{"title":null,"symptom":"After installing KB5005575, installation of printers using Internet Printing Protocol (IPP) might not complete successfully. Devices which had connected to and installed the printer prior to the installation of KB5005575 are unaffected and print operations to that printer will succeed as usual. Note IPP is not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises and organizations.","workaround":"This issue is resolved in KB5006745 .","applies_to":""},{"title":null,"symptom":"After installing KB5005619 on a print server, printing properties defined on that server might not be correctly provided to clients. Note this issue is specific to print servers and does not impact standard network printing. This issue will not cause printing operations to fail, however, custom settings defined on the server – for example, duplex print settings – will not be applied automatically, and clients will print with default settings only. This issue results from an improper building of the data file which contains the printer properties. Clients which receive this data file will not be able to use the file content and will instead proceed with default printing settings. Clients who","workaround":"This issue is resolved in KB5006745 .","applies_to":""},{"title":null,"symptom":"After installing this update, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication. You might receive the prompt, \"Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials.\" and \"The login attempt failed\" in red.","workaround":"This issue is addressed in KB5007254 .","applies_to":""},{"title":null,"symptom":"You might receive a prompt for administrative credentials every time you attempt to print in environments in which the print server and print client are in different times zones. Note The affected environments described in this issue are not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises and organizations.","workaround":"This issue is resolved in KB5006745 .","applies_to":""},{"title":null,"symptom":"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations.","workaround":"This issue is resolved in KB5007254 .","applies_to":""},{"title":null,"symptom":"Universal Windows Platform (UWP) apps might not open on devices that have undergone a Windows device reset. This includes operations that were initiated using Mobile Device Management (MDM), such as Reset this PC, Push-button reset, and Autopilot Reset.UWP apps you downloaded from the Microsoft Store are not affected. Only a limited set of apps are affected, including: App packages with framework dependencies Apps that are provisioned for the device, not per user account. The affected apps will fail to open without error messages or other observable symptoms. They must be re-installed to restore functionality.","workaround":"This issue is addressed in KB5015879 for all releases starting September 14, 2021 and later.","applies_to":""}],"ms_none_known":false,"ms_highlights":null,"title":"October 12, 2021—KB5006699 (OS Build 20348.288)","build_type":"release","channel_label":"Release","branch":null,"kind":"cumulative","kind_label":"Cumulative update","is_dotnet":false,"status":null,"line":{"status":"supported","note":"Supported LTSC release"},"created":1634040000,"created_iso":"2021-10-12T12:00:00Z","uuid":null,"permalink":"/builds/windowsserver/20348.288/","tag_url":"/builds/windowsserver/2022/","index_url":"/builds/windowsserver/","api_url":"https://search.windowsforum.com/api/builds/build/windowsserver/20348.288","records":[],"summary":null,"known_issues":[],"linked":{"news":[],"tutorials":[],"threads":[{"thread_id":257261,"node_id":88,"title":"All of your 3G devices will lose cellular service in 2022. Here's what you need to know.","replies":1,"views":1226,"post_date":1634025306,"last_post_date":1726094608,"url":"https://windowsforum.com/the-water-cooler.88/all-of-your-3g-devices-will-lose-cellular-service-in-2022-heres-what-you-need-to-know.257261/","kind":"coverage","match":"line","pinned":false,"score":0.9981}],"total":1,"exact":0,"window_days":45},"related":{"history":[{"build":"20348.380","title":null,"created":1637582400,"kb":"KB5007254","build_type":"release","channel_label":"Release","kind":null,"url":"/builds/windowsserver/20348.380/","current":false},{"build":"20348.350","title":null,"created":1636459200,"kb":"KB5007205","build_type":"release","channel_label":"Release","kind":null,"url":"/builds/windowsserver/20348.350/","current":false},{"build":"20348.320","title":null,"created":1635249600,"kb":"KB5006745","build_type":"release","channel_label":"Release","kind":null,"url":"/builds/windowsserver/20348.320/","current":false},{"build":"20348.288","title":null,"created":1634040000,"kb":"KB5006699","build_type":"release","channel_label":"Release","kind":null,"url":"/builds/windowsserver/20348.288/","current":true},{"build":"20348.261","title":null,"created":1632744000,"kb":"KB5005619","build_type":"release","channel_label":"Release","kind":null,"url":"/builds/windowsserver/20348.261/","current":false},{"build":"20348.230","title":null,"created":1631620800,"kb":"KB5005575","build_type":"release","channel_label":"Release","kind":null,"url":"/builds/windowsserver/20348.230/","current":false},{"build":"20348.202","title":null,"created":1629979200,"kb":"KB5005104","build_type":"release","channel_label":"Release","kind":null,"url":"/builds/windowsserver/20348.202/","current":false}],"history_total":94,"prev":{"build":"20348.261","title":null,"created":1632744000,"kb":"KB5005619","build_type":"release","channel_label":"Release","kind":null,"url":"/builds/windowsserver/20348.261/","current":false},"next":{"build":"20348.320","title":null,"created":1635249600,"kb":"KB5006745","build_type":"release","channel_label":"Release","kind":null,"url":"/builds/windowsserver/20348.320/","current":false},"wave":[]},"source":"microsoft","indexable":false,"generated":1790211804}