Lỗi Illustrator (Ai) tự tắt gây ra rất nhiều phiền toái cho người dùng. Hãy cùng ColorME tìm cách khắc phục nhanh chóng sự cố này nhé! Show
I.Lỗi Illustrator tự thoát ra do sai khác phiên bản hệ điều hành WindowsHệ điều hành Windows có 02 phiên bản phổ biến là Windows 32 bit và Windows 64 bit. Khi mua máy tính và cài đặt Illustrator (Ai) bạn hãy chú ý tải đúng phiên bản 32 bit hoặc 64 bit cho máy tính nhé. Điều này khá quan trọng vì nó sẽ ảnh hưởng đến hiệu suất của hệ điều hành, đôi khi sẽ gây ra lỗi, xung đột. Nếu Ai của bạn là phiên bản 64 bit trong khi hệ điều hành chỉ là 32 bit thì việc Ai tự thoát ra là điều dễ hiểu. Lỗi Ai tự thoát ra do sai khác phiên bản hệ điều hành Để khắc phục lỗi Ai tự tắt này, việc đầu tiên bạn cần làm là kiểm tra xem CPU của máy (Windows) là phiên bản nào: Bước 1: Mở Control Panel -> View by -> nhấp vào mũi tên hướng xuống và chọn Large icon -> nhấp chuột vào System Mở System và kiểm tra phiên bản CPU Bạn có thể xem bản Windows mình đang cài là 32 bit hay 64 bit tại mục System type thuộc cửa sổ System: nếu bạn thấy 32-bit Operating System thì máy cài bản Windows 32 bit, 64-bit Operating System thì Windows đang cài trên máy tính là bản 64 bit. Khi đã kiểm tra xong phiên bản hệ điều hành, bạn có thể cài đặt lại bản Illustrator (Ai) tương thích là 32 bit hoặc 64 bit nhé! Cài đặt lại phiên bản Illustrator (Ai) phù hợp Ngoài lỗi tự tắt, Ai cũng thường xuyên xảy ra các sự cố khác khiến người dùng thấy phiền toái. Bạn có thể tham khảo một số bài viết của chúng mình về cách khắc phục các lỗi đó nhé:
II. Lỗi Illustrator (Ai) tự RestartNếu đang thao tác trên Ai và ứng dụng tự khởi động lại, rất có thể Ai đã xảy ra lỗi thuộc các tình huống sau: II.1. Ai tự Restart do lỗi phần mềmĐể khắc phục, bạn hãy khởi động máy -> Setting -> Update & Security -> Recovery -> Get started -> Delete all driver... Chọn Get Started và Delete All Driver II.2. Ai tự Restart do RAM máy yếuKhi Delete All Driver không khắc phục được lỗi thì có thể Ai tự Restart do RAM máy yếu. Bạn hãy chuyển Cache của Ai sang ổ D. Chuyển Cache của Ai sang ổ D II.3. Ai tự Restart do tự động Update hệ điều hànhWindows tự động Update có thể khiến Ai tự động Restart. Bạn hãy tắt Automatic Update để khắc phục: Bước 1: Gõ Update trong ô Search -> Chọn Windows Update settings -> Advanced options. Chọn Windows Update settings -> Advanced options Bước 2: Tại Pause updates -> Chọn Pause until -\> Chọn vào mục Select date. Chọn Select date Bước 3: Chọn ngày bạn muốn cập nhật trên Windows. III. Tạm kếtBài viết của chúng mình xin kết thúc tại đây, mong rằng nó sẽ giúp bạn khắc phục được lỗi Ai tự tắt bản thân đang gặp phải. Nếu bạn đam mê đồ họa và đang tìm kiếm một lộ trình học thiết kế bài bản với mức giá phải chăng, hãy tham khảo We recommend that Windows users download and use NVIDIA drivers (version 531.41 or higher). This will resolve any crashing issues that may have been present with older drivers. For more information, see the NVIDIA documentation. To avoid crash on launch issues when using Remote Desktop on Windows with an AMD GPU, install the Auto-detect-updates from AMD to update the GPU drivers. General known issuesLoading a large number of plug-ins takes a long time (only macOS)Issue: While loading a large number of plugins for the first time during startup, the application may seem to be non-responsive while initial loading is in progress. Workaround: Avoid aborting the application during this process because it will require those plugins to re-initialize again during launch. Clearing the plug-in cache will also require the initialization of the plugins. We are looking at ways to optimize this process in future versions. Upgrade to macOS Sonoma (Version 14) leads to the video app failing on launchAdobe video apps fail to launch on macOS Sonoma (version 14), and the following error message is displayed: Adobe Premiere Pro 2024 is damaged and can't be opened. You should move it to the Trash. This issue affects all versions of Adobe apps and isn't related to the new 2024 version update, so downgrading to 2023 versions will not resolve the issue. While Sonoma users are more likely to get this error, it may also appear if you use a previous macOS version. Adobe video and audio products no longer support RosettaStarting with version 24.0, Adobe video and audio products no longer support Rosetta emulation (Intel versions running on Apple M1/M2). Please be aware that the Creative Cloud desktop still shows the Rosetta option on M1/M2 machines, but this will still launch the native Apple Silicon version. Intel versions can only be run on Mac Intel machines. The Open using Rosetta option is no longer available in the Get Info window. Poor playback performance in Macintosh M2 Studio or Mac Pro with multiple monitorsIssue: A customer with a Macintosh M2 Studio or Mac Pro with multiple monitors may experience poor playback performance. Workaround: Enable Displays have separate Spaces in macOS System Settings \> Desktop & Dock. Apple and Adobe are working on a permanent fix for this issue. December 2023 Release (Version 24.1)
Premiere Pro is impacted as Adobe Media Encoder crashes while attempting to copy-ingest some camera cardsIssue: Premiere Pro is impacted as it relies on Adobe Media Encoder for ingest, and Adobe Media Encoder is crashing when using the ingest-copy setting to import certain file structure camera cards such as ARRI, AVCHD, Canon XF, Panasonic P2, Canon RAW, XDCAM EX, or XDCAM HD. Workaround: Copy the camera card first, then import through the media browser with Ingest settings turned off. October 2023 Release (Version 24.0)OVERLAYS VIA TRANSMIT DO NOT WORK CORRECTLY DURING PLAYBACKIssue: When the transmit overlays are enabled via the Enable overlays with Transmit and Enable overlays during playback settings (Wrench menu in Program monitor), the Transmit monitor might not display the video content correctly. Workaround: Turn off Enable overlays with Transmit to display the frames correctly. A partial workaround would be to use the metadata effect to display a subset of the overlay information. August 2023 Release (Version 23.6)The export function fails when trying to publish media directly from Premiere Pro to Twitter (X)Issue: When a user attempts to publish media directly from Premiere Pro to Twitter (X), the export function fails, given recent changes at Twitter (X) and their APIs. Workaround: This issue will be fixed in an upcoming release. In older versions, you'll need to export media locally and publish through Twitter (X). June 2023 Release (Version 23.5)ARRIRAW files from the ALEXA 35 cannot be played in Premiere ProIssue: ARRIRAW files from the ALEXA 35, using Software Update Package 1.1 or later, cannot be played in any version of Premiere Pro. Workaround: The issue is now fixed in the v23.6 beta. an exported HEVC file can be played, but cannot be scrubbedIssue: When an HEVC file is exported, it can be played but faces issues when scrubbed forward to any point in the video. Workaround: We'll let you know when a fix is available. But if you're experiencing this issue, you can test the fix in the v 23.6 Beta version. Dynamic link compatibility issuesIssue: Using Dynamic Link between app versions of 23.5 with lower versions of 23.x causes rendering issues in Windows. Resolution: If using Dynamic Link in version 23.x, we recommend that all app versions (Premiere Pro, After Effects, or AME) have 23.5 or higher installed. Since there is no version of Character Animator 23.5, this is a special case. If you're using Dynamic Link with Character Animator 23.1, ensure the other apps are not at version 23.5. Instead, they must be at 23.0, 23.1, 23.2, 23.3, or 23.4. May 2023 Release (Version 23.4)Clips reset to the first frame after relinking in Text-Based EditingIssue: When transcribed clips in a timeline are taken offline and relinked, clips shift and reset to the first frame. Effects, transitions, and speed changes can also be removed or impacted. Resolution: Update to Premiere Pro 23.5 for a fix to this issue. If an update is not possible, follow this workaround: If you get the media relinking dialog in 23.4 and have previously used transcription, close and don't save the project. Make a backup of your project file to be safe, and use one of these options:
Certain custom keyboard shortcuts are reset to defaultIssue: Certain custom keyboard shortcuts reset to their default value on the first launch after updating to 23.4 or on the next launch after customization when using 23.4. Workaround: We'll let you know when a fix is available. But if you're experiencing this issue, use one of these options:
April (Version 23.3) and February (Version 23.2)Export mode fails to load in Premiere Pro 23.2 and 23.3Export mode fails to load and prevents exporting. A loading spinner is shown, but the Export mode fails to load. Selecting File \> Export \> Media or using the keyboard shortcut (Cmd + M /Ctrl + M), there is no result; you stay in Edit mode. In these situations, exports won’t work in Premiere Pro. In this state, Quick Export also fails to function. This issue is known to affect Premiere Pro versions 23.2 and 23.3 on macOS and Windows. If you are experiencing this issue, follow the workarounds posted here to get your export completed. February 2023 Update (Version 23.2)Playing Apple ProRes RAW after updating to NVIDIA’s latest driversIssue: There is a known issue with the latest NVIDIA game-ready drivers when running Adobe applications on machines with NVIDIA cards, which can cause Apple ProRes RAW playback to show black frames. Workaround:
December 2022 Release (Version 23.1)Export issue for H.264 and HEVC with Premiere Pro 23.1Issue: An issue affecting H.264 and HEVC or H.265 exports on Windows with Premiere Pro 23.1. The issue impacts H.264 and HEVC or H.265 exports to folders with names that use double-byte characters, such as Chinese, Japanese, Korean, or extended ASCII characters, like accents and umlauts. Affected users will see this message: “File importer detected an inconsistency in the file structure of %filename.mp4%. Reading and writing this file’s metadata (XMP) has been disabled.” Workaround: We'll let you know when a fix is available. But if you're experiencing this issue, use one of these options:
October 2022 Release (Version 23.0)Issue with the Font Sync in Premiere Pro on macOS Ventura 13Issue: The MOGRT gets applied, but the font never syncs because Creative Cloud login items were disabled, and Premiere Pro did not enable Core Sync items at the app launch. Workaround: Open the Creative Cloud Desktop app, then go back into Premiere Pro and let the font sync. For more details, see Fix login item issues for Adobe Creative Cloud on macOS Ventura. Issue with imported AAF files with multitrack audio on Apple siliconResult: While on Apple silicon, importing an AAF file with multi-channel audio, represented as multi-mono audio, will stutter during playback. Expected: The file instance imported via AAF should play as well as the file instance that was directly imported. Workaround: Use PPro Win or PPro on Mac Intel. Unable to select Video Rendering and Effects options on Windows devices with Intel GPU and NVIDIA Graphic cardsIssue: You are unable to select from the Use options from the Video Rendering and Effects dropdown because it is greyed out. Or, if you open any project that uses OpenCL or CUDA, you get an error message - "Mercury Playback Engine is not available." Workaround: When OpenCL™ and OpenGL® Compatibility Pack is installed, it adds another implementation of OpenCL to the machine, along with one by Microsoft, and NVIDIA is by default chosen as an OpenCL device. If OpenCL™ and OpenGL® Compatibility Pack is installed, we recommend you remove the compatibility pack. Go to Settings \> Apps \> Apps & features \> OpenCL™ and OpenGL® Compatibility Pack \> Uninstall. The compatibility pack is a backup implementation designed for ARM devices, thus, should not impact other installed applications. |