Jump to content

Search the Community

Showing results for tags 'bug'.

  • 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. Microsoft has updated the official Windows 11 Health Dashboard documentation with details about a newly found issue in the latest Windows 11 update. According to the software giant, Windows 11 2022 Update users might experience problems with app freezing when changing IME (Input Method Editor) input modes. Windows IME or Input Method Editor is a built-in tool that allows users to enter text in languages hard to represent on a standard QWERTY keyboard. The Chinese, Japanese, Korean, and other East Asian languages have larger numbers of characters that require customers to use combinations of keys processed and interpreted by the IME. Per Microsoft's findings, turning on, off, or changing input modes causes apps to become unresponsive on Windows 11 2022 Update. The problem does not affect customers with Windows 10 and the initial release of Windows 11. Also, it will not bother you if you only use English or other languages with Latin or Cyrillic scripts. Those who rely on Windows IME can mitigate the problem by installing the freshly released KB5020044 update. It adds some "Moment 2" features to Windows 11 and fixes other non-security issues, like those related to gaming on 22H2. If installing a preview update is not an option, Microsoft says you can workaround the issue by changing the input mode with the IME mode icon in the taskbar. Apps freeze only when using keyboard shortcuts to manage the IME. Microsoft confirms app freezes with IME in Windows 11 2022 Update
  2. Here is another confirmed bug in recent updates for Windows 10 and 11: besides all sorts of problems caused by authentication bugs, users might experience issues using the Direct Access feature after temporarily losing network connectivity or transitioning between Wi-Fi networks or access points. Direct Access is a feature that allows Windows users to access corporate networks without traditional VPN connections, providing a constant connection to organizations whenever there is working internet. Microsoft makes it clear that the bug with Direct Access does not affect the ability to use other remote access solutions, such as VPN or Always On VPN (Microsoft recommends using the latter on systems with Windows 10 and newer). Microsoft has applied the Known Issue Rollback (KIR) tool to mitigate the problem with Direct Access feature on Windows 10 and 11. As usual, KIR requires about 24 hours to reach the affected devices on non-managed devices. Enteprise-managed computers can get the fix faster using special group policies from the official Windows documentation. The software giant says the Direct Access bug affects client Windows 10 and 11 versions (LTSC 2019, 20H2, and newer), Windows Server 2019, and 2022. Regular home users with active VPN connections and apps for remote access are unaffected. Microsoft confirms problems with Direct Access on Windows 11 and 10
  3. Nvidia has released today its latest WHQL-certified Windows DCH display driver with version 526.47. The new driver is game ready for Sackboy: A Big Adventure, Victoria 3 and WRC Generations – The FIA WRC Official Game. Aside from game support, it brings DLSS 3 support to F1 2022. The DLSS 3 update lands in a few days time on October 31st. In the release notes for this driver, Nvidia has also acknowledged the false reading issue currently plaguing its cards. The company believes it is related to an incompatibility problem with the Desktop Window Manager (DWM) and has provided a workaround. The company has also resolved a few bugs. They are: [Cyberpunk 2077] In game map may display corruption [3829994] Dell XPS 9560 may crash and reboot when using desktop applications [3737715] [RTX 30 series] Lower performance in Minecraft Java Edition [3702953] 165Hz refresh rate option not availlable on Samsung Odyssey Ark monitor [3840122] When using two or more monitors, GeForce Experience Shadowplay/Gamestream may select the wrong monitor [200633408] Videos played back in Microsoft Edge may appear green if NVIDIA Image Scaling is enabled upon resuming from hibernate or booting with fastboot. [3624218] Here are the open issues that remain: Toggling HDR on and off in-game causes game stability issues when non-native resolution is used.[3624030] [DirectX 12] Shadowplay recordings may appear over exposed when Use HDR is enabled from the Windows display settings. [200742937] Monitor may briefly flicker on waking from display sleep if DSR/DLDSR is enabled. [3592260] Maxon - Cinema4D + Redshift3D vidmemory allocations cause TDR or Driver Crash [3659104] RedCine-X Pro potential crash while working with effects during video playback [3809401] Desktop Window Manager (dwm.exe) service may report higher GPU usage on some RTX 30- series configurations [3830387] Workaround: disable Hardware-accelerated GPU Scheduling from the Windows Settings VTube Studio may crash to black screen [3838158] Temporary workaround: Delete the file VTube Studio Data\Plugins\x86 64\GPUManagementPlugin.dll [Forza Horizon 5] Some PC configurations may see rainbow like artifacts in game after extended gameplay [3685123] [Daz Studio] Application crashes after updating to latest driver when trying to run simulation [3838022] [Call of Duty: Modern Warfare II] Flashing corruption can be seen randomly while playing the game. [3835099] When both NVIDIA Low Latency Mode is set to Ultra in the NVIDIA Control Panel and NVIDIA Reflex is set to “Boost + Enabled” in a game, the graphics card will not return to idle clock speeds after exiting the game until the PC is rebooted. [3846389] The Nvidia GeForce 526.47 WHQL Game Ready driver is now available for download through the GeForce Experience app, while standalone links can be found below. The release notes are here (PDF). Desktop GPUs: GeForce Game Ready Driver Download: Windows 11, 10 – DCH (US version) Notebook GPUs: GeForce Game Ready Driver Download: Windows 11, 10 – DCH (US version) Nvidia confirms Windows 11 Task Manager reporting is broken with latest 526.47 driver
  4. It is not unusual for Windows updates to be buggy, and the situation is especially pronounced when we are dealing with a massive feature update like the one for the recent Windows 11 22H2. Among the several issues, one of the more glaring ones has been related to Nvidia graphics cards. And the issues aren't exclusive to the new RTX 4000 Ada Lovelace GPUs, either, as older gen cards are also affected. In case you missed it, users began reporting about performance related bugs and problems almost immediately as Windows 11 22H2 hit general availability. Nvidia quickly released an emergency software update to fix the issue. The update was later bundled with the Game Ready driver. Since display drivers are cumulative, the fix is also present in the latest 522.25 update as well. However, even with the said fix in place, users and even reviewers are still finding issues. Some of them are related to performance of course, as the gaming performance can still be all over the place due to poor frametime and framepacing, something which has been a bug on 22H2 either due to Windows 11 itself, or for some incompatibility problem in Nvidia's own drivers. Aside from performance issues, there is another bug where the 3D readings for Nvidia GPUs in Task Manager is seemingly upside down. An idle graphics card will show close to 100% usage for its 3D section even though the card is actually doing nothing. This bug came to our attention when one of Neowin's readers, SoLiD_MasteR reported about it on one of the news stories. Here is a screenshot of the issue posted by a Reddit user, washed_king_jos on their RTX 3070 Ti: As you can see above, the apparent 3D usage for the GPU is 96% though the card itself is clearly idling at a pleasantly cool temperature of 39 °C. The readings appear to be inverted, which means the actual usage in this capture instance may be 4%. Nvidia readings on Task Manager are all topsy turvy in Windows 11 22H2
  5. In today's episode of "What Windows 11 22H2 breaks this time," we have the broken Windows Hello authentication system. According to the latest update from the software giant, users could experience problems with Windows Hello sign-in methods, such as face recognition, fingerprint, or regular PIN. Microsoft says the bug affects customers who have set up Windows Hello before installing the Windows 11 2022 Update (or 22H2). The problem should not bother you if you have enabled Windows Hello after getting to the latest Windows 11 version. Botched Windows Hello does not mean affected customers are fully locked-out of their systems. Windows 11 falls back to Microsoft Account or offline account passwords if Windows Hello is unavailable. Still, Microsoft has applied a compatibility hold to protect customers from the frustrating experience. Affected systems will not get the Windows 11 2022 Update until Microsoft provides a permanent fix. You can bypass the problem by installing KB5017389, the first optional cumulative update for Windows 11 22H2. Microsoft says it will remove the safeguard in mid-October 2022, and you can expect the bugfix to arrive in today's Patch Tuesday update. Broken Windows Hello has joined the ever-growing list of known issues in Microsoft's latest operating system. The company has already confirmed performance downgrades in solid-state drives, broken provisioning, crippled printers, problems with Remote Desktops, and gaming issues caused by the new security features. Therefore, if your computer sees no update and cannot get to Windows 11 22H2 "naturally," you better not force the update and stay on Windows 10 or the initial version of Windows 11. Source: Microsoft Microsoft confirms Windows 11 22H2 breaks Windows Hello
  6. As reports had suggested, Microsoft begun rolling out Windows 11, version 22H2 last month. And as one would expect, it hasn't been a complete smooth sailing. For example, many users reported that the update was failing with an error code "0x800f0806". Interestingly, one of our Neowin members managed to figure out a workaround for the problem. Then there are the usual suspects, like printer problems, where a new printer policy was leading to printers being not detected post the 2022 Update. Another related issue led Microsoft to block the update altogether on affected devices. Following that, Microsoft issued a word of warning to IT admins as it discovered that provisioning is currently broken for Windows 11 22H2. In the meantime, the Redmond firm re-visited another issue which led to massive slow-downs in large file copy speeds when done remotely on a 22H2 system. The company said that around 40% lower speeds were being observed. However, users are reporting even worse performance hits. ivicask, who is a regular on the Microsoft tech community forums, claims they're seeing over a 100% performance hit: I would just want to correct 40% slower statement from Ned, im seeing way over 100% difference on setups like 10gb NICs (5gb/s vs 2gb/s) difference, or on SMB multi channel setups with multiple gigabit NICs. While the issue was initially thought to be affecting the Server Message Block (SMB) protocol mainly, Microsoft's Ned Pyle has now confirmed that their initial suspicion was a bit off. Apparently, the problem exists somewhere else: I can't share too many details yet, but we know exactly where it is getting slower in Kernel, nothing to do with SMB or compression. Regardless, Microsoft has provided a detailed workaround in case you are struggling against this problem: Symptom Workaround Copying large multiple gigabyte (GB) files might take longer than expected to finish on Windows 11, version 22H2. You are more likely to experience this issue copying files to Windows 11, version 22H2 from a network share via Server Message Block (SMB) but local file copy might also be affected. Windows devices used by consumers in their home or small offices are not likely to be affected by this issue. To mitigate this issue, you can use file copy tools that do not use cache manager (buffered I/O). This can be done by using the built-in command-line tools listed below: robocopy \\someserver\someshare c:\somefolder somefile.img /J or xcopy \\someserver\someshare c:\somefolder /J We are working on a resolution and will provide an update in an upcoming release. We will keep you posted. The Windows 11 22H2 file copy performance bug could be far worse than first thought
  7. Thousands of Firefox users reported crashes of the Firefox web browser to Mozilla, the maker of the browser. The, often angry user comments, all reported that Firefox had crashed out of a sudden on Windows machines. Mozilla started its investigation and discovered, rather quickly, that Avast software was the culprit. Avast, maker of security products, is a popular choice when it comes to third-party antivirus protections on Windows. It became clear quickly that the issue affected all versions of Microsoft's Windows operating system on which certain versions of the Avast Antivirus software were installed on. The issue in Avast software was critical, as it was the causing the top 5 desktop browser crashes on Windows on release, and the top 20 desktop browser crashes on release. Antivirus applications are notorious for interfering with legitimate applications on Windows machines. In this particular case, it appears that Avast versions 18.0.1473.0 and older are causing the crashes of the Firefox web browser. Mozilla decided to block Avast's DLL files using Firefox's DLL blocklist file to stop the crashes from happening. An update to Firefox 105.0.3 is available already, which includes the new entry to the blocklist. The new version of Firefox Stable addresses just the one issue. According to it, the crashes may also be caused by AVG Antivirus software. Avast acquired AVG in 2016 and has since then brought antivirus products closer together. Mitigated frequent crashes for Windows users with Avast or AVG Antivirus software installed Firefox users who run Avast or AVG software may want to update the Firefox web browser to the latest stable release right away. They may also want to check for Avast or AVG updates as well to make sure the latest versions of the security applications are run on the system. Mozilla employee Gabriele Svelto has another suggestion: uninstall Avast or AVG products. Firefox users may select Menu > Help > About Firefox to update. If the browser does not open, they may download Firefox from the Mozilla website instead to install the update. Closing Words Bugs or false positives are common, and they may lead to crashes of third-party applications and other issues. Often, users of these programs blame the innocent third-party application and not the real culprit, the antivirus solution, when crashes or other issues occur. Issues like these may see numerous users migrate to another browser, with a good chance that they are lost for the foreseeable future. Mozilla reacted very quickly to the issue, which is commendable. Now You: when was the last time you experienced crashes in programs that you use? Mozilla rushes to address an Avast bug that causes crashes in Firefox
  8. Microsoft has confirmed another issue in the recently released Windows 11 2022 Update. Ned Pyle, Principal Program Manager in the Windows Server engineering group, has published a post on the Tech Community forums, warning users about performance degradation when copying large files from a remote computer to a system running the latest version of Windows 11. According to Ned, Windows 11 2022 Update users can experience up to 40% less throughput over SMB when copying large files weighing several gigabytes or more. The bug does not affect the initial release of Windows 11, so those sticking to the previous release will not experience issues with copying from a remote computer. Interestingly, the bug is not exclusive to SMB, which means users might notice performance dips even when copying local files. While Microsoft is busy investigating the problem and figuring out the fix, affected customers can use robocopy or xcopy with the /J parameter to restore the lost performance. Expect to hear from Microsoft about this problem soon. Microsoft recently acknowledged another problem exclusive to the latest Windows 11 release. The company said users with specific printer drivers might lose some features, such as color, two-sided printing, paper size settings, etc. The affected devices will not get the update until Microsoft has a permanent fix. Microsoft confirms performance degradation in Windows 11 22H2 when copying large files
  9. As reports had suggested, Microsoft released Windows 11 version 22H2 to the general availability channel on September 20. You can read all about the new exciting stuff in these articles here. A few days before that, some users received the 2022 feature update early with new devices. The machines were shipping with build 22621.521 (KB5017321) which was indeed the 22H2 update as confirmed later by Microsoft. However, like it's usually the case, the new update is not without its issues though. Last night, we reported about a problem related to updating to this new feature update. The update process is failing for many with the error code "0x800f0806". Luckily, there are a couple of fixes available that we have outlined in this article. For those that have managed to update, there are other problems for users who have Nvidia graphics cards in their systems. There are reports of unstable framerates and stuttering, and lower than typical CPU usage in games. Users across Reddit and Microsoft forums have echoed similar sentiments. Reddit user ChoPT says the issues were present in insider builds too. They write: I was having serious performance hitches, both on the desktop and especially in gaming (this completely broke gsync as well). Drops to ~30fps randomly from ~120, in non-graphically intense tests. Screen tearing like crazy. I have a VERY powerful system (12700k, 3080 Ti, DDR5 ram), so it's not a hardware issue, and I tried turning all the new graphics settings off as well, so it wasn't that either. [..] I'm a pretty big gamer, so this is unfortunately a deal-breaker until it can be fixed. But the performance issues on the desktop also just made everything feel a bit sluggish. These same problems were present in the insider build I tried months ago, and I am very disappointed they are still present at release. Rolled back, and all the problems went away. Another user Nahett77 says their CPU usage dropped from around 80% down to just around 5%: I have been experiencing insane stuttering in games. My CPU usage in games have dropped down significantly, in some from 80% to 5%. Just went back to the last update and my in game experience is much better. Fortunately for those experiencing such problems, Nvidia has confirmed that it is looking into the matter. Manuel Guzman, Software QA at the company has requested for more feedback from the affected users on the Reddit thread. In case you are reading the article and are facing similar issues, you can provide feedback to Nvidia using this form. Source: Reddit (1, 2, 3), Microsoft forum via How-To Geek Edit: Updated with quotes from users experiencing the issues for additional context. Windows 11 22H2 apparently causing problems on Nvidia graphics cards
  10. As reports had suggested, Microsoft released Windows 11 version 22H2 to the general availability channel on September 20. You can read all about the new exciting stuff in these articles here. A few days before that, some users received the 2022 feature update early with new devices. The machines were shipping with build 22621.521 (KB5017321) which was indeed the 22H2 update as confirmed later by Microsoft. Since release, many, however, are reporting of problems and issues when trying to update to Windows 11 22H2. According to these reports, the update is failing with an error code "0x800f0806". This is apparently happening when trying to do an in-place upgrade via Windows Update in Settings due to some compatibility issue or something similar. A clean install though is seemingly working fine. Thankfully, a Reddit user by the name rap1021 has found a solution to the issue. Apparently, manually downloading and installing the update seems to bypass this problem caused by trying to do an upgrade via Windows Update. To do so, simply head over to Microsoft's Update Catalog website and download the update. Other known solutions like running the "sfc /scannow" via Command Prompt, or resetting the Windows Update mechanism don't appear to be working either according to the same user, and manually downloading the update is seemingly the best bet. Another user, CusiDawgs, on the same thread says the latest version of Windows 11 Installation Assistant also resolves the problem. You can download it from Microsoft's official website here. Source: rap1021 (Reddit) via CusiDawgs (Reddit) Edit: Looks like one of our Neowin members "kiddingguy" had also noticed the issue and came up with the workaround. So here's a shoutout to them! Windows 11 22H2 update failing with error 0x800f0806, here are potential fixes
  11. Malwarebytes has addressed an issue that prevented users from accessing websites and services hosted on the google.com domain, including Google search and Youtube. According to a large number of reports from people affected by this, their browsers were prevented from accessing Google sites after Malwarebytes flagged and blocked them as malicious. As many shared, they were swarmed by a barrage of malware notifications, all pointing to various websites on google.com subdomains tagged as containing malware. "Malwarebytes pushed a bad update it seems. I couldn't access any Google websites and was getting constant malware notifications from Google websites," one impacted customer said. "I turned off real time web protection and now it works fine. Any device I have that doesn't have Malwarebytes (Android phone, other windows devices) wasn't affected." Malwarebytes quickly picked up on what was going on and explained in a tweet published in response to the stream of user reports that this was caused by a temporary issue affecting a web filtering component module in the company's security products. "We are aware of a temporary issue with the web filtering component of our product that may be blocking certain domains, including http://google.com," the company said. Malwarebytes blocking google.com (Twitter) False positive fix rolling out Malwarebytes also provided a workaround for impacted users, which required them to disable the buggy module by opening Malwarebytes and toggling off the Web Protection option in the Real Time Protection card. One hour, the anti-malware software vendor revealed that it had resolved the issue and all customers' software would update on its own to remove the false positive errors. "The issue is now resolved, and the update should happen automatically," Malwarebytes told affected users via Twitter. "If you are still experiencing issues, please ensure the Malwarebytes client is updated to the latest version." However, according to some reports, the issue might still impact enterprise customers since some endpoints still see Google's domains being blocked. The most likely reason is that the update still has to finish rolling out to Malwarebytes' entire customer base. Malwarebytes mistakenly blocks Google, YouTube for malware
  12. The Windows 10 KB5017308 cumulative update released this Patch Tuesday is reportedly causing Group Policy Object (GPO) issues, according to admin reports. According to reports shared across multiple social networks and on Microsoft's online community, GPO file operations will no longer work as they can no longer create or copy shortcuts correctly after installing KB5017308. "Specifically, we copy a batch file into public\documents, then copy a shortcut to the current user's desktop to run it," one admin said on Reddit. "Since the update, the icons are not transferring over for the shortcut (i.e they are blank icons now) and the batch file is actually empty when copied over." Another one confirmed this issue on the Microsoft Community website, saying that all shortcuts created by GPO are "created empty with 0 bytes and no info where shortcut "leads" to." While Microsoft is yet to officially acknowledge the issue and provide a fix or a workaround, multiple Windows admins have reported that un-checking the "Run in user security context" option on the affected GPOs will address the shortcut creation problems. Installing the Windows 10 KB5017308 update (BleepingComputer) Others have also suggested a more radical fix that requires manually uninstalling and hiding the KB5017308 cumulative update. "To remove the LCU after installing the combined SSU and LCU package, use the DISM/Remove-Package command line option with the LCU package name as the argument. You can find the package name by using this command: DISM /online /get-packages," Microsoft says. "Running Windows Update Standalone Installer (wusa.exe) with the /uninstall switch on the combined package will not work because the combined package contains the SSU. You cannot remove the SSU from the system after installation." However, it's important to mention that, since Microsoft bundles all security fixes into a single update, removing KB5017308 may resolve the bug but will also remove all fixes for recently patched security vulnerabilities. KB5017308 also failing to install Another seemingly widespread problem encountered after deploying KB5017308 is affecting Windows 10 systems that will hang on reboot after installation with an 0x800F0845 added to the event log. "Ever since that update was downloaded the machine hangs on the required reboot after the install. I have disabled updates until I can find a fix. I've tried to download the update and install manually but get the same results," a user report reads. Those affected say that the automatic rollback will only trigger after rebooting the affected systems twice in a row. While downloading the update from the Microsoft Update Catalog and installing it manually usually fixes issues where the updates can't be deployed, users who tried it said that, in this case, they encountered the same reboot hang bug. The KB5017308 cumulative update was released on Tuesday to resolve bugs and address security vulnerabilities on systems running Windows 10 20H2, 21H1, and 21H2. This Windows 10 update is mandatory and will automatically be installed by Windows Update during the servicing window. H/T Günter Born Windows 10 KB5017308 causing issues with Group Policy settings
  13. It's fair to say Microsoft hasn't had the best record when it comes to keeping up with times. From the infamous Y2K or the Millennium bug, to the more recent Y2K22 Exchange server glitch and daylight savings time (DST) issue. Eitan Caspi, a LinkedIn user, recently found a similar bug in Microsoft's Outlook wherein a glitch in the "Go To Date" option takes users back to 1930. This behaviour has made Caspi humorously call this glitch "Future to the back". In their post, the steps to replicate the bug have been given: Verify you use the latest Outlook 365 (may be relevant to other versions as well, I didn't try) Go to the Calendar section Use the keyboard combination of "CTRL+G" (Go To Date) I use a date format of dd/mm/yy, so I typed 31.12.29 (or 31/12/29, . or / will do the same). Please do the same and submit. You will be transferred to the the last day of December 2029, cool, that's fine. It is just for reference Now do almost the same, but this time type the next day of the day from above - type 1.1.30 and submit. POW…! You are now at the first day of January 1930… Basically, the Go To Date option seems to be working only till 2029, and trying to navigate to 2030 takes us back a 100 years to 1930. Via: The Register Bizarre Microsoft Outlook glitch takes you back to the depressing 1930
  14. Microsoft has officially confirmed what some users have been reporting for several days. According to a notification published in the official Windows Health Dashboard information, the recent Security update for Secure Boot DBX (KB5012170) causes computers to boot into BitLocker recovery, prompting users to enter their recovery keys. Besides officially acknowledging this weird bug, Microsoft revealed temporary workarounds for affected and yet-to-be affected systems: Those who have already installed KB5012170 and are now getting BitLocker recovery prompts must enter their BitLocker recovery keys. The official guidance is available in the documentation from Microsoft. Those who are yet to install KB5012170 or restart their systems after applying the update can temporarily suspend BitLocker to bypass the bug: Run Command Prompt as Administrator and enter the Manage-bde -protectors -disable %systemdrive% -rebootcount 2 command. Install KB5012170. Restart your computer two times. BitLocker should be back running after the second restart. You can verify its status using the Manage-bde -protectors -Enable %systemdrive% command. Interestingly, Microsoft says the BitLocker bug does not affect all computers. According to Microsoft, users who have successfully restarted their computers twice after applying KB5012170 will not get the BitLocker recovery prompt. Also, the bug does not bother Windows 10 systems, only Windows 11. Another issue KB5012170 is causing is the 0x800f0922 error when users attempt to install the Security update for Secure Boot DBX. As Microsoft investigates the problem, customers can bypass the bug by updating UEFI to the latest versions. Microsoft confirms BitLocker issues in the latest Windows updates
  15. Microsoft has notified Windows 10 and 11 users about a new known issue in the operating system. According to the Windows Health Dashboard documentation, Windows currently struggles with opening specific XPS documents (Microsoft's alternative to Adobe PDF, which has nothing to do with the Dell XPS lineup). Besides the inability to open XPS and OXPS documents in non-English languages, XPS Viewer stops responding and starts hogging CPU and RAM resources until it crashes upon reaching 2.5GB of RAM usage. After installing KB5014666 or later updates, XPS Viewer might be unable to open XML Paper Specification (XPS) documents in some non-English languages, including some Japanese and Chinese character encodings. This issue affects both XML Paper Specification (XPS) and Open XML Paper Specification (OXPS) files. When encountering this issue, you may receive an error, "This page cannot be displayed" within XPS Viewer or it might stop responding and have high CPU usage with continually increasing memory usage. When the error is encountered, if XPS Viewer is not closed it might reach up to 2.5GB of memory usage before closing unexpectedly. Microsoft says the problem originates from KB5014666 and KB5014666 (Windows 10 19044.1806 and Windows 11 22000.778), released on June 26 and 28. The company is busy investigating the bug and promises to release a fix in the upcoming releases. Unfortunately, there are no temporary workarounds. It is worth noting that the problem will not bother the vast majority of regular Windows 10 consumers. Apart from the fact that the XPS format failed to gain traction, Microsoft stopped bundling Windows 10 with XPS Viewer in version 1803. Still, you can install XPS Viewer as an optional Windows component in the Settings app. The broken XPS Viewer app is not the only known problem Microsoft is investigating. The company recently confirmed that Windows updates released after June 28 might cause issues with USB printers. Microsoft confirms problems with opening XPS documents in Windows 10 and 11
  16. In a post on Reddit, Microsoft representatives have confirmed that the Edge browser is currently experiencing problems with syncing Collections across devices. Many users have reported issues, such as the inability to toggle on or off collections sync in the profile settings and changes not appearing on other devices. The good news is that Microsoft is aware of the issues, and the needed bugfixes are coming soon. According to an Edge Community Manager on Reddit, Microsoft will fix the broken Collection sync button in the next Android release. Other issues, such as changes in Collections not appearing on other devices, should be gone in Edge 104, which is due to arrive early next month. Besides fixing the known bugs, the Microsoft Edge team is busy adding new features to Collections in the browser. The software giant recently announced several new productivity-focused capabilities, such as collaborative editing, images and video support, and a feed with ads recommended content. Do you use the Collections features in Microsoft Edge? If so, are you experiencing sync issues? Microsoft confirms Collections sync problems in Edge
  17. Microsoft has confirmed that KB5014666, released on June 28, 2022 (the one adding several new printing features), causes printing issues on systems with Windows 10. According to the company, the bug causes Windows 10 to display duplicates of a single printer with a "Copy1" suffix. More importantly, applications referring to a specific printer by name cannot print a document. The software giant says it is working on fixing the problem in a future update, and, meanwhile, users can file a feedback report and try temporary workarounds: Open the Settings app, navigate to “Bluetooth & devices”, and select “Printers & scanners” If there appears to be a duplicate installation of an existing printer, such as with suffix "Copy1", confirm if printing works for this printer. This printer should operate as expected. If there is a need to use the original printer installation and not the duplicate, right-click the duplicate printer, select "Printer properties" and select the "Ports" tab. Observe the port in use. Open "Printer properties" on the original printer and select the "Ports" tab. From the list displayed, select the port option in use by the duplicate printer. If this original printer works normally, the duplicate copy printer can be removed. If the steps above do not restore the broken printing capabilities, Microsoft recommends attempting the following: Update the print driver for your device. For guidance, see Install the latest driver for your printer. If you already have the latest driver, consult the printer Manufacturer’s web site for any device firmware updates. If you are still having issues, uninstalling and reinstalling your printer might help. Turn off your printer and disconnect any cables. Open the Settings app, navigate to “Bluetooth & devices”, and select “Printers & scanners.” Select the affected printer and select the "Remove Device" option. Restart your device. Turn on your printer and reconnect it to your device. According to the Windows Health Dashboard, the new printing bug affects only Windows 10 21H2, 21H1, and 20H2 (including Windows Server). On the Windows 11 side, Microsoft recently confirmed problems with the Start menu after the updates the company released on June 23, 2022. Microsoft confirms Windows 10 updates break USB printers
  18. Earlier today, Microsoft issued an advisory regarding a problem that is causing the Start menu on certain Windows 11 PCs to not open. The company has determined that the KB5014668 update (Build 22000.778) and newer releases are affected. It writes: After installing KB5014668 or later updates, we have received reports that a small number of devices might be unable to open the Start menu. On affected devices, clicking or selecting the Start button, or using the Windows key on your keyboard might have no effect. The company has issued the following workaround as it has advised individuals and organizations to perform a Known Issue Rollback (KIR). Resolution: This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue can resolve it by installing and configuring a special Group Policy. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> KB5014668 220721_04201 Known Issue Rollback -> Windows 11 (original release). For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback. Group Policy downloads with Group Policy name: Download for Windows 11, version 21H2 - KB5014668 220721_04201 Known Issue Rollback The KB5014668 update has been plagued with issues. For example, it was meant to fix an OS upgrade fail bug but ironically itself started causing installation fails. Microsoft has also been having Start menu related issues for a while.This month's Patch Tuesday update broke Start menu access; and a few days ago, the firm released Beta channel build 22622.436 which resolved a Start crash on Insider builds. Microsoft confirms Windows 11 Start menu fails to start, issues workaround
  19. Microsoft released Windows 11 build 25158 to Insiders flighting the Windows 11 Dev Channel recently. The new build brings some interesting new features like various Search styles, and more widget options, as well as the usual general improvements and bug fixes. However, with the addition of the new widget options, it looks like the weather reporting and reading has broken on the latest build. The issue was noticed first by Twitter user Xeno. As you can see in the images below, the weather and temperature readings have apparently wildly fluctuated, with Windows saying it's a heat wave at 64 °F (equivalent to 17.78 °C). Meanwhile, on the Celsius scale, it says it's cloudy. Although the Build 25158 has a few known issues in the widget, none of them seem to acknowledge this one: [Widgets] [NEW] Notification badge number may appear misaligned on the taskbar. [NEW] In some cases, the notification banner for some badging will not appear in the widgets board. We’re working on the fix for an issue causing Widgets preferences (temperature units and pinned widgets) to unexpectedly get reset to default. However, Senior Product Manager of Microsoft, Brandon LeBlanc, in a response to Xeno has confirmed that it is indeed a bug, and it is being looked at. Brandon has also added that there can be a brief pause or freeze in the weather readings when the system is resumed from sleep. Windows 11 build 25158: Microsoft confirms weather readings are all over the place
  20. Microsoft is investigating user reports that MS Access runtime applications stop opening after installing this month's Patch Tuesday Office/Access security updates. According to customers' complaints on Microsoft's official community website and Reddit, July's cumulative updates trigger this issue for MS Access 2016 and MS Access 2013 are KB5002112 and KB5002121, respectively. "The Access product team is investigating this issue. Thank you for the report, we will update soon," Shane Groff, a software design engineer at Microsoft, said in a Microsoft Answers thread. The company also acknowledged this as a known issue in the support documents detailing the two buggy Microsoft Office security updates. "After this update is installed, when you open an ACCDE or MDE file in Microsoft Access, you might receive an error message that states, 'Requested type library or wizard is not a VBA project'," the advisory reads. "Additionally, the file won't open. Microsoft is researching this issue and will update this article when a fix is available." Affected users report that the bug affects MS Access compiled databases (e.g., MDE, ACCDE), including on MS Access in Office365. Remove buggy updates to address this known issue While Microsoft did not provide a workaround or a temporary fix until they released an update to address this known issue, customers who reported being impacted said that removing the offending updates would resolve the problems. However, keep in mind that uninstalling these security updates will also remove security updates addressing a medium severity Microsoft Office security feature bypass vulnerability (CVE-2022-33632). This is because Microsoft bundles all security fixes into a single update. Removing the cumulative updates may fix the bugs but will also remove fixes for security flaws patched during the June Patch Tuesday. Therefore, uninstalling these problematic updates should be a last resort option and only done if absolutely necessary. To make sure that the updates won't be reinstalled, you need to download and run the "Show or hide updates" troubleshooter from here, click on 'Next,' select the update that you want to hide, and restart your device if prompted. Microsoft investigates July updates breaking Access applications
  21. Microsoft has updated its Office documentation with a notification about a newly found issue in Outlook. According to the company's findings, Outlook Desktop users on Windows 11 might encounter problems with built-in search. The program might not display the most recent emails in the search results. The bug affects POP, IMAP, and offline Exchange accounts, which use the local Windows Search service to index and locate emails. Microsoft says Microsoft 365 and connected Exchange accounts are unaffected. Microsoft is currently investigating the new bug. Meanwhile, users can bypass the problem using a temporary hack. Microsoft recommends disabling Windows Desktop Search to force Outlook to switch to its built-in search service. Here is how to do that: Press Win + R and type regedit. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows and select Edit > New > Key. Rename the new key to Windows Search. Select the Windows Search Key and click Edit > New > DWORD Value. Rename the new value to PreventIndexingOutlook and press Enter. Open the PreventIndexingOutlook value and change its value data to 1. Use 0 to revert the changes. Click Ok to save the changes. Close Registry Editor and restart Outlook. Interestingly, this is not the first time Microsoft recommends users to disable Windows Search Service to fix problems in Outlook Desktop. A similar situation happened last year to those willing to pull the trigger and try the first preview builds of Windows 11. You can learn more about the bug in the official documentation. Microsoft warns about search issues in Outlook on Windows 11
  22. For those looking forward to a new Windows Insider build today, Microsoft has confirmed it isn't happening as the company is busy "chasing down" a bug in the upcoming Dev Channel flight, likely Build 25156. Although the announcement wasn't made by the Windows Insider Twitter account, Microsft's Senior Program Manager Brandon LeBlanc revealed this on Twitter in response to a tweet by user WZor. Their exchange, which is a slightly humorous one, is given below: We do wonder what kind of bug the developer team has caught as nothing more about it was said. We will likely know it soon enough when the build is out next week in the known issues list if Microsoft isn't able to fix it. Microsoft confirms it's chasing down a bug in the Windows 11 23H2 Dev Channel
  23. Microsoft says it addressed a known issue that was causing all Microsoft Edge tabs running IE (Internet Explorer) mode to stop responding if one of the opened sites displayed a modal dialog box after issuing a window.focus call. The IE mode problems affect devices running Windows 11 (version 21H2), Windows 10 (versions 20H2, 221H1, and 21H2), and Windows Server 2022 after installing the KB5014019, KB5014023, and KB5014021 optional preview cumulative updates. After deploying these Windows updates, "IE mode tabs in Microsoft Edge might stop responding when a site displays a modal dialog box," Microsoft explained. "A modal dialog box is a form or dialog box which requires the user to respond before continuing or interacting with other portions of the webpage or app." Microsoft has fixed this issue using Known Issue Rollback (KIR), a Windows capability designed to help revert buggy Windows non-security fixes delivered via Windows Update. After being pushed using KIR, the fix reaches all consumer and non-managed business devices within a day. However, customers can also speed up the fix rollout to their systems by restarting impacted Windows devices. "Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices," Microsoft added. Group policies available for enterprise To resolve this IE mode tab issue in Microsoft Edge on affected enterprise-managed devices, admins have to install and configure a specific KIR Group Policy associated with the systems' Windows version. You can download the two Group Policies by clicking the links below: KB5014019 Known Issue Rollback — Windows 11 KB5014023 Known Issue Rollback — Windows 10 The step-by-step procedure to deploy a Known Issue Rollback via Group Policy requires opening the Group Policy Editor and navigating to either Local Computer Policy or the Domain policy on your domain controller to choose the Windows version you want to target. Detailed information on how to deploy and configure KIR Group Policies is available on Microsoft's support website. Last week, Microsoft also resolved known Wi-Fi hotspot issues and Microsoft 365 sign-in issues triggered by the June 2022 Windows updates. Microsoft: Recent Windows updates caused Edge freeze issues
  24. Living in 2022 with a Windows device that has only 4GB of RAM and a puny 64GB of eMMC storage is not something you can call fun. Still, devices with such modest specs can do light PC work as long as a firmware update does not entirely brick them. Unfortunately, that is what happened to the owners of the original Surface Go. A thread on Microsoft support forums reveals numerous reports from the first-gen Surface Go owners with complaints about a firmware update bricking their devices. In early May 2022, Microsoft released a set of patches that threw multiple devices into an unbootable state. Upon attempting to start their base-config Surface Go, users see a "No Bootable Device" error. As of now, there is no way to bypass the problem, which means affected devices will remain bricked until Microsoft provides a workaround. Interestingly, this is not the first time a firmware update bricks Surface computers. In February, a new storage driver did the same to the third-gen Surface Book, and Microsoft quickly pulled the update. For some reason, the botched firmware update for the first-gen Surface Go is still available for download. If you have the original Surface Go with eMMC storage, pause Windows Update and do not install the latest firmware. You cannot uninstall firmware on Surface devices, so disabling Windows Update is the only way to ensure your tablet will not download the problematic driver. Fortunately, it appears that Microsoft is aware of the issue. One of the affected users reported that Microsoft Business Support let them know that the company's engineers are investigating the problem. Still, there is no information on when the needed fix will be available or how the affected users will have to restore their now-dead Surface Go tablets. Latest firmware update bricks base configs of Surface Go
  25. After much speculation, Microsoft confirmed that Windows 11 Insider build 22621 was the RTM build. And soon after that, the company released Build 22621 to the Release Preview channel too. And while the build only listed a couple of known issues, the release appears to have brought back a Windows 11 security related bug that was already fixed once. The issue was brought to our attention by one of our Neowin forum members nekrosoft13 who noticed that several of their PCs were being shown the message "Standard hardware security not supported" on the Device security page in Windows Security settings even though their system does apparently meets the necessary requirements. Image: nekrosoft13 (Neowin forum) The issue doesn't appear to be a one-off case here as several other users are also complaining about this Build 22621 bug on Feedback Hub on a previous thread. As mentioned above, the bug isn't new and Microsoft had fixed the issue earlier with build 22000.100 like the company promised in the Feedback Hub thread. If you're wondering what the requirements for Standard hardware security are, Microsoft has defined these as following: Your device meets the requirements for standard hardware security This means your device supports memory integrity and core isolation and also has: TPM 2.0 (also referred to as your security processor) Secure boot enabled DEP (Data Execution Prevention) UEFI MAT (Memory Attributes Table) However, when a user PC doesn't meet one or more of these requirements, the Standard hardware security not supported feature is displayed, though in the case of this bug, it is apparently being shown even when the criteria are met. Windows 11 22H2 build 22621 bug shows "hardware security not supported" on supported PCs
×
×
  • Create New...