Circuit Verge

Tag: address

  • iMessage crashes on iPhones running iOS 18. Learn how to address this issue.

    iMessage crashes on iPhones running iOS 18. Learn how to address this issue.

    iOS 18, released last Monday, has been causing issues for Apple users due to a critical bug found in the iMessage app. This bug can crash the device and lead to data loss in a particular scenario.

    A critical issue in iMessage is creating a problem on iOS 18.

    When an individual shares an Apple Watch watch face during an iMessage chat, it initiates a sequence of events. For users on iOS 18, it is crucial not to reply when they receive a message containing this watch face.

    If the message is replied to, the iMessage application will crash each time the user attempts to access that chat. The crashes may happen so often that it becomes challenging to engage in other conversations. iMessage is also unreliable on beta editions of iOS 18.1, iPadOS 18.1, and macOS 15.1.

    The bug impacts both the sender and the recipient of the message, showing similar symptoms for both parties.

    Divulgação: Apple
    Imagem: JonPauling/Pexels

    Resolving the iMessage bug on iOS 18.

    The sole option available then is for both users to erase the phone conversation, which will also remove all message history and any attachments like photos and videos not saved elsewhere in iMessage.

    If the conversation is deleted by the user and then attempted to be recovered from the deleted items section, the bug will resurface, rendering this approach ineffective. It is anticipated that Apple will tackle this issue in the upcoming iOS 18 update (likely to be named iOS 18.0.1), which is eagerly awaited. Apple is expected to provide a fix for this issue on iOS, macOS, and watchOS platforms soon. Users are advised to refrain from responding to messages on threads if someone shares an Apple Watch watch face until an update is rolled out.

  • Windows 11 24H2 has been corrected to address issues with Western Digital SSD failures.

    Windows 11 24H2 has been corrected to address issues with Western Digital SSD failures.

    Some users experienced problems with Western Digital and SanDisk SSDs following the Windows 11 24H2 update, but the issue has been resolved with a firmware update from Western Digital addressing the Host Memory Buffer (HMB) function.

    Which models were impacted?

    Certain SSD models have been found to have compatibility problems.

    • The firmware version for the WD_BLACK SN770 NVMe SSD 2TB (WDBBDL0020BNC, WDS200T3X0E) is 731130WD.
    • The firmware of the WD_BLACK SN770M NVMe SSD 2TB (WDBDNH0020BBK, WDS200T3X0G) is 731130WD.
    • The firmware for the 2TB WD Blue SN580 NVMe SSD is version 281050WD.
    • The firmware version of the WD Blue SN5000 NVMe SSD 2TB (WDBS3F0020BNC, WDS200T4B0E) is 291020WD.
    • SanDisk Extreme M.2 NVMe SSD 2TB (SDSSDX3N-2T00) firmware version is 731130WD.

    How to implement a correction.

    Western Digital suggests using their Dashboard tool to resolve the problem. This tool not only facilitates the installation of new firmware but also monitors SSD health, temperature, speed, and available space. Upon installation, the software will alert you about new firmware updates, which can be easily completed by following on-screen instructions.

    Take necessary safety measures

    If you own one of the impacted SSDs and have not yet gotten the Windows 11 24H2 update, it is advised to proactively install the new firmware to prevent potential instability issues. Additionally, note that Windows Update may temporarily prevent the installation of update 24H2 on devices with these SSDs to prevent known issues.

    If your Windows 11 24H2 system has been updated and is unstable, you can apply a temporary fix using the Windows Registry Editor to modify the HMB allocation until the firmware update is implemented.

    1. Open the Start menu, search for Regedit, and then right-click on the matching result.
    2. Select “Run as administrator”.
    3. Explore HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\StorPort.
    4. Create a new DWORD value named HmbAllocationPolicy if it is not already present.
    5. Double-click on the value and change it to 2.
    6. Save the modifications and reboot the system.

    This adjustment should maintain system stability until the installation of the new firmware. Disabling the HMB entirely by setting the value to 0 can also provide a temporary solution in certain situations.

    Paraphrased: Origin