Jump to content

Search the Community

Showing results for tags 'windows 10'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Site Related
    • News & Updates
    • Site / Forum Feedback
    • Member Introduction
  • News
    • General News
    • FileSharing News
    • Mobile News
    • Software News
    • Security & Privacy News
    • Technology News
  • Downloads
    • nsane.down
  • General Discussions & Support
    • Filesharing Chat
    • Security & Privacy Center
    • Software Chat
    • Mobile Mania
    • Technology Talk
    • Entertainment Exchange
    • Guides & Tutorials
  • Off-Topic Chat
    • The Chat Bar
    • Jokes & Funny Stuff
    • Polling Station

Categories

  • Drivers
  • Filesharing
    • BitTorrent
    • eDonkey & Direct Connect (DC)
    • NewsReaders (Usenet)
    • Other P2P Clients & Tools
  • Internet
    • Download Managers & FTP Clients
    • Messengers
    • Web Browsers
    • Other Internet Tools
  • Multimedia
    • Codecs & Converters
    • Image Viewers & Editors
    • Media Players
    • Other Multimedia Software
  • Security
    • Anti-Malware
    • Firewalls
    • Other Security Tools
  • System
    • Benchmarking & System Info
    • Customization
    • Defrag Tools
    • Disc & Registry Cleaners
    • Management Suites
    • Other System Tools
  • Other Apps
    • Burning & Imaging
    • Document Viewers & Editors
    • File Managers & Archivers
    • Miscellaneous Applications
  • Linux Distributions

Categories

  • General News
  • File Sharing News
  • Mobile News
  • Software News
  • Security & Privacy News
  • Technology News

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

  1. The September 2021 Patch Update is released and Microsoft is now rolling out new KB5005565 and KB5005566 cumulative updates for recent versions of Windows 10. Today's cumulative updates include security fixes for PCs with May 2021 Update (version 21H1), October 2020 Update (version 20H2), and May 2020 Update (version 2004). The update is now rolling out via Windows Update, WSUS, and the Microsoft Update Catalog with numerous bug fixes and performance enhancements. The full list of today's cumulative updates is below: Windows 10 version 1507 — KB5005569 (OS Build 10240.19060) Windows 10 version 1607 — KB5005573 (OS Build 14393.4651) Windows 10 version 1703 — EOS Windows 10 version 1709 — EOS Windows 10 version 1803 — EOS Windows 10 version 1809 — KB5005568 (OS Build 17763.2183) Windows 10 version 1903 — EOS Windows 10 version 1909 — KB5005566 (OS Build 18363.1801) Windows 10 version 2004, 20H2 and 21H1 — KB5005565 (OS Builds 19041.1237, 19042.1237, and 19043.1237) Like every Patch Tuesday, you can check for and install new updates by going to Settings, clicking on Windows Update, and selecting 'Check for Updates' to install the updates. Windows Update offering today's updates If you own multiple PCs or if you would like to patch the PCs manually, you can learn more about how to do so here. Today's Patch Tuesday updates also fix 60 security vulnerabilities, including a Windows MSHTML zero-day vulnerability tracked as CVE-2021-40444. What's new in the KB5005565 cumulative update With the KB5005565 update, Microsoft has addressed a bug that causes Bluetooth headsets to only work for voice calls and another bug that provides the wrong Furigana result when you cancel the Japanese reconversion. The company has also updated an issue that resets syncing for Microsoft OneDrive to “Known folders only” after you install a Windows update. After installing this update, Windows 10 2004 will be updated to build 19041.1237, Windows 10 20H2 will be updated to build 19042.1237, and Windows 10 21H1 will be updated to build 19043.1237. This cumulative update comes with the following highlighted fixes: Addresses an issue that causes PowerShell to create an infinite number of child directories. This issue occurs when you use the PowerShell Move-Item command to move a directory to one of its children. As a result, the volume fills up and the system stops responding. Updates a rare condition that causes Bluetooth headsets to only work for voice calls. Updates an issue that provides the wrong Furigana result when you cancel the Japanese reconversion. Updates an issue that resets syncing for Microsoft OneDrive to “Known folders only” after you install a Windows update. Updates an issue that prevents audio headsets that connect to a device using USB from working if the device has certain third-party audio drivers. Updates an issue with resizing images that might produce flickering and residual line artifacts. Updates an issue that prevents you from typing any words in the username box during the out-of-box experience (OOBE) process. This issue occurs when you use the Chinese Input Method Editor (IME). Updates an issue with copying and pasting a text box into Office 365 apps. If you use an IME, you won’t be able to insert text into the text box. Updates an issue that might cause your device to stop working when making a touch input gesture. This issue occurs if you bring more fingers into contact with the touchpad or screen during the middle of the gesture. Updates an issue that might cause an external monitor to display a black screen after Hibernation. This issue might occur when the external monitor connects to a docking station using a certain hardware interface. Updates an issue that resets the brightness for standard dynamic range (SDR) content on high-dynamic range (HDR) monitors. This occurs after you restart your device or reconnect to the device remotely. Windows 10 version 1909 is getting KB5005566 with identical fixes. Windows 10 KB5005565 & KB5005566 cumulative updates released
  2. Microsoft releases Windows 10 builds 19042.985, 18363.1556 - here's what's new Yet another month has passed, and Microsoft is once again releasing its set of Patch Tuesday updates for all supported versions of Windows, including a multitude of Windows 10 versions. For regular users with Windows 10 Home or Pro, only versions 20H2, 2004, and 1909 are getting updates today, and even then, support for version 1909 ends today, so this is the last update you'll get unless you have an Enterprise or Education SKU. For Windows 10 version 2004 and 20H2, the cumulative update is the same, and it's labeled KB5003173, which you can download manually here. This will bring the build number up to 19041.985 and 19042.985, depending on which version you have, and it includes these highlights: Updates to improve security when Windows performs basic operations. Updates to improve Windows OLE (compound documents) security. Updates security for Bluetooth drivers. The full list of fixes is below: 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. Security updates to Windows App Platform and Frameworks, the Windows Kernel, Windows Media, the Microsoft Scripting Engine, and the Windows Silicon Platform. If you're still using Windows 10 version 1909, this is the last update you'll get if you have Windows 10 Home or Pro, and you may want to consider upgrading to a newer version to stay secure going forward. The update is KB5003169 and it brings the build number up to 18363.1556. You can download it manually here, and the highlights of the update are: Updates to improve security when Windows performs basic operations. Updates an issue that might cause scroll bar controls to appear blank on the screen and not function. Updates to improve Windows OLE (compound documents) security. Updates security for Bluetooth drivers. And here are the additional fixes and improvements included: Addresses an issue that might cause scroll bar controls to appear blank on the screen and not function. This issue affects 32-bit applications running on 64-bit Windows 10 (WOW64) that create scroll bars using a superclass of the USER32.DLL SCROLLBAR window class. This issue also affects HScrollBar and VScrollBar controls and classes derived from System.Windows.Forms.ScrollBar. A memory usage increase of up to 4 GB might occur in 64-bit applications when you create a scroll bar control. Security updates Windows App Platform and Frameworks, the Windows Kernel, the Microsoft Scripting Engine, and the Windows Silicon Platform. Finally, there are a bunch of updates for versions of Windows 10 that are only supported in specific SKUs or servicing channels. Here's a quick rundown of everything else being released today: Version KB Build Download Support 1809 KB5003171 17763.1935 Update Catalog Enterprise and Education SKUs 1803 KB5003174 17134.2208 Update Catalog 1607 KB5003197 14393.4402 Update Catalog Long-Term Servicing Branch 1507 KB5003172 10240.18932 Update Catalog For Windows 10 versions 1803 and 1809, these are also the final updates for Enterprise and Education SKUs. Version 1809, however, will live on in the Long-Term Servicing Channel alongside the other two LTSB releases. As usual, these updates are mandatory and they'll be installed automatically sooner or later. You can download them manually using the links above to avoid surprises. Source: Microsoft releases Windows 10 builds 19042.985, 18363.1556 - here's what's new
  3. Microsoft has released the optional KB5005101 Preview cumulative update for Windows 10 2004, Windows 10 20H2, and Windows 10 21H1 with fixes for thirty-four issues. This preview update is part of Microsoft's June 2021 monthly "C" update, allowing Windows 10 users to test the upcoming fixes and changes to be released on September 14th as part of Patch Tuesday. Unlike updates released on Patch Tuesday, this preview update is optional and only contains bug fixes, performance enhancements, and improvements. It does not include any security updates. You can install this update by going to Settings > Windows Update and clicking on 'Check for Updates.' As this is an optional update, you will need to click on the 'Download and install' link for the update to be installed, as shown below. KB5005101 update offered in Windows Update Windows 10 users can also manually download and install the KB5005101 preview update from the Microsoft Update Catalog. Bluetooth and USB headphone issues fixed This update tests two fixes for issues Windows 10 users have been experiencing with Bluetooth and USB headphones. "Addresses an issue that prevents USB audio headsets from working on devices that support USB audio offload. This issue occurs if you installed third-party audio drivers on the devices," explained Microsoft in the KB5005101 support bulletin. "Addresses a rare condition that prevents Bluetooth headsets from connecting using the Advanced Audio Distribution Profile (A2DP) for music playback and causes the headsets to only work for voice calls." These issues do not appear to be common, but will likely be eagerly awaited fixes with many people working remotely. What's new in the Windows 10 KB5005101 update After installing the KB5005101 update, Windows 10 2004 will have its build number changed to 19041.1202, Windows 10 20H2 to build 19042.1202, and Windows 10 21H1 to build 19042.1202. The Windows 10 KB5005101 cumulative update preview includes 34 improvements or fixes, with the ten highlighted changes listed below: Updates a rare condition that causes Bluetooth headsets to only work for voice calls. Updates an issue that provides the wrong Furigana result when you cancel the Japanese reconversion. Updates an issue that resets syncing for Microsoft OneDrive to “Known folders only” after you install a Windows update. Updates an issue that prevents audio headsets that connect to a device using USB from working if the device has certain third-party audio drivers. Updates an issue with resizing images that might produce flickering and residual line artifacts. Updates an issue that prevents you from typing any words in the username box during the out-of-box experience (OOBE) process. This issue occurs when you use the Chinese Input Method Editor (IME). Updates an issue with copying and pasting a text box into Office 365 apps. If you use an IME, you won’t be able to insert text into the text box. Updates an issue that might cause your device to stop working when making a touch input gesture. This issue occurs if you bring more fingers into contact with the touchpad or screen during the middle of the gesture. Updates an issue that might cause an external monitor to display a black screen after Hibernation. This issue might occur when the external monitor connects to a docking station using a certain hardware interface. Updates an issue that resets the brightness for standard dynamic range (SDR) content on high-dynamic range (HDR) monitors. This occurs after you restart your device or reconnect to the device remotely. With this release, there are three known issues with KB5005101: Using the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app that automatically allows the input of Furigana characters, you might not get the correct Furigana characters. Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. After installing the June 21, 2021 (KB5003690) update, some devices cannot install new updates, such as the July 6, 2021 (KB5004945) or later updates. You will receive the error message, "PSFX_E_MATCHING_BINARY_MISSING". You can find a complete list of improves and fixes and detailed explanations of the known issues in the KB5005101 support bulletin. Windows 10 KB5005101 Cumulative Update released with 34 fixes
  4. Microsoft will make it easier for Windows 10 users to check if their computer is compatible with Windows 11 by alerting people via Windows Update. When Windows 11 was first announced, it came with new system requirements that will likely require many Windows 10 users to purchase new hardware to upgrade to the new operating system. These requirements include a TPM 2.0 security processor and newer CPUs, even if existing hardware runs Windows 10 without a problem. Microsoft recently added new CPUs to the Windows 11 compatibility list - the Intel Core X-series, Xeon W-series, and the Intel Core 7820HQ CPUs. However, they also stated that no AMD Zen 1 processors would be compatible, and we will likely not see further additions in the near future. According to WindowsLatest, Microsoft is testing a new feature in the Windows 10 21H2 preview builds that will tell users if their device is compatible with Windows 11. As shown below, when upgrading to Windows 11, Windows Update will check if a device is compatible and display the results directly in the window. Windows Update to tell if Windows 11 is compatible with a device You can read the full text of this notification below: "Great news—your PC meets the minimum system requirements for Windows 11. Specific timing for when it will be offered can vary as we get it ready for you. Note: Some Windows 10 features aren’t available in Windows 11. Certain apps and features may have additional requirements." – Windows Update Windows Update will likely alert the user to run the PC Health Check tool for more detailed information or, hopefully, directly list the incompatible hardware if a device is not compatible. Unfortunately, when BleepingComputer conducted a similar Windows 11 upgrade test using the latest Windows 10 21H2 build, Windows Update did not show us any information about whether our device was compatible. Likely, this new feature is currently being tested for a wider release at a later date. BleepingComputer has reached out to Microsoft about this new feature but has not heard back. Windows Update will tell if you can upgrade to Windows 11
  5. Windows 10 comes with built-in personalization settings to help you customize the desktop and it provides plenty of options by default. However, if you want to get the most out of your desktop, we recommend these third-party open-source programs. Fluent Search Fluent Search is an open-source app that lets you search for running apps/processes, browser tabs, bookmarks, files, and more. Unlike Windows Search, Fluent Search offers accurate results and it lets you jump easily between running apps and browser tabs. Fluent Search can also search for any open windows and it can even attempt to locate app-specific content inside them, such as buttons, hyperlinks, and more. Unlike Windows Search, search tags can filter search results easily. In addition to these features, Fluent Search also advanced Machine Learning models to learn your usage patterns and suggest results. You can download Fluent Search from Microsoft Store. Modern Flyout Modern Flyout is an open-source project that will replace Windows 10 or Windows 11's audio, aeroplane, and brightness flyouts with a customizable flyout with a modern UI. The native flyout is not permanently closed but will be hidden when you've this third-party tool installed. At the moment, the following flyouts can be modernized: Audio Flyout Media session Flyout Airplane Mode Brightness Scroll Lock Number Lock Caps Lock Insert / Overtype mode You can download Modern Flyout from Microsoft Store. PowerToys for Windows 10 Windows 10 PowerToys suite is developed by Microsoft and it will allow you to extend File Explorer's capabilities, optimize app windows for big monitors, resize images, and more. Some of the PowerToys include: Image Resizer Windows File Explorer's preview pane Replace slow Windows Search with Run-like tool. Modify Keyboard shortcuts Batch File Renamer Color Picker Read more: How to supercharge Windows 10 with PowerToys. Windows Terminal Windows Terminal is another open-source software developed by Microsoft and it can help users launch multiple shell/console tabs in the same operating system. Using Windows Terminal, you can replace PowerShell or Command Prompt instances. Windows Terminal can have a tab with a PowerShell console, another with the Windows 10 command prompt, and another with a WSL Ubuntu shell. Windows Terminal Windows Terminal is highly customizable and it also comes with a dedicated settings page. You can also make changes to the config file to change the background or map keyboard commands. You can download the Terminal from the Microsoft Store. Customize your Windows 10 experience with these free tools
  6. Microsoft has released a new Optional Cumulative Update KB5005103 for Windows 10 1909 in preparation for next month’s Patch Tuesday. Optional Updates are released early to allow IT staff to test and validate updates prior to their wide roll-out and are not pushed out automatically. Today’s Optional Update for Windows 10 1909 (Education and Enterprise) takes the OS to version 18363.1766 and has the following highlights: Highlights Updates an issue that prevents the Windows Movies and TV app from playing some videos (.mp4 files). Updates an issue that resets syncing for Microsoft OneDrive to “Known folders only” after you install a Windows update. Improvements and fixes This non-security update includes quality improvements. Key changes include: Addresses an issue that prevents users from tracking Distributed Component Object Model (DCOM) activation failures. Addresses a threading issue that might cause the Windows Remote Management (WinRM) service to stop working when it is under a high load. Addresses an issue that causes the Windows Management Instrumentation (WMI) provider host process to stop working. This occurs because of an unhandled access violation that occurs when using the Desired State Configuration (DSC). Addresses an issue that causes file migration between Distributed File System (DFS) paths that are stored on different volumes to fail. This issue occurs when you implement the migration using PowerShell scripts that use the Move-Item command. Addresses an issue that prevents you from writing to a WMI repository after a low memory condition occurs. Addresses an issue that might prevent you from minimizing an application that uses unthemed windows. Addresses an issue that prevents the Windows Movies and TV app from playing .mp4 media files that contain Pixel Aspect Ration (PAR) information. Addresses an issue that causes Authentication Mechanism Assurance (AMA) to stop working. This issue occurs when you migrate to Windows Server 2016 (or newer versions of Windows) and when using AMA in conjunction with certificates from Windows Hello for Business. Addresses an issue that prevents Secure Launch from working on some devices. Addresses an issue that prevents Code Integrity rules from working correctly when specifying Package Family Name rules in a Code Integrity policy. This issue occurs because of the incorrect handling of case-sensitive names. Addresses an issue that prevents the ShellHWDetection service from starting on a Privileged Access Workstation (PAW) device and prevents you from managing BitLocker drive encryption. Addresses an issue in Windows Defender Exploit Protection that prevents some Microsoft Office applications from working on machines that have certain processors. Addresses an issue that causes the Input Method Editor (IME) toolbar to appear even when the Remote App is closed. Addresses an issue with a critical exception that the Open File dialog fails to handle. As a result, a Microsoft Foundation Class (MFC) application unexpectedly closes. Addresses an issue that might occur when you configure the policy, “Delete user profiles older than a specified number of days on system restart”. If a user has been signed in for longer than the time specified in the policy, the device might unexpectedly delete profiles at startup. Addresses an issue with the Microsoft OneDrive sync setting “Always keep on this device”. The setting is unexpectedly reset to “Known folders only” after you install a Windows update. Addresses an issue that might create duplicate built-in local accounts, such as administrator or guest account, during an in-place upgrade. This issue occurs if you previously renamed those accounts. As a result, the Local Users and Groups MMC snap-in (lusrmgr.msc) appears blank with no accounts after the upgrade. This update removes the duplicate accounts from the local Security Account Manager (SAM) database on the affected machines. If the system detected and removed duplicate accounts, it logs a Directory-Services-SAM event, with ID 16986, in the System event log. Increases the default number of entries in the local security authority (LSA) Lookup Cache to improve lookup performance in high lookup volume scenarios. Addresses stop error 0x1E in srv2!Smb2CheckAndInvalidateCCFFile. Addresses an issue that might cause a system to stop working after a deduplication filter detects damage in a reparse point. This issue occurs because of deduplication driver changes introduced in a previous update. Addresses an issue with using the robocopy command with the backup option (/B) to fix data loss. This issue occurs when the source location contains tiered Azure File Sync files or tiered Cloud Files. Stops running queries against OneSettings APIs from the obsolete Storage Health feature. Known issues in this update Microsoft is not currently aware of any issues with this update. You can download the update from the Windows Catalogue here. via XDA-Dev Microsoft release Optional Cumulative Update KB5005103 for Windows 10 1909 with MP4 fix, more
  7. Some Windows 10 administrators experienced an odd behavior on devices running Windows 10 version 2004 or higher that started in May 2021. Any attempt at installing cumulative updates for the operating system would result in a PSFX_E_MATCHING_BINARY_MISSING error and failure to install the update. The issue started to happen on devices after the May 25, 2021 update, KB5003214, or the June 21, 2021, KB5003690, updates were installed on affected machines. Affected are machines running Windows 10 versions 2004, 20H2 and 21H1. According to Microsoft, the issue may occur on devices on which outdated resource records were removed from automatically. Microsoft describes the cause of the issue in the following way: This issue occurs on devices that have been scavenged automatically to remove outdated resource records. When a system is scavenged, the recently installed latest cumulative update (LCU) is marked as permanent and the older components are removed from the system. After scavenging is complete and a device is in this state, you cannot uninstall KB5003214 or KB5003690, and you cannot install future LCUs. Microsoft published a solution on August 24, 2021 on its support website. Administrators need to perform an in-place upgrade to resolve the issue. Microsoft notes that in-place upgrades are only available to devices that have been online for at least 30 days. For ARM devices, it is only working if the update KB5005932 has already been installed on the device. Open the Start menu. Type cmd. Command Prompt should be displayed as the first result. Select "run as administrator" to launch it with elevated rights. Run the following command: Reg.exe Add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion /v AllowInplaceUpgrade /t REG_DWORD /f /d 1 The command marks the system for an in-place upgrade. The Registry key will be removed automatically after the in-place upgrade has completed. Microsoft notes that it may take up to 48 hours before the upgrade is offered to the device. The device will be upgraded to a clean version of the operating system along with the latest monthly security update installed. Closing Words Being unable to install any updates for Windows 10 is quite the serious problem. Microsoft released several updates with critical security patches since May 25th, which the affected systems missed out on because of the issue. Microsoft has a fix for Windows 10's PSFX_E_MATCHING_BINARY_MISSING update error
  8. By offering the extended support, organizations could safely run Windows 10 for years after its planned 2025 retirement. Microsoft will almost certainly offer extended support to Windows 10 that will let organizations safely run the operating system for years after its putative 2025 retirement date. While nothing is certain where Microsoft's concerned, the company does tend to stick with a practice that's proved out. If something, like the concept of Extended Security Updates (ESUs), has generated revenue and squelched commercial customer complaints, that's a twofer Microsoft will take every time. Latest clue comes from Server 2012 The latest clue that ESUs are here to stay came last month, when Microsoft announced that it will offer three years of additional, paid support for Windows Server 2012, Windows Server 2012 R2 and SQL Server 2012. "Customers that cannot meet the end of support deadline and have Software Assurance or subscription licenses under an enterprise agreement enrollment will have the option to buy Extended Security Updates to get three more years of security updates," Debbi Lyons, Director, product marketing, Azure SQL and Database Migration, and Vijay Kumar, director of product marketing, Windows Server and Azure Arc, wrote in a July 14 post to a company blog. Windows Server 2012 and 2012 R2 are due to exit support Oct. 12, 2023; SQL Server 2012 exhausts its support July 12, 2022. ESUs will be sold for all these products in one-year increments for a maximum of three years past the original end-of-support. Thus, ESU licenses for Windows Server 2012 R2 would run to Oct. 12, 2024, Oct. 12, 2025, and Oct. 12, 2026. Windows Server 2012 and 2012 R2, and SQL Server 2012, join other venerable operating systems and products that have been offered ESU coverage by Microsoft, including Windows Server 2008, Windows 7 and Dynamics AX 2009. Bet on ESUs for Windows 10 With precedents like these — the last two Windows Server editions, the last two SQL Server editions, and the last Windows client — it's an easy bet that Microsoft will continue to crank out ESUs for software that reaches its sell-by date. In chronological order for Windows, those dates are: Windows 10: Oct. 14, 2025 Windows Server 2016: Jan 12, 2027 Windows Server 2019: Jan. 9, 2029 Because Microsoft has standardized on three years' worth of ESUs, paid one year at a time, priced lowest the first year, then higher each following year — to encourage customers to upgrade to a still-supported edition — those practices will be continued for Windows Server. (The first year for Windows Server 2012 and 2012 R2 ESU, for instance, will cost 75% of the license cost, with the next two years running 100% and 125%, respectively.) Windows 10 will almost certainly keep to those parameters; the first ESU will extend support to Oct. 14, 2026, with the second and third years pushing out support to October 2027 and October 2028. Although it may be easy for some to dismiss the idea of ESUs for Windows 10 simply because the successor Windows 11 is, at least initially, largely a UI and UX remodel, that would be to underestimate the impact of the latter's change to hardware requirements. Because Microsoft will demand that Windows 11-eligible devices sport 8th-generation or later Intel processors, some in-place PCs will be unable to run the OS. (The percentage in an organization largely depends on the org's replacement cycle tempo.) The number of affected systems will be significantly smaller by Windows 10's retirement in four years, but few things raise customer hackles more than Microsoft making them spend hardware budgets simply to run the next iteration of some software. Computerworld's forecast: Microsoft will offer ESUs for no other reason than to soothe such customers, no matter the number of unable-to-run-11 machines. Microsoft likely to offer Extended Security Updates for Windows 10 in 2025 (May require free registration to view)
  9. The Windows 10 Alt+Tab keyboard shortcut is a staple of the operating system, but some users are reporting issues with the feature after installing the August 2021 Cumulative update (KB5005033 ). “It breaks Alt-Tab switching games that run in “full screen” mode. Switching to such games gives you a black screen and no way to return to the game. Again uninstalling this update reverts to normal working behaviour,” said one user on the Feedback Hub. “Furthermore, Windows 10 under this update sometimes Alt-Tabs out of the fullscreen game immediately after starting up the game from Steam. Basically, the fullscreen game now starts up minimized on my taskbar. If I try to click the game to go to its fullscreen mode, Win10 immediately alt-tabs from the fullscreen and I’m back to square one,” complained another. Uninstalling the Cumulative Update fixes the issue, but there is an even easier fix. For some reason, Microsoft’s News and Interest taskbar widget is involved in the issue, and disabling the superfluous gadget also appears to fix the problem. To do that, right-click anywhere on the taskbar, scroll up to the ‘News and interests’ menu item and select ‘Turn off’. The issue also appears to occur with the July 2021 preview optional update (KB5004296), and the same fix also works there. Are any of our readers affected by this bug? Let us know below. via WindowsLatest Windows 10 Cumulative Update KB5005033 is breaking Alt+Tab for some – here’s the easy fix
  10. Along with the Windows 10 version 21H1 Build 19043.1198 (KB5005101) announcement, Microsoft today announced the release of Windows 10 21H2 Build 19044.1200 (KB5005101) to the Release Preview Channel. This build is available for Insiders who are already on Windows 10, version 21H2 in the Release Preview Channel. This build includes support for new WiFi standard, improved Windows Hello for Business support and more. Find the full change log below. What’s new in Windows 10 Build 19044.1200: Adding WPA3 H2E standards support for enhanced Wi-Fi security Windows Hello for Business introduces a new deployment method called cloud trust to support simplified passwordless deployments and achieve a deploy-to-run state within a few minutes 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 compute intensive workflows It also includes the following improvements: We fixed an issue that prevents users from tracking Distributed Component Object Model (DCOM) activation failures. We fixed a threading issue that might cause the Windows Remote Management (WinRM) service to stop working when it is under a high load. We fixed an issue that causes the Windows Management Instrumentation (WMI) provider host process to stop working. This occurs because of an unhandled access violation that occurs when using the Desired State Configuration (DSC). We fixed an issue that causes file migration between Distributed File System (DFS) paths that are stored on different volumes to fail. This issue occurs when you implement the migration using PowerShell scripts that use the Move-Item command. We fixed an issue that prevents you from writing to a WMI repository after a low memory condition occurs. We fixed an issue that resets the brightness for standard dynamic range (SDR) content on high-dynamic range (HDR) monitors. This occurs after you restart the system or reconnect to the system remotely. We fixed an issue that might cause an external monitor to display a black screen after Hibernation. This issue might occur when the external monitor connects to a docking station using a certain hardware interface. We fixed a memory leak that occurs when you use nested classes within VBScript. We fixed an issue that prevents you from typing any words in the username box during the out-of-box experience (OOBE) process. This issue occurs when you use the Chinese Input Method Editor (IME). We fixed an issue that causes applications that use a shim to stop working. This issue occurs on devices that do not have edgegdi.dll installed. The error message is, “The code execution cannot proceed because edgegdi.dll was not found”. We fixed an issue that might prevent you from minimizing an application that uses unthemed windows. We fixed an issue that might cause your device to stop working during a touch input gesture. This issue occurs if you bring more fingers into contact with the touchpad or screen during the middle of the gesture. We fixed an issue with resizing images that might produce flickering and residual line artifacts. We fixed an issue with copying and pasting a text box into Office 365 apps. The IME prevents you from inserting text into the text box. We fixed an issue that prevents USB audio headsets from working on laptops that support USB audio offload. This issue occurs if you installed third-party audio drivers on the laptops. We fixed an issue that prevents Code Integrity rules from working correctly when specifying Package Family Name rules in a Code Integrity policy. This issue occurs because of the incorrect handling of case-sensitive names. We fixed an issue that prevents the ShellHWDetection service from starting on a Privileged Access Workstation (PAW) device and prevents you from managing BitLocker drive encryption. We fixed an issue in Windows Defender Exploit Protection that prevents some Microsoft Office applications from working on machines that have certain processors. We fixed an issue that causes the IME toolbar to appear even when the Remote App is closed. We fixed an issue that might occur when you configure the policy, “Delete user profiles older than a specified number of days on system restart”. If a user has been signed in for longer than the time specified in the policy, the device might unexpectedly delete profiles at startup. We fixed an issue with the Microsoft OneDrive sync setting “Always keep on this device”. The setting is unexpectedly reset to “Known folders only” after you install Windows updates. We fixed an issue that provides the wrong Furigana result when a user cancels the Japanese reconversion. We fixed a rare condition that prevents Bluetooth headsets from connecting using the Advanced Audio Distribution Profile (A2DP) for music playback and causes the headsets to only work for voice calls. We added the “Target Product Version” policy. With this, administrators can specify the Windows product they want devices to migrate to or remain on (for example, Windows 10 or Windows 11). We increased the default number of entries in the local security authority (LSA) Lookup Cache to improve lookup performance in high lookup volume scenarios. We fixed an issue that might create duplicate built-in local accounts, such as administrator or guest account, during an in-place upgrade. This issue occurs if you previously renamed those accounts. As a result, the Local Users and Groups MMC snap-in (msc) appears blank with no accounts after the upgrade. This update removes the duplicate accounts from the local Security Account Manager (SAM) database on the affected machines. If the system detected and removed duplicate accounts, it logs a Directory-Services-SAM event, with ID 16986, in the System event log. We fixed a stop error 0x1E in srv2!Smb2CheckAndInvalidateCCFFile. We fixed an issue that might cause transfer validations to fail with the error, “HRESULT E_FAIL has been returned from a call to a COM component”. This issue occurs when you use Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012 as sources. We fixed an issue that might cause a system to stop working after a deduplication filter detects damage in a reparse point. This issue occurs because of deduplication driver changes introduced in a previous update. We fixed an issue with using the robocopy command with the backup option (/B) to fix data loss. This issue occurs when the source location contains tiered Azure File Sync files or tiered Cloud Files. We stopped running queries against OneSettings APIs from the obsolete Storage Health feature. We enabled over 1400 new mobile device management (MDM) policies. With them, you can configure policies that Group Policies also support. These new MDM policies include administrative template (ADMX) policies, such as App Compat, Event Forwarding, Servicing, and Task Scheduler. Starting in September 2021, you can use the Microsoft Endpoint Manager (MEM) Settings Catalog to configure these new MDM policies. Known issue: The Windows Update settings page may hang after you download an optional update. Close and reopen the Windows Update settings page if you encounter this. To check and see if you’re running Windows 10, version 21H2, just type “winver” into the Windows search box on the Taskbar. It should show as “Version 21H2”. Source: Microsoft Microsoft releases Windows 10 Build 19044.1200 (21H2) with support for new Wi-Fi standard and more
  11. Microsoft today announced the release of Windows 10, version 21H1 Build 19043.1200 (KB5005101) to the Release Preview Channel Insiders who are on Windows 10, version 21H1. This build includes several new bug fixes, you can find the full list below. Windows 10 Build 19043.1200 update includes the following improvements: We fixed an issue that prevents users from tracking Distributed Component Object Model (DCOM) activation failures. We fixed a threading issue that might cause the Windows Remote Management (WinRM) service to stop working when it is under a high load. We fixed an issue that causes the Windows Management Instrumentation (WMI) provider host process to stop working. This occurs because of an unhandled access violation that occurs when using the Desired State Configuration (DSC). We fixed an issue that causes file migration between Distributed File System (DFS) paths that are stored on different volumes to fail. This issue occurs when you implement the migration using PowerShell scripts that use the Move-Item command. We fixed an issue that prevents you from writing to a WMI repository after a low memory condition occurs. We fixed an issue that resets the brightness for standard dynamic range (SDR) content on high-dynamic range (HDR) monitors. This occurs after you restart the system or reconnect to the system remotely. We fixed an issue that might cause an external monitor to display a black screen after Hibernation. This issue might occur when the external monitor connects to a docking station using a certain hardware interface. We fixed a memory leak that occurs when you use nested classes within VBScript. We fixed an issue that prevents you from typing any words in the username box during the out-of-box experience (OOBE) process. This issue occurs when you use the Chinese Input Method Editor (IME). We fixed an issue that causes applications that use a shim to stop working. This issue occurs on devices that do not have edgegdi.dll installed. The error message is, “The code execution cannot proceed because edgegdi.dll was not found”. We fixed an issue that might prevent you from minimizing an application that uses unthemed windows. We fixed an issue that might cause your device to stop working during a touch input gesture. This issue occurs if you bring more fingers into contact with the touchpad or screen during the middle of the gesture. We fixed an issue with resizing images that might produce flickering and residual line artifacts. We fixed an issue with copying and pasting a text box into Office 365 apps. The IME prevents you from inserting text into the text box. We fixed an issue that prevents USB audio headsets from working on laptops that support USB audio offload. This issue occurs if you installed third-party audio drivers on the laptops. We fixed an issue that prevents Code Integrity rules from working correctly when specifying Package Family Name rules in a Code Integrity policy. This issue occurs because of the incorrect handling of case-sensitive names. We fixed an issue that prevents the ShellHWDetection service from starting on a Privileged Access Workstation (PAW) device and prevents you from managing BitLocker drive encryption. We fixed an issue in Windows Defender Exploit Protection that prevents some Microsoft Office applications from working on machines that have certain processors. We fixed an issue that causes the IME toolbar to appear even when the Remote App is closed. We fixed an issue that might occur when you configure the policy, “Delete user profiles older than a specified number of days on system restart”. If a user has been signed in for longer than the time specified in the policy, the device might unexpectedly delete profiles at startup. We fixed an issue with the Microsoft OneDrive sync setting “Always keep on this device”. The setting is unexpectedly reset to “Known folders only” after you install Windows updates. We fixed an issue that provides the wrong Furigana result when a user cancels the Japanese reconversion. We fixed a rare condition that prevents Bluetooth headsets from connecting using the Advanced Audio Distribution Profile (A2DP) for music playback and causes the headsets to only work for voice calls. We added the “Target Product Version” policy. With this, administrators can specify the Windows product they want devices to migrate to or remain on (for example, Windows 10 or Windows 11). We increased the default number of entries in the local security authority (LSA) Lookup Cache to improve lookup performance in high lookup volume scenarios. We fixed an issue that might create duplicate built-in local accounts, such as administrator or guest account, during an in-place upgrade. This issue occurs if you previously renamed those accounts. As a result, the Local Users and Groups MMC snap-in (msc) appears blank with no accounts after the upgrade. This update removes the duplicate accounts from the local Security Account Manager (SAM) database on the affected machines. If the system detected and removed duplicate accounts, it logs a Directory-Services-SAM event, with ID 16986, in the System event log. We fixed a stop error 0x1E in srv2!Smb2CheckAndInvalidateCCFFile. We fixed an issue that might cause transfer validations to fail with the error, “HRESULT E_FAIL has been returned from a call to a COM component”. This issue occurs when you use Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012 as sources. We fixed an issue that might cause a system to stop working after a deduplication filter detects damage in a reparse point. This issue occurs because of deduplication driver changes introduced in a previous update. We fixed an issue with using the robocopy command with the backup option (/B) to fix data loss. This issue occurs when the source location contains tiered Azure File Sync files or tiered Cloud Files. We stopped running queries against OneSettings APIs from the obsolete Storage Health feature. We enabled over 1400 new mobile device management (MDM) policies. With them, you can configure policies that Group Policies also support. These new MDM policies include administrative template (ADMX) policies, such as App Compat, Event Forwarding, Servicing, and Task Scheduler. Starting in September 2021, you can use the Microsoft Endpoint Manager (MEM) Settings Catalog to configure these new MDM policies. Known issue: The Windows Update settings page may hang after you download an optional update. Close and reopen the Windows Update settings page if you encounter this. Source: Microsoft Microsoft releases Windows 10 Build 19043.1200 (21H1) to Release Preview Channel Insiders
  12. Microsoft may be planning to update the UI of the Your Phone app on Windows 10 and 11. An image of the updated appearance was leaked by Alumia, who says it applies to the Compact UI of the app. The main change appears to be that the connection status icons are now next to the image of your handset rather than below. The old UI can be seen below: The new UI will presumably roll out to Insiders in the near future. via ALumia Microsoft’s Your Phone app getting Compact UI updates
  13. Telegram Desktop for Windows 10 has received a new update, bringing a number of new but relatively minor features. Changelog NEW AUTO-DELETE SETTINGS Enable auto-delete in your chats to remove messages after 1 month (also 1 day or 1 week). SHARED GIFS Quickly find all GIFs from a chat using the new GIF section in Shared Media. PASSWORD RECOVERY Reset your Two-Step Verification password even if you forgot your old password and don’t have a recovery email. To do this, you must be logged into your account. The reset takes 7 days and can be cancelled from any of your devices. NEW APPEARANCE Enjoy a new app icon and default background. You can download and install the Telegram Desktop on your Windows 10 PC from the below link, or you can head over to Microsoft Store and search for the app. Telegram Desktop Developer: ‪Telegram Messenger LLP‬ Price: Kostenlos via onMSFT Telegram Desktop app with new auto-delete settings, more
  14. The August 2021 Patch Tuesday is out and Microsoft has published several new cumulative updates (KB5005033 & KB5005031) for recent versions of Windows 10. Today's cumulative updates include security fixes for PCs with May 2021 Update, October 2020 Update, and May 2020 Update. The update is rollout via Windows Update, WSUS and Microsoft Update Catalog with numerous bug fixes and performance enhancements. Like every Windows Update, you can open Settings, click on Windows Update, and select 'Check for Updates' to install the updates. The full list of today's cumulative updates is below: Windows 10 version 1507 — KB5004249 (OS Build 10240.19003) Windows 10 version 1607 — KB5004238 (OS Build 14393.4530) Windows 10 version 1703 — EOS Windows 10 version 1709 — EOS Windows 10 version 1803 — EOS Windows 10 version 1809 — KB5004244 (OS Build 17763.2061) Windows 10 version 1903 — EOS Windows 10 version 1909 — KB5004245 (OS Build 18363.1679) Windows 10 version 2004, 20H2 and 21H1 — KB5004237 (OS Builds 19041.1110, 19042.1110, and 19043.1110) If you own multiple PCs or if you would like to patch the PCs manually, you can learn more about how to do this here. Microsoft also fixed 44 security vulnerabilities in the August 2021 Patch Tuesday updates. These updates include three fixes for zero-day vulnerabilities that were actively exploited or publicly disclosed, like PrintNightmare and PetitPotam. What's new in the KB5005033 cumulative update With the KB5005033 update, Microsoft has released numerous security and non-security improvements. For example, Microsoft fixed an issue that prevents power plans and Game Mode from working as expected, resulting in lower frame rates and reduced performance while gaming. Another bug has been fixed that causes the File Explorer window to lose focus when you are mapping a network drive. This cumulative updates comes with the following highlighted fixes: Changes the default privilege requirement for installing drivers when using Point and Print. After installing this update, you must have administrative privileges to install drivers. If you use Point and Print, see KB5005652, Point and Print Default Behavior Change, and CVE-2021-34481 for more information. We fixed an issue that prevents gaming services from opening certain games for desktop users. We fixed an issue 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 fixed an issue with an MDM service that fails to correctly apply certain junk mail rules. We fixed an issue that always reports the update build revision (UBR) as zero (0) on a device during enrollment to an MDM service. We fixed an issue with auditing events 4624 and 5142 that display the wrong event template when Dutch is the display language. We fixed an issue that causes System Integrity to leak memory. We fixed an issue that plays the sound for selecting something in a game loudly when you press the trigger button on a game controller. We fixed an issue that prevents power plans and Game Mode from working as expected. This results in lower frame rates and reduced performance while We fixed an issue that prevents you from accessing a network drive that maps to a Distributed File System (DFS) root after you sign out. Windows 10 version 1909 is getting KB5005031 with identical fixes. Windows 10 KB5005033 & KB5005031 cumulative updates released
  15. Right now, Microsoft has two different OneNote apps for Windows devices, the OneNote app installed with Office and the OneNote for Windows 10 app available in the Microsoft Store. Microsoft has now announced that it will unify both the apps to create a single OneNote app that will deliver great note taking experience on Windows. As a result, the current OneNote for Windows 10 app will be retired in the future. The OneNote app which is part of Office suite will get a visual refresh, the latest Microsoft pen and ink improvements and a new navigational UI layout option. The OneNote app will get new features and key existing features currently unique to OneNote for Windows 10. OneNote for Windows 10 users will get an in-app invitation to update to the OneNote app. We anticipate invitations to start in the second half of 2022. We will have a future announcement dedicated to IT pros that will detail the available controls over the timing and experience of updating users to the OneNote app. If you are using OneNote for Windows 10 app today, you will be able to migrate to the updated OneNote app in the future. All notebooks you have today in OneNote and OneNote for Windows 10 will continue to work in the updated app. Source: Microsoft Microsoft to retire OneNote for Windows 10 app
  16. Microsoft Defender and Microsoft Edge on Windows 10 will automatically block potentially unwanted applications (PUAs) by default starting this month. Starting with the Windows 10 2004, the May 2020 update, Microsoft added a new 'Potentially unwanted app blocking' setting in Windows security that causes Microsoft Defender to block these types of applications. Since its release, this feature has been disabled by default, but starting this month, Microsoft will begin to block PUAs when detected on a computer automatically. "Starting in early August 2021 we'll begin turning it on by default to make it easier for you to keep your systems performing at their best," Microsoft announced in a short support bulletin today. Windows 10 users who do not wish to block PUAs by default can turn the feature off by opening the Windows Security setting screen, clicking on App & browser control, and selecting Reputation-based protection settings. At the Reputation-based protection settings screen, you can disable the 'Potentially unwanted app blocking' setting. Windows Security Potentially unwanted app blocking setting The 'Block Apps' option will enable Microsoft Defender's built-in PUA scanning and blocking feature. The 'Block downloads' will control whether the 'Block potentially unwanted apps' setting is enabled in the new Microsoft Edge browser. When enabled, SmartScreen will block PUAs and PUPs as they are downloaded. This cchange to automatic blocking is beneficial for all users of Microsoft Defender as BleepingComputer has found over the years that programs marked as PUAs or PUPs should be classified as malware as they perform malicious behavior on a computer. However, due to legal concerns, many companies do not block them automatically or ignore them. With Microsoft automatically blocking PUAs, it could encourage the security industry to do a better job at blocking these unwanted applications. What are potentially unwanted applications? Potentially unwanted applications, otherwise known as PUAs or PUPs, are not quite malware but pretty close. They are usually created by legitimate legal entities who skirt the boundaries of what would be considered "respectable" software, and in most cases, perform unwanted behavior on a computer. These programs range from browser extensions, adware, programs that send usage data without permission, Windows system cleaners and antivirus programs that use false positives, and programs that do not provide promised functionality. Microsoft's criteria for designating a program as a potentially unwanted application is listed below: Advertising software: Software that displays advertisements or promotions, or prompts you to complete surveys for other products or services in software other than itself. This includes software that inserts advertisements to webpages. Torrent software (Enterprise only): Software that is used to create or download torrents or other files specifically used with peer-to-peer file-sharing technologies. Cryptomining software: Software that uses your device resources to mine cryptocurrencies. Bundling software: Software that offers to install other software that is not developed by the same entity or not required for the software to run. Also, software that offers to install other software that qualifies as PUA based on the criteria outlined in this document. Marketing software: Software that monitors and transmits the activities of users to applications or services other than itself for marketing research. Evasion software: Software that actively tries to evade detection by security products, including software that behaves differently in the presence of security products. Poor industry reputation: Software that trusted security providers detect with their security products. The security industry is dedicated to protecting customers and improving their experiences. Microsoft and other organizations in the security industry continuously exchange knowledge about files we have analyzed to provide users with the best possible protection. Unfortunately, some legitimate software may be lumped in with these criteria and detected by Microsoft Defender's PUA blocking feature. For example, crypto mining applications and torrent software commonly have legitimate purposes but may now be detected by Microsoft Defender and removed. In those, cases it is advised that you create exclusions in Microsoft Defender to prevent those files from being quarantined rather than disabling the entire feature. Windows 10 to automatically block potentially unwanted apps
  17. Windows 10 now lets you install WSL with a single command Microsoft says the Windows Subsystem for Linux (WSL) can now be installed on Windows 10, version 2004 or later using a single terminal command. "In the latest Windows Insider Preview builds, you can install everything you need to run WSL just by running wsl.exe --install," Windows Developer Platform Program Manager Craig Loewen said. "We’re excited to announce that this functionality is now officially backported to Windows 10 version 2004 and higher, which will make installing WSL on those builds much easier!" To get access to this new feature, you have to update your computer to Windows 10 2004 or later via Windows Update or install the KB5004296 preview cumulative update, which also comes with fixes for fixes Windows 10 gaming issues. How to install and use WSL While previously you had to jump through several hoops such as installing multiple packages and toggling on several OS settings, now you only have to open a Command Prompt window as administrator and run the wsl.exe --install command. This automatically enables WSL and installs Ubuntu as the default distro and the latest WSL Linux kernel version on the device. After the installation process is completed and the computer is rebooted, the newly deployed Ubuntu distribution will automatically start logging in. Once WSL is installed, you can use wsl --update to update the Linux kernel and wsl --update rollback to switch to a previous kernel version. You can also use wsl --status to get an overview of your WSL configuration, including the default distro type, default distro, and the currently installed Linux kernel version. A short WSL history WSL was released in 2018 and it is designed as a compatibility layer that makes it possible for Windows 10 users to run Linux binaries in ELF format natively on their computers, in a PowerShell or Windows 10 command prompt. Since the initial release, Microsoft has also launched WSL 2, which increases file system performance, supports full system call compatibility, and uses virtualization tech to run a full Linux kernel inside a lightweight virtual machine (VM). Even though users have been asking Microsoft to also add support for the Wayland protocol in WSL to allow GUI Linux apps to work on Windows since at least 2016, the company only announced that it would introduce Linux GUI support last year at BUILD 2020. The new feature, dubbed WSLg (short for Windows Subsystem for Linux GUI), was released in April and began rolling out to all Insiders in May with the rollout of Windows 10 Insider Preview Build 21364 to the Dev Channel. As previously described, WSLg allows you to use Linux GUI applications in Windows as you would use them on a Linux desktop. Microsoft provides step-by-step guidance on how to install and launch Linux GUI apps on your PC. Once installed, these Linux apps can be launched from the Start menu or a Command Prompt window. Windows 10 now lets you install WSL with a single command
  18. Microsoft releases optional Windows 10 updates with a ton of fixes Microsoft has released cumulative updates for the three most recent versions of Windows 10, along with version 1909 currently supported for specific SKUs, as part of its “C” week release. These optional “quality” updates are usually released one or two weeks after Patch Tuesday. These fixes will also be rolled into the next month’s Patch Tuesday updates for those who choose to avoid installing these patches. The update rolling out to Windows 10 versions 2004, 20H2, and 21H1 is KB5004296, bumping up the build numbers to 19041.1151, 19042.1151, and 19043.1151, respectively. Since the three versions are based on the same codebase – with versions 20H2 and 21H1 being just enablement packages –, they are serviced with identical patches. The same update will soon roll out to Insiders running Windows 10 version 21H2 in the Release Preview channel, bumping the version to 19044.1151. These are Insiders that were moved from the Beta channel to Release Preview due to the incompatibility of their systems for Windows 11. Users with compatible devices, however, received the first Windows 11 build today. As for what’s new with the updates, there is the usual crop of bug fixes, addressing issues with gaming reliability and more. While the changelog does note a fix for a printing issue when using a USB connection, the firm is yet to address the problem relating to printing and scanning when using smart card authentication. Here are the highlights of the updates heading out to versions 2004, 20H2, and 21H1: Updates an issue that prevents gaming services from opening certain games for desktop users. Updates an issue 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. Updates an issue that plays the sound for selecting something in a game loudly when you press the trigger button on a game controller. Updates an issue that prevents power plans and Game Mode from working as expected. This results in lower frame rates and reduced performance while gaming. Updates an issue that fails to detect that you are connected to the internet after you connect to a virtual private network (VPN). Updates an issue 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. And here is the complete list of fixes, which is a fairly long one: Addresses an issue with searchindexer. After you sign out, searchindexer 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. Addresses an issue that prevents gaming services from opening certain games for desktop users. Addresses an issue 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. Changes 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. Addresses an issue that might cause the File Explorer window to lose focus when you are mapping a network drive. Addresses an issue that causes File Explorer to stop working after reaching 99% completion when you are deleting many files on a mapped network drive. Addresses a timing issue in the Group Policy Registry Telemetry that causes Group Policy extension processing to fail. Addresses an issue 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. Addresses an issue with an MDM service that fails to correctly apply certain junk mail rules. Addresses an issue that always reports the update build revision (UBR) as zero (0) on a device during enrollment to an MDM service. Addresses an issue 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. Addresses an issue with auditing events 4624 and 5142 that display the wrong event template when Dutch is the display language. Addresses an issue that causes System Integrity to leak memory. Addresses an issue that plays the sound for selecting something in a game loudly when you press the trigger button on a game controller. Addresses an issue that prevents power plans and Game Mode from working as expected. This results in lower frame rates and reduced performance while gaming. Addresses an issue in which "Network Internal Access" appears on the taskbar network icon on systems that access the internet from certain domains. Addresses an issue in which the Network Connectivity Status Indicator (NCSI) fails to detect internet connectivity after you connect to a virtual private network (VPN). Addresses an issue 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. Addresses 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. Addresses an issue that incorrectly routes some audio channels when streaming using certain fixed channel layouts. Addresses an issue that always displays devices that RemoteFX USB redirects as "Remote Desktop Generic USB Device" instead of the actual device name. Addresses an issue in which Set-RDSessionCollectionConfiguration does not set the camerastoredirect:s:value custom property. Addresses a Local Security Authority Subsystem Service (LSASS) domain controller memory leak that is reported in Privileged Access Management (PAM) deployments. Addresses an issue that prevents you from accessing a network drive that maps to a Distributed File System (DFS) root after you sign out. Addresses an issue 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. Addresses an issue that prevents access to files on a Server Message Block (SMB) share when you enable Access Enabled Enumeration (ABE). Addresses an issue that prevents the Windows Server service from starting if SrvComment is greater than 128 characters. Addresses an issue 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 command line. Addresses an issue with an unhandled Open File dialog critical exception. As a result, Microsoft Foundation Class (MFC) applications might close unexpectedly. Adds a new policy that creates generic strings and removes branding-specific terms, such as “Windows” or “PC”, for IoT Enterprise editions. For example, we changed “computer” to “device”. Instead of "Getting Windows ready," we changed that to "Getting things ready" and so on. These generic strings display on a user’s screen when an update is in progress. Addresses an issue 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. And here are the known issues listed in the changelog that users must be aware of: Symptoms Workaround When using the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app that automatically allows the input of Furigana characters, you might not get the correct Furigana characters. You might need to enter the Furigana characters manually. Note The affected apps are using the ImmGetCompositionString() function. We are working on a resolution and will provide an update in an upcoming release. Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone servicing stack update (SSU) released March 29, 2021 or later. Note Devices that connect directly to Windows Update to receive updates are not affected. This includes devices using Windows Update for Business. Any device connecting to Windows Update should always receive the latest versions of the SSU and latest cumulative update (LCU) without any extra steps. To avoid this issue, be sure to first slipstream the SSU released March 29, 2021 or later into the custom offline media or ISO image before slipstreaming the LCU. To do this with the combined SSU and LCU packages now used for Windows 10, version 20H2 and Windows 10, version 2004, you will need to extract the SSU from the combined package. Use the following steps to extract the using SSU: Extract the cab from the msu via this command line (using the package for KB5000842 as an example): expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cab Extract the SSU from the previously extracted cab via this command line: expand Windows10.0-KB5000842-x64.cab /f:* You will then have the SSU cab, in this example named SSU-19041.903-x64.cab. Slipstream this file into your offline image first, then the LCU. If you have already encountered this issue by installing the OS using affected custom media, you can mitigate it by directly installing the new Microsoft Edge. If you need to broadly deploy the new Microsoft Edge for business, see Download and deploy Microsoft Edge for business After installing the June 21, 2021 (KB5003690) update, some devices cannot install new updates, such as the July 6, 2021 (KB5004945) or later updates. You will receive the error message, "PSFX_E_MATCHING_BINARY_MISSING". For more information and a workaround, see KB5005322. Those running Windows 10 version 1909 Enterprise, Education, or IoT Enterprise will be offered KB5004293, bumping up the version to build 18363.1714. You can head to the knowledge base article to look at the complete list of fixes and known issues. Those looking to download the update manually can do so from the Update Catalog here for versions 2004, 20H2, and 21H1, and here for version 1909. However, the updated packages have not been made available at the time of writing. As mentioned earlier, these updates will show up as optional updates and are opt-in only. The fixes in these patches will be rolled into the Patch Tuesday packages next month. Microsoft releases optional Windows 10 updates with a ton of fixes
  19. New Windows 10 KB5005394 emergency update fixes printing issues Microsoft has released a cumulative out-of-band update to fix a known printing issue preventing some printers and scanners from working correctly. "Addresses an issue with devices that do not comply with section 3.2.1 of the RFC 4556 specification," Microsoft explains in the KB5005394 support document. "Noncompliant printers, scanners, and multifunction devices might not work when you use smart card authentication (PIV). This issue occurs after you install the July 13, 2021 update on domain controllers (DC) in your environment." Fixed on a limited number of affected Windows versions The printing issues affect both client and server Windows platforms, starting with Windows 7 SP1 / Windows Server 2008 SP2 and later: Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1 Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 However, based on the support document published today, the KB5005394 cumulative update released today by Microsoft only applies to Windows 10 1809, Windows Server 1809, and Windows Server 2019. This out-of-band update can only be installed manually as a standalone package available for download through the Microsoft Update Catalog. Microsoft has also released the KB5005392 OOB update to address the printing issues on Windows 7 SP1 or Windows Server 2008 R2 SP1 devices. When it confirmed this known printing issue on Friday, Microsoft also added that all affected smart card authenticating devices should work as expected when using username and password authentication. Issue caused by security flaw hardenings The known issue is caused by hardening changes for CVE-2021-33764. It only impacts smart card authenticating printers, scanners, and multifunction devices, which "don't support DH or advertise support for des-ede3-cbc ("triple DES") during the Kerberos AS request." Affected Windows 10 users are advised to first check if they have the latest drivers and firmware installed for non-compliant and misbehaving printers or scanners. If the devices are up-to-date, impacted users should contact the device manufacturer and ask for setting changes or updates to make the printer or scanner compliant with the CVE-2021-33764 hardenings deployed via July's Windows 10 security updates. Microsoft is still working to mitigate the issue on all affected Windows versions to re-enable printing and scanning on impacted devices. "This will allow time for device manufacturers to release compliant firmware and drivers for their devices," Microsoft explains. "Further, it should allow time to update settings, firmware, and drivers in your environment and make them compliant." Update: Added info on KB5005392 OOB update. New Windows 10 KB5005394 emergency update fixes printing issues
  20. Microsoft’s fix for Windows 10 gaming issues is coming soon With the release of Windows 10's March 2021 updates and subsequent updates, some users have been experiencing performance issues when playing games. These gaming issues include decreased frame rate, stuttering in certain games, and flickering textures. The problem was widely reported in March and NVIDIA had even recommended that users should remove the recent Windows 10 updates to resolve these issues in response. In April, a server-side emergency patch was immediately issued by Microsoft in response to user complaints and the same fix is now included in July 2021 patch for Windows 10 version 21H1, 20H2, and version 2004. However, some users are still having issues, suggesting that the patch was incomplete. Thankfully, Microsoft is testing another fix. In release notes of beta build 19043.1147, Microsoft has confirmed that it's working on a fix for an issue that prevents power plans and game mode from working, causing lower FPS and reduced performance for gamers. "We fixed an issue that prevents power plans and Game Mode from working as expected. This results in lower frame rates and reduced performance while gaming," the company noted in the changelog. In addition to gaming fix, Microsoft is also fixing an issue that causes the File Explorer window to lose focus when you are mapping a network drive. These bug fixes will be released in the production channel as part of the upcoming optional update and August 2021 Patch Tuesday. Microsoft’s fix for Windows 10 gaming issues is coming soon
  21. Windows July update breaks printing and scanning when using smart-cards Microsoft seems to be having to deal with issues related to printers for a while now. This year alone, starting with the March update that caused the blue screen of death (BSOD) when trying to print, and more recently with the PrintNightmare print spooler service vulnerability. And Microsoft's troubles aren't stopping there. Today, the firm has confirmed that its recent July security update version KB5004237, which was released on July 13, is causing problems when printing on certain systems when trying to utilize smart cards for user authentication. This time, alongside printing problems, scanning on such systems may also not work. According to the Redmond firm, the KB5004237 July 13 cumulative update fixed printing problems on such printers that were connected via USB. However, it seems the update has also introduced a new bug as a result of the changes made for dealing with the CVE-2021-33764 vulnerability. This is causing the new issue on Domain Controller servers which act as gatekeepers responsible for dealing with such authentication requests. It has been noted however that while working with smart cards may fail, username and password authentication should work without issue. Here's how Microsoft has described the problem: After installing updates released July 13, 2021 on domain controllers (DCs) in your environment, printers, scanners, and multifunction devices which are not compliant with section 3.2.1 of RFC 4556 spec, might fail to print when using smart-card (PIV) authentication. The problem has been detailed a bit more under KB5005408 which explains that client printers and scanners must be compliant with either of the following: Use Diffie-Hellman for key-exchange during PKINIT Kerberos authentication (preferred). Both support and notify the KDC of their support for des-ede3-cbc ("triple DES”). Here, KDC refers to a Key Distribution Center. The Windows platforms affected by this issue are: Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1 Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 Microsoft has said that it's investigating the issue and will provide a temporary workaround. For people having problems, the company has asked to update the necessary drivers and firmware and to consult with the device manufacturers when needed. You may find more details about the problem here on the company's official page. Windows July update breaks printing and scanning when using smart-cards
  22. Microsoft shares workaround for Windows 10 SeriousSAM vulnerability Microsoft has shared workarounds for a Windows 10 zero-day vulnerability dubbed SeriousSAM that can let attackers gain admin rights on vulnerable systems and execute arbitrary code with SYSTEM privileges. As BleepingComputer previously reported, a local elevation of privilege bug (dubbed SeriousSAM) found in recently released Windows versions allows users with low privileges to access sensitive Registry database files. Affects Windows 10 versions released since 2018 The security flaw, publicly disclosed by security researcher Jonas Lykkegaard on Twitter and yet to receive an official patch, is now tracked by Microsoft as CVE-2021-36934. "An elevation of privilege vulnerability exists because of overly permissive Access Control Lists (ACLs) on multiple system files, including the Security Accounts Manager (SAM) database," Microsoft explains in a security advisory published on Tuesday evening. "An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. An attacker must have the ability to execute code on a victim system to exploit this vulnerability." As Microsoft further revealed, this zero-day vulnerability impacts Windows releases since October 2018, starting with Windows 10, version 1809. Lykkegaard also found that Windows 11 (Microsoft's not yet officially released OS) is also impacted. Workarounds now available The databases exposed to user access by this bug (i.e., SYSTEM, SECURITY, SAM, DEFAULT, and SOFTWARE) are stored under the C:\Windows\system32\config folder. Mimikatz creator Benjamin Delpy told BleepingComputer that anyone could easily take advantage of the incorrect file permissions to steal an elevated account's NTLM hashed password and gain higher privileges via a pass-the-hash attack. While attackers can't directly access the databases due to access violations triggered by the files always being in use by the OS, they can access them through shadow volume copies. Microsoft recommends restricting access to the problematic folder AND deleting Volume Shadow Copy Service (VSS) shadow copies to mitigate this issue. Users should be aware that removing shadow copies from their systems could impact system and file restore operations, such as restoring data using third-party backup apps. These are the steps needed to block exploitation of this vulnerability temporarily: Restrict access to the contents of %windir%\system32\config: Open Command Prompt or Windows PowerShell as an administrator. Run this command: icacls %windir%\system32\config\*.* /inheritance:e Delete Volume Shadow Copy Service (VSS) shadow copies: Delete any System Restore points and Shadow volumes that existed prior to restricting access to %windir%\system32\config. Create a new System Restore point (if desired). Microsoft is still investigating the vulnerability and is working on a patch that will most likely be released as an out-of-band security update later this week. "We are investigating and will take appropriate action as needed to help keep customers protected," Microsoft told BleepingComputer Microsoft shares workaround for Windows 10 SeriousSAM vulnerability
  23. I IN NO WAY TAKE ANY CREDIT FOR THIS IT WAS TAKEN FROM MDL FORUM AND SOME POSTS BY MEMBERS ON THIS FORUM! Manual: Tools: Microsoft Telemetry Tools Bundle v2.33 Windows 10 Lite v9 Private WinTen v0.84 Blackbird v6 v1.0.80.2 [Works with Win 7/8/8/1/10] O&O ShutUp10 v1.8.1423 WPD - Windows Privacy Dashboard v1.4.1834 WindowsSpyBlocker v4.36.0 Spybot Anti-Beacon v3.5 [Works with Win 7/8/8/1/10] W10Privacy v3.7.0.8 Privatezilla v0.50.0 SharpApp v0.46.1 Debotnet v0.7.8 Disable Windows 10 Tracking v3.2.3 Destroy Windows Spying v1.0.1.0 [Works with Win 7/8/8/1/10] [NOT RECOMMENDED AS NOT UPDATED ANYMORE]
  24. New Windows 10 vulnerability allows anyone to get admin privileges Windows 10 and Windows 11 are vulnerable to a local elevation of privilege vulnerability after discovering that users with low privileges can access sensitive Registry database files. The Windows Registry acts as the configuration repository for the Windows operating system and contains hashed passwords, user customizations, configuration options for applications, system decryption keys, and more. The database files associated with the Windows Registry are stored under the C:\Windows\system32\config folder and are broken up into different files such as SYSTEM, SECURITY, SAM, DEFAULT, and SOFTWARE. As these files contain sensitive information about all user accounts on a device and security tokens used by Windows features, they should be restricted from being viewed by regular users with no elevated privileges. This is especially true for the Security Account Manager (SAM) file as it contains the hashed passwords for all users on a system, which threat actors can use to assume their identity. SAM file can be read by anyone Yesterday, security researcher Jonas Lykkegaard told BleepingComputer he discovered that the Windows 10 and Windows 11 Registry files associated with the Security Account Manager (SAM), and all other Registry databases, are accessible to the 'Users' group that has low privileges on a device. These low permissions were confirmed by BleepingComputer on a fully patched Windows 10 20H2 device, as shown below. File permissions on the SAM file With these low file permissions, a threat actor with limited privileges on a device can extract the NTLM hashed passwords for all accounts on a device and use those hashes in pass-the-hash attacks to gain elevated privileges. As the Registry files, such as the SAM file, are always in use by the operating system, when you attempt to access the file, you will receive an access violation as the files are open and locked by another program. Cannot access the open SAM file However, as the Registry files, including the SAM, are usually backed up by the Windows shadow volume copies, Lykkegaard says you can access the files through shadow volumes without an access violation. For example, threat actors can use the following Win32 device namespace path for shadow volume copies below to access the SAM file by any user on the computer. \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\Windows\System32\config\SAM Using these low and incorrect file permissions, along with shadow volume copies of the files, Security researcher and Mimikatz creator Benjamin Delpy has told BleepingComputer that you could easily steal an elevated account's NTLM hashed password to gain higher privileges. This attack is demonstrated in the video below created by Delpy and shared with BleepingComputer that shows Mimikatz using an NTLM hash to gain debug privileges. In addition to stealing NTLM hashes and elevating privileges, Delpy told BleepingComputer that this low privileged access could allow for further attacks, such as Silver Ticket attacks. It is unclear why Microsoft changed the permissions on the Registry to allow regular users to read the files. However, Will Dormann, a vulnerability analyst for CERT/CC, and SANS author Jeff McJunkin, said Microsoft introduced the permission changes in Windows 10 1809. Strangely, Dormann stated that when installing a fresh version of Windows 10 20H2 from June, the loose permissions were not present. Therefore, it is not clear if Microsoft fixed the permission issue when performing a clean installation of Windows but did not fix it when upgrading to new versions. BleepingComputer has reached out to Microsoft for more information but has not heard back at this time. New Windows 10 vulnerability allows anyone to get admin privileges
  25. Microsoft changes course, gives gamers a reason to stick with Windows 10 SDK preview explains what is, isn't Windows 11-exclusive about new load-boosting tech. Enlarge / Microsoft has advertised "Xbox Velocity Architecture" to summarize a range of game-loading boosts for its newest consoles. The upcoming DirectStorage API is primed to bring some of those benefits to Windows PCs, but now that it is spread across two OSes, with varying speed expectations on each, will it have the same impact? Microsoft 37 with 26 posters participating Microsoft's Windows 11 unveiling in June came with announcements across the company's many departments, including a warning from the company's gaming division: you'll need Windows 11 to play games that employ select "next-gen" APIs, particularly the new DirectStorage API. On Friday, the company's DirectX team walked that OS restriction back. "Microsoft is committed to ensuring that when game developers adopt a new API, they can reach as many gamers as possible," DirectX Program Manager Hassan Uraizee writes in explaining that the upcoming DirectStorage API will no longer be Windows 11-exclusive. This statement comes alongside Microsoft's launch of a DirectStorage preview program that will let developers immediately begin testing this feature in intensive 3D software. The API, among other things, redirects I/O calls for 3D graphical assets directly to a computer's GPU. How “full” is “full potential”? Uraizee's post says that one other previously announced DirectStorage pillar, a jump to higher-speed SSD storage, has also moved into "optional" territory. Essentially, Microsoft is now claiming that developers can expect any game-loading pipeline built on DirectStorage to scale down to lower-performing computers while still benefiting from OS-level tweaks like decompressing assets via the GPU—aided largely by DirectX's Agility SDK, which can be dropped into various Windows versions (Win10 version 1909 and higher) and work without expected conflict with other OS elements. Even so, Windows 11's "storage stack upgrades" will be exclusive to that OS, and thus Uraizee says that gamers will want Windows 11 to access the "full potential" of DirectStorage. But one of DirectStorage's implied sales pitches is the ability to design real-time 3D worlds that revolve around a revolutionized I/O approach—one where wide-open landscapes and detailed elements no longer have to be hidden by mid-game trickery (i.e., waiting in an elevator or crawling through a thin passageway). Uraizee's brief explanation doesn't draw a line in the sand regarding how DirectStorage and its Win10 and Win11 variants will or won't factor into such ambitions for PC games. "DirectStorage-enabled games will still run as well as they always have, even on PCs that have older storage hardware (e.g., HDDs)," he writes, but "as well as they always have" is a decidedly last-gen description. Once we see more ambitious console exclusives for the Xbox Series X/S and PlayStation 5, whose specs include aggressive SSD and I/O defaults, we'll see whether Uraizee's optimism will apply to those games' PC ports on slower-storage systems. Either way, this is a big walkback from Microsoft's previous announcements about DirectStorage. Perhaps Microsoft noticed how many interested gamers' PCs failed last month's Windows 11 compatibility test—due either to a lack of solid-state media or a motherboard that failed checks for Trusted Platform Module (TPM)—and scrambled to guarantee that its DirectX 12 Ultimate ambitions aren't further limited. Already, DX12U requires more modern GPUs, including Nvidia's RTX 2000 and 3000 families and AMD's RDNA 2 line, and in a chip-shortage universe, uptake to compatible GPUs has been slow. Microsoft changes course, gives gamers a reason to stick with Windows 10
×
×
  • Create New...