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 acknowledges the blurry News and Interests text issue on Windows 10 Earlier this year, Microsoft introduced News and Interests, a feature that allowed Windows 10 users to access weather, news, traffic updates and more directly from the taskbar. Just last month, Microsoft started rolling out the News and Interests feature to all the Windows 10 users. However, soon after the update was released, users started complaining about the blurry text in News and Interests on the taskbar. Earlier today, Microsoft updated its Windows 10 Health Dashboard page to acknowledge the bug. The company wrote: Certain display configurations might cause blurry text on the news and interests button in the Windows taskbar. The company also noted that it is working on a fix which will be available in an "upcoming release". However, it did not specify the display configurations that are affected by the bug or when can users expect a patch. In the meantime, users can navigate to Settings > System > Display and set the recommended Scale and Layout. Furthermore, they can also switch News and Interests to 'icon only' which will hide the text and will act as a temporary workaround for the problem. If you are not happy with the feature then you can follow our guide to turn off the News and Interests widget permanently. Microsoft acknowledges the blurry News and Interests text issue on Windows 10
  2. Microsoft Teams hit by a bug, wants users to select a certificate [Update] Microsoft Teams seems to be experiencing a bug since this morning. A recent update seems to have caused a "Select a certificate" prompt to be displayed to Teams users before they can use the software. The issue shows up when the service tries to reach us-prod.asyncgw.teams.microsoft.com while signing into the service. The prompt displays to users even before they can log in to use the software. Microsoft has acknowledged the bug and is tracking the issue under the 'TM261228' advisory, where the company said: "We've determined a recent deployment, designed to improve service performance, is inadvertently causing impact. We're reverting the update while we monitor the affected environment to validate that it resolves the issue." Microsoft Teams users in Brazil, Costa Rica, APAC, EMEA, and EU are reported to be receiving the errors. However, Microsoft says only those users served through the infrastructure in North America are affected. Some users have been able to use the service by restarting the Microsoft Teams client. Update: Microsoft has tweeted that it has reverted the update that caused the issue and can confirm that the service is restored and functional. Source: Microsoft via Bleeping Computer Microsoft Teams hit by a bug, wants users to select a certificate [Update]
  3. Windows 10 KB5003214 update causes taskbar display glitches The latest Windows 10 2004, 20H2, and 21H1 preview update is causing display issues and glitches on the taskbar's system tray. Last week, Microsoft released the optional Window 10 KB5003214 preview update so that users and the enterprise can test the fixes coming in the mandatory June 2021 Patch Tuesday updates. This update also enables the new Windows 10 News and Interests taskbar news feed for all users of Windows 10 2004 and later. Since installing this update, numerous users report that the system tray in the Windows 10 taskbar began having display glitches where tray icons disappear, get pushed to the right, overlay each other, or get pushed off the edge of the screen. "I'm experiencing an issue that I've traced to the new "News and interests" taskbar feature. I got this feature recently - within the last few weeks, I don't recall exactly because I shut it off immediately - and things were fine," a user posted on Reddit. "But after a few updates yesterday (21H1, KB5003214, KB5003254), the notification area in the far right edge of the taskbar began behaving strangely." An example of these display glitches is shown below, where you can see the system tray icons all overlaying each other in a mess. System tray display glitches Source: Reddit After users experimented with different settings, it was determined that the bug is caused by disabling the News and Interests widget on the taskbar. Once disabled and a new system tray icon is shown, it triggers the glitch. Once you enable the News and Interests widget again on the taskbar, the icons begin to display correctly. Windows 10 users affected by this bug found that it could be fixed by uninstalling the KB5003214 preview update, but unless Microsoft fixes the issue before June 8th's Patch Tuesday, all users will be faced with this issue. H/T WindowsLatest Windows 10 KB5003214 update causes taskbar display glitches
  4. Microsoft Outlook bug prevents viewing or creating email worldwide A Microsoft Outlook update released today for the desktop client introduced bugs that prevent users from creating or viewing mail. Today, Microsoft released Outlook version 2104 build 13929.20372, and after installing the update, users of the click-to-run desktop client found that they could no longer properly view emails or create new ones. When attempting to view an email, instead of seeing the entire message body, they only see a small portion or a single line of the email message, as shown below. Missing Outlook email content Source: BleepingComputer To make it even more frustrating, when creating a new email message, every time you press enter, all the previously written content will be removed, as shown below. Outlook email text disappearing when you press enter Source: BleepingComputer The Microsoft 365 Status Twitter account has tweeted that they are investigating an issue with "email message visibility in Outlook," and that Outlook on the Web is unaffected. In an incident status message in the Microsoft 365 Admin Center titled 'EX255650: Issue affecting viewing email content in Outlook', Microsoft suggests users use web and mobile clients until the issue is resolved. Title: Issue affecting viewing email content in Outlook User Impact: Users may be unable to view email message content within Outlook. More info: Initial reports indicate that Outlook on the web is unaffected and users with access to Outlook on the web can view email messages there while we work on a solution. Current status: We're gathering and analyzing data in an effort to isolate the cause of impact. Initial reports indicate that impact is specific to the Outlook client and users with access to other protocols, such as Outlook on the web or the Outlook mobile app, can view message content in those platforms as a potential workaround. Scope of impact: This issue could affect any user attempting to view an email message in the Outlook client. How to fix the Microsoft Outlook issues If you are experiencing this issue in Microsoft Outlook, users have reported that you can fix the bug by rolling back to a previous Microsoft Outlook version. BleepingComputer has tested this method, and it resolved the problems in our Outlook desktop client. Method 1: Roll back Microsoft Office to latest April 2021 release To roll back to the April 23rd, 2021, release and fix the Microsoft Outlook problems, please follow these steps: Open a command prompt by clicking on the Start Menu and typing CMD. When the 'Command Prompt' result appears, click on it. In the command prompt type cd "C:\Program Files\Common Files\microsoft shared\ClickToRun" and press enter. You will now be in the ClickToRun folder. Type officec2rclient.exe /update user updatetoversion=16.0.13901.20462 and press enter. Entering commands in Command Prompt Microsoft Office will now download the specified version of Microsoft Office and roll back to that previous version. Please be patient as this may take a few minutes or longer, depending on your computer and Internet connection speed. Rolling back Microsoft Office to the previous version When the updates are finished installing, you will be shown a screen stating 'Updates were installed.' You can press the Close button on this screen. Microsoft Office updates were installed Microsoft Outlook will now be rolled back to the previous version, and you should be able to start Microsoft Outlook again. You can now close the Command Prompt by clicking on the X button. Please let us know if this works for you. This is a developing story. Source: Microsoft Outlook bug prevents viewing or creating email worldwide
  5. SDK Bug Lets Attackers Spy on User’s Video Calls Across Dating, Healthcare Apps Apps like eHarmony and MeetMe are affected by a flaw in the Agora toolkit that went unpatched for eight months, researchers discovered. A vulnerability in an SDK that allows users to make video calls in apps like eHarmony, Plenty of Fish, MeetMe and Skout allows threat actors to spy on private calls without the user knowing. Researchers discovered the flaw, CVE-2020-25605, in a video-calling SDK from a Santa Clara, Calif.-based company called Agora while doing a security audit last year of personal robot called “temi,” which uses the toolkit. Agora provides developer tools and building blocks for providing real-time engagement in apps, and documentation and code repositories for its SDKs are available online. Healthcare apps such as Talkspace, Practo and Dr. First’s Backline, among various others, also use the SDK for their call technology. SDK Bug Could Have Impacted Millions Due to its shared use in a number of popular apps, the flaw has the potential to affect “millions–potentially billions–of users,” reported Douglas McKee, principal engineer and senior security researcher at McAfee Advanced Threat Research (ATR), on Wednesday. McKee said he did not find evidence of the bug is being exploited in the wild. The flaw makes it easy for third parties to access details about setting up video calls from within the SDK across various apps due to their unencrypted, cleartext transmission. This paves the way for remote attackers to “obtain access to audio and video of any ongoing Agora video call through observation of cleartext network traffic,” according to the vulnerability’s CVE description. Researchers reported this research to Agora.io on April 20, 2020. The flaw remained unpatched for about eight months until Dec. 17, 2020 when the company released a new SDK, version 3.2.1, “which mitigated the vulnerability and eliminated the corresponding threat to users,” McKee said. Researchers first were alerted to an issue when, during their analysis of the temi ecosystem, they found a hardcoded key in the Android app that pairs with the temi robot. Upon further exploration, they found a connection to the Agora SDK through “detailed logging” by developers to the Agora.io dashboard, McKee said. Upon examination of the Agora video SDK, researchers discovered that it allows information to be sent in plaintext across the network to initiate a video call. They then ran tests using sample apps from Agora to see if third parties could leverage this scenario to spy on a user. SDK Bug Allows Attackers to Circumvent Encryption What they discovered through a series of steps is that they can, a scenario that affects various apps using the SDK, according to McKee. Further, threat actors can hijack key details about calls being made from within apps even if encryption is enabled on the app, he said. The first step for an attacker to exploit the vulnerability is to identify the proper network traffic he or she wants to target. ATR achieved this by building a network layer in less than 50 lines of code using a Python framework called Scapy “to help easily identify the traffic the attacker cares about,” McKee explained. “This was done by reviewing the video call traffic and reverse-engineering the protocol,” he said. In this way researchers were able to sniff network traffic to gather information pertaining to a call of interest and then launch their own Agora video applications to join the call, “completely unnoticed by normal users,” McKee wrote. While developers do have the option in the Agora SDK to encrypt the call, key details about the calls are still sent in plaintext, allowing attackers to acquire these values and use the ID of the associated app “to host their own calls at the cost of the app developer,” McKee explained. However, if developers encrypt calls using the SDK, attackers can’t view video or hear audio of the call, he said. Still, while this encryption is available, it’s not widely adopted, McKee added, “making this mitigation largely impractical” for developers. Other Apps Impacted by Faulty SDK In fact, in addition to temi, researchers examined a cross-section of apps on Google Play that use Agora—including MeetMe, Skout and Nimo TV—and found that all four of the applications have hardcoded App IDs that allow access to call details and do not enable encryption. “Even though the encryption functions are being called, the application developers are actually disabling the encryption based on this documentation,” McKee explained. “Without encryption enabled and the setup information passed in cleartext, an attacker can spy on a very large range of users.” Agora did not immediately respond to an email request for comment sent by Threatpost on Thursday. ATR said the company “was very receptive and responsive to receiving” information about the vulnerability, and that after testing the SDK they “can confirm it fully mitigates CVE-2020-25605.” Source: SDK Bug Lets Attackers Spy on User’s Video Calls Across Dating, Healthcare Apps
  6. Google Photos Videos Were Shared With Strangers Google's Takeout service was designed to let people download their data, but accidentally sent videos from Google Photos accounts to strangers. Google has confirmed videos saved in your Google Photos account could have been sent to a stranger because of a "technical issue." As reported by 9to5Google, the issue was rooted in Google's Takeout service which is designed to let people download their data. However, from Nov. 21 to Nov. 25 last year those backups could have had videos that "incorrectly exported to unrelated users' archives." Even though some videos could have been shared with other people, Google has not been specific as to which videos were shared. Instead, the tech giant says that "one or more videos in your Google Photos account was affected by this issue." In a statement, Google said: "We are notifying people about a bug that may have affected users who used Google Takeout to export their Google Photos content between November 21 and November 25. These users may have received either an incomplete archive, or videos—not photos—that were not theirs. We fixed the underlying issue and have conducted an in-depth analysis to help prevent this from ever happening again. We are very sorry this happened." Google also says that the issue affected less than 0.01 percent of Photos users attempting Takeouts, and no other product was affected. However, since Google Photos has over one billion users, even such a small percentage means around 100,000 people potentially had their videos shared with strangers. Source: Google Photos Videos Were Shared With Strangers
  7. New Docker Container Escape Bug Affects Microsoft Azure Functions Cybersecurity researcher Paul Litvak today disclosed an unpatched vulnerability in Microsoft Azure Functions that could be used by an attacker to escalate privileges and escape the Docker container used for hosting them. The findings come as part of Intezer Lab's investigations into the Azure compute infrastructure. Following disclosure to Microsoft, the Windows maker is said to have "determined that the vulnerability has no security impact on Function users, since the host itself is still protected by another defense boundary against the elevated position we reached in the container host." Azure Functions, analogous to Amazon AWS Lambda, is a serverless solution that allows users to run event-triggered code without having to provision or manage infrastructure explicitly while simultaneously making it possible to scale and allocate compute and resources based on demand. By incorporating Docker into the mix, it makes it possible for developers to easily deploy and run Azure Functions either in the cloud or on-premises. Since the trigger code is an event (e.g., an HTTP request) that is configured to call an Azure Function, the researchers first created an HTTP trigger to gain a foothold over the Function container, using it to find sockets belonging to processes with "root" privileges. From there, one such privileged process associated with a "Mesh" binary was identified to contain a flaw that could be exploited to grant the "app" user that runs the above Function root permissions. While the Mesh binary in itself had little to no documentation to explain its purpose, Intezer researchers found references to it in a public Docker image, which they used to reverse engineer and achieve privilege escalation. In the final step, the extended privileges assigned to the container (using the "--privileged" flag) were abused to escape the Docker container and run an arbitrary command on the host. Intezer has also released a proof-of-concept (PoC) exploit code on GitHub to probe the Docker host environment. "Instances like this underscore that vulnerabilities are sometimes out of the cloud user's control," Intezer Labs researchers said. "Attackers can find a way inside through vulnerable third-party software. "It's critical that you have protection measures in place to detect and terminate when the attacker executes unauthorized code in your production environment. This Zero Trust mentality is even echoed by Microsoft." Source: New Docker Container Escape Bug Affects Microsoft Azure Functions
  8. Some M1 Mac users reporting screensaver takeover bug Including me Photo by Vjeran Pavic / The Verge I picked up a new MacBook Air with Apple’s M1 chip, and I’ve absolutely loved it so far. It’s really speedy and the battery is fantastic. But I’ve been dealing with one nagging issue. Every once in a while, for reasons that I haven’t been able to figure out, a screensaver will suddenly take over the entire computer — despite the fact that I never use a screensaver. And frustratingly, the screensaver renders my laptop inoperable until I completely close the screen and reopen it. It seems I’m not the only one seeing this bug, according to this MacRumors article. Others have shared similar issues with M1-equipped MacBook Airs, Pros, and Minis on MacRumors’ forums, Reddit (in a few threads), and Apple’s support forums. And one user on MacRumors said they’ve seen the bug on their 16-inch MacBook Pro, which has an Intel chip, so perhaps this is a problem with macOS Big Sur. Here’s a video of the bug, shared by MacRumors forum member dawideksl: Many people reporting the issue in this Reddit thread say they have multiple accounts on the same computer. And for what it’s worth, I’ve set up two accounts on my MacBook Air. One user on Apple’s support forums disabled Fast User Switching and said they weren’t seeing the screensaver, so perhaps that’s a workaround until Apple addresses the bug. Apple didn’t immediately reply to a request for comment. Some M1 Mac users reporting screensaver takeover bug
  9. Windows 10 bug crashes your PC when you access this location A bug in Windows 10 causes the operating system to crash with a Blue Screen of Death simply by opening a certain path in a browser's address bar or using other Windows commands. Last week, BleepingComputer learned of two bugs disclosed on Twitter by a Windows security researcher that can be abused by attackers in various attacks. The first bug allows an unprivileged user or program to enter a single command that causes an NTFS volume to become marked as corrupted. While chkdsk resolved this issue in many tests, one of our tests showed that the command caused corruption on a hard drive that prevented Windows from starting. Today, we look at the second bug that causes Windows 10 to perform a BSOD crash by merely attempting to open an unusual path. Opening this path causes a BSOD Since October, Windows security researcher Jonas Lykkegaard has tweeted numerous times about a path that would immediately cause Windows 10 to crash and display a BSOD when entered into the Chrome address bar. When developers want to interact with Windows devices directly, they can pass a Win32 device namespace path as an argument to various Windows programming functions. For example, this allows an application to interact directly with a physical disk without going through the file system. Lykkegaard told BleepingComputer that he discovered the following Win32 device namespace path for the 'console multiplexer driver' that he believes is used for 'kernel / usermode ipc.' When opening the path in various ways, even from low-privileged users, it would cause Windows 10 to crash. \\.\globalroot\device\condrv\kernelconnect When connecting to this device, developers are expected to pass along the 'attach' extended attribute to communicate with the device properly. CDCreateKernlConnection showing the 'attach' extended attribute Lykkegaard discovered if you try to connect to the path without passing the attribute due to improper error checking, it will cause an exception that causes a Blue Screen of Death (BSOD) crash in Windows 10. Even worse, low privileged Windows users can attempt to connect to the device using this path, making it easy for any program executed on a computer to crash Windows 10. In our tests, we have confirmed this bug to be present on Windows 10 version 1709 and later. BleepingComputer was unable to test it in earlier versions. BleepingComputer reached out to Microsoft last week to learn if they knew of the bug already and if they would fix the bug. “Microsoft has a customer commitment to investigate reported security issues and we will provide updates for impacted devices as soon as possible,” a Microsoft spokesperson told BleepingComputer. Threat actors can abuse the bug While it has not been determined if this bug could be exploited for remote code execution or elevation privilege, in its current form, it can be used as a denial of service attack on a computer. Lykkegaard shared with BleepingComputer a Windows URL file (.url) with a setting pointing to \\.\globalroot\device\condrv\kernelconnect. When the file is downloaded, Windows 10 would try to render the URL file's icon from the problematic path and automatically crash Windows 10. BSOD caused by accessing the \\.\globalroot\device\condrv\kernelconnect BleepingComputer has since found numerous other ways to exploit this bug, including methods to cause BSODs automatically on Windows login. In a real-life scenario, this bug could be abused by threat actors who have access to a network and want to cover their trail during an attack. If they have admin credentials, they could remotely execute a command that accesses this path on all of the Windows 10 devices on a network to cause them to crash. The havoc caused on the network could delay investigations or prevent administrative controls from detecting an attack on a particular computer. In 2017, a similar attack scenario was used by threat actors during a bank heist on the Far Eastern International Bank (FEIB) in Taiwan. In that attack, the threat actors deployed the Hermes ransomware on the network to delay investigations into the attack. Source: Windows 10 bug crashes your PC when you access this location
  10. Windows 10 build 21292.1010 breaks x64 emulation on ARM PCs As of mid-December, Windows Insiders with ARM64 PCs were able to run x64 apps in emulation, opening up the PCs to the rest of the Windows ecosystem. Yesterday, however, the team released a cumulative update for the latest Dev channel build, and as it turns out, the update breaks the feature, so you might want to skip it. The update in question is KB4601937, and the blog post has been updated to day, "After installing Build 21292.1010 (KB4601937), x64 emulation on ARM PCs will not work. There is an issue with the way the update is installed that breaks this functionality. As a workaround, you can uninstall KB4601937 to get x64 emulation working again on your ARM PC." This cumulative update was introduced as something that includes nothing that's new. According to Microsoft, it only exists to test out the servicing pipeline, meaning that the company just wants to make sure, as it does periodically, that it hasn't broken the ability to ship cumulative updates. But being an update with no features, it would be reasonable to expect that it's low-risk, and that it wouldn't break. The update should be easy enough to roll back, if you're experiencing issues. From Windows Update, go to 'View update history', and select 'Uninstall updates'. Windows 10 build 21292.1010 breaks x64 emulation on ARM PCs
  11. Microsoft fixes Secure Boot bug allowing Windows rootkit installation Microsoft has fixed a security feature bypass vulnerability in Secure Boot that allows attackers to compromise the operating system’s booting process even when Secure Boot is enabled. Secure Boot blocks untrusted operating systems bootloaders on computers with Unified Extensible Firmware Interface (UEFI) firmware and a Trusted Platform Module (TPM) chip to help prevent rootkits from loading during the OS startup process. Rootkits can be used by threat actors to inject malicious code into a computer's UEFI firmware, to replace the operating system's bootloader, to replace parts of the Windows kernel, or camouflage maliciously crafted drivers are legitimate Windows drivers. The security feature bypass flaw, tracked as CVE-2020-0689, has a publicly available exploit code that works during most exploitation attempts which require running a specially crafted application. "An attacker who successfully exploited the vulnerability might bypass secure boot and load untrusted software," Microsoft explains. Affected Windows versions include multiple Windows 10 releases (from v1607 to v1909), Windows 8.1, Windows Server 2012 R2, and Windows Server 2012. How to install the security update To block untrusted or known vulnerable third-party bootloaders when Secure Boot is toggled on, Windows devices with UEFI firmware use the Secure Boot Forbidden Signature Database (DBX). The KB4535680 security update released by Microsoft as part of the January 2021 Patch Tuesday addresses the vulnerability by blocking known vulnerable third-party UEFI modules (bootloaders) to the DBX. Users have to install this standalone security update in addition to the normal security update to block attacks designed to exploit this Secure Boot vulnerability. If automatic updates are enabled on the computer, the security update will be installed automatically, without user intervention needed. However, on systems where updates need to be installed manually, you will be required to first download KB4535680 for their platform from the Microsoft Update Catalog. Next, you will have to make sure that a specific Servicing Stack Update is installed before deploying the standalone security update (you can find the list here). If you also need to manually install the January 2021 Security Updates, the three updates should be installed in the following order: Servicing Stack Update Standalone Secure Boot Update listed in this CVE January 2021 Security Update On systems where Windows Defender Credential Guard (Virtual Secure Mode) is also enabled, installing the KB4535680 standalone update will require two additional reboots. Microsoft also released guidance for applying Secure Boot DBX updates after the disclosure of the BootHole GRUB bootloader vulnerability in July 2020 which also allows for Secure Boot bypass. The company added at the time that it "plans to push an update to Windows Update to address" the BootHole vulnerability in 2021. Source: Microsoft fixes Secure Boot bug allowing Windows rootkit installation
  12. Cyberpunk 2077 reportedly has a nasty save game corruption bug on PC Big-time crafters beware (Image credit: CD Projekt Red) There’s now evidence that Cyberpunk 2077 on PC is affected by one of the worst kinds of bug – a save game corruption gremlin. As Tom’s Hardware spotted, apparently larger saved games (over 8MB) can be plagued with the possibility of going bad, and this might affect those who really get into the crafting side of Cyberpunk 2077 – seeing as that’s a major cause of the file size becoming larger. This complaint from PC gamers surfaced on CD Projekt Red’s own forums and via Reddit, with one post doing a good bit of digging and comparing, coming to the conclusion that crafting and 8MB+ save game file sizes are to blame. If you get hit by this bug, when trying to load a game, you’ll see an error message instead: “Saved data is damaged and cannot be loaded”. According to some of the reports from affected gamers, once the save game file starts to creep up towards 8MB, you may experience long loading times that involve staring at a black screen for 30 seconds or so. If this is happening, consider it a warning that if your save continues to expand, you may experience a corruption issue (so perhaps lay off on the crafting – although that’s hardly an ideal solution). While the developer is apparently aware of a problem here, according to Tom’s, there has been no official announcement of the bug – although a moderator on the CD Projekt Red forums has offered a bit of advice in terms of backing up saves and repairing the game, although the feedback to the usefulness of those measures is rather negative. Furthermore, you should consider re-enabling any mods you might have been using that you’ve disabled. Apparently this could cause problems with save data, as the moderator states: “Any modification to the game can leave reference data that will corrupt the game’s ability to read the save files unless the modifications are also running.” GOG.com has further acknowledged this issue in a support center troubleshooting post, which advises those affected that: “Unfortunately the save is damaged and can’t be recovered. Please use an older save file to continue playing and try to keep a lower amount of items and crafting materials.” Stadia woes The bug has also been observed on Google Stadia saves as well as with the PC version of Cyberpunk 2077, so streamers, you’ve been warned. Seemingly the console versions aren’t affected, but of course they have their own major issues as we’ve seen. Indeed, the PC version is in far better shape than either the PS4 or Xbox One flavors, generally speaking when it comes to performance and polish, but a save game corruption popping up is a distinct blow on PC to say the least. Whether hotfix 1.05, which just arrived for consoles and is planned to land on the PC soon, will do anything, we shall just have to see, but nothing is mentioned in the patch notes. In the aforementioned support post, GOG.com noted: “The save file size limit might be increased in one of the future patches, but the corrupted files will remain that way.” If nothing is done with version 1.05 on PC, the next patch is due in January – unless the developer decides to release a standalone hotfix of some kind. Whatever the case, this is a nasty bug which really does need to be dealt with sooner rather than later. Cyberpunk 2077 reportedly has a nasty save game corruption bug on PC
  13. Another iOS 14 bug resets default app settings for the email and browser apps One of the major new features in iOS 14 is the ability to set third-party apps as the default for the email and browser apps. However, a bug in the OS ended up resetting the app defaults to Apple’s offerings every time the device was restarted. The Cupertino giant issued a fix for the issue with iOS 14.0.1. As it turns out, the problem might persist, this time resetting the defaults every time the user-defined apps are updated via the App Store. Twitter user David Clarke posted a video of the behavior (spotted by The Verge) where an update to the Gmail app results in the default email app switching to Apple Mail. The setting for the default browser app supposedly behaves similarly, resetting any defaults set by users. The problem seems to be present on the latest iOS 14.1 update released yesterday. Considering that the issue has been confirmed to affect both the email and browser defaults, it is less likely that the behavior is caused by the apps itself and not the OS. It is possible that the upcoming iOS 14.2 update contains a fix for the problem, though, the release notes for iOS 14.2 Beta 4 do not contain a mention of the issue. For now, users affected by these problems can turn off automatic updates so as to not have to constantly change the defaults every time the apps are updated. Another iOS 14 bug resets default app settings for the email and browser apps
  14. No more distractions WhatsApp’s latest iOS update stops showing an unread notification badge on its app icon for messages you’ve muted. It’s a minor but welcome change that arrived with version 2.19.110 of the iOS app. The change applies for both individual and group chats. The messaging app’s mute feature is invaluable if you want to reduce distractions, particularly if you’re a participant in any large group chats. Before the update, muting a chat would only stop your phone from vibrating and playing a notification sound when it received a new message, while doing nothing about the anxiety-inducing red notification badge placed on the app’s icon on the home screen. The new update only affects iOS users. On Android, meanwhile, WhatsApp has a separate “Show notifications” toggle which you can either tick or untick when you’re muting a chat. Source: WhatsApp fixes the notification badge on muted iOS chats (via The Verge)
  15. Samsung began rolling out Android 10 based One UI 2.0 Beta builds to Galaxy S10 devices early this month amid reports of a possible delay. The successor to Android 9.0 Pie-based One UI is more of an iterative update that brings with it polishes and improvements to existing features along with Android 10-specific features such as the gesture navigation system. However, users that are running the beta builds were in for a surprise when a recent update locked them out of their devices – refusing to accept any authentication methods. Users running recent One UI 2.0 Beta builds began reporting that they were unable to unlock their devices through the way of a pin, password or biometrics after restarting the phones. The only preventive measure for those that still had access to their device was to disable all lock screen authentication methods through the Lock Screen settings. For those that were locked out, one of the ways to circumvent the issue was by deleting all authentication methods through Samsung’s Find My Mobile service (provided it was enabled). However, if that service was not enabled, there was no other option but to reset the device and roll back to Android 9 Pie through Smart Switch. Some users also reported that they have been unable to set a pin/password even after rolling back to Pie. Considering the severity of the issue, the firm was quick to release a hotfix for the problem that is now rolling out to all One UI 2.0 Beta users. The critical update package is about 131MB in size, carrying build number G970FXXU3ZSL and should be available to all S10 variants running the beta software. It should be noted that users that are currently locked out will have to either delete their authentication presets first or roll back and re-join the beta since the device will not initiate the update if the device is locked. Running beta software always brings a few risks with it, so it is best to have one’s device backed up in case something goes wrong. As a precaution for any such issues in the future, you can turn on Find My Mobile from Settings > Biometrics and Security > Find My Mobile. Source: 1. Samsung rolls out hotfix for One UI 2.0 Beta after update locks out users (via Neowin) 2. Critical Galaxy S10 Android 10 beta update out, fixes device lock issue (via SamMobile)
  16. Claps and cheers: Apple stores' carefully managed drama Those ‘geniuses’ in the bright, sleek Apple store are underpaid, overhyped and characters in a well-ma Steve Jobs wanted customers to understand the Apple store “with one sweep of the eye,” as if gods standing on Mount Olympus. Indeed, the outlets seem to speak for themselves. Bright, uncluttered, and clad in glass, they couldn’t contrast more sharply with the big-box labyrinths they were designed to replace. Neither could their profit margins. Since launching in 2001, the instantly recognizable stores have raked in more money – in total and per square foot – than any other retailer on the planet, transforming Apple into the world’s richest company in the process. Yet the very transparency of the Apple store conceals how those profits are made. When we think of “tech”, we rarely think of retail stores, and when we think of “tech workers” we rarely think of the low-waged “geniuses” who staff them. Most media coverage of tech companies encourages us to forget that the vast majority of their employees are not, in fact, coders in Silicon Valley: they’re the suicidal assemblers of your phone, the call-center support staff, the delivery drivers and the smiling shop floor staff who make up the majority of Apple’s workforce. The Apple store was explicitly designed as a brand embassy rather than a dedicated source of technical knowledge. As Ron Johnson, the former Target executive who came up with the concept, told the Harvard Business Review, “People come to the Apple store for the experience – and they’re willing to pay a premium for that … Apple is in the relationship business as much as the computer business.” Johnson and Jobs wanted ambassadors whose ostensible role was not to sell products – uniquely, Apple store employees receive no commission – but to create positive customer sentiment and repair trust in the brand when it broke. That was hard to do if your stuff was lumped in with everyone else’s in a big electronics store, overseen by third-party staff lacking any special expertise or interest in what you wanted to sell. The goal was to take full control of the brand image while humanizing it. The problem, however, was that humans can be rather unruly. Fortunately for Apple, someone had been hard at work fixing that bug. In 1984, a group of professors at Harvard Business School published a book, Managing Human Assets, aimed at updating workplace organization for a new era. The book was based on the first new compulsory course at the Harvard Business School in a generation, launched in 1981. Ron Johnson started his MBA at Harvard the next year, graduating as the book itself was released. Previously, the book argued, labor discipline could be achieved in a relatively straightforward top-down manner, but now it required something else. “The limitations of hierarchy have forced a search for other mechanisms of social control,” the authors said. The mechanisms they proposed consisted, at root, of treating employees as nominal stakeholders in business success, but within narrow limits that would increase rather than challenge shareholder profitability. Johnson put many of these ideas into practice. He found the first cohort of Apple store employees by personally interviewing every manager and offering jobs to upbeat staff working for competitors. He sent the first five managers through the Ritz-Carlton training program to learn concierge skills. Then he developed a training program for the in-house production of “geniuses”. (Jobs reportedly hated the term at first, finding it ridiculous. True to form, he asked his lawyers to apply for a trademark the following day.) How do you create an engaged, happy, knowledgable workforce that can pass, however implausibly, as an entire battalion of geniuses in towns across the country? More importantly, how do you do all of that without the stick of the authoritarian boss or the carrot of a juicy commission? Apple’s solution was to foster a sense of commitment to a higher calling while flattering employees that they were the chosen few to represent it. By counterintuitively raising the bar of admission, crafting a long series of interviews to weed out the mercenary or misanthropic, Johnson soon attracted more applicants than there were posts. Those keen enough to go through the onerous hiring process were almost by definition a better “fit” for the devotional ethos of the brand, far more receptive to the fiction that they weren’t selling things but, in an oft-repeated phrase, “enriching people’s lives”, as if they’d landed a job at a charity. “When people are hired,” Johnson explained, “they feel honored to be on the team, and the team respects them from day one because they’ve made it through the gauntlet. That’s very different from trying to find somebody at the lowest cost who’s available on Saturdays from 8 to 12.” While not the lowest, the cost of these eager staff was still low – relative to industry averages, to the amount they made for the company, and to the $400m that Johnson earned in his seven years at Apple. Lower wages also had another, less obvious effect. As Apple store managers explained to the New York Times, the lack of commissions meant that the job didn’t pay well enough to support those with dependents: older workers were functionally excluded from representing the brand without the need for a formal policy – or the attendant specter of discrimination lawsuits that it would raise. Deploying psychology, not the maximizing calculus of economic rationality (money), allowed Apple to turn hiring and wages into managerial props. The sense of higher calling and flattery doesn’t stop with the hiring process, of course. Make it through the gauntlet and you are “clapped in” by existing workers: given a standing ovation as if receiving a prize. The clapping, according to employees, continues until new hires, perhaps after a confused delay, begin clapping too, graduating from outside spectator to part of the performance – part of the team. Leave the company and you’re “clapped out”. Products are clapped, customers waiting overnight to buy them are clapped, their purchases are clapped, claps are clapped. Clap, clap, clap. “My hands would sting from all the clapping,” said one manager. Claps, cheers, performances of rapturous engagement provided, by design, a ready-mixed social glue to bind teams together, reaffirming both the character of the brand and employees’ cultish devotion to it. It might be expected that Apple store employees are, as their name implies, tech gurus with incredible intellects. But their true role has always been to use emotional guile to sell products. The Genius Training Student Workbook is the vaguely comical title of the manual from which Apple store employees learn their art. Prospective geniuses are taught to use empathetic communication to control customer experience and defuse tension, aiming to make them happy and relax their purse strings. One of the techniques the book teaches is the “three Fs”: feel, felt, found. Here’s an example from the book, meant to be role-played by trainees: Customer: This Mac is just too expensive. Genius: I can see how you’d feel this way. I felt the price was a little high, but I found it’s a real value because of all the built-in software and capabilities. When customers run into trouble with their products, geniuses are encouraged to sympathize, but only by apologizing that customers feel bad, lest they implicate Apple’s products as the source of the trouble. In this gas-lit performance of a “problem free” brand philosophy, many words are actually verboten for staff. Do not use words like crash, hang, bug, or problem, employees are told. Instead say does not respond, stops responding, condition, issue, or situation. Avoid saying incompatible; instead use does not work with. Staff have reported the absurdist dialogues that can result, like when they are not allowed to tell customers that they cannot help even in the most hopeless cases, leading customers into circular conversations with employees able neither to help nor to refuse to do so. Apple’s “geniuses” perform on a stage that’s as carefully managed as they are. Jobs and Johnson wanted to control every aspect of the Apple stores, down to the specific color of the bathroom signs. Almost every detail is trademarked, from stairs to display tables to storage racks. Even the supposedly “intuitive” layout, so obvious that it can be understood by all, is considered unique enough to warrant a suite of intellectual property protections. In part to counter the falling sales volume of a saturated market, Apple has spent the past two years overhauling its stores to work even harder. Potted trees have been added to give a green splash to the signature grey and, in a move so ridiculous it’s almost certain to be a hit, the Genius Bar has been rebranded the “Genius Grove”. Windows are opened to blur the distinction between inside and outside, and the stores are promoted as quasi-public spaces. “We actually don’t call them stores any more,” the new head of retail at Apple, former Burberry executive Angela Ahrendts (2017 salary: $24,216,072), recently told the press. “We call them town squares.” The town square. It’s an almost-quaint symbol of participatory civic life – a world away from the big-box sprawl that characterized the retail imaginary of the late 20th century, or even the digital isolation of the 21st. Apple’s goal has been to create spaces for people to just hang out in, extending the original insight that focusing on everything other than cold hard cash will paradoxically be the best way to rake it in. In Ahrendts’s vision, “the store becomes one with the community”. But the real hope seems to be closer to the opposite, that the community will become one with the store. After Apple recently won the race to surpass a $1tn valuation, CEO Tim Cook emailed staff to explain, “Financial returns are simply the result of Apple’s innovation, putting our products and customers first, and always staying true to our values.” While seductive, this story is, like the Apple store itself, a managed fiction. Apple’s system of operation is less the result of genius than of capture and control. Semiconductors, microprocessors, hard drives, touch screens, the internet and its protocols, GPS: all of these ingredients of Apple’s immense profitability were funded through public dollars channeled into research through the Keynesian institution called the US military. They are the basis of Apple’s products, as the economist Mariana Mazzucato has shown. The company’s extraordinary wealth is not simply a reward for innovation, or the legacy of “innovators” like Steve Jobs. Rather, it flows from the privatization of publicly funded research, mixed with the ability to command the low-wage labor of our Chinese peers, sold by empathetic retailers forbidden from saying “crash”. The profits have been stashed offshore, tax free, repatriated only to enrich those with enough spare cash to invest. But, as the public well from which it has drawn past innovations runs dry, the company’s ability to repeat the success of the iPhone is evaporating. Federal funding for scientific research is in deep decline, and Apple isn’t likely to make up the gap. To keep profitability high, Apple is moving to ever-more-luxury price tags for ever-more-marginal improvements (like the iPhone XS Max) and expanding its ability to extract rent by controlling the creativity of others (through Apple Music or the App Store, both impossible to sign out of without landing in pop-up purgatory). All the while its brand embassies sell a different story with a smile. Source
  17. This new Windows 10 bug could be bad news for gamers Error code 0x803F8001 (Image credit: Shutterstock) Users of the Xbox Game Bar may have noticed a few issues after a recent update of Windows 10, and it seems the latest bug to plague the Microsoft operating system is crashing the Xbox Game Bar on launch, and even completely blocking some users completely. The error message appearing on screen reads 0x803F8001, and appears to be caused by a server-side change made to Windows 10 on November 5. The bug is a global issue and only affects users with Windows 10 version 1809 or later, so if you utilize the Xbox Game Bar and haven't updated your machine yet, it may be best to hold off until the error is resolved No solution yet At the time of writing, there doesn’t appear to be a fix for the issue, with forums filling with user reports and complaints. It also isn’t apparent what’s actually causing the issue, and no official statement from Microsoft has been made. We’ve contacted Microsoft for a response, but until then, this unfortunately looks to be a case of simply waiting it out. Via Windows Latest This new Windows 10 bug could be bad news for gamers
  18. Microsoft warns Windows 10 update breaks Office updates The Windows 10 update bugs are mounting (Image credit: Shutterstock) Microsoft has warned Windows 10 users that recent updates come with a number of bugs. Reportedly, one of the flaws prevents individuals from updating Office products due to a certificate loss issue. After downloading October 2020 Patch Tuesday updates, some Windows 10 users received an error message reading, “Download of Office 365 file failed, error =” when trying to apply the latest Office updates. Microsoft is yet to reveal a workaround for the problem, meaning individuals must uninstall the faulty Windows update, then update Office and then re-install the Windows patch. Microsoft engineer David James tweeted that the issue seems to be caused by the Windows 10 updates generating a certification failure, which prevents Memcm and Configuration Manager from downloading Office updates. Update denied Unfortunately for Microsoft, the Office update error is not the only issue users have been having with its Windows patches recently. There have also been reports of October Windows 10 patches causing File Explorer issues and even the dreaded Blue Screen of Death. Microsoft has not commented on these system crash issues but did admit that system and user certificates could be lost during the update process. “This primarily happens when managed devices are updated using outdated bundles or media through an update management tool such as Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager,” a Microsoft support document explained. “This might also happen when using outdated physical media or ISO images that do not have the latest updates integrated.” Microsoft recommends that users install patches for their operating system using the official Windows Update service, rather than any other method in order to reduce the likelihood of any issue cropping up. Via Windows Latest Microsoft warns Windows 10 update breaks Office updates
  19. Facepalm: It’s been almost two weeks since Microsoft officially ended its extended support for Windows 7, but the Redmond firm is introducing another free update for the OS that fixes a bug it introduced in the final public updates. As reported by The Verge, one of Microsoft’s final free Windows 7 updates—KB4534310—is causing wallpaper problems for some users. After installation, an image can display as black when set to Stretch. The issue only appears to affect stretched wallpapers, fit, fill, tile, or center options still work normally. Microsoft had initially said that the fix would only be available to organizations who pay the expensive Extended Security Updates (ESUs), but it has now decided to offer it for free to everyone running Windows 7 and Windows Server 2008 R2 SP1. While the bug isn’t exactly a major one, the fact Microsoft introduced it just as the company stopped supporting non-paying Windows 7 users is a bad look. Pushing out the fix to everyone will help avoid some negative PR. ESUs aren’t cheap. During the first year, those using Windows 7 Enterprise will pay $25 per machine. This doubles to $50 in the second year and goes up to $100 for the third year. It’s even more expensive for those using Windows 7 Pro. ESUs for this version start at $50 before going up to $100 in year two and $200 during year three. Many businesses have been slow to migrate from Windows 7 to Windows 10, including the German government, which has to pay Microsoft around $886,000 for ESUs. In other Windows 7 news, the Free Software Foundation is demanding that the OS be released as free software. Source: https://www.techspot.com/news/83729-microsoft-issuing-free-windows-7-fix-after-introducing.html
  20. Signal Users on Android Need to Update Right Now Image: Signal Signal, a popular encrypted messaging app, has recently patched a flaw that left Android users’ audio calls vulnerable to bad actors. Basically, the bug would’ve let someone answer calls for you—and it could all happen without you even knowing. Google’s Project Zero team reported the bug on September 27, and Signal fixed it in version 4.47.7, which was released last week. According to the bug report, the gist is a logic error in the Android client. There’s a method called “handle CallConnected” which allows a call to finish connecting. In normal usage, it’s employed when you accept an incoming call and when the caller’s device is notified that you’ve accepted the call. With a modified client, a bad actor could “send the ‘connect’ message to a callee device when an incoming call is in progress, but has not yet been accepted by the user,” Project Zero researcher Natalie Silvanovich wrote in the bug report. “This causes the call the be answered, even though the user has not interacted with the device.” This particular bug is somewhat similar to that FaceTime flaw that popped up earlier this year, in which users could eavesdrop on others before a call was answered. Both involve tricking the programs into thinking a call has been accepted when they haven’t. Unlike the FaceTime bug, however, the Signal bug is limited to audio calls—thankfully, Signal requires users to manually enable video. As the Next Web points out, the iOS version of Signal has a similar problem to the Android app; however, a UI quirk means it can’t be exploited in quite the same way. Still, Silvanovich recommends “improving the logic in both clients, as it is possible the UI problem doesn’t occur in all situations.” An iOS update is not available as of publication, but Signal users on Android should make sure they’re running the most current version of the app. Source: Signal Users on Android Need to Update Right Now
  21. Successful exploitation allows attackers to steal potentially sensitive information, change appearance of the web page, and perform phishing, spoofing and drive-by-download attacks. Users of the Microsoft Outlook for Android app should update their apps to avoid a range of attacks. The bug (CVE-2019-1460) would allow an attacker to perform cross-site scripting (XSS) attacks on the affected systems and run scripts in the security context of the current user, according to Microsoft’s advisory on the bug. XSS occurs when malicious parties inject client-side scripts into web pages, which trick the unsuspecting user’s browser into thinking that the script came from a trusted source. In this case, the computing giant said that the issue exists in the way Microsoft Outlook for Android software parses specifically crafted email messages – thus, an attacker could exploit the vulnerability by sending just such an email. Czech firm Cybersecurity Help said in a posting this week that the problem was an “Improper Neutralization of Input During Web Page Generation” problem that exists due to insufficient sanitization of user-supplied data. The adversary would need to be authenticated to the same network as the potential victim in order to carry out an attack, Microsoft said. A write-up by Symantec said that an attacker can exploit this issue to conduct spoofing attacks, while Cybersecurity Help added that an attacker could “steal potentially sensitive information, change appearance of the web page, perform phishing and drive-by-download attacks.” Users should ensure that they have the latest version of the app, and update it manually if they haven’t received an auto-update. Beyond installing that update, Symantec also noted that mitigation includes running the software as a nonprivileged user with minimal access rights. Researcher Rafael Pablos was credited with finding the bug, which Microsoft rates as “important” in severity. It’s listed as having a 5.6 out of 10 severity rating on the CVSS v.3 vulnerability rating scale. Source
  22. Microsoft acknowledges Windows 10 bug causing forced reboots, fix in the works Microsoft has acknowledged a new issue that affects Windows 10 versions 1809 and newer that causes the Local Security Authority Subsystem Service (LSASS) to fail on some devices, forcing users to reboot the system. Though the problem was reported widely after this month’s Patch Tuesday updates, the company has acknowledged the bug in the known issues section of the KB articles for impacted versions, which also include articles for the May updates. The LSASS process is tasked with enforcing security policies on a system that verifies user logon, password changes, and more. The problem relates to a failure in the LSASS.exe file which leads to users losing access to any accounts currently active on the machine. This forces users to reboot the machine. A Microsoft Tech Community thread (spotted by BleepingComputer) detailing the problem was first posted on May 27. Image: BleepingComputer The only workaround, for now, is to uninstall the June Patch Tuesday cumulative updates, meaning that users will have to uninstall KB4561608 (1809), KB4560960 (1903 and 1909), or KB4557957 (2004). However, those that skipped the June updates and are still sporting the May patches will have to uninstall KB4551853 (1809) or KB4556799 (1903 and 1909). Users that manually installed the fixes that were rolled out last week for the printer issues will need to roll back those patches. One of the support forum responses suggests that the company intends to roll out a fix via its July Patch Tuesday updates. Microsoft says that it is working on a resolution, but has not provided any timelines for when the fix will roll out to affected versions of the OS. Microsoft acknowledges Windows 10 bug causing forced reboots, fix in the works
  23. Debilitating 'Outlook needs to close' bug linked to a bad Windows cumulative update Microsoft has acknowledged that a combination of the June 2-or-later version of Microsoft 365 (nee Office 365) and the June Win10 cumulative updates cause Outlook to disavow its PST files. The source of the problem seems to be a bug in the cumulative updates. Microsoft / lVcandy / Aleksei Derin / Getty Images Internecine conflict seems to be a recurring theme at Microsoft, but this one takes it to new levels. Somehow, somebody forgot to test the latest patched version of Outlook with the latest patched version of Windows. The result is an error message that makes Outlook inoperable. The official announcement appears on the Microsoft 365 support site: After updating to Version 2005 Build 12827.20268 or higher and starting Outlook you may see the following error prompt: The Outlook Team is investigating this issue with the Windows Team. We are not sure yet if the primary fix will come from Outlook or Windows. When we have more information on fix details we will add them here. Microsoft If you click OK, the ScanPST Inbox Repair Tool starts. Go through the repair process, reboot, and - surprise! - you get the error message again. Wash. Rinse. Repeat. No telling how many hours have been wasted over the weekend on this one. The good news, though, is that your PST file is fine – and always has been. As best I can tell, the show-stopper bug only occurs on machines that: Use PST, not OST, files; Run Microsoft 365 version 2005 Current Channel release 12827.20268 (from June 2) or Current Channel release 12827.20336 (from June 9); And have installed the June 2020 Win10 cumulative update (KB 4557957 for version 2004, KB 4560960 for versions 1903 or 1909, or KB 4561608 for version 1809). Microsoft’s solution – published in that Microsoft 365 support article – involves manually editing the Registry to make Outlook disregard the bogus “corrupt” PST file on startup. In fact, the “corrupt” PST file isn’t corrupt at all. It’s just Windows messin’ with Outlook. If you don’t want to pummel your Registry, Diane Poremsky at Slipstick has an easy downloadable solution. The insider report I have says that the bug is actually in the June cumulative updates, but that it’ll be easier for Microsoft to fix the problem by working around it in a new Microsoft 365 Current Channel release. You might expect that the Office people aren’t particularly happy about this one. Tell me once again…, who tests this stuff? Solace for muzzled Outlook devs available on the AskWoody.com Lounge. Debilitating 'Outlook needs to close' bug linked to a bad Windows cumulative update
  24. Microsoft Your Phone bug is reducing volume for other apps on Windows 10 Microsoft announced the Your Phone app for Windows 10 users at Build 2018 and the app became popular pretty quickly. Microsoft has been consistent with the updates and the app recently enabled RCS messaging for Samsung smartphones. However, it looks like the app has a nasty bug that has been causing issues for some users. According to a Redditor, Microsoft Your Phone app “lowers the volume of every single application when I make or receive a call no matter what, and the applications will remain low volume until restarted.” Unfortunately, the bug seems to be caused by a Windows setting that controls the volume when using VoIP. While Microsoft hasn’t addressed the issue officially, disabling the said setting helped a lot of users. If you’re facing a similar issue then you can follow the steps below to fix the problem. Right-click on the speaker icon in the system tray and select Open Volume Mixer. Click on your primary Playback device and navigate to the Advanced tab. Once there, uncheck the option Allow applications to take exclusive control of this device and apply the settings. The aforementioned workaround should fix the issue but it is a temporary solution and you will have to wait for Microsoft to address it officially to completely close the bug. Your Phone app has been consistent for the most part but even the best softwares are not immune to bugs which seems to be the case here. Source: Microsoft Your Phone bug is reducing volume for other apps on Windows 10 (MSPoweruser)
  25. Microsoft is working on a fix for 'Error code 6' crash on Microsoft Edge for Mac Microsoft has acknowledged an issue on Microsoft Edge for Mac that is causing the web browser to crash with 'Error code 6'. Earlier this week, users took to Microsoft Answers forum (via Techdows) to report the issue with Edge on macOS Catalina. According to users, Microsoft Edge started crashing after updating to Safari 14. The browser crashes after opening a new tab, settings, and even Edge extensions, with the error, "The page is having a problem. Try coming back to it later”. It also suggests users to refresh the page or open a new tab but none of the workarounds solves the problem. Fortunately, the Microsoft Edge Dev Twitter account has now confirmed that the culprit has been found and they are working on a fix that will roll out to Edge users in all the channels. In the meantime, the Edge Dev team has suggested rebooting Mac as a temporary fix to the problem. Some users have tried reinstalling Microsoft Edge but that does not fix the problem and hence, is not advised. Unfortunately, we don't know what exactly caused the problem but we do expect Microsoft to shed light on the problem once the fix has rolled out to Mac users. Microsoft is working on a fix for 'Error code 6' crash on Microsoft Edge for Mac
×
×
  • Create New...