NewApp Digest
search bot

DISM

Windows 11 KB5121003 update breaks Teams and Outlook on ARM devices
Winsage
August 20, 2026

Windows 11 KB5121003 update breaks Teams and Outlook on ARM devices

Following the KB5121003 Patch Tuesday update, users on ARM64 devices like Surface Laptop 7 and Surface Pro 11 are facing startup failures with Microsoft Teams and New Outlook, while traditional Win32 applications remain unaffected. Reverting to the previous update restores functionality, but recovery options have not resolved the issue. The root cause appears to be broken AppModel Runtime package states, leading to dependency issues and 0x80073CFC errors. This problem is similar to one caused by update KB5094126 earlier this year. Creating new Windows profiles offers only temporary relief, and administrators are advised to pause the deployment of KB5121003 on ARM devices until the issue is addressed.
How to Troubleshoot an Unresponsive Windows 11 Taskbar and Start Button
Winsage
August 20, 2026

How to Troubleshoot an Unresponsive Windows 11 Taskbar and Start Button

An unresponsive Taskbar or Start button in Windows 11 can be caused by various issues, including a problematic version of Windows 11 (25h2), frozen Windows Explorer, incomplete or corrupted updates, graphics driver issues, and interference from third-party extensions. To troubleshoot the unresponsiveness, users can try the following steps: 1. Lock the PC using Win + L and then unlock it. 2. Check hardware to ensure no buttons on the mouse or keys on the keyboard are stuck. 3. Restart Windows Explorer via Task Manager by selecting "Windows Explorer" and choosing "Restart Task." 4. Clear notifications by accessing the System Tray and selecting "Clear all" or using the "Do Not Disturb" button. 5. Update Windows by navigating to "Settings," then "Windows Update," and checking for updates. 6. Run SFC and DISM checks by opening Command Prompt as Admin and executing the commands "DISM.exe /Online /Cleanup-image /RestoreHealth" followed by "sfc /scannow," then restart the PC.
Windows 11 is fully removing a legacy tool that malware and ransomware have abused for years, meet WMIC
Winsage
August 17, 2026

Windows 11 is fully removing a legacy tool that malware and ransomware have abused for years, meet WMIC

Microsoft is removing the Windows Management Instrumentation Command-line (WMIC) from Windows 11 to enhance security by eliminating a tool that has been exploited by malware and ransomware. WMIC will not be included in Windows 11 versions 24H2, 25H2, and 26H2, with complete removal scheduled for the August 2026 Patch Tuesday update. The decision to remove WMIC is based on the availability of more secure alternatives like PowerShell. WMIC has been a vector for attacks, allowing threat actors to disable antivirus solutions and access sensitive data. Microsoft has phased out WMIC since 2021, encouraging users to transition to modern tools while continuing to support the underlying Windows Management Instrumentation (WMI) infrastructure.
Why Does Windows Explorer Use So Much Memory?
Winsage
July 28, 2026

Why Does Windows Explorer Use So Much Memory?

A user on Reddit reported that Windows Explorer was using over 21GB of memory, which can cause performance issues on systems with less than 8GB of RAM. One cause of excessive memory consumption is third-party shell extensions, which can be identified by booting into Safe Mode. A tool called ShellExView can help locate problematic extensions. To create a system restore point, users can press Win + R, type systempropertiesprotection.exe, click Create, enter a description, and click Create. Windows Explorer may also retain large caches of temporary data, leading to high memory usage. To clear temporary files, users can press Win + I, navigate to System > Storage > Temporary files, check the relevant boxes, and click Remove files. They can also manually clean the thumbnail and icon cache by deleting specific files in the %localappdata% directory. Corrupted system files can contribute to high memory usage, and users can run DISM and SFC tools to repair these files by accessing the Terminal (admin) and executing the commands DISM.exe /Online /Cleanup-image /Restorehealth and sfc /scannow.
Microsoft: Some Windows PCs fail to install latest monthly updates
Winsage
June 10, 2026

Microsoft: Some Windows PCs fail to install latest monthly updates

Microsoft has warned customers about potential installation complications with the latest monthly updates on certain Windows devices upgraded to Windows 11 versions 24H2 or 25H2. Users may encounter error codes 0x80073712 or 0x800f0993 when attempting to install cumulative updates for June 2026. Affected devices include a small fraction of those running Windows 10 versions 22H2 and 21H2, as well as Windows 11 version 23H2. Users may find that updates have failed, and the specified error codes will appear in the Windows Update log files. Microsoft plans to deploy a resolution for unmanaged enterprise devices and personal PCs after a system restart, with no new devices in these categories affected starting from May 19, 2026. For impacted devices, Microsoft has released specific updates as part of its June 2026 Patch Tuesday to prevent the issue. However, the problem will not be fixed for systems already upgraded to Windows 11 versions 24H2 or 25H2, and users are advised to remove the affected package using a command in an elevated Command Prompt. If this does not resolve the issue, users may need to perform a Windows 11 in-place upgrade. Microsoft has previously addressed similar challenges related to Windows update installations, including issues from the March 2026 non-security preview update and the January 2026 optional non-security preview updates.
Windows 11 New Build Adds Screen Tint, Voice Isolation, and Plug-and-Play Braille Display Support
Winsage
May 25, 2026

Windows 11 New Build Adds Screen Tint, Voice Isolation, and Plug-and-Play Braille Display Support

Microsoft has released the Windows 11 Insider Experimental Preview Build 26300.8497, introducing new accessibility features including a Screen Tint option, Voice Isolation in Voice Access, and upgrades to Magnifier and Narrator. The Screen Tint setting allows users to apply a color overlay to reduce screen brightness, beneficial for those with eye strain. It can be accessed in the Settings menu under Accessibility and operates independently of the Night Light feature. The update also enhances Narrator by adding support for plug-and-play braille displays that comply with the HID standard, allowing immediate connection via USB without additional drivers. Compatible braille models include Orbit Reader 20, Orbit Slate 340, Freedom Scientific Focus 40, and APH Mantis Q40. The build addresses several bugs, including a crash in explorer.exe, duplicate Energy Saver quick settings, and issues with audio muting on certain devices. Build 26300.8497 is being rolled out to the Windows 11 Insider Experimental channel, with no announcement yet on availability for the broader user base.
Fix: You'll need a new app to open this windowsdefender link
Tech Optimizer
April 26, 2026

Fix: You’ll need a new app to open this windowsdefender link

The message “You’ll need a new app to open this windowsdefender link” indicates issues with the Windows operating system when the Windows Security app fails to launch via the windowsdefender protocol. This can prevent users from accessing the security dashboard, despite Microsoft Defender continuing to operate in the background. Common scenarios leading to this error include clicking on Virus & Threat Protection, trying to open Windows Security from the Start menu, interacting with a Defender notification, or following the uninstallation of third-party antivirus software. Root causes may include corrupted Windows Security app registration, damaged system files, third-party antivirus interference, misconfiguration of the Security Center service, or malware interference. To resolve the issue, users can verify that required services are running, repair system files using SFC and DISM, re-register the Windows Security app, check for third-party antivirus conflicts, and perform a repair installation of Windows. Specific steps include checking the status of the Security Center and Microsoft Defender Antivirus Service, executing repair commands in CMD, re-registering the Windows Security app using PowerShell, uninstalling third-party antivirus software, and performing an in-place upgrade if necessary.
Windows Server 2025 Update KB5082063: Error 0x80073712 due to Media Player; and Error 0x800F0983
Winsage
April 18, 2026

Windows Server 2025 Update KB5082063: Error 0x80073712 due to Media Player; and Error 0x800F0983

Cumulative update KB508206, released on April 14, 2024, for Windows Server 2025, is causing installation failures for some administrators. Error code 0x800F0983 has been acknowledged by Microsoft as an issue related to the update process, while error code 0x80073712 has been linked to the legacy Windows Media Player application. Reports indicate that the installation of KB5082063 is problematic, particularly on systems configured in German, with users experiencing persistent failures despite attempts to use repair commands. The installation issues may be related to missing files associated with the Media Player language packs, affecting various language configurations.
What to do when device settings don't migrate to Windows 11
Winsage
April 17, 2026

What to do when device settings don’t migrate to Windows 11

On October 10, 2025, Microsoft ceased support for Windows 10, ending technical assistance, feature updates, and security updates. Organizations are required to transition to Windows 11. During the migration, IT administrators may face errors indicating that certain device settings were not successfully migrated, which can disrupt user experience. Causes of these errors include outdated or incompatible device drivers, failing physical components, incompatible software, restrictive group policies, missing registry keys, and interference from third-party tools. Affected devices may malfunction, impacting productivity. IT teams can troubleshoot these issues by restarting computers, identifying problematic devices using Device Manager, verifying and updating device drivers, checking physical devices, ensuring the operating environment is up to date, utilizing Microsoft command-line utilities, and performing clean boots or system restores if necessary.
Search